LarsiLund

Most recent activity

• First trials - and errors

  @LarsiLund started

  • 8 comments
  • 2,971 views

  @allObjects replied
• First trials - and errors

  in Puck.js, Pixl.js and MDBT42 • 8 years

  

  I blink the roman "digits" in sequence. With three LED:s numerals up to 50 (the number 40 and 50 twisted by only using X) can be presented by only using short blinks, and with much fewer blinks than morse code.

  I handle the "output" using an interval timer, which means that I output only the last "message" encountered. It repeats every three seconds for a minute. After a button click it is reactivated for another minute.

  I have encapsulated my simple UI (with code for both input and output) in a handy class, and used it in quite a few hacks.

  If someone is interested I can probably encapusate it in a convenient library.

• First trials - and errors

  in Puck.js, Pixl.js and MDBT42 • 8 years

  

  When "trying to connect to each other" i used the code in the "fast" sample which keeps the connection alive. This probably prevents connections in the opposite direction.

  I will try again with the "slow" version. Initiating the connection for every button press should probably make it. As long as all sessions are closed properly...

  When it comes to debugging, I do not want any hardwiring. I like the feeling of juggling with a handful of Pucks like a pile of casino chips. I want to keep juggling while keeping a few pucks under the loupe. Thats half the charm of Puck (or at least 90%)...

  I am trying to make the Puck as expressive as it can be, by using the LED:s for debug output in roman numeral format (I=red, V=green, X=blue).

  I am enjoying this. Big time!

• First trials - and errors

  in Puck.js, Pixl.js and MDBT42 • 8 years

  

  I received my Pucks today and immediately started to try to give them life.

  As I am running Windows 10 i am limited to using the native IDE, but after a few hours I was up and running.

  The "Controlling other Pucks" is a great starter sample, but seems to have a few limitations:

  1. When the slave Puck is paired with Windows it is not found by the master Puck. I have to unpair in Windows to make it work.
     
  2. I tried to meake two pucks connect to each other, but the fist connection seems to disable the reverse connection.
     
     

  Both issues probably has to do with BLE limitations. As it is hard to debug an unpaired Puck, I have not been able to dig deeper.

  Can anyone help me with this? Do I have to release the outgoing connection on Puck1 to make it accept incoming connections from Puck2?