Group Actions
Engagement
  • Author Author: TechnoChic
  • Date Created: Date Created
  • Views 2318 views
  • Likes 7 likes
  • Comments 6 comments
Related
Recommended

Syncing NeoPixel Animations Over Radio * 07 *

TechnoChic
Syncing NeoPixel Animations Over Radio * 07 *

Welcome back! Natasha here. :)  

This is the seventh of 10 blog posts featuring each video in my series on animating LEDs with micro:bit and Make Code. If you've just stumbled upon this post, start from the beginning here.

Let's set up the radio to sync NeoPixel animations with micro:bit!

Watch it now:

micro:bit radio communication

In this video, I show you how to set-up and use the micro:bit's built-in radio to send the animation mode to other micro:bits.

This skill is perfect for syncing bike wheels, multi-part projects, or multiple people!

Radio In Microsoft Make Code

Building on the last video, it takes just a few blocks to add radio functionality and send the animation mode to other micro:bits in the same radio group. 

Using micro:bit as a remote for LED Animations

In no time, you'll be changing animations from across the room and syncing your projects together!

How did it go?

Did you sync multiple micro:bits? What other data would you want to send over radio?

Comment below or join the Discord channel to share your questions and ideas. 

See you there! Slight smile

  • in reply to beacon_dave

    I would only use the radio group feature to separate radios that will never communicate from one another - placing them on different channels and keeping all radios that will send/receive ANY data on the same channel.

    Name/value pairs are the way to go if you want to isolate some micro:bits and not others. Any micro:bit can ignore a command if there isn't any code written to react to it. And, you could write communication only between your micro:bits that the whole group doesn't know about, but still react to the incoming group commands if you'd like. For example, I'm thinking of making my bike music reactive so I would send the audio data to only my micro:bits but listen for the color mode from the radio group. Slight smile Notes

  • Nice update.

    Good explanation of how the radio can work between the micro:bits.

  • in reply to TechnoChic

    Sounds like the 16 button matrix could also be useful for allowing your riders to set the radio group at ride time rather than programming time.

    For an additional layer of robustness, one could perhaps consider adding a secondary group code as a prefix to the protocol commands. However it looks like you are limited to 8 characters in the key-value pair, but if you send a string, then it looks like that increases to 19 characters.

    One downside to the radio groups is that it doesn't appear to allow for a 'broadcast to any group'. Would perhaps have been nice to have group 0 or 255 reserved for this sort of functionality without having to loop through changing radio group each time. e.g. if you wanted broadcast beacons on a route that forced a colour change as every rider rode past to create a rainbow type effect, then using radio groups the beacon would need to set the radio group, send the message, set the next radio group, repeat the message and so on up to 256 times to make sure every micro:bit could receive it.

    If a rider has multiple micro:bits (front wheel, frame, rear wheel, jacket, helmet...) then this could also be interesting as you may not want all micro:bits to change on a single radio group command however all micro:bits will need to be joined to the same radio group to communicate via a handlebar or wrist controller micro:bit. So this may require local key's, group keys and broadcast keys to cover all bases. Alternatively you roll all three into a single 19 character string and parse it.

  • in reply to beacon_dave

    So far all the people who took my workshop remained in the same group- but theoretically as long as each group agrees to use a different channel it should work just fine. 

    I created a 16-mode protocol that dictates the color for each mode - that way everyone in the group can experiment with different animations but the color would all be the same. (Ex: mode 4 = yellow, mode 11= red, white, blue etc. ) I also added a second parameter in case we wanted to change a different variable as a group, but never implemented it. I chose 16 modes because I intend to use a 16 button matrix as a controller but haven’t had time to build it yet. :-p 

    You can check out the system in the second half of this blog post: technochic.net/.../led-bikes-how-to-code-the-lights