Dp4d #135
Open
Dp4d #135
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
This is needed when switching from one receive mode to another.
missed a few instances when moving from BPSK to BFSK
This implements a master controller (m4ster) that will - when started by a host PC connected via USB(serial) - manage association to up to 10 rad1o devices in "dp4d" (client) mode. Free controller slots are announced. dp4ds claim a free slot and send controller data (continuous X/Y coordinates, button presses) to the m4ster, as well as a randomly chosen ID (randomness is sampled from RF noise).
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.
a minor new feature for rflib, and a new example with potential practical use: the "dp4d", a way to use 1-10 rad1os as remote control devices. 1 rad1o must be in "m4ster" mode and will manage devices and forward controller data to a host PC connected via USB-CDC (serial).