Thank you @Gordon for the clarification. That was the snippet I was using.
Puck.IR([500,500,500,500,500])
Now for the tough part. How to troubleshoot IR detection, when one is unable to see infrared output. Sorry, only born with super human strength and X-Ray vision.
Have an IR pair circuit with three inches separating the detector and emitter, as in a beam break circuit. When the beam is broken, a colored LED illuminates. This works as expected.
However, when I substitute the Puck for the emitter, [Puck visible LED side facing detector] there isn't any apparent detection.
ahhh ha!! . . . Forgot the old cell phone video mode trick. That device does make the IR LED transmission visible.
Wondering what the Puck IR emitter range is? In my circuit, I seem to need to be quite close. e.g. One inch. Are you able to point me to a spec sheet? Any experience with an expected transmission distance?
re: "I don't understand the question - do you have a link to where it says that?"
This is the link that is returned in the browser, which indicates 404
Should your link be working, I wonder if browser caching is partly a cause. I'm using Chrome Version 59.0.3071.115
or, . . . as we suspect here in the States that all web traffic is intercepted and stored in the massive Zettabyte storage site in Utah USA, https://en.wikipedia.org/wiki/Utah_Data_Center
and the returned link became corrupt from their tampering somehow.
https://www.forensicmag.com/article/2013/09/data-storage-issues
"1 Zettabyte (ZB) – is equal to 1 billion Terabytes and represents approximately 36 million years of stored HD video. Recently it was reported that the National Security Agency facility located in Utah will be able to store 5 Zettabytes of information."
'The truth is out there' . . . [fade to familiar sound byte] . . . . and . . . . . cut
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Thr 2017.08.03
Thank you @Gordon for the clarification. That was the snippet I was using.
Now for the tough part. How to troubleshoot IR detection, when one is unable to see infrared output. Sorry, only born with super human strength and X-Ray vision.
Have an IR pair circuit with three inches separating the detector and emitter, as in a beam break circuit. When the beam is broken, a colored LED illuminates. This works as expected.
However, when I substitute the Puck for the emitter, [Puck visible LED side facing detector] there isn't any apparent detection.
ahhh ha!! . . . Forgot the old cell phone video mode trick. That device does make the IR LED transmission visible.
Wondering what the Puck IR emitter range is? In my circuit, I seem to need to be quite close. e.g. One inch. Are you able to point me to a spec sheet? Any experience with an expected transmission distance?
From page: http://www.espruino.com/Puck.js#ir-infrared
Fifth line below the heading "IR / Infrared"
Re:
Should your click event 'turn on a cheap IR lightbulb is' be different, than when clicked I get:
This is the link that is returned in the browser, which indicates 404
Should your link be working, I wonder if browser caching is partly a cause. I'm using Chrome Version 59.0.3071.115
or, . . . as we suspect here in the States that all web traffic is intercepted and stored in the massive Zettabyte storage site in Utah USA, https://en.wikipedia.org/wiki/Utah_Data_Center
and the returned link became corrupt from their tampering somehow.
https://www.forensicmag.com/article/2013/09/data-storage-issues
"1 Zettabyte (ZB) – is equal to 1 billion Terabytes and represents approximately 36 million years of stored HD video. Recently it was reported that the National Security Agency facility located in Utah will be able to store 5 Zettabytes of information."
'The truth is out there' . . . [fade to familiar sound byte] . . . . and . . . . . cut