iMo

Do not use kHz MHz GHz in those 4 fields. Do use k M G only and we'll gain 2 more digits to show.. It is clear it is a...

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

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

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,...

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..

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](https://github.com/NanoVNA-Saver/nanovna-saver/files/4906887/debug.txt)

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...

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](https://github.com/NanoVNA-Saver/nanovna-saver/files/4906929/debug.txt) ![Sweep with v035 and 0847dfu and...

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 -...

The same problem here with Win10., Icestudio version 0.5.1n200523 downloaded today. Python 2.7 and 3.7 and 3.8 installed. Quick hack: 1. go to Environment Variables -> System variables -> Path...