开云体育

non float data value?!
get this on both versions, once connected, any ideas anybody?

screen shot

Hi Dean,
generally, you get this message when the NanoVNA sends data to the
application which falls outside the expected range of valid data. Far
outside, in fact.

There are two steps to remedy this:
1) Make sure your NanoVNA is calibrated before you even started. It needs
to be calibrated across the entire range you intend to use it over. Do a
2-port calibration, not just the short-open-load.
2) If that doesn't help, update your firmware to a newer version, such as
edy555's 0.2.3, which fixes some of the transmission errors that were
present earlier.



Looking at your screenshot, I think step 1 should be sufficient.

I hope this helps, otherwise don't hesitate to ask again.
--
Rune / 5Q5R

Hi

I visited J?rgen, OZ1BNN, yesterday where we tested his NanoVNA which if probably from the same batch as mine. His NanoVNA has the "non floating error" galore. We did try to calibrate but in vain. A F/W has not been tried. However, we also suspect a possible bad connection in the USB connector.

I don't know neither the format of the data frames nor the communication protocol. But I wonder if it would make sense to add some kind of hash to the frame to make it more robust thus enabling a retransmission?

Bo

I do know that I haven't seen those errors since upgrading to newer
firmware, such as 0.2.3. So I think that might be a viable solution in
general, along with calibrating the device.

If it's just a few transmission errors - a maximum of 20 errors per data
segment - the application will power through it. But more systematic
errors, such as is seen when the device is not calibrated, cannot be
compensated for. The valid data range for S11 data is +/- 1.000, and the
application considers it a fail if it sees values beyond +/- 9.5.

--
Rune / 5Q5R

sorted, recalibrated, now working :-)
Thank you Rune.