ofeastaien

Most recent activity

• Will rechargeable puck.js be available in the future?

  @ofeastaien started

  • 5 comments
  • 1,758 views

  @Gordon replied
• Will rechargeable puck.js be available in the future?

  in Puck.js, Pixl.js and MDBT42 • 4 years, 1 month

  

  Hi Gordon,

  I currently deal with signal of acc and gyro for motion detect. Some features might require highly sampling rate to accomplish. Therefore, a rechargeable Puck might be the best implementation for clients in several scenario. It is fine so far as I kept the features in development. I'm looking forward to the nRF52840-based device!

  Cheers

• Will rechargeable puck.js be available in the future?

  in Puck.js, Pixl.js and MDBT42 • 4 years, 1 month

  

  Hi Espruino Team,

  I'm working on the development based on Puck.js v2.
  And I'm pretty satisfied with the hardware spec and development environment.
  However, many of my clients are asking for the rechargeable feature of the device.
  So I'm curious that will the rechargeable battery spec (maybe Puck.js v3, v4, or.... ) be released in the future?
  Or if there has an existing spec relevantly similar to Puck.js v2?

  Best regards

• Question for the value of accelerometer on Puck.js

  @ofeastaien started

  • 5 comments
  • 2,098 views

  @ofeastaien replied
• Question for the value of accelerometer on Puck.js

  in Puck.js, Pixl.js and MDBT42 • 4 years, 2 months

  

  Hi Gordon,

  Thank you for your reply. I think that I will go through with the method I mentioned. And keep looking forward to your solutions. Thanks again :)

• Question for the value of accelerometer on Puck.js

  in Puck.js, Pixl.js and MDBT42 • 4 years, 2 months

  

  Hi Gordon,

  Currently, I use negative value of z component for adjusting this problem. Might the problem be fixed in the firmware for the future release?

  Best regards

• Bug while calling Puck.getBatteryPercentage() in firmware v2.07 (Puck.js v2)

  @ofeastaien started

  • 4 comments
  • 1,323 views

  @ofeastaien replied
• Bug while calling Puck.getBatteryPercentage() in firmware v2.07 (Puck.js v2)

  in Puck.js, Pixl.js and MDBT42 • 4 years, 2 months

  

  Hi Gordon,

  Always nice to hear from you. :)
  I've downloaded 2v07.33 and upgraded to my Puck. The bug has been eliminated.
  Thank you for your fix quickly.

  Best regards

• Bug while calling Puck.getBatteryPercentage() in firmware v2.07 (Puck.js v2)

  in Puck.js, Pixl.js and MDBT42 • 4 years, 2 months

  

  Hi all,

  I have experienced the bug while calling Puck.getBatteryPercentage() and NRF.getBattery() in firmware v2.07, the values were 0 and -3.6, respectively. It is OK while I downgrade to v2.06. These wrong values existed only if I send my code (for my own server and service) to RAM (using Web IDE). I've tested two Puck.js devices I have. Just report the issue for the reference. Thank you all my lovely Espruino team.

  Best regards

• Question for the value of accelerometer on Puck.js

  in Puck.js, Pixl.js and MDBT42 • 4 years, 2 months

  

  Hi All,

  According to the description on page 18/115 of the "LSM6DS3TR-C.pdf", the x, y, z axis is following the principle of right-hand rule.
  However, I just used

  Puck.accel()
  

  to get the corresponding acceleration values along the x,y,z axis to test 6 static poses of puck.js, i.e., +x, -x, +y, -y, +z, -z axis along with gravity direction. I got the coordinate system illustrated in the attached figure. This is not followed the right-hand rule. Is there something I missed?