-
-
Notifications
You must be signed in to change notification settings - Fork 264
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 fixes #968
Merged
Merged
NanoVNA fixes #968
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previously this would error out because attributes of a Frequency object can't be changed.
Previously, some default stimulus settings were applied locally but not written to the device, so they could get out of sync. The protocol does not allow for observing the user-entered sweep parameters, so the alternative option of reading the device's current settings at startup is not possible.
Previously this would error out as it was passing `numpy.float64` objects to `range`.
Thanks for this! Someone had submitted a PR to my fork but I didn't get the chance to merge it before the PR into upstream. I'll take a look at this in a bit! |
@cafeclimber how about this PR? |
jhillairet
approved these changes
Dec 2, 2023
Thank you @miek |
Merged
Hey sorry about not having the chance to review this PR. I know it's merged now so I'll try my best to take a look this week and submit PRs if I find anything :) thanks for the contribution, @miek |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've been trying to use the NanoVNA support included in the recent VNA overhaul, but I ran into lots of basic runtime errors. Looking back over #744, I'm not sure if anyone with a NanoVNA was able to test it before merging, so that probably explains it.
I've gone through and fixed everything I could find to get it functioning, doing my best to keep to the API that was there. I've been testing with a LiteVNA (which implements the NanoVNAv2 protocol) using the following script:
and it seems to be working well with this set of changes:
(uncorrected output of course)