I found if I remove all of the usrx LED entries in the blinkLED.js except usr3 and the system does not seem to become unresponsive after running the example. I did move to P8_23 gpio22 to attempt to set a PWM pin for anther example. Ex: const leds = ["USR3", "P8_23"]; //const leds = ["USR0", "USR1", "USR2", "USR3", "P9_15"];
Cheers, Jon On Thu, Oct 24, 2019 at 10:28 PM jonnymo <[email protected]> wrote: > Jason, > > I added this to my BB AI and ran the .js script from the Cloud9 IDE and it > did in fact blink an LED connected to P9.15 as well as the usrx LEDs. > > Now, I did set P9.15 as an Output pin in the am5729-beagleboneai.dts file > so I am not sure if this is necessary in this case. > > Also, from the Cloud9 IDE, the nodejs script stays active and causes the > BB AI to become very in console response. > This is what is left behind. > > *debian@beaglebone:~/developement$ ps -aef |grep .js* > *root 569 1 0 21:44 ? 00:00:01 /usr/bin/nodejs > autorun.js* > *debian 22055 1 2 22:18 ? 00:00:06 /usr/bin/nodejs server.js > --packed -w /var/lib/cloud9* > *debian 22105 22055 1 22:18 ? 00:00:03 > /opt/cloud9/.c9/node/bin/node > /opt/cloud9/build/standalonebuild/node_modules/vfs-child/child.js > {"root":"/","metapath":"/.c9/metadata","wsmetapath":"/.c9/metadata/workspace","readOnly":false,"debug":false,"homeDir":"/home/debian","projectDir":"/var/lib/cloud9","nakBin":"/opt/cloud9/build/standalonebuild/node_modules/nak/bin/nak","nodeBin":["/opt/cloud9/.c9/node/bin/node","/usr/bin/nodejs"],"tmuxBin":"/usr/bin/tmux","defaultEnv":{"CUSTOM":43},"inProcess":false}* > > > Perhaps there is a way to reset the function of the usrx LEDs after the > script runs? > > Cheers, > > Jon > > > On Thu, Oct 24, 2019 at 11:01 AM Jason Kridner <[email protected]> wrote: > >> Realized I hadn't published the work already done on putting BeagleBone >> AI GPIO pins into the node.js BoneScript library. >> >> Any testing on this version would really be appreciated. >> >> >> debian@beaglebone:/var/lib/cloud9/sensors$ *cd /usr/local/lib* >> debian@beaglebone:/usr/local/lib$ *sudo npm install --unsafe-perm >> [email protected]* >> >> npm WARN deprecated [email protected]: CoffeeScript on NPM has moved >> to "coffeescript" (no hyphen) >> npm WARN deprecated [email protected]: Please use the native JSON object >> instead of JSON 3 >> npm WARN deprecated [email protected]: Please use the native JSON object >> instead of JSON 3 >> [email protected] node_modules/winston/node_modules/colors -> >> node_modules/colors >> [email protected] node_modules/winston/node_modules/cycle -> node_modules/cycle >> [email protected] node_modules/winston/node_modules/eyes -> node_modules/eyes >> [email protected] node_modules/winston/node_modules/isstream -> >> node_modules/isstream >> [email protected] node_modules/winston/node_modules/pkginfo -> >> node_modules/pkginfo >> [email protected] node_modules/winston/node_modules/stack-trace -> >> node_modules/stack-trace >> /usr/local/lib >> └─┬ [email protected] >> └── [email protected] >> >> npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.1.2 >> (node_modules/chokidar/node_modules/fsevents): >> npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for >> [email protected]: wanted {"os":"darwin","arch":"any"} (current: >> {"os":"linux","arch":"arm"}) >> npm WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@~0.1.4 >> (node_modules/sensortag/node_modules/noble/node_modules/xpc-connection): >> npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for >> [email protected]: wanted {"os":"darwin","arch":"any"} (current: >> {"os":"linux","arch":"arm"}) >> npm WARN enoent ENOENT: no such file or directory, open >> '/usr/local/lib/package.json' >> npm WARN lib No description >> npm WARN lib No repository field. >> npm WARN lib No README data >> npm WARN lib No license field. >> debian@beaglebone:/usr/local/lib$ *node -pe >> "require('bonescript').bone.getPinObject('p9.15').ai.gpio"* >> 76 >> >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/28ae9679-ddb7-42e3-9437-aa56dacb147d%40googlegroups.com >> <https://groups.google.com/d/msgid/beagleboard/28ae9679-ddb7-42e3-9437-aa56dacb147d%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAG99bkqLwpj4ApLyhZo0NgzZYqjfQPKV6qttY_rgnUzogEzPFw%40mail.gmail.com.
