litevVNA support #754
Open
litevVNA support #754
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
Based on NanoVNA-Saver#534 (comment) data
readVersion() -> read_fw_version()
read_features() -> init_features()
getFeatures() to get_features()
redrathnure
force-pushed
the
feat/litevna-support-screenshots
branch
from
13b4090 to
714fb90
Compare
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.
Initial version for LiteVNA support. Based on #534 discussion.
Followimg features were tested:
Pull Request type
Please check the type of change your PR introduces:
What is the current behavior?
LiteVNA64 is detected as SAA2 device. This works somehow however it isn't possible to unitize all hardware functionality (e.g. enable more than 1023 points)
Issue Number: 534
What is the new behavior?
Does this introduce a breaking change?
Other information
na