Avatar for fiws

fiws

Member since Mar 2019 • Last active May 2019
  • 2 conversations
  • 9 comments

Most recent activity

  • in Puck.js, Pixl.js and MDBT42
    Avatar for fiws

    Thanks. I'll test the cutting edge build asap. :)

  • in Puck.js, Pixl.js and MDBT42
    Avatar for fiws

    My puck stopped advertising my services after updating to 2v02.
    I've tried:

    • resetting
    • hard resetting
    • flashing multiple times

    I can confirm that reverting to 2v01 resolved this issue.

    I've just used the demo code from the docs:

    NRF.setAdvertising({
      0x180F : [95]
    });
    

    The service did not show up in nRF connect or EspruinoHub.

    • 15 comments
    • 601 views
  • in Puck.js, Pixl.js and MDBT42
    Avatar for fiws

    did you flash Pixl with the new version, link provided in #6,#7 and that doesn't work?

    I did not for my colleagues pixl, because i thought there might be more to test on the shipped version – and also … it's not mine. I only flashed the development version on my pixl. Do you want me to test the development version on his pixl as well?

    Yes (functional) to development version, No (fails) to original shipped version. ??

    That's right. NFC is now working on my pixl with 2v01.69 (from the link in #6) but it did not work previously with the shipped version (2v01)

    To clarify: I just wanted to report that: I think the shipped 2v01 firmware has NFC problems on the Pixl.

  • in Puck.js, Pixl.js and MDBT42
    Avatar for fiws

    Sorry for the vague response @Robin. As @Gordon stated the difference of events is normal.

    The issue is that NFC with the shipped 2V01 firmware does not work at all on the Pixl.js
    That is what I observed with our 2 devices.

  • in Puck.js, Pixl.js and MDBT42
    Avatar for fiws

    I can reproduce the issue with a new Pixl.js board (ordered in the same batch) from a colleague running 2v01. So it indeed seems to be a firmware issue.

  • in Puck.js, Pixl.js and MDBT42
    Avatar for fiws

    That did the trick!

    It could have been me not holding it in the right spot in the first place to be honest, i'm not sure.
    There is still something that i don't get:

    I've started counting NFCon and NFCoff events and my stats look like this:

    on: 38
    off: 714
    

    is that normal? I would assume that those numbers should be identical, no?
    I get a lot of off events when my phone is near the pixl but not in the "right spot".

  • in Puck.js, Pixl.js and MDBT42
    Avatar for fiws

    Hi @Gordon. Thanks for clarifying. I just noticed the backlight going off while holding the phone near it.

    So I changed my code to this:

    NRF.nfcURL("http://espruino.com");
    NRF.on('NFCon', function() { console.log('nfc on'); });
    NRF.on('NFCoff', function() { console.log('nfc off'); });
    

    The result is that i get nfc off like 30 times (but never nfc on) when i move my phone near the pixl (back or front – doesn't really matter) but nothing opened on my phone. It worked with the puck. I've also tried a nfc detection app, no luck.

  • in Puck.js, Pixl.js and MDBT42
    Avatar for fiws

    It got shipped with the latest version:

    >process.env
    ={
      VERSION: "2v01",
      GIT_COMMIT: "748a4d3",
      BOARD: "PIXLJS",
      FLASH: 524288, RAM: 65536,
      SERIAL: "51ce5f62-7b5098e4",
      CONSOLE: "Bluetooth",
      MODULES: "Flash,Storage,hea" ... "el,graphical_menu",
      EXPTR: 536882408 }
    

    I am powering it via micro usb. I've also tried a CR2032 (brand new).

Actions