Skip to content
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

Two comm modes need to be consolidated. #23

Open
ghost opened this issue Apr 14, 2015 · 0 comments
Open

Two comm modes need to be consolidated. #23

ghost opened this issue Apr 14, 2015 · 0 comments

Comments

@ghost
Copy link

ghost commented Apr 14, 2015

The two communication modes (uplink LF=640kHz and uplink LF=160kHz) represented by the '640kHz' branch and 'master' branch, respectively, need to be consolidated. It is increasingly unwieldy to keep them alive in separate branches, and therefore both users and developers could benefit from consolidation.

I propose that we have the WISP automatically choose a mode based on the reader's requested protocol spec in the Query command. This shouldn't be a tremendously difficult task. For simple clock adjust routines, use of function pointers may help simplify the implementation of a multiprotocol WISP. Most everything else falls into place with a simple clock adjustment for switching btwn these two protocols.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants