Broken data in graphs (v035)

[igor-m]

It seems there is a bug in v035 graph calculations or elsewhere. Here is an example with the v034 and v035 - the same settings and connected to an H4 terminated with stock coax and stock 50ohm load (continual sweep, not calibrated).

[RandMental]

 Have you Recalibrated the 0.3.5 version?     The jaggered lines normally means you need to recalibrate.  .  -------- Original message --------From: IMO [email protected] Date: 2020/07/11 11:46 (GMT+02:00) To: NanoVNA-Saver/nanovna-saver [email protected] Cc: Subscribed [email protected] Subject: [NanoVNA-Saver/nanovna-saver] Broken data in graphs (v035) (#239) It seems there is a bug in v035 graph calculations or elsewhere. Here is an example with the v034 and v035 - the same settings and connected to an H4 terminated with stock coax and stock 50ohm load (continual sweep, not calibrated).

—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe. [ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/NanoVNA-Saver/nanovna-saver/issues/239", "url": "https://github.com/NanoVNA-Saver/nanovna-saver/issues/239", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[igor-m]

The graphs are broken when "calibrated" as well - see below. The calibration has been done within saver v035.

[igor-m]

The same cal procedure with v034 and sweep. The calibration has been provided within v034.

[zarath]

Very strange behaviour... Mostly jumps at the 300/600/900/1200 MHz marks

[igor-m]

All above done with the ORIGINAL FACTORY H4 firmware (Feb21st). I'm going to flash the NanoVNA-H4 v0.8.4.7.dfu in..

PS: here it is with "2kHz bandwidth", 201 points, saver v035, 0847dfu, fresh calibration done inside the v035. Looks a little bit more noisy than the v304 above.

[zarath]

@igor-m are you able to run source code installation? It seems, that it is only happen with older sweep / scan command. If I do a scan mask command it's looks allright.

P.S. can you give me the debug output? nanovna-saver.exe -D debug.txt

[igor-m]

The 0847dfu works unreliably with the v305 however, it loads nonsense upon connect into start/stop and usually crashes the app. I was lucky to get the above sweep, it seems..

[igor-m]

Enclosed the debug.txt (H4-0847fw and v035 saver). After the connect it reads nonsense into STOP frequency and crashes after couple of seconds while doing nothing.. debug.txt

[zarath]

ok. crash is because of data validation... there are very high data readings. And there is a code path that then simply crashes :-( So if data validation is disabled it should run further ...

[igor-m]

This is a "successful" start, params as above, but I OFF/ONed the H4, then started v035, the START/STOP was empty, I entered 100M/1500M, then I connected H4, it read in the H4 default START/STOP freqs (50K/900M), the single sweep has been done ok, but graphs are with glitches (see below). NO CALibration DONE. Attached the debug.txt from this session.. debug.txt

[igor-m]

This is as above but with Calibration done inside v035 (50kHz/900Mhz). Still glitches in the graphs.. PS: none glitches on the H4 LCD..

debug.txt

[zarath]

can you try https://github.com/zarath/nanovna-saver/actions/runs/165679524

[igor-m]

036pre- After connecting freshly started H4 (H4-0847fw, default 50k/900M, internally calibrated) it took over start/stop 27/30MHz(??) and did a sweep. I entered 50k/900M in and I did a sweep - see below (2010points). Looks promising..

[zarath]

So I just have to investigate which firmwares are able to do scan mask command >= 0.7.1 of original nanovna...

[github-actions[bot]]

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a 👍 Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs. Thank you for your contributions!