Add support for the SuperTimer II. #386
Open
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
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.
Our pack has a Supertimer II which DerbyNet doesn't yet support. The manufacturer doesn't provide protocol documentation or support any other software than their (very old) Windows software. I sniffed the protocol last year, wrote up this timer implementation, and successfully ran our derby with it. It's an old timer without many features that appear to be common with modern timers. The Legacy device class seemed appropriate for it. It does support a probe, so the device is automatically recognized when legacy mode is enabled.
Just noticed there's another implementation with a PR. This also fixes #206