Note that the markers in nanovna-saver and the nanovna display are set
independently. Did you manually set those specific marker values in
Saver? Or were they automatically set by saver? Do the marker values on
the Saver data display screen match the ones you see, or the ones you typed
into this message? Saver's algorithm for setting the bandwidth markers for
the highpass may not be identical to the algorithm on the nanovna itself,
so it would not be surprising if they did not exactly match.
On Sat, Aug 26, 2023, 2:20 PM Larry Mollica AD6G <auubtab4b8@...>
wrote:
Sorry if this has been addressed already. I've made attempts to find some
discussion of this here but so far unable to track it down.
The frequency axis in NanoVNA saver (0.3.10-Win7, same for 0.3.8) & Python
3.7.9 appears to not agree across the graph with the markers. Please see
attached (High pass after.png). The frequency axis & markers appear correct
on the NanoVNA screen, they only disagree in NanoVNA Saver.
Markers:
1 = 146.19 MHz
2 = 146.5
3 = 146.79
Note that marker 1 appears to the right the graph's 146.2M. Marker 2 is
correct. Marker 3 is to the left of where it should be.
Is there some way to correct this? Thanks
