I had my V2p4 connected via USB to NanoVNA saver doing many S11 and S21 measurements running on latest FW from few days ago and it was all working fine. Had started and stopped both the software and the nano many times. Then I left it on last night since it was calibrated and measurement I hadn't finished and I wanted to keep it at a constant steady state temperature to finish later.
When I came back in the morning, the NanoVNA-Saver was presenting weird data when I would do a scan. Thinking maybe there was some bug that presented itself only after being on many hours, I powered off my V2p4, shutdown (hard power off) then restarted the computer, turned the V2p4 back on, and upon attempting to connect NanoVNA-Saver to the V2p2, the console would print the error:
"Error reading version registers":
Then quits.
Running the V2p4 stand-alone still seems to function.
Thoughts ?
-=dave
Beware of cheap underperforming clones
As of 2022 there are many badly performing clones on the market. V2/3GHz NanoVNA uses parts like ADF4350 and AD8342 which are costly and clones have been cutting costs by using salvaged or reject parts.
See official store and look for V2 Plus4/V2 Plus4 Pro versions only to avoid getting a bad clone. We have stopped selling V2.2 versions since October 2020, so all V2 hardware that are not Plus or Plus4 are not made by us and we can not guarantee performance.
Click here to join and see most recent posts.
"Error reading version registers" from NanoVNA-Saver #nanovna-saver
BTW: You can store a cal setup on the PC to be accessed later without a
recal.
Dave - WØLEV
On Fri, Dec 31, 2021 at 9:19 PM Dave Johnson <davejohnson3000@gmail.com>
wrote:
> I had my V2p4 connected via USB to NanoVNA saver doing many S11 and S21
> measurements running on latest FW from few days ago and it was all working
> fine. Had started and stopped both the software and the nano many times.
> Then I left it on last night since it was calibrated and measurement I
> hadn't finished and I wanted to keep it at a constant steady state
> temperature to finish later.
>
> When I came back in the morning, the NanoVNA-Saver was presenting weird
> data when I would do a scan. Thinking maybe there was some bug that
> presented itself only after being on many hours, I powered off my V2p4,
> shutdown (hard power off) then restarted the computer, turned the V2p4 back
> on, and upon attempting to connect NanoVNA-Saver to the V2p2, the console
> would print the error:
>
>
>
> "Error reading version registers":
>
> Then quits.
>
> Running the V2p4 stand-alone still seems to function.
>
> Thoughts ?
>
> -=dave
>
>
>
>
>
>
--
*Dave - WØLEV*
*Just Let Darwin Work*
Of course, but it was the hourish of normalizing to steady in order for the cal to be valid at my cold workbench that I really wanted to avoid (as I mentioned).
UPDATE:
I finally tried putting the unit in DFU mode then power-cycled. Saver connected without issue afterwards. That’sa bug within the realm of the nano no matter how you slice it. Since OwO won’t release source, I’m sure it will most likely never get fixed unless he stumbles across it and is interested enough to resolve.
73
-=dave - AI4ME
To reply to this topic, join https://groups.io/g/NanoVNAV2