Avatar for Thinkscape


Member since May 2017 • Last active Jun 2018
  • 5 conversations

Most recent activity

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

    Ok, checked that no other devices are trying to connect to it. Even having an open browser tab wouldn't work because the browser kills those web bl connections.

    After you message last month, I've given the pug a fresh battery - unsure if the old one was dead or not (didn't measure).

    I went to bed after reading your last reply, the puck was "dead". In the middle of the night it started flashing red again, then stopped. It's doing that now every few hours, so the battery is not dead.

    Just tried hard-resetting it again few moments ago -- puck is dead again, not responding to more resets, not advertising, nothing. I've also inspected the reported battery levels right after changing the battery on June 10th (see attachment). Started fluctuating 2h after replacing the battery, went down to 80% and stayed there until it stopped advertising and began to blink red.

    I'll buy new set of batteries tomorrow, from a different place (to have a chance of different batch). Maybe the current ones are super dodgy, although it wouldn't explain the second puck which is happy with its cell :

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

    Ok, so the same puck, problems again.
    It went AWOL from BL on may 27...

    Take a look at the attachment - two puck.js, one had battery 100% for months, the other one got fresh battery, was near 100%, then started fluctuating weirdly and then drained itself to 0% within 2 weeks. Both run the same code.

    I gave it a fresh battery yesterday. Today it started flashing red again. I did a full reset moments ago - waited through the last few red blinks. After that - dead. No bluetooth advertisement, soft-restarting does nothing, holding the button while restarting doesn't even show the green LED.

    I'm puzzled as to what is happening with it :-(

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

    I've got 2 pucks.

    1. I've replaced their batteries and updated to firmware v97.
    2. I've uploaded same code via Web IDE.
    3. One puck is happy and working all the time.
    4. The other puck, after ~2-3h, will start blinking red.
    5. It advertises as "Puck js XXX" instead of my name (which means it's reset itself and not running my code)
    6. When trying to connect via Web IDE, it shows up on the list but then "error connecting" pops up.
    7. Nail-reset doesn't help.
    8. Taking out battery and reinserting after 1min allows to connect again, re-upload code.
    9. After ~2-3h, it will start blinking red again.

    What can I do?

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

    Hey again! :-)

    This time, it's about Puck.getBatteryPercentage().

    I've got two pucks, purchased together. One is showing a steady 100% battery at all measurements (calls to getBatteryPercentage()), the other one is fluctuating up to 15%. Measurements are made every 30s, the code is the same, no connections, only BLE advertisements.

    Here's how it looks like on a 12h graph:

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

    I'm testing something now... I've put the over-high puck into freezer for a minute (went down to ~15 deg). I've then put them together on a table and let them "settle".

    The second puck has also been triggering button presses when I picked it up, or when gently tapping it (without the click, just vibrations).

    I've since reset it again, uploaded my code again and let it settle with temp. I now have around 3 deg difference between them, which is not bad. I'm calibrating them now with a primitive thermometer.

    I'll try to get a more accurate one and calibrate them both again, and see if I get this weird behaviour again.

    I'll report back. Thanks!

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

    Hey guys, I need some advice.

    I've purchased two Puck-s (to start with), and I'm running exactly the same code on both, which reports temperature via BLE advertising (example from docs).

    I'm seeing wildly different readings between both -- look at the screenshot below.
    One would report 19, while the other: 27 degrees.

    Is it something I should consider normal?