I just measured a bandpass filter on 2.4 GHz with NanoVNA V2_2. With only 1 marker the frequency values are correct, but adding more markers, the values show incorrect frequencys with a "-" sign. (e.g. -1895.967MHz instead of 2400MHz).
Firmware is: git-20200617-1a9a11d.
At 1.3 GHz everything is ok. I found out, that this fault happen exactly at 2147 MHz. Moving the marker bejond that value, it switches to a "-" sign and couts backward.
A signed 32bit integer can count to max. 2 147 483 647, as Chirstian Zietz explaind in nanovna-users@groups.io. So this may be a SW-bug. He recommended to use unsigned integer.
73, DK5DN
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.
marker
schweppe 2020/10/23 07:41
OwO 2020/10/23 23:37
This is fixed in the latest firmware I think, try upgrading.
To reply to this topic, join https://groups.io/g/NanoVNAV2