vrtisworks2

Comments

• Matt, I only have 12 lights attached, so that's 43 bytes of data (including the 0xff). I am not sure how Processing handles the s.write... but I am issuing that for each byte. When I first started this on Node on the Edison, I was doing a wri…

  in Controlling LightBuddy- output not updating until the next command is sent Comment by vrtisworks2 April 2016
• Thanks Matt, I can't see in the code where it should buffer anything. I did get it to work 'sort of'. See the attached file. By sending out another triplet after what I really want to display, I force what I want to show up, and the odd tr…

  in Controlling LightBuddy- output not updating until the next command is sent Comment by vrtisworks2 April 2016
• I seem to have dug the hole even deeper. I tried a few different variations of delays after the 0xff, two 0xff's in a row (with and without a delay between). Now the tiles all just blink once when I send the 0xff (all on dim), but the actual pat…

  in Controlling LightBuddy- output not updating until the next command is sent Comment by vrtisworks2 April 2016
• Interesting.. even when I try creating basically the same task in Processing, I see the same problem. I send triplets to set all the leds in the string, and nothing happens until I start sending the NEXT command. It isn't a timing problem, becau…

  in Controlling LightBuddy- output not updating until the next command is sent Comment by vrtisworks2 April 2016