开云体育

Good evening all,
I got out my NanoVNA (Black without shields) and without thinking i pulled the lastest firmware and flashed it. I calibrated like ive done so many time before, and made sure the "correction" was highlighted after the calibration was done. After all said and done i reconnected the 50 ohm load and the smith chart was all over the place (see photo). I changed to span to 50khz to 300 mhz and it appeared to be normal (see photo).

What am i doing wrong? The previous firmware worked great, with zero issue (like the issues im having now) to 900 mhz.

KE8CPD,
I have the same NanoVNA (Black without shields) as you and also just upgraded to version 0.2.3. I'm pretty sure all version 0.2.3 firmware have the battery icon which I don't see on your photos. I upgraded using hugen's official release at . My NanoVNA came with the two trace software and I wanted to upgrade to four trace. The previous advice, when upgrading from two trace to four trace, was to load "CLEAR_MEMORY_DFU.dfu" first and then load the four trace software. Hugen says that is not necessary with his 0.2.3 release. In any event, if you use his release and things don't look right after calibration, ensure that "Correction" is highlighted under the "Cal" menu.

Herb

On Sun, Oct 13, 2019 at 06:31 AM, hwalker wrote:

I'm pretty sure all version 0.2.3 firmware have the battery icon which I don't
see on your photos.

This icon disappears if voltage on the pin is below 100 mV. So, you can get picture with no battery if diode is not installed.

Regarding to the edy555 firmware, there is some difference with hugen79 firmware:
1) hugen79 firmware has imbalance gain correction, which is missing from edy555 firmware
2) hugen79 firmware has a little different logic for frequency band/gain change.
3) hugen79 firmware has correct default touch calibration, which works ok with NanoVNA-H hardware even with no touch calibration. edy555 firmware has different default touch calibration which is incompatible with NanoVNA-H hardware, so you're needs to calibrate touch screen after switch to the edy555 firmware.

On Sun, Oct 13, 2019 at 05:40 AM, KE8CPD wrote:

I changed to span to 50khz to 300 mhz and it appeared to be normal (see photo).

I'm not sure what is wrong? Could you please explain your issue more detail?

If correction is disabled you can enable it with CAL => CORRECTION menu. Does it solve your issue?

QRP wrote:

…. icon disappears if voltage on the pin is below 100 mV. So, you can get picture with no battery if diode is not installed.

Regarding to the edy555 firmware, there is some difference with hugen79 firmware:
1) hugen79 firmware has imbalance gain correction, which is missing from edy555 firmware
2) hugen79 firmware has a little different logic for frequency band/gain change.
3) hugen79 firmware has correct default touch calibration, which works ok with NanoVNA-H hardware even with no touch calibration. edy555 firmware has different default touch calibration which is incompatible with NanoVNA-H hardware, so you're needs to calibrate touch screen after switch to the edy555 firmware.

----------------------------------------------------

Very useful info. However I have not installed the diode and I still get a battery icon (see attachment). I thought the way it worked is that if a diode was not installed the icon always showed as empty.

- Herb

On Sun, Oct 13, 2019 at 07:25 AM, hwalker wrote:

However I have not installed the diode and I still get a battery icon (see
attachment). I thought the way it worked is that if a diode was not installed
the icon always showed as empty.

Yes, the battery is measured for the first time and it shows battery icon. If battery voltage is below 100 mV, further battery measurement is disabled. But battery icon still visible until overwrite with some other drawing.

For example, open some screen which overwrite screen area with the battery icon and it disappears. For example open CONFIG => VERSION or DISPLAY=>SCALE=>ELECTRIC DELAY. When you return to the original screen the battery icon will disappears, because battery measurement is disabled due to voltage below 100 mV.

Ok so the issue stemmed from trying to use it with Nano-saver, and got a error (see below)(info: this is only two lines of what it spit out).

2019-10-13 08:38:17,772 - NanoVNASaver.SweepWorker - WARNING - Got a non-float data value: 12.828430175 4.697909355 (12.828430175)
2019-10-13 08:38:17,972 - NanoVNASaver.SweepWorker - CRITICAL - Tried and failed to read data 0 20 times. Giving up.

So after a quick google search i found that the correction needed to be turned on. I turned it on and it did not help.

So the issue is that when the sweep is set to ago above 300 mhz the readings do not make sense. On a 50 ohm load it should have one point on the smith chart (red trace), and in the photo showing the span 50 khz to 900 mhz it clearly do not show the 50 ohm load as a dot on the smith chart (red trace). But when I change the span to 50 khz to 300 mhz the smith chart looks normal with a 50 ohm load.

This issue happened when i updated the firmware.

I flashed the hugen79 firmware (pull and built this morning) and still has the same issue.


!*! Side note !*! : Does anyone know to revert to an old firmware. Running Ubuntu, ive tried "git revert <hash>, then im not able to build.

Going from your picture, it looks like the calibration didn't "take". In
your picture of 50k-900M span, 50k-300M looks right, and the rest just
looks weird. So I would expect it to be that you need to do the full
calibration on the device itself again, including remembering to press
reset, and saving to slot 0. It *may* be an issue with the harmonic mode
used above 300MHz.

--
Rune / 5Q5R

KE8CPD,
The group firmware repository below might be your best bet for locating the old firmware. Try the hugen or edy555 folders.

/g/nanovna-users/files/Firmware/All%20%28known%29%20publicly%20available%20NanoVNA%20DFU%20files%20from%20May%205,%202019%20through%20to%20Sept%2029,%202019

- Herb

KE8CPD,
Can you confirm that when you power up your NanoVNA that you see a battery icon, and that the CONFIG => VERSION menu shows 0,2.3. Just to confirm the upgrade is taking.


- Herb

Yes the firmware did take. the version show 0.2.3-11 + <hash> i didnt get a change to write it down before i reflashed it with 0.1.1.



Once i reflashed back to 0.1.1, and re calibrated the smith chart looks correct under a 50 ohm load. I tried ever release 0.2.x released version as well, and those all cause the issue. So its confirmed its a firmware issue at least my device.

So before i downgraded to 0.1.1 firmware, i did a full calibration including clicking reset and saving to slot 0. I made sure the correction was selected as well. The correction was taking effective at least from what could tell from the output of Nano-saver cli. But the correction above 300 mhz still was not correcting what ever issue is there.


After i downgraded to 0.1.1 the smith chart was correct with a 50 ohm load. So between 0.1.1 and 0.2.x something change with the harmonic mode that caused the issue with my device. Im not seeing any more reports of this issue, but i have not modified (minus adding a plastic case) the nanovna in any way.

Good Evening Everyone,
It looks like this thread has kinda died a bit. I am still without a fix for my issue. I tried again to updated the firmware this evening and still ran into issues above 300mhz. I calibrated it (see photo of correction turned on) and the photo of the version.

Anything beyond the 0.2.x firmware is causing the issues, since 0.1.1 works just fine. I have seen other people have similar issues with the new firmware on this group.

KE8CPD6,

I had the same issue as you. After clearing the config data and recalibrate, it seems to work OK. Here is what I did.

- Plug in the USB
- Use putty or any terminal software to connect to NanoVNA
- At shell interface, type "clearconfig", then "saveconfig". This is equivalent to load "CLEAR_MEMORY_DFU.dfu".
- Redo calibration.

AA6KL,
Thanks for the info and tips, I was successful in clearing the config and saving the cleared config to slot 0. Re-calibrated the device, and there was still no change with the smith chart above 300 mhz.


Firmware verison 0.1.1 is fine above 300 mhz, and anything above 0.1.1 causes the issue. So i still going back on the firmware is the issue (at least on my device).

I am joining the club. After update to 0.3.0 i got the same issue. Tried everything mentioned here but no help. I am now going to search for v 0.1.1 to see if it helps.

After returned to hugen_900_aa_aug-2-19.dfu firmware, calibration goes ok. but that is very old firmware, so old that it does not even have version number.

Can you point me where to download compiled version 0.1.1?

Pedja,
Try the NanoVNA-H_AA_20191018.dfu firmware @ .

On 23.10.2019. 12:21, hwalker wrote:

Pedja,
Try the NanoVNA-H_AA_20191018.dfu firmware @ .

In meantime I tried NanoVNA-H_AA_20191018.dfu which reports as version 0.2.3-2 and it seems to work ok to. This is good as this is somewhat modern firmware version.

I hope this issue with most recent firmware versions would be resolved.



--
73,

YT9TP, Pedja

KE8CPD,

I have had the same problem when upgrading FW on my nano & a friends. Using the '.DFU' file 'DMR-CLEAR_MEMORY_DFU.dfu' (loading it prior to loading the upgrade FW).

Hope this helps,

Steve, AK4R