Not a single thing? Really?
Really.
Same exact procedure with the different versions of software gives me different results.
No fixture, turn on the vna, then start the software and select defaults. Hit link and 1.08 will automatically update the data points to 401. Even if I use the 1.10 defaults. 1.10 just remains at 101.
And I am not pulling your plonker.
Peter
Same firmware that I informed you of a week ago. You even gave me an attaboy for documenting the firmware version.
So you have gone back to the problematic firmware that I gave you an attaboy for telling us what not to use? Last I knew:
https://www.eevblog.com/forum/rf-microwave/nanovna-custom-software/msg3525476/#msg3525476Which is why all your earlier screen shots show 101 data points up until now. At least we now know what has happened.
Just saying that something has changed between 1.08 and 1.10.
Of course it did. Did you think I roll the version for the fun of it?
The way the Nano works, there is a command to request the frequencies that it uses. In my early versions of the software, I would request the frequency, then the two data sets. To speed things up, I would request only the first data set if I was using S11. Later I only requested the frequencies when I changed one of the setting that would effect it. Again, to increase the speed.
When the V2+ came out, they were smart enough to do away with all that. It's up to the software to calculate the table. When I went to a common code base, I had left the frequency request in there. The number of elements the Nano returns is the number of data points I used.
Now we want to sweep / zoom faster. Simple solution, ditch that frequency command. The Nano has always used 101 data points, so lock it down and calculate the tables like how the V2+ works. This is much faster as we don't have to wait for the Nano to send us that data.
This works fine with the 1.08 firmware which at least defaults to 101 data points. Of course, if you use firmware that has a different number of data points, its not going to magically use them. It's not just the number of data points that are a problem, the frequencies the software calculates would be wrong as well.
They may have added similar commands as the V2+ that allows you to program in the data points. You can imagine the nightmare this firmware mess can cause. This is why the manual provides a link to the version I tested with.
The software was tested with the following firmware.
https://github.com/ttrftech/NanoVNA/releases/tag/0.8.0
An attempt was made to test hugen79 1.0.45 NanoVNA-H_20210130.dfu which caused random errors in the data. This was something that was found early on when I first started to look at the NanoVNA. Sadly, a year has passed and the firmware is still unstable.
The fact you have gone back to that version tells me there is some feature it has that is worth having bad data.