Jerry, You're stuck on this point but it's simply not true. It's not the kernel. The issue here is the API level used to build the app. That's it. It's the API level. When the Play Store says that an

ai0k.net@groups.io> wrote: Nope, it's not the kernel version, it's the version of the Android API that the application was built under. Newer API versions don't support very old versions of Android. h

These kinds of loop antennas have very narrow bandwidth. The fact that the NanoVNA is splitting the frequency range you're testing into discrete buckets (400 or so of them) means that if a dip happens

What this means: ------ File "/Users/bobegan/nanovna-saver/src/NanoVNASaver/Formatting.py", line 57, in <module> def format_frequency_inputs(freq: Number | str) -> str: TypeError: unsupported operand

The current release on Github doesn't have downloads. (Which is why it's tagged "Sorry, No Binary".) You need to go backwards in the history if you want a pre-packaged download. Use https://github.com

Peter, Thanks. That worked for me. However, I had to install Python 3.10 or later, however, not the 3.9 that comes with MacOS. 73, -Rick

That's 0.5.5 which is x86_64 only (i.e. 64-bit Intel). It won't run on an Apple Silicon Mac. I get the following error: "nanovna-server" can't be opened because Apple cannot check it for malicious sof

The AM radio in my car works just fine. Chevy BoltEV. How short our memories are - does nobody else remember "alternator noise"? Cars are mobile noise generators. 73, -Rick <craig.cherry=kalmia.com@gr

"HW version: 4.3_MS". That's a MS5351 device. 73, -Rick wrote:

The USB-C port on the NanoVNA systems is reported to be rudimentary, and not capable of properly negotiating the voltage it wants. 5 Volts is expected. Use a USB-A to USB-C cable and this won't usuall

llaassllaaass@...> wrote: You probably need to remove that /usr/local/bin/python - 2.7 is quite old. Apple ships 'python3' in /usr/bin/python3 There's no /usr/local/bin/py* on my ARM Mac. I'm us

Al, Just to verify: if you turn the device on, it's working with some version of NanoVNA firmware. It's not dead or bricked, it's just running firmware that's missing features and you're trying to re-

Just another hint: some cheap cables (see for example the one shipped with the NanoVNAs) won't work for both orientations. If the device doesn't work, unplug the USB-C plug and rotate it 180 degrees,

Yes, I remember Microfortnights. :) The DEC VMS operating system's TIMEPROMPTWAIT configuration parameter - which says how long the system waits for the user to enter the clock time before giving up -

There's also the fact that a 100 MHz square has a Fourier decomposition into decreasing amplitude of odd harmonics of sine waves. The 100 MHz square wave is represented by a 100 MHz sine wave, a lower

Larry, I'm using your patched DfuSe tool. Makes it a lot easier to understand what you're doing. It is unfortunate how many people clearly didn't bother to look at any of the resources here. -Rick

Answered in the other thread. 73, -Rick

DfuSe uses weird terminology. "Upload" means to take a snapshot of the device and save it on your PC (it uploads from the VNA to your computer?) You have to use the box on the right to download to the

The language isn't changing because there is no English translation of this article on the site. The language choice menu "works" for content that has an English version, and doesn't when it doesn't e

dOK, so you have a NanoVNA-H4. Did you flash "NanoVNA H4 v1.0.69.dfu" ? There's two different files - one for the small screen (-H) and one for the 4 inch screen (-H4). Since it's a H4, you need to en