-
Notifications
You must be signed in to change notification settings - Fork 305
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NanoVNA not recognized by Python script #150
Comments
Update: I figured from the NanoVNA-Saver that it uses VID = 0x04b4
PID = 0x0008 for the S-A-A V2 model, and although at first it seems to work, it doesn't respond. E.g. I run |
The V2 firmware doesn't support on device gui when connected to usb. Therefore it has no screenshot option. |
@zarath One more thing: I've managed to get everything working and I'm able to output touchstone files, plot them etc., but I see that the |S21| values disagree between the NanoVNA alone (i.e. not connected to python/a computer) and the ones the python script is measuring. My understanding is that once I calibrate the device (SOLT) and connect it to the computer, the python interface does not seem to pick up the latest calibration on file. Is there a simple way to either load the latest calibration on file or manually re-run the SOLT calibration again through python, or do I write something up and save each state (OPEN, SHORT, LOAD, THRU) as a separate |
Oh, that's of course a lot more work... V2 just delivers uncalibrated data via usb and it is requiered to do it by ones own. |
Solved with scikit-rf's calibration tool, thanks! |
Hello |
@Haydarjammoul I had to change my VIDPIDs to: |
@edy555 @cho45 I'm trying to run the Python script, but I get
Even though my NanoVNA does get recognized fine by NanoVNA-Saver, listing:
/dev/cu.usbmodemDEMO1 (S-A-A-2)
Anyone faced this issue or has any idea what the issue could be? I also tried debugging using
print(device_list)
, and I see a difference:NanoVNA plugged in:
vs.
Nano VNA not plugged in:
Thanks in advance!
The text was updated successfully, but these errors were encountered: