Thanks! That worked. The only save button in my particular firmware is in the CAL page - I assumed that was just for saving the calibration values, but it seems to save the operating state too.
|
Firmwares upgrade only NanoVNA-H4 version.
Today, Hugen also released changes to the H-4 version.
NanoVNA-H4 version compiled on Feb 21, 2020
@hugen79 hugen79 released this 3 hours ago
This update file is only for the 4-inch version NanoVNA-H 4 ! ! !
1.Fix the problem of insensitive touch screen;
2. Fixed the problem that the center frequency is higher than 1G;
3. Fix the problem of mark residue;
4. Update ChibiOS to 18.2
5. Correct the battery display ratio
6. Allow saving Smith display format settings
|
On Thu, Feb 20, 2020 at 09:09 PM, Keith N wrote:
"I did notice a minor issue when inputting a frequency. In any of the modes (start, stop, center and span) after
entering the first digit, the rightmost digit of the previous frequency is partially visible on the input line. Looks like the input box needs to be
a bit wider."
==============================================================
Ken,
I have verified Keith's issue regarding the input field (see attachment). As he said the right most digit of the previous frequency value is still visible when you start to enter the new value.
- Herb
|
Hi, I have upgraded to this latest version. Haven't had time yet to test
for stray lines, but I did notice a minor issue when inputting a
frequency. In any of the modes (start, stop, center and span) after
entering the first digit, the rightmost digit of the previous frequency is
partially visible on the input line. Looks like the input box needs to be
a bit wider.
Keep up the great work.
Keith VK4AKA
toggle quoted message
Show quoted text
On Fri, Feb 21, 2020 at 2:22 PM Ken Liao, AA6KL <kuohsing@...> wrote: Hi Kurt,
Are the small stray lines from measurement curves or from markers? Did
you notice any pattern that causes these stray lines? Did you see this
with edy555's firmware?
All the above information can help me a lot in identify the source and
debug.
Regards,
Ken
|
Re: NanoVNA-Saver and the new _H4 firmware
Hi David,
As Herb mentioned, it will be helpful if you submit an issue report at Hugen's NanoVNA-H master for NanoVNA-H or F303 branch for NanoVNA-H4. A detail description with operating procedure to duplicate the issue would be helpful. If the issue is specific to my software release, then please file an issue report at my tree.
Regarding the binary release, Hugen does more thorough test than I do. Thus, Hugen's release can be considered "formal" or "stable". I am using ChibiOS 18, much newer than edy555 or Hugen's ChibiOS 3. I need more time to prove that the new OS release is stable enough for NanoVNA-H4. Nevertheless, whenever I fix a bug, I would port it back to Hugen's tree.
Regards,
Ken
|
Hi Kurt,
Are the small stray lines from measurement curves or from markers? Did you notice any pattern that causes these stray lines? Did you see this with edy555's firmware?
All the above information can help me a lot in identify the source and debug.
Regards,
Ken
|
Re: NanoVNA-Saver and the new _H4 firmware
Hi Herb I did several test to 900MHz with the NanoVNA-Saver both with 500 point and 100Points with NanoVNA precalibrated and uncalibrated same good results The calibration kit was HP85033C and a sweep of a 20cm HP APC7 airline so the attached screenshot can be considered state of the art for Hugen-H4. It is super to 300MHz very good to 700MHz and not that bad to 900MHz and running outside the Smith Chart from 700 to 900MHz Kind regards Kurt -----Oprindelig meddelelse----- Fra: [email protected] < [email protected]> P? vegne af Jos Stevens Sendt: 20. februar 2020 23:51 Til: [email protected]Emne: Re: [nanovna-users] NanoVNA-Saver and the new _H4 firmware Herb, Well, my calibration tryal was @ 1010 points ( 10 segs) , frequency range 1MHz to 50 MHz, CH0 only, on a Windows 10 PC. Regards, Jos Op 20-2-2020 om 18:51 schreef hwalker:
I also flashed the new firmware version 1.3 into my NanoVNA-H4 and performed a 404 pts, 50k - 1 GHz calibration using NanoVNA-Saver to see if I could duplicate Jos' report. My calibration using the NanoVNA-saver "wizard" went fine and I had no problem applying, saving, or restoring/applying the calibration.
I did a full recalibration and touchscreen recal after loading ver 1.3, even though it didn't seem to be necessary.
- Herb
|
Re: NanoVNA-Saver and the new _H4 firmware
Herb,
Thanks for the reply.;? Strange, the only difference is that I didn't use "ideal standard" but had set for "load = 49.85 Ohms" i.s.o? 50 Ohms, but I don't think, this makes a difference; Anyhow its very late now in The Netherlands, will check more tomorrow.
Greetz
Jos
Op 21-2-2020 om 00:23 schreef hwalker:
toggle quoted message
Show quoted text
On Thu, Feb 20, 2020 at 02:51 PM, Jos Stevens wrote:
Well, my calibration? tryal was @ 1010 points ( 10 segs) , frequency range 1MHz to 50 MHz, CH0 only, on a Windows 10 PC.
================================================================
Jos,
I just ran NanoVNA-saver cal on my -H4 using 1010 points ( 10 segs) , frequency range 1MHz to 50 MHz (see attached) and still had no problem applying the calibration.
My computer is also a Windows 10 PC. I did run a full SOLT instead of just an SOL. Shouldn't make any difference. Hopefully, another -H4 user can run a similar calibration and help to narrow things down for you.
- Herb
|
Re: NanoVNA-Saver and the new _H4 firmware
On Thu, Feb 20, 2020 at 12:47 PM, David Fragale wrote:
Does this flash cure the problem of momentary markers loading behind programmed ones..and does this cure the nasty problem of the CH Z disappearing and needing to be reawakened to get a display of "Z" even though I specified it be displayed and the control page actually showing it was supposed to be present/displayed ?
=========================================================================
David,
The version 1.3 release is meant to address the NanoVNA-H4 "stray display artifacts" issue reported to hugen. The NanoVNA-H4 only has CH0 and CH1, so I'm not sure which "CH Z" or "control page" you are referring to.
If you note an -H4 hardware or firmware related issue you should submit it to hugen's GitHub page and he or Ken will usually try to resolve it, as they have for other -H4 issues we have submitted. I generally submit an issue report if no one else does, but only after verifying the issue myself. My NanoVNA-H4 has not displayed any of the hardware or firmware issues you have reported.
- Herb
|
Re: NanoVNA-Saver and the new _H4 firmware
On Thu, Feb 20, 2020 at 02:51 PM, Jos Stevens wrote:
Well, my calibration? tryal was @ 1010 points ( 10 segs) , frequency range 1MHz to 50 MHz, CH0 only, on a Windows 10 PC.
================================================================
Jos,
I just ran NanoVNA-saver cal on my -H4 using 1010 points ( 10 segs) , frequency range 1MHz to 50 MHz (see attached) and still had no problem applying the calibration.
My computer is also a Windows 10 PC. I did run a full SOLT instead of just an SOL. Shouldn't make any difference. Hopefully, another -H4 user can run a similar calibration and help to narrow things down for you.
- Herb
|
Re: A Good source for Calibrated Loads in formats other than SMA -
#calibration
Hi I will create a document soon with all the settings required for the NanoVNA-saver both for the male and female kit based on Rosenberger parts. They will include the L and C coefficients used by NanoVNA-saver. The male and female loads are individually measured by SDR kits with a 4 wire tester and value written on the inside label of the wooden box. The short open and thru delays are contained in the calibration kit file, a standard part of the VNWA software and thus not suppled with the delivery of the kit. These will be included with my document to support purchase from SDR-Kits of these super calibration kit. I just need to find the time ? Kind regards Kurt -----Oprindelig meddelelse----- Fra: [email protected] < [email protected]> P? vegne af jsternmd Sendt: 20. februar 2020 19:53 Til: [email protected]Emne: Re: [nanovna-users] A Good source for Calibrated Loads in formats other than SMA - #calibration Another good source for Precision with full specification are Rosenberger (German) sold by <> www.sdr-kits.net
|
Re: A Good source for Calibrated Loads in formats other than SMA -
#calibration
I ahve a set of them. They are high quality PL259 plug to SMA with good
quality SMA OSL.
The OSL tested on Agilent 8357C PNA were good past 3ghz but
not to 6. The PL adapted loads of course start to diverge around
120mhz as PL259 are not really good at UHF (they appear as a
25 to 35 ohm impedance bump). Not at all surprising as they
are NOT a constant Impedance connector.
As DC to 30 mhz (maybe a little higher) they are close as precision
as you will likely get allowing for the connector.
The following common connectors are constant impedance and
good to a minimum of 3ghz some higher:
BNC, TNC, SMA, SMB, N
Do be careful as there are 50 ohm and 75 ohm versions of most
of them (not interchangeable).
There are many others some better but not common.
The oddball is u-fl, good to very high but not a user friendly
connector due to size and fragility.
Allison
-----------------
No direct email, it goes to bit bucket due address harvesting in groups.IO
|
Hi Keen Thank you I did update the H4 and used is for a couple of hours. It look good. Only in rare cases there is small straylines, e.g. just one yellow one, and it disappear very quickly. So to speak like what happens on the H version now and then. Kind regards Kurt -----Oprindelig meddelelse----- Fra: [email protected] < [email protected]> P? vegne af Ken Liao, AA6KL Sendt: 20. februar 2020 14:03 Til: [email protected]Emne: Re: [nanovna-users] #nanovna-h4 stops at boot screen Kurt and Herb, I fixed the stray display artifacts left by moving markers. Please give a try and let me know if there is still any issue. Ken
|
Re: NanoVNA-Saver and the new _H4 firmware
Herb,
Well, my calibration? tryal was @ 1010 points ( 10 segs) , frequency range 1MHz to 50 MHz, CH0 only, on a Windows 10 PC.
Regards,
Jos
Op 20-2-2020 om 18:51 schreef hwalker:
toggle quoted message
Show quoted text
I also flashed the new firmware version 1.3 into my NanoVNA-H4 and performed a 404 pts, 50k - 1 GHz calibration using NanoVNA-Saver to see if I could duplicate Jos' report. My calibration using the NanoVNA-saver "wizard" went fine and I had no problem applying, saving, or restoring/applying the calibration.
I did a full recalibration and touchscreen recal after loading ver 1.3, even though it didn't seem to be necessary.
- Herb
|
Re: Android app cable not working!
OK, progress... sort of. but not yet quite working. The new OTG cable installed. Result is it shows a connection available but the web app then displays ERROR: Failed to claim interface On Wed, Feb 19, 2020 at 5:52 PM Kayak via Groups.Io <kayak1176@...> wrote:
Joerg, thank you maybe that is the "simple thing" preventing this?
Would this otg adapter cable suffice, do you think?
amazon.com/Cable-Matters-2-Pack-Adapter-Inches/dp/B00GM0OZ4O
On Wed, Feb 19, 2020 at 11:20 AM Joerg-ex DB2OO <exDB2OO@...> wrote:
Kayak,
it seems to me, that you place the OTG adapter at the NanoVNA and not at the smartphone. Why do you need otherwise the"...USB-A
|
Re: A Good source for Calibrated Loads in formats other than SMA -
#calibration
Referring to the OP reference, they look a lot like N male to to SMA female adapters with a male SMA O/S/L screwed onto them. So you can as well buy one N male to SMA female adapter for 3$ on eBay -- NanoVNA Wiki: /g/nanovna-users/wiki/homeNanoVNA Files: /g/nanovna-users/filesErik, PD0EK
|
Re: errors of "error" models
#107': On the Missing Terms in NanoVNA firmware - ERRATUM
Dear Erik,
Thank you very much indeed for your valuable comment,
since you forced us to recheck the related code.
No, we can not explain that, simply because we erroneously
noticed this absence.
We are terribly sorry for the inconvenience.
Please accept our apologies.
Hence, we withdrawn this proposition:
Best regards,
gin&pez@arg
:107'#
|
Re: A Good source for Calibrated Loads in formats other than SMA -
#calibration
|
Re: NanoVNA-Saver and the new _H4 firmware
Does this flash cure the problem of momentary markers loading behind programmed ones..and does this cure the nasty problem of the CH Z disappearing and needing to be reawakened to get a display of "Z" even though I specified it be displayed and the control page actually showing it was supposed to be present/displayed ??Other than the NanoVNA being sensitive to the lay of the USB cable in the vicinity of the UUT ( which is a lot easier to counteract if you ditch the short USB jumper supplied and switch to a 3 ft. cable ( and add? ferrite shells on the ends around the uUSB connector? housings)? . That longer cable gives you the chance to actually elevate a UUT and puts your body proximity effect as far away as possible .
? DWF , KA4CNPIn a message dated 2/20/2020 12:51:40 PM Eastern Standard Time, herbwalker2476@... writes:
? I also flashed the new firmware version 1.3 into my NanoVNA-H4 and performed a 404 pts, 50k - 1 GHz calibration using NanoVNA-Saver to see if I could duplicate Jos' report.? My calibration using the NanoVNA-saver "wizard" went fine and I had no problem applying, saving, or restoring/applying the calibration.
? I did a full recalibration and touchscreen recal after loading ver 1.3, even though it didn't seem to be necessary.
- Herb
|
Re: nanovna saver display
Thank you Stefano!? I will try that tonight.
73
Glen K4KV
toggle quoted message
Show quoted text
On 2/20/2020 13:54, stefano bello wrote: Hi Glen,
IMHO it is only a problem of resetting charts.
As you have a frequency range problem:
1) Point the mouse cursor on the chart that show the wrong behaviuor.
2) right click to show the chart management menu.
3) On such menu left click Reset because the VNA Saver could have some "memory" of previous measurement
4) Then always on this menu choose Frequency axis and left click on Automatic
5) Alternatively you can choose Frequncy axis then customize the minimum and maximum frequency.
Sometime the problem is on Data Axis ( vertical ) and the chart management menu can help too.
Stefano I3VBP
|
Gyula Molnar
Kurt Poulsen
gin&pez@arg