Minor issues with v1.3.1 and NanoVNA-F V2 (fw 0.6.0)
Posted: Mon 23. Feb 2026, 20:57
Discovered a couple of issues that would make using this much nicer, and a couple of limitations:
1. you are currently limiting the number of points to 500, the NanoVNA can go up to 801. Last time I tried on the NanoVNA itself, if you enter a number larger than it's max, it sets the number of points to the Max, so you could allow any number to be entered and then read back that value, let the NanoVNA control the bounds limit.
2. Screen shot doesn't work. This worked under 0.5x fw, but with 0.6.0, it appears to be downloading the screenshot, but all I see in the screenshot window is the galaxy image (I'm assuming this is a default image you have set). Debug log below
3. The calibration documentation is not clear - the pop-up menu says "Use Internal" - that SEEMS to be the configuration for using the NanoVNA's internal calibration, but the documentation says that "Use Internal" is for using VNAMate's calibration, maybe a selector for "Use VNA calibration" or "Use Application Calibration".
4. One issue I had was that when I launch and connect, it reset the state of my VNA. I had been using the VNA not connected to the computer and I wanted to take a screenshot. My thought process was:
-- on the VNA
- stop scanning (what I want is showing on the screen)
- connect USB cable
-- on computer
- launch VNAMate
- take screenshot
Unfortunately, when I connected, it changed the calibration selection and number of points and erased the screen.
Here is the debug log when I tried to do a screen shot (item #2 above):
15:43:26.541 Out: capture
15:43:26.544 Out: \n
15:43:26.547 In: c
15:43:26.547 In: a
15:43:26.547 In: pt
15:43:26.547 In: ur
15:43:26.547 In: e
15:43:26.550 In: \r\n
15:43:26.553 In:
15:43:26.553 In: ,c,c,c,c,c,c
15:43:26.553 In: ,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c
15:43:26.553 In: ,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c
15:43:26.554 In: ,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c
15:43:26.554 In: ,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c
15:43:26.554 In: ,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c
15:43:26.554 In: ,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c
15:43:26.554 In: ,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c
15:43:26.554 In: ,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c
15:43:26.554 In: ,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c
15:43:26.554 In: ,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c
... much more of the same thing and some lines that just said (null)
1. you are currently limiting the number of points to 500, the NanoVNA can go up to 801. Last time I tried on the NanoVNA itself, if you enter a number larger than it's max, it sets the number of points to the Max, so you could allow any number to be entered and then read back that value, let the NanoVNA control the bounds limit.
2. Screen shot doesn't work. This worked under 0.5x fw, but with 0.6.0, it appears to be downloading the screenshot, but all I see in the screenshot window is the galaxy image (I'm assuming this is a default image you have set). Debug log below
3. The calibration documentation is not clear - the pop-up menu says "Use Internal" - that SEEMS to be the configuration for using the NanoVNA's internal calibration, but the documentation says that "Use Internal" is for using VNAMate's calibration, maybe a selector for "Use VNA calibration" or "Use Application Calibration".
4. One issue I had was that when I launch and connect, it reset the state of my VNA. I had been using the VNA not connected to the computer and I wanted to take a screenshot. My thought process was:
-- on the VNA
- stop scanning (what I want is showing on the screen)
- connect USB cable
-- on computer
- launch VNAMate
- take screenshot
Unfortunately, when I connected, it changed the calibration selection and number of points and erased the screen.
Here is the debug log when I tried to do a screen shot (item #2 above):
15:43:26.541 Out: capture
15:43:26.544 Out: \n
15:43:26.547 In: c
15:43:26.547 In: a
15:43:26.547 In: pt
15:43:26.547 In: ur
15:43:26.547 In: e
15:43:26.550 In: \r\n
15:43:26.553 In:
15:43:26.553 In: ,c,c,c,c,c,c
15:43:26.553 In: ,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c
15:43:26.553 In: ,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c
15:43:26.554 In: ,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c
15:43:26.554 In: ,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c
15:43:26.554 In: ,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c
15:43:26.554 In: ,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c
15:43:26.554 In: ,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c
15:43:26.554 In: ,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c
15:43:26.554 In: ,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c
15:43:26.554 In: ,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c,c
... much more of the same thing and some lines that just said (null)