noahneibaron

Most recent activity

• Controlling Access to Serial Service on NRF

  @noahneibaron started

  • 5 comments
  • 1,572 views

  @noahneibaron replied
• Controlling Access to Serial Service on NRF

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

  

  Thanks, this is great!

• Controlling Access to Serial Service on NRF

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

  

  @fanoush thanks for the link. Lots of good options there, somehow missed that in the documentation. Will probably go with the changing the connectable option to false after a minute of pressing a button or powering up.

• Controlling Access to Serial Service on NRF

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

  

  I'd like to secure the serial service so that it's only available to connect to within a minute or so of powering on Espruino. The idea is to secure the javascript if someone doesn't have access to power cycling the device or pressing a physical button. Is it possible to disable this service or possibly change the device to non-connectable after a minute of powering on?

• Interval Stopping Unexpectedly After Running for Some Time (using MDBT42Q breakout, fw 2v01)

  @noahneibaron started

  • 8 comments
  • 3,113 views

  @Gordon replied
• Interval Stopping Unexpectedly After Running for Some Time (using MDBT42Q breakout, fw 2v01)

  in Puck.js, Pixl.js and MDBT42 • 5 years, 7 months

  

  Thanks for the tip. I ran some experiments with different intervals and I did see the memory usage increase from 219 to 254 when reducing the interval from 2000ms to 200ms and vice-versa saw the memory use decrease when increasing the interval, so I think this is a helpful tool to determine what the fastest interval can be.

• Interval Stopping Unexpectedly After Running for Some Time (using MDBT42Q breakout, fw 2v01)

  in Puck.js, Pixl.js and MDBT42 • 5 years, 7 months

  

  Update: I ran a similar script on a pixljs and could see the error when in a state running a high-frequency interval. I'm guessing the interval is too frequent causing a backlog of operations and resulting in a low memory error. I will try increasing the interval period and re-running the test.

• Interval Stopping Unexpectedly After Running for Some Time (using MDBT42Q breakout, fw 2v01)

  in Puck.js, Pixl.js and MDBT42 • 5 years, 7 months

  

  Thank you both for the reply. I read your other conversation regarding clearWatch() and agree with the suggestions. I'll also try @Gordon error logging suggestion using both 2v01 and 2v03 firmware versions. Will post back if I discover anything.

• Interval Stopping Unexpectedly After Running for Some Time (using MDBT42Q breakout, fw 2v01)

  in Puck.js, Pixl.js and MDBT42 • 5 years, 7 months

  

  After running for some time (a few weeks or so) the interval set with setInterval() and modified periodically with changeInterval() will unexpectedly stop. Interval periods are set between 1000ms and 100ms. When I connect to the device I try to use changeInterval() on the console and get "Uncaught Error: Unknown Interval" so it appears the interval is gone, as if clearInterval() was called. I checked to see if that could be the case and am not seeing anything. Is there a reason why the an interval would stop except calling clearInterval()? Is there a max time an interval can run?

• Button used 150 uA of Power using setWatch()

  @noahneibaron started

  • 4 comments
  • 2,061 views

  @Gordon replied