moving Tone feature over from firmata/arduino #24
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.
Copied this over from the firmata/arduino repo and made some updates.
To do:
If duration is optional, make sure noTone() is called during a systemReset
Note: It would be helpful if the call to firmataExt.reset() in the systemResetCall function of ConfigurableFirmata was before the pins are reset to their default modes. This would enable the reset function of any particular feature class to perform any cleanup based on a specific pin mode. For example, ensuring that noTone() is called for any TONE pins. I'm not sure if this has any negative effects yet.