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

common optional SYSEX commands #89

Open
monteslu opened this issue Jun 1, 2017 · 2 comments
Open

common optional SYSEX commands #89

monteslu opened this issue Jun 1, 2017 · 2 comments

Comments

@monteslu
Copy link
Contributor

monteslu commented Jun 1, 2017

Thinking it would be cool if we kept some documentation around of SYSEX commands people are using. Things such as the codes for neopixel interaction in node-pixel or the accelerometers in playground-io.

No set in stone registry, just documentation on what's being used to help avoid collisions or give guidance on implementation for new hardware.

@soundanalogous
Copy link
Member

soundanalogous commented Jun 1, 2017

there is a place to do that here: https://github.com/firmata/protocol/blob/master/feature-registry.md

If it's not in the registry, then it shouldn't be used in any public library. If there's a collision, it's the fault of the library author in that case for not getting it into the registry. (well which is sorta unfair since I didn't create the registry until a few months ago... but going forward that should be the practice).

@soundanalogous
Copy link
Member

These types of hardware-specific features should also use the Extended ID (00H nnH nnH). For example we can add IDs for the accelerometers in playground-io, but they have to be the 3 byte variety.

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

2 participants