erik,
I've been trying to transfer some of my NanoVNA scripts over to the S-A-A-2, and although its communicating, I'm operating blind. Any remote commands to the S-A-A-2 cause the screen to go white with the a "NanoVNA V2_2 USB MODE" message. There doesn't seem to be a command for exiting the USB Mode and the S-A-A-2 stays in that mode even after closing the serial port and exiting a script. The only way I have been able to exit the USB Mode and get back to a normal screen is by cycling power to the S-A-A-2.
Have you been able to find a reset or change mode command while modifying TAPR? Cycling power is not elegant. Actually, exiting the NanoVNA-QT program leaves the S-A-A-2 in the same state, which, is not the way to treat the user. This doesn't seem like Gabriel's usual attention to detail. In this area I would score one for the NanoVNA. I left an issue report at the GitHub page.
It also looks like the S-A-A-2 does not transfer corrected data over USB. Any external program or script will need to apply its own correction data. I don't envy Rune's effort to port NanoVNA-saver to this device. The communications protocol is totally different from the NanoVNA. Even enumerating the serial port required code changes, at least on my windows PC.
Additionally, it appears Gabriel decided to enforce re-calibration if the user changes frequency range. No more interpolation allowed. That's probably a good thing, but will puzzle some prior NanoVNA user's.
- herb
- Herb
- Herb
