¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Nanovna-Users
  2. Messages
Expanded Topics Messages
Date
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));
}

20190730_221810.jpg

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.
Locked Re: Correct button?

 

Hi Alan,
I just want to point out that the polynomial + delay + impedance method for
characterising standards is itself just an approximation.

In this day and age (of cheap storage) it is simpler to just sweep the
standards on a calibrated VNA, get an s-param file for each one and use
that data in the calcs - with some interpolation for the in-between
frequencies.
This gives the highest accuracy as there is no modelling error.
It also means you can use any old standard you like. The polynomial models
don't fit poorly made standards very well over a wide frequency range,
hence the need for high quality expensive parts.

However I'm not sure if this device has the storage available to do it this
way, if not the old school approach might be the best way.

Regards,
Roger

On Tue, 30 Jul 2019 at 08:49, alan victor <avictor73@...> wrote:

Thanks! That is helpful. The fact that the polynomial code to describe the
open is present implies he was aware of the situation and at this point
elected to put it aside. So for all intent and purpose, the loads are
assumed to be ideal and that tends to agree with the final sweep to check
the loads after cal. The check returns them to be IDEAL... And they are
anything but ideal as that is the electrical-physical nature of a SMA
connector.

Alan

________________________________
From: [email protected] <[email protected]> on behalf of
Roger Henderson <hendorog@...>
Sent: Monday, July 29, 2019 8:32 PM
To: [email protected] <[email protected]>
Subject: Re: [nanovna-users] Correct button?

I checked the code repo's posted and this is what I think the situation is
with the standards:

The load is assumed to be perfect - i.e. the assumption is that nothing is
reflected from the load.
The open is assumed to have a single C0 capacitance term of 50e-15F
The short is either assumed to be perfect, or is assumed to be 180degrees
away from the open. I am not quite sure on that.

There is some unused code which looks to be intended to create a
C0,C1,C2,C3 model of the open, but it is not used.

Roger

On Mon, 29 Jul 2019 at 14:37, alan victor <avictor73@...> wrote:

You are correct and I confirmed on the big box, that is the function
performed.

This turns CAL ON or OFF. Again, I suspect hp as well others, added this
function as an aid to be sure the correction data sets make sense as a
corrective measurement is conducted on a component. Its much easier to do
this then preset the instrument and have to do a complete re calibration.

Alan

________________________________
From: [email protected] <[email protected]> on behalf of
alan
victor <avictor73@...>
Sent: Monday, July 29, 2019 1:20 AM
To: [email protected] <[email protected]>
Subject: Re: [nanovna-users] Correct button?

Good suggestion and it does appear to toggle in that manner.

Now, I have to think why I would toggle corrections ON and OFF, other
than
to see if the corrections ON make sense.

I am not sure this is a good place to bring up the fact that the
STANDARDS
provided with the nanoVNA are taken, I believe, by the device and the
firmware as IDEAL. Point in fact, they are NOT. Not an issue at lower
frequencies unless you want to split hairs. But as you approach 900 MHz,
bottom line, when measuring a component, you are not going to get the
correct answer.

I emailed the developer on this topic but as of now, no response.

Alan

________________________________
From: [email protected] <[email protected]> on behalf of
Roger Henderson <hendorog@...>
Sent: Monday, July 29, 2019 1:10 AM
To: [email protected] <[email protected]>
Subject: Re: [nanovna-users] Correct button?

I would guess it is a mode switch between: 'Apply calibration
corrections'
and 'Don't apply calibration corrections'

This feature is present in other VNA's. Am not in front of a device to
confirm it though.

Regards,
Roger

On Mon, 29 Jul 2019 at 13:06, alan victor <avictor73@...> wrote:

Good question Ernst. Let me take a look and see if I can figure it
out. I
have a guess that it may have to do with the fact that the standards,
open,
short, load are NOT perfect. But... the softkey selection does not lead
to
additional menu selection. So far now, it appears to be a PLACE HOLDER
for
further work.

Alan

________________________________
From: [email protected] <[email protected]> on behalf of
dk1vi <dk1vi@...>
Sent: Sunday, July 28, 2019 11:44 PM
To: [email protected] <[email protected]>
Subject: [nanovna-users] Correct button?

Hi,
what is the purpose of the "CORRECT" button in the calibration menu?
I have not read anything about it or did I miss something?
Ernst
Re: Possible location of latest VNA source code??

Lapo Pieri
 

Hi,
11:32 Mon 29 Jul 19 , DMR wrote:
After compilation it works exactly the same as yours.

There is still a problem, an error occurs when compiling if
USE_PROCESS_STACKSIZE = 0x200
USE_EXCEPTIONS_STACKSIZE = 0x200

With these values, everything compiles without errors.
USE_PROCESS_STACKSIZE = 0x100
USE_EXCEPTIONS_STACKSIZE = 0x100
Where are these vars?

Hi hugen! Share the full working code please.
I take the full code from here:



Are we talking about different source code?

Lapo, IK5NAX
Re: nano cases...

 

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 :-)

On 7/29/2019 10:19 AM, Burt K6OQK wrote:
Personally, I'd rather see this instrument in a tablet size, something I can easily see; in a real metal box with Type-N connectors and sturdy switches and push-buttons.?? My need is for an instrument that I can carry to antenna sites for broadcast antenna work.?? I understand where some folks like tiny pocket size instruments, not sure why, but I'm probably going to go to something like an HP e5061B - a totally different area of an instrument.?? I like the 8753c or ES but they are pretty big and heavy for schleping to transmitter sites.

Burt, K6OQK

At 05:32 AM 7/29/2019, Frank S wrote
I don't think it is worth putting a Pinto engine into a Cadillac Escalade. It doesn't make it a pocket size antenna analyzer anymore

On 7/29/2019 4:51 AM, Dr. David Kirkby from Kirkby Microwave Ltd wrote:
On Mon, 29 Jul 2019 at 06:17, kh6sky <kh6sky@...> wrote:

These cases look nice and fulfill a need but my tendency to spastically
knock stuff off the bench means I will use a larger metal box with switches
and connectors moved to the outer box. The power and control switches seem
too delicate to last.?? Another reason to put the unit in a box is the
delicate USB connector.
I agree entirely. I think any case should extend out *everything* so you
never put any strain on the device apart from the screen, which I can see
no way of avoiding.

So I think these should be on a case

1) RF connectors - I would use N, not SMA,
2) USB
3) Toggle switch
4) Power switch

For the LED, one could have 3 possibilities
* Small hole
* light pipe
* desolder LED and run wire.

For the battery, I guess one can get away with using the tracks on the


If the plastic case were re-enforced around the USB connector it might help
prevent disasters like mine.
I personally don???t think any amount of reinforcement is going to work as a
long term solution. That will only delay the inevitable a while.

Dave.

Dave.

Burt I. Weiner Associates
Broadcast Technical Services
Glendale, California U.S.A.
biwa@...
K6OQK
39081 - 39100 of 39714