Avatar for DanTheMan827

DanTheMan827

Member since Jul 2020 • Last active Jan 2021
  • 3 conversations
  • 7 comments

Most recent activity

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

    Yeah it's a v2, it was in a pocket inside of its case and went through a full wash cycle and then the dryer.

    I still have the original holder and button, I was able to solder one of the ground legs back on and it worked and the IDE was able to connect, but I removed it again just so there wasn't a risk of it tearing the remaining pad off from the stress.

    I do have my doubts on if the NFC antenna is still 100% though... my code that was previously working now fails to read/write completely with it failing with a generic NFC error on my corresponding app for the puck, that would unfortunately make it unusable for the intended purpose of being a NFC tag emulator with a backdoor for rewriting after locking the "tag"

    Looking at this image, the left side of the battery holder tore the pad right off the PCB, and the button is gone

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

    So, my puck.js went through the washing machine and dryer and that resulted in the button and battery holder falling off.

    I'm wondering what kind of button I could get to replace the damaged one since the pads for the button are still intact (the battery holder pads however...)

    I figured I'll just add some pin headers and give it at least some use as a dev board if I can't somehow secure the battery holder since one of the mounting pads are gone.

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

    You were right, my phone was caching the services, I turned off bluetooth and back on again and it showed up as expected...

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

    I'm trying to create and advertise a BLE service that I can read and write binary data to, but I can't seem to get the service to actually present itself to a connected device, it does advertise however...

    This is the code I've been trying to get working without any success...

    var test = "No data";
    NRF.setServices({
      "78290001-d52e-473f-a9f4-f03da7c67dd1": {
        "78290002-d52e-473f-a9f4-f03da7c67dd1": {
          value : [0, 0, 0, 0, 0, 0, 0, 0,],
          maxLen: 8,
          readable : true,
          writable : true,
          notify: true,
          indicate: true,
          onWrite : function(evt) {
            test = evt;
          }
        }
      }
    }, { uart : false, advertise: ["78290002-d52e-473f-a9f4-f03da7c67dd1"]­ });
    
    setWatch(function() {
      NRF.setServices({ }, { uart : true });
    }, BTN, { repeat: false, edge:"rising", debounce:50 });
    

    My end goal is to have a service that I can write to and then respond back to the device writing the data, I think I could do this by updating the value in the onWrite callback?

    I've been testing with the NRC Connect app and I have the newest firmware on the puck

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

    Oh, I misread, it was potentially 5 years without advertising...

    http://forum.espruino.com/conversations/­297334/

    My usage when actually connecting to the puck would be to connect, transfer about 572 bytes of data, then disconnect... I definitely don't need high-bandwidth mode so that's good to know.

    I suppose I could also increase the advertising interval and lower the BLE transmit power since it'll only need to function within a foot or two of the device that's writing to it and it doesn't need to be detected immediately since the application itself will be scanning in the background for it.

    I don't have a target for the battery life, but I also don't want it to go flat prematurely if I can do simple things to prevent it.

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

    I'm working on a project that simulates NTAG215 tags from the puck.js which will communicate over BLE for managing the NFC tag data, but my question is how long would the expected battery life be in this situation?

    I've read that with just a simple BLE beacon that the battery life is 1-5 years but I don't know how that would be affected by having NFC enabled.

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

    Right now I'm messing around with emulating the NTAG215 NFC specification, it turned out to actually be fairly straightforward to get the basic stuff working.

Actions