One of the arguments made in favor of Node.js is using the same language on the server and client, reducing the number of platforms to maintain and encouraging code reuse. The OpenROV project takes this a step further and uses Javascript to control the hardware of a miniature submersible. Javascript powers the server that runs the robot and routes data, the web UI for controlling the robot, and communicates with the Arduino hardware to physically move the sub and read the sensors.
The project does not use any bleeding edge or exotic, just node.js, serialport, and socket.io, but it combines hardware and software in an exciting way.
One of the arguments made in favor of Node.js is using the same language on the server and client, reducing the number of platforms to maintain and encouraging code reuse. The OpenROV project takes this a step further and uses Javascript to control the hardware of a miniature submersible. Javascript powers the server that runs the robot and routes data, the web UI for controlling the robot, and communicates with the Arduino hardware to physically move the sub and read the sensors.
The project does not use any bleeding edge or exotic, just node.js, serialport, and socket.io, but it combines hardware and software in an exciting way.
I gave a less code-centric talk about the OpenROV project at JS.everywhere(2013): http://pchristensen.com/blog/articles/javascript-underwater-my-js-everywhere-talk-about-openrov/