Does node.js not include packages in opkg yet?

[Theodore Borromeo]

Also, as per https://github.com/paul99/v8m-rb/pull/19#issuecomment-24131056 , you can tune node via libv8 parameters via command line, which may help getting this tuned.

[Dan L.]

Hey @Theodore-Borromeo

setTimeout(helper.setPinSync(0,true), 500); will set the pin immediately. The first argument of setTimeout should be a function, but you're actually just passing in the return value of setPinSync (which is undefined). You probably meant to do this:

setTimeout(function() {
    helper.setPinSync(0, true);
}, 500);

BUT, doing that will still just delay that call by 0.5s. If you do that a bunch of times in an infinite while loop, you're actually just queueing an infinite amount of timers to run, but since the loop never ends, the timers never get a chance to run. An infinite while/for loop will halt all timers, due to the way V8's event loop works.

Instead you probably want to use setInterval, not in a loop:

var lightState = false;
setInterval(function() {
	
	// Toggle
	lightState = !lightState;
	
	// Set value
	helper.setPinSync(0, lightState);
	
}, 500);

Or you could recursively call setTimeout. This one will toggle the light on/off at random intervals:

var lightState = false;

// Function which is triggered every 0+ to 1 seconds
var next = function() {
	
	lightState = !lightState;
	
	helper.setPinSync(0, lightState);
	
	setTimeout(next, Math.random() * 1000);
	
}

next();

I also put some samples on GitHub

https://github.com/manspaniel/node-omega-gpio

[Theodore Borromeo]

@Dan-L. Yeah, as soon as I posted the do-while loop that will continuously call a function some half a second into the future, I realized that I wasn't going to get far. In any case, the do while loop was a hold over from me sleeping for half a second and toggling on and off forever.

But I'll def take a look later and see your examples. Coincidentally, the newest firmware has a way to set the GPIO pins directly via the "GPIO Helper Tool" app! I hope that they reimplement their landing page as a webapp hosted by a node.js server running on device! That would be poetic

[Lazar Demin]

@Theodore-Borromeo About the Console, the front-end is implemented in HTML and Javascript, and the back-end uses the OpenWRT UBUS service, which is language independent.

Don't worry, we plan to release a detailed guide on how to implement your own apps and how to extend the UBUS service! No definite timeline for this guide but it's definitely on our list of priorities.

[Theodore Borromeo]

@Boken-Lin @Lazar-Demin
from borromeotlhs/onion-omega:v1

is now available for use in a Dockerfile. it'll contain the entirety of the toolchain per your cross compile environment setup guide.

Regards,
TJ

[Boken Lin]

@Theodore-Borromeo This is fantastic! We'll put it up on our website so that everyone can use it to compile their firmwares

[Theodore Borromeo]

@Boken-Lin That's fine, but I still haven't compiled a thing with it!! Can anyone test it to compile some drivers and stuff?

[Boken Lin]

@Theodore-Borromeo I will test it out when we are doing our own compilation stuff. BTW, would you be able to write a simple tutorial in markdown showing the steps to get the image up and running on Docker? I think it can be a really useful thing to have on our wiki!

[Theodore Borromeo]

@Boken-Lin Assuming you know how to use docker, there are only a few ways to run it:

1.) Pull the image from docker hub and run an interactive console. e.g.:
docker pull borromeotlhs/onion-omega:v1
docker run -it 'borromeotlhs/onion-omega:v1' /bin/bash

2.) Pull the image from docker hub, reference it in your own Dockerfile 'FROM' line, run resultant image built from that Dockerfile. e.g.:
docker pull borromeotlhs/onion-omega:v1

<Dockerfile>
MAINTAINER joeschmoe@schmoenet.com
FROM borromeotlhs/onion-omega:v1

RUN . . .
</Dockerfile>

docker build -t 'my-new-image' .
docker run -it 'my-new-image' /bin/bash

There But yeah, let me know what repo you want me to write this out in Markdown, and I'll try to get to it.

PS
My vote for a package you all could try: https://github.com/OnionIoT/OpenWRT-Packages/tree/master/iojs

[Chris Ward]

@Theodore-Borromeo Is this your published docker image - https://hub.docker.com/r/borromeotlhs/onion-omega/ Is it best to start with this then?

[Christopher Hiller]

Has anyone had success building the iojs 2.x package?

[Chris Ward]

@Theodore-Borromeo I got your docker container running. Is it supposed to have node compiled, or do I still need to follow that process. As soon as I got the bash prompt I tried to get the node version, but node is not found.

➜  ~  docker run -it 'borromeotlhs/onion-omega:v1' /bin/bash
onion@2af6d87347d6:/openwrt$ ls
BSDmakefile  LICENSE   README          config  feeds       feeds.conf.default  package   scripts      target toolchain
Config.in    Makefile  appendtoconfig  docs    feeds.conf  include             rules.mk  staging_dir  tmp     tools
onion@2af6d87347d6:/openwrt$ node --version
bash: node: command not found

[Theodore Borromeo]

@Chris-Ward I compiled node from a completely different process than Onion's buildroot. It is also available at:
borromeotlhs/docker-onion-omega-nodejs

This image will contain the precompiled node and v8 binaries in them, I think in a folder called 'node_deploy'. That image will, I assume, have a working toolchain in it, though not entirely sure it was specifically suited to the onions hardware (tho node and v8 seem to work).

good luck!

[Boken Lin]

@Theodore-Borromeo Great job Theodore!

[Theodore Borromeo]

@Chris-Ward https://hub.docker.com/r/borromeotlhs/docker-onion-omega-nodejs/

[Chris Ward]

@Theodore-Borromeo When I pull, I get a latest not found. Did you push this?

[Theodore Borromeo]

@Chris-Ward Uggh. I didn't push it, you're right. Please copy the Dockerfile at: https://hub.docker.com/r/borromeotlhs/docker-onion-omega-nodejs/~/dockerfile/

into:
mydockerfile

and then run:
cd mydockerfile/
docker build -t '<yourusername>/docker-onion-omega-nodejs' .

until I get this uploaded after I build on my ancient personal machine

[Theodore Borromeo]

@Chris-Ward Turns out that I can't push a tag to an Automated Build, and as the build failed, I had to delete and recreate this repo.

Pushing now. . . Failed

Please try building as per above, and let me know. I'll have to rerun the build at home and push from there

[Chris Ward]

@Theodore-Borromeo looks like the actual dockerfile (recipe) is gone now from docker hub. Do you want to email it to me? veggie2u at cyberward.net

[Theodore Borromeo]

@Chris-Ward ugh. I'm an idiot

Here is the github repo the automated build was supposed to work from:
https://github.com/borromeotlhs/docker-onion-omega-nodejs/blob/master/Dockerfile

HTH,
TJ