-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
Wireless RGB #149
Comments
It would also be nice to be able to use I2C or SPI for this, as you could then use something like the Mega connected over I2C for the I/O. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@TylerSeiford you mean you have a 32u4 board connected via SPI or I2C to a mega? |
Yes, such that you could use the mega (or any similar arduino) to expand the IO capabilities of the 32u4 (for example, to enable more interrupt capable pins for fan tachometer measurements). |
On the mega you can use the HoodLoader 2 bootloader, and the internal hardware Serial connection. I don't really see an advantage for using SPI over Serial. SPI only send bytes and the synchronization for sending and receiving must be handled on top. I2C have a acknowledge mechanism but by default only a 32 byte buffer. I also think both need interrupts, so may not work correctly with FastLED. |
There were multiple requests on wireless RGB with CLP, if this is even possible and how to do it. Because CLP is modular it's simple to use it with existing wireless technologies. It is only required that the wireless technologies can reliably transmit (bidirectional) data with an adequate bandwidth. The wireless connection is only used as a bridge between a USB-HID compatible Arduino and remote device.
Two approaches are possible to implement wireless RGB with CLP:
On the remote device CLP is running with an adapter for the wireless connection.
A more detailed description should be added to the Wiki.
The text was updated successfully, but these errors were encountered: