Thread: LEDs
View Single Post
  #8   Spotlight this post!  
Unread 23-05-2014, 15:35
DohertyBilly DohertyBilly is offline
Registered User
FRC #0111 (WildStang)
Team Role: Tactician
 
Join Date: Nov 2012
Rookie Year: 2013
Location: Schaumburg, IL
Posts: 51
DohertyBilly is a glorious beacon of lightDohertyBilly is a glorious beacon of lightDohertyBilly is a glorious beacon of lightDohertyBilly is a glorious beacon of lightDohertyBilly is a glorious beacon of lightDohertyBilly is a glorious beacon of light
Re: LEDs

Quote:
Originally Posted by nathanwalters View Post
Most people have covered the whole NeoPixel/Arduino design pattern, so I'll skip over that. One thing that hasn't been mentioned that my team (111) did is robot-Arduino communication. We had an I2C link between the robot and the Arduino. Whenever we wanted to update the LEDs on an event, say, the start of a match, raising our arms, or shooting, we'd send a command/payload byte combination to the Arduino which would then update the LEDs. The relevant Java class of our 2013 code is here: https://github.com/wildstang111/2013...ems/WsLED.java
This year we actually changed the way we communicated with the LEDs. We changed the strip we used (from LPD8806 to Adafruit NeoPixel) and the NeoPixel library disabled interrupts over I2C. Long story short, we lost control a few times. Because of this, we used the 4 leftover digital I/O ports on the sidecar to just send a binary number to the arduino, which changed the pattern based on that.
__________________