@Kit-Bishop repo-link to all published drawings, for reference https://github.com/OnionIoT/technical-drawings

@WereCatf Thank you! This is the type of info that belongs in a central repository of some sort. If only there were a web technology built around users contributing their knowledge of specific situations for others to use.

/s

As an FYI, there are technical drawings published for the Omega1 and docs that should be helpful w/ regards to developing cases for Omega2. https://wiki.onion.io/Documentation/Hardware/Technical-Drawings/Omega-and-Expansions-Technical

@Boken-Lin are there plans to update these for Omega2? Any plans to open the wiki for us to share knowledge?

@Kit-Bishop repo-link to all published drawings, for reference https://github.com/OnionIoT/technical-drawings

@WereCatf Thank you! This is the type of info that belongs in a central repository of some sort. If only there were a web technology built around users contributing their knowledge of specific situations for others to use.

/s

@WereCatf That is hugely helpful! Does this work with the MMC interface as well? I may need to go format a USB drive as ext4 now.

@Duane-Morin try running firstboot then restart and oupgrade -f. That got me back to the initial setup where you can install the web console. It did keep all of my effed up settings Wish it was easier to wipe the entire slate clean.

As a side note, I've also started work on a Johnny-five adapter Omega-io that calls the fast-gpio, i2cget, i2cset, atty and sysfs for access to the Omega2 io. It's still very early, and completely untested at this point, but should be pretty close.

In the next version, I'd like to actually add direct bindings to the c libs, but baby-steps come first.

As an FYI, there are technical drawings published for the Omega1 and docs that should be helpful w/ regards to developing cases for Omega2. https://wiki.onion.io/Documentation/Hardware/Technical-Drawings/Omega-and-Expansions-Technical

@Boken-Lin are there plans to update these for Omega2? Any plans to open the wiki for us to share knowledge?

Hey everyone! I'm excited to get my Omega2 up and running for an IoT project I'm working on. I'd like to use Node.js as my primary runtime because JS is where I'm most comfortable.

I've got Node & NPM installed, but node modules require C/C++ code to be compiled on the target platform. I've gone ahead and installed node-gyp and gcc as dependencies of this process. What I'm running into now (with node-microtime and others) is the following:

> microtime@2.1.2 install /app/src/js/node_modules/rpi-ws2801/node_modules/microtime
> node-gyp rebuild

make: Entering directory '/app/src/js/node_modules/rpi-ws2801/node_modules/microtime/build'
  CXX(target) Release/obj.target/microtime/src/microtime.o
  SOLINK_MODULE(target) Release/obj.target/microtime.node
/usr/bin/ld: cannot find -lpthread
collect2: error: ld returned 1 exit status
make: *** [microtime.target.mk:114: Release/obj.target/microtime.node] Error 1
make: Leaving directory '/app/src/js/node_modules/rpi-ws2801/node_modules/microtime/build'

I can't seem to find ANY dev versions of libraries on opkg, but do find that I have libpthread already installed on my system. Is there a way to add dev-libs to opkg, or another way to compile these modules, on-device?

The console adapter is just an SSH client into the device. I skipped is and simply use SSH through my terminal instead.

I really enjoy working in Node.js and my typical IoT stack uses Node and Johnny-five for uniform APIs across devices.

To support that on the Omega2+ I just received, I've started work on an adapter for Johnny-five, and thought people would be interested in helping/using it.

Presently I'm using fast-gpio as an interface to the Omega2 GPIO, and have implemented digitalRead, digitalWrite, and analogWrite. There is code in the adapter for i2c, but I haven't done any work on it to adapt it to the Omega2.

The lib is presently available on NPM (omega2-io), and on github as a beta. No guarantees whether it will work or not at this point.

In the future, it might be good to build gyp-bindings directly to the C libraries rather than using the default utils, but spawning fast-gpio from node will likely work as a sufficient stopgap for many applications.