Poop Poop and More Poop

Design Brief

Client: Anyone
Designers: NBD with some YT help
Problem Statement: The purpose of this design brief is to create a funny poopEmoji which will require some interaction.
My plan is to design when pressing A a standard poopEmoji will display, press B and its an animated poopEmoji, and when you shake the MicroBit, it will reset to blank.
Flowchart:
On Start - set 2 variables: poopEmoji & animatePoopEmoji
On radio received string with Logic of if/then
On Button A: poopEmoji
On Button B: animatePoopEmoji with short pauses to reflect animation, repeats 3 times loop
On Shake: Reset to no LED’s

Supplies

HEX FILE: poopEmoji

YT Video: poopEmoji

Step 1: On Start

On Start - set 2 variables: poopEmoji & animatePoopEmoji & radio set group to 1

Step 2: On Button A

On Button A: poopEmoji

Step 3: On Button B

On Button B: animatePoopEmoji with short pauses to reflect animation, repeats 3 times loop

Step 4: On Shake

On Shake: Reset to no LED’s

Step 5: On Radio Received

On radio received with the string with 2 If then logic for poop, animatedPoop with pauses and the loop for the animatedPoop

Step 6: Video of End Product

This is the video showing how it works.

Reflection:

I created an art piece using an LED grid. I did a poopEmoji and an animatedPoopEmoji. It was an idea I saw on Youtube because I was having a hard time thinking about something to do. Well the project created the poop picture that stands still, the animated poop emoji with some pauses looks like its moving and then there is a third element which I added on that if you shake it, it will reset to blank or no led’s displayed. I am proud that I got it to work. I was having some issues but once I figured out I needed to turn on the 2nd MicroBit, it went swimmingly. Same as above, getting it to work. I looked at the 2nd MicroBit a bit more and felt that it had an on/off switch. Once that happened, it was smooth sailing. The feedback I would give would be to look over all of your equipment first! Then proceed from there because, at least you will know if it's your program or the equipment or user error, as it was in my case.