Recently, Federico Fissore added node.js to the package repository for the Arduino Y\u00fan. Here’s how you get node to communicate with the Arduino processor on the Y\u00fan via the Bridge library.<\/p>\n
To do this, you’ll need an Arduino Y\u00fan, a microSD card, a microUSB cable and a wifi connection. You should be familiar with the basics of the Arduino Y\u00fan and node.js in order to get the most out of this post.<\/p>\n
All of the code for this post can be found on my GitHub repository<\/a>.<\/p>\n <\/p>\n First you’ll need to install node on the Y\u00fan<\/a>. Make sure you’ve upgraded to the current Y\u00fan software image<\/a> and have connected to the internet via wifi. Then ssh into your Y\u00fan, or connect to the command line interface using the the YunSerialTerminal sketch. <\/p>\n You may want to expand the disk space on your Y\u00fan first, to make enough space for node and other tools. This means you’ll be moving most of the linux filesystem over to an SD card rather than using the built-in flash memory. If you try to install node.js and the install fails, lack of disk space could be one reason it woudl happen. There’s a tutorial on how to expand the disk space<\/a> on the Arduino site. <\/p>\n To install node.js and issue the following commands:<\/p>\n That’s it. Now you have node.js onboard. You can check that it’s okay by checking the version:<\/p>\n You should get the version number in reply.<\/p>\n Once you’ve got that working, you’ll undoubtedly want to communicate with the Y\u00fan’s Arduino processor from node. You can do this using the Bridge library. On a microSD drive, make a directory for your node scripts. I called mine Note:<\/strong> The Y\u00fan automatically treats the microSD card’s Once you know node’s working, try running a simple server on it. Create the following file in the To run this, make sure you’re in the \/arduino\/node directory and type the following on the command line:<\/p>\n Then in the browser, go to your Y\u00fan’s IP address, port 8080. For my machine on my network, it’s 192.168.1.110:8080. You’ll get a hello web page that tells you your client address, and you’ll see the same info on the command line of the Y\u00fan. Congratulations, you’ve got your first node script working on the Y\u00fan!<\/p>\n You may find it tedious to edit text on the Y\u00fan, and equally tedious to continually remove your SD card to save files. You can use scp to transfer files as well. To do this, change directories on your local machine to\u00a0your project directory, then to transfer the server.js file to the You’ll be prompted for your Y\u00fan’s password and the file will automatically overwrite whatever’s there.<\/p>\n Starting a node script from the Arduino processor using Bridge is easy. You use the Bridge library’s Process class and call the node script using You can use this BridgeToNode sketch, and replace When you run this, it will launch server.js once you open the Serial Monitor (the line The Now that you have a server running and communicating with the Arduino processor it’s time to get the Arduino processor communicating back to node. Create the following node script in the node directory on your Y\u00fan:<\/p>\n This node script uses the readline module<\/a> to exchange data with the stdin and stdout. When the Bridge library calls this script, anything you print to console.log will get sent to Bridge, and anything that you send from the Arduino via Bridge with a newline at the end (for example, if you used Run the NodeToSerial sketch above again, this time replacing server.js with echo.js again. The Arduino will launch echo.js. This script starts by saying hello, then echoes back to you anything you send it. It doesn’t do much by itself, but it shows you how to effect two-way communication between node and the Arduino processor. <\/p>\n Being able to communicate between a node script and the Arduino processor has lots of uses. You can write scripts in node to make http calls and filter the results for you, or write node servers as an alternative to the Y\u00fan’s built in REST server. With control of the programming on both the Arduino and the Linux processors, you can decide how you want to structure the communication between them, to take best advantage of both.<\/p>\n All of the code for this post can be found on my GitHub repository<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" Recently, Federico Fissore added node.js to the package repository for the Arduino Y\u00fan. Here’s how you get node to communicate with the Arduino processor on the Y\u00fan via the Bridge library. To do this, you’ll need an Arduino Y\u00fan, a microSD card, a microUSB cable and a wifi connection. You should be familiar with the … <\/p>\n
\n$ opkg update
\n$ opkg install node
\n<\/code><\/p>\n$ node -v<\/code><\/p>\n\/arduino\/node<\/code>. Then insert it into your Y\u00fan. For reference, its path from the command line is \/mnt\/sda1\/arduino\/node<\/code>. <\/p>\n\/arduino\/www\/<\/code> directory as a public web directory. Anything you put in there will be served out as static HTML. So you may not want to put your node scripts in this directory, so they’re not visible via the browser. That’s why I created a node directory at the same level as the www directory, but outside it.<\/p>\nRunning a Simple Server<\/h3>\n
\/arduino\/node\/<\/code> directory, called server.js<\/code>:<\/p>\n\r\n\r\n[github_cv url='https:\/\/github.com\/tigoe\/NetworkExamples\/blob\/master\/BridgeToNode\/server.js']\r\n\r\n<\/pre>\n
$ node server.js<\/code><\/p>\nFile Transfer to the Y\u00fan<\/h3>\n
\/arduino\/node<\/code> directory on the Y\u00fan, type the following:<\/p>\nscp server.js root@yournode.local:\/mnt\/sda1\/arduino\/node\/.<\/code><\/p>\nCommunicating from Bridge to Node<\/h3>\n
Process.runShellCommandAsynchronously()<\/code>. Anything that node sends via console.log will be sent to your Arduino sketch, and you can read it using Process.read(). Here’s how you’d launch the server.js script:<\/p>\n
\nProcess nodejs;
\nnodejs.runShellCommandAsynchronously(\"node \/mnt\/sda1\/arduino\/node\/server.js\");
\n<\/code><\/p>\necho.js<\/code> with server.js<\/code><\/p>\n\r\n\r\n[github_cv url='https:\/\/github.com\/tigoe\/NetworkExamples\/blob\/master\/BridgeToNode\/NodeToSerial\/NodeToSerial.ino']\r\n\r\n<\/pre>\n
while (!Serial);<\/code> stops the sketch until you do so), and if you go to the server in a browser as you did above, you’ll see the console.log results in the Serial monitor. Node is now talking to the Arduino processor. <\/p>\nProcess.runShellCommandAsynchronously()<\/code> is important in the sketch above. It tells Arduino to launch the sketch but not to wait for a result. This way, node can do its business and the Arduino sketch can do its business, and they’re not waiting for each other.<\/p>\nCommunicating from Node to Bridge<\/h3>\n
\r\n\r\n[github_cv url='https:\/\/github.com\/tigoe\/NetworkExamples\/blob\/master\/BridgeToNode\/echo.js']\r\n\r\n<\/pre>\n
println()<\/code>) will appear as data in the linereader.on()<\/code> function. Save this sketch to your node directory on your Y\u00fan.<\/p>\nConclusion<\/h3>\n