开云体育

Glad you got it working. A few questions. 1. What Hugen version are you running now? 2. Did you use the NanoVNA-H4-MS or NanoVNA-H4-SI version? The SI version is for the original clock chip which is

Hello, Have you not listened to my podcast on this? The Windows and the Mac binaries are just that. You put them where you like. Of course, on the Mac /Applications is where you typically drop your

Got it working !!! I had decided to send this back to Amazon and try another in case I may have gotten a bad one. I flashed the 'original' Hugen FW back but must have used a newer version by mistake.

Hi. It looks like you are having the dreaded Clock Generator instability around 300MHz. You can see the spurs around 300 and 600MHz on the yellow traces in your photos. The basic design of the NanoVNA

Hugen, Is this a problem with the SI version chips? Thanks, Mike N2MS

If it is in dfu mode, then upload the firmware and reboot. This should work. If the device is in dfu mode, only a usable program can bring it out of this mode. -- Gyula HA3HZ ( http://ha3hz.hu )

Hi Leif, I'm still using the win7-32 bit version, as are you. I think a lot of people are like that, they just don't talk about it. The article about NanoVNA on my website therefore appeared after my

This is because DiSlord's firmware uses the 3rd harmonic at 600MHz, and the VCO frequency division factor is set to 6, which requires the VCO of the MS5351 to be locked at 1200MHz, but not every

For me, it's very simple I have a Windows Seven Pro version and I have a Windows XP virtual machine on it. When migrating from 7 to 10, can't reinstall this Window XP VM and I need it for some mapping

an i prefer the even more actual version from dislord (just 2 weeks old!!) https://github.com/DiSlord/NanoVNA-App/tree/main/Win32/Release greetz sigi dg9bfc Am 30.08.2022 um 23:38 schrieb Roger Need

I download the python from git and run it, rather than trying to do it from a binary. I've also used pip https://github.com/NanoVNA-Saver/nanovna-saver

OK, I re calibrated at 280, it was worse. I went to 250, re-calibrated, worse yet. Went to 200 and re-calibrated even worse. I think my nano is bad.

OK, I found what you were talking about. Mine was set to 300M and I changed to 280 as you suggested. Will do another cal and see what happens. Thanks!!

I prefer NanoVNA app by OneOfEleven instead of NanoVNA Saver. It has better graphing capability and it is easier to scale plots. A forked version with some bug fixes by Owen Duffy is available at the

In order to run on WIN 7 you need to install the required driver (WIN 10 has this built-in). Here is a link to my Box account where you can download it >>

OK it works at lower frequencies so we know the problem. It is what DiSlord described in his posts. The 5351 Clock chip used in the nanoVNA is only guaranteed to 200 MHz but it usually works up to 300

As I understand it, he threshold setting changes where the internal generator switches from fundamental to harmonic mode or similar. The threshold you are setting will depend upon the capability of

can someone point me to the correct links for nanaVNA-saver for mac OS X and documentation for how to install? I found a zip file which appears to contain a binary, but no install instructions, and it

I appreciate all the help with this!! I apologize that I don't know a lot of the terminology for this nanovna. I'm still not certain if there is an issue with the nanovna itself. If you suspect one,

Not seeing my post after changing the range. I'll post the pics again. That seems to correct the issue. Thanks!!