¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Re: Possible location of latest VNA source code??

 

Thanks - I didn't think to look at the reset circuit of the DSP.
It's an easy fix.

With regards to upper frequency limits of this device, might there be a way to extend it to just beyond the 902-928MHz HAM band - maybe to 950MHz?
I know response will be not great, but it will still be useful performing rough checking on antenna systems.

You have done excellent work on this unit - thanks!

Regards,
Larry

On Tue, Jul 30, 2019 at 09:38 PM, <hugen@...> wrote:


On Wed, Jul 31, 2019 at 09:29 AM, Larry Rothman wrote:
Hugen,
Can you please tell me what you changed so I can fix my white unit?
I assume it is an issue with the charger/inverter circuit design?

Thanks,
Larry

On Tue, Jul 30, 2019 at 09:21 PM, <hugen@...> wrote:
The white gecko copied the design of my earlier version, there is a
power-on timing issue, and my new hardware has fixed this problem.
Try to add c38 on my schematic.


Re: Smith chart impedance printout

 

Hi Lapo

My +1 to display as R +/-Jx.

Even will be ideal to display as line graphics: SWR, R and JX !
As some antenna analyzers done it, Rigexpert etc...


73,
Serge


Re: Possible location of latest VNA source code??

 

On Sat, Jul 27, 2019 at 06:55 PM, Joe Rocci wrote:


Huge
The "Reference" links at the bottom of the GitHub page don't work.

Joe
The link has been corrected.


Re: Possible location of latest VNA source code??

 

On Wed, Jul 31, 2019 at 09:29 AM, Larry Rothman wrote:


Hugen,
Can you please tell me what you changed so I can fix my white unit?
I assume it is an issue with the charger/inverter circuit design?

Thanks,
Larry

On Tue, Jul 30, 2019 at 09:21 PM, <hugen@...> wrote:
The white gecko copied the design of my earlier version, there is a power-on
timing issue, and my new hardware has fixed this problem.
Try to add c38 on my schematic.


Re: Possible location of latest VNA source code??

 

Hugen,
Can you please tell me what you changed so I can fix my white unit?
I assume it is an issue with the charger/inverter circuit design?

Thanks,
Larry

On Tue, Jul 30, 2019 at 09:21 PM, <hugen@...> wrote:
The white gecko copied the design of my earlier version, there is a power-on timing issue, and my new hardware has fixed this problem.


Re: Possible location of latest VNA source code??

 

On Tue, Jul 30, 2019 at 01:36 AM, Lapo Pieri wrote:


Hi,
02:32 Mon 29 Jul 19 , hugen@... wrote:
You may have pressed the touch screen while adc is initializing.
No, I don't I'm sure

It might be better to add a wait.
I agree. I don't know STM32, I usually develop on NXP LPCxxxx but it seems
to me good.

void adc_init(void)
{
rccEnableADC1(FALSE);

/* Calibration procedure.*/
ADC->CCR = 0;
while (ADC1->CR & ADC_CR_ADEN)
;
ADC1->CR |= ADC_CR_ADCAL;
while (ADC1->CR & ADC_CR_ADCAL)
;

ADC1->CR = ADC_CR_ADEN;
while (!(ADC1->ISR & ADC_ISR_ADRDY))
;
}
Ok, now it works but after a full power-down.
I mean: after re-build and fw load
($ dfu-util -d 0483:df11 -a 0 -s 0x08000000:leave -D build_900/ch.bin)
on subsequent reset it hangs again just after start and stop frequency
printout; switching off and then on rapidly (blue led remains on) it hangs
again. Switching off, waiting for blue led to go down and switching on again
it works. Why?

Many thanks!

Lapo, IK5NAX

Since powering up from DFU mode, aic3204 fails to be initialized at power-on, which will cause I2C abnormality. Re-powering up will make aic3204 normal initialization work normally.


Re: Possible location of latest VNA source code??

 

Such a change will cause the adc to fail to calibrate properly, although this will not cause major errors, but it is not recommended.
Do not compile the 1300Mhz version, there will be a big error above 900MHz!
The white gecko copied the design of my earlier version, there is a power-on timing issue, and my new hardware has fixed this problem.


Re: Possible location of latest VNA source code??

DMR
 

Larry Rothman,
Once again, with the original firmware there are no problems with the inclusion. I corrected the code, now nothing freezes.

void adc_init(void) {
rccEnableADC1(FALSE);
ADC->CCR = 0;
ADC1->CR |= ADC_CR_ADCAL;
ADC1->CR = ADC_CR_ADEN;
while (!(ADC1->ISR & ADC_ISR_ADRDY));
}


Re: Possible location of latest VNA source code??

 

I just had a look at hugen's schematic.
He runs a battery charger/inverter chip off of the battery to get +5v.
He then uses a 3.2v LDO regulator (XC6206P322MR) chip to run most of the electronics.
I'm wondering if some of the copies of the original design are using an inferior 3.2v regulator chip or subb'ed it with something else.

It might not fix your issue, which appears to be S/W, but I know that others have some power-up issues like I have with my gecko.

Just a thought...

Larry


Re: Possible location of latest VNA source code??

 

One thing you might want to try is to compile a DFU for hugen's 300MHz firmware, then use any free ARM disassembler and compare your compile to Hugen's.
You may be able to zero-in on the problem area.

If you do find the problem, please share with the forum members.
I hope this helps.

Larry

On Tue, Jul 30, 2019 at 01:47 PM, DMR wrote:


The hang occurs both on battery power and on port USB.
With native, stock firmware never freezes.

With native firmware does not hang.
With the firmware, which is compiled from source Hugen, freezes.


Re: Possible location of latest VNA source code??

DMR
 
Edited

The hang occurs both on battery power and on port USB.
With native, stock firmware never freezes.

With native firmware does not hang.
With the firmware, which is compiled from source Hugen, freezes.


Re: Possible location of latest VNA source code??

 

My white Gecko clone hangs at the splash screen sometimes as well when running off the battery but never hangs when powered by the USB port.
Does yours hang when powered by USB or battery?
These devices use both 5v AND 3.6v supplies and I'm wondering if the vna will hang if the supplies don't come up quickly at the same time.

Try disconnecting the battery and run it only from a USB source to see what happens.
Since the 3.6v battery powers the uP, a defective one might cause issues.

Regards,
Larry

On Tue, Jul 30, 2019 at 11:55 AM, DMR wrote:


Everything is smooth, my analyzer freezes on the splash screen. The code below
does not fix this. Sometimes it works, sometimes every other time. I have an
original firmware dump STM32, merged when I bought the device, there are no
problems with freezing at the start. I see a problem not only with me. This
happens on all tapes of firmware, 300, 900, 1300MHz. Is there a solution to
this bug?


Re: Possible location of latest VNA source code??

DMR
 

Everything is smooth, my analyzer freezes on the splash screen. The code below does not fix this. Sometimes it works, sometimes every other time. I have an original firmware dump STM32, merged when I bought the device, there are no problems with freezing at the start. I see a problem not only with me. This happens on all tapes of firmware, 300, 900, 1300MHz. Is there a solution to this bug?


Re: nanovna sharp issue on Windows 10 64 bit

 

Thank you Hugen! release 1.03 works very good for me


Re: nano cases

 

Frank,

Why don't you try something like what I drew for message /g/nanovna-users/message/608 ?
Since I don't own a 3D printer (yet), I would assume my design could be printed on it's side.
You could make the surface for the panel-mount N adapters thicker for rigidity and even design-in a few gussets or centre structure for more strength by the RF connectors.
My original thinking on the design was that the sloped top and bottom surfaces would minimise back-front flexing.
Just a thought.

A note on that pesky USB port..., I use a Bird SK4000 antenna analyser at work. Bird originally designed the unit using only a micro USB port for charging and data transfer.
It was a big design mistake - they replaced a lot of those ports. The next generation of the SK4xxx series had a barrel plug for charging in addition to the micro USB data port.

Maybe you can design a case that also houses a flush-mount barrel jack for charging.

NOTE- if anyone is thinking of adding an external non-usb charging port, please keep in mind that it will need to disconnect the USB +5V line when an external charger is inserted - or install a Schottky isolation diode so you don't try to push power back down the USB line.

Regards,
Larry

On Mon, Jul 29, 2019 at 09:47 PM, Frank S wrote:

My original reason to design a case for this little thing, is the open
sides are a place for something to get in and short the beast out. I
never liked "test equipment" to get dirt or particles to get in.
Since through the trouble of designing and printing a few to work the
bugs out, I figured others might want to enclose theirs. To try and take
this device and kluge it into a metal case I don't think would be worth
it. Now, redesign it so it will fit in a case (with the appropriate
connectors) in a metal box might be another way to go.?? For some people,
they don't have the equipment/ ability to make the mods.


Re: nano cases...

Dr. David Kirkby from Kirkby Microwave Ltd
 

On Tue, 30 Jul 2019 at 00:38, Frank S <ka2fwc@...> wrote:

I agree... to a point. This thing isn't a "real" VNA (in the commercial
respect). I don't know if I would have used it when I schlepped up a
water tower in Melbourne Australia. I had a Keysight N9914 :-)

I am guessing that the N9914 is about 25 dB more expensive!

I have been unlikely with FieldFoxs. Bought an N9923A reconditioned from
Agilent. I found endless firmware bugs, then it had a hardware failure. I
returned that to Agilent.

Then I bought a used N9912A, which was DOA.

The first NanoVNA I bought had a faulty screen. Hugen said they are
delicate. There is also a larger (3.2¡±) version of that available. I am
considering trying to fit a larger screen.
--
Dr. David Kirkby,


Re: Smith chart impedance printout

 

Yes, my error. Oh well, only a hand calculator away!


Re: LabView Interface

 

Hello Joe and nice work on your LabVIEW interface to the nanoVNA. I'm wondering if you plan on sharing this with the group? I would be very interested in learning how you did what you did.

I have been successful in sending commands to the nanoVNA and getting it to respond using standard LabVIEW Serial Communications examples, but they are all still very crude and, as you said, the serial communications is a little sketchy at time.

Anything that you would like to share would be greatly appreciated.

Thanks and "nice job" on your vi.

Larry


Re: nano cases

 

My original reason to design a case for this little thing, is the open sides are a place for something to get in and short the beast out. I never liked "test equipment" to get dirt or particles to get in.
Since through the trouble of designing and printing a few to work the bugs out, I figured others might want to enclose theirs. To try and take this device and kluge it into a metal case I don't think would be worth it. Now, redesign it so it will fit in a case (with the appropriate connectors) in a metal box might be another way to go.?? For some people, they don't have the equipment/ ability to make the mods.

On 7/29/2019 9:34 PM, kh6sky wrote:
I get it Frank. Boxing it up does have some downside. I think it depends on what you want to do with it, how much use/abuse it will receive, and whether or not your hands are more functional than catcher's mitts. For some of us this will be in the "fun-to-play-with" category. For someone like me it might be my only VNA.



Re: nano cases

 

I get it Frank. Boxing it up does have some downside. I think it depends on what you want to do with it, how much use/abuse it will receive, and whether or not your hands are more functional than catcher's mitts. For some of us this will be in the "fun-to-play-with" category. For someone like me it might be my only VNA.