• I have a couple of original pucks. What is the latest version of the firmware I can use with them? I upgraded to v2.0.5 and was seeing some weird behaviour with the magnetometer.

    With this code to log the x,y,z values:

    Puck.on('mag', function(xyz) {
      console.log(xyz);
    });
    Puck.magOn();
    

    I get crazy values that jump all over the place with 2v05:

    { "x": -515, "y": -515, "z": -515 }
    { "x": -9, "y": -2057, "z": -2057 }
    { "x": -129, "y": 32639, "z": 32639 }
    { "x": 0, "y": 3071, "z": -1 }
    { "x": -258, "y": -258, "z": -258 }
    { "x": -129, "y": 32639, "z": 32639 }
    { "x": 0, "y": 3071, "z": -1 }
    

    The same code on 1v95 give sensible readings:

    { "x": -3165, "y": 757, "z": -3567 }
    { "x": -3172, "y": 759, "z": -3571 }
    { "x": -3177, "y": 761, "z": -3566 }
    { "x": -3176, "y": 762, "z": -3567 }
    
  • Sorry about that - I'll look into this now. 2v04 will be absolutely fine, but 2v05 should have worked.

  • I'm just looking into this, and it seems that Puck.mag() works fine on 2v05 and later. It's just magOn that has problems.

  • Ok, if you try a 'cutting edge' build from https://www.espruino.com/binaries/travisĀ­/master/ then it should now be fixed. I'll try and get a 2v06 release out soon with this sorted.

    That was a particularly strange issue - I've basically just had to revert to using the original I2C code to get it working reliably.

  • Thanks for the fast reply, Gordon.

    For a moment I thought the 1v and 2v in the firmware version number might relate to v1 and v2 puck support.

    Robin

  • Post a reply
    • Bold
    • Italics
    • Link
    • Image
    • List
    • Quote
    • code
    • Preview
About

Latest firmware for original Kickstarter puck.js

Posted by Avatar for RobinSummerhill @RobinSummerhill

Actions