Security News
GitHub Removes Malicious Pull Requests Targeting Open Source Repositories
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
serialport
Advanced tools
For all discussions, designs, and clarifications, we recommend you join our Gitter Chat room: https://gitter.im/voodootikigod/node-serialport
Imagine a world where you can write JavaScript to control blenders, lights, security systems, or even robots. Yes, I said robots. That world is here and now with node-serialport. It provides a very simple interface to the low level serial port code necessary to program Arduino chipsets, X10 wireless communications, or even the rising Z-Wave and Zigbee standards. The physical world is your oyster with this goodie. For a full break down of why we made this, please read NodeBots - The Rise of JS Robotics.
For getting started with node-serialport, we recommend you begin with the following articles:
For most "standard" use cases (node v0.10.x on mac, linux, windows on a x86 or x64 processor), node-serialport will install nice and easy with a simple
npm install serialport
We are using node-pre-gyp to compile and post binaries of the library for most common use cases (linux, mac, windows on standard processor platforms). If you are on a special case, node-serialport will work, but it will compile the binary when you install.
This assumes you have everything on your system necessary to compile ANY native module for Node.js. This may not be the case, though, so please ensure the following are true for your system before filing an issue about "Does not install". For all operatings systems, please ensure you have Python 2.x installed AND not 3.0, node-gyp (what we use to compile) requires Python 2.x.
Ensure that you have at a minimum the xCode Command Line Tools installed appropriate for your system configuration. If you recently upgraded the OS, it probably removed your installation of Command Line Tools, please verify before submitting a ticket.
You know what you need for you system, basically your appropriate analog of build-essential. Keep rocking! Ubuntu renamed the node
binary nodejs
which can cause problems building node-serialport
. The fix is simple, install the nodejs-legacy package that symlinks /usr/bin/nodejs => /usr/bin/node
or install the more up to date nodejs package from Chris Lea's PPA.
# Ubuntu node
sudo apt-get install nodejs nodejs-legacy
# Or Chris Lea's PPA Node (more up to date)
sudo add-apt-repository ppa:chris-lea/node.js
sudo apt-get update
sudo apt-get install nodejs
sudo apt-get install build-essential
npm install serialport
sudo apt-get update
sudo apt-get upgrade -y
wget https://node-arm.herokuapp.com/node_archive_armhf.deb
sudo dpkg -i node_archive_armhf.deb
More information can be found at node-arm.
npm install serialport
Opening a serial port:
var SerialPort = require("serialport").SerialPort
var serialPort = new SerialPort("/dev/tty-usbserial1", {
baudrate: 57600
});
When opening a serial port, you can specify (in this order).
You MUST wait for the open event to be emitted before reading/writing to the serial port. The open happens asynchronously so installing 'data' listeners and writing before the open event might result in... nothing at all.
Assuming you are connected to a serial console, you would for example:
serialPort.on("open", function () {
console.log('open');
serialPort.on('data', function(data) {
console.log('data received: ' + data);
});
serialPort.write("ls\n", function(err, results) {
console.log('err ' + err);
console.log('results ' + results);
});
});
You can also call the open function, in this case instantiate the serialport with an additional flag.
var SerialPort = require("serialport").SerialPort
var serialPort = new SerialPort("/dev/tty-usbserial1", {
baudrate: 57600
}, false); // this is the openImmediately flag [default is true]
serialPort.open(function (error) {
if ( error ) {
console.log('failed to open: '+error);
} else {
console.log('open');
serialPort.on('data', function(data) {
console.log('data received: ' + data);
});
serialPort.write("ls\n", function(err, results) {
console.log('err ' + err);
console.log('results ' + results);
});
}
});
You can also list the ports along with some metadata as well.
var serialPort = require("serialport");
serialPort.list(function (err, ports) {
ports.forEach(function(port) {
console.log(port.comName);
console.log(port.pnpId);
console.log(port.manufacturer);
});
});
Out of the box, node-serialport provides two parsers one that simply emits the raw buffer as a data event and the other which provides familiar "readline" style parsing. To use the readline parser, you must provide a delimiter as such:
var serialport = require("serialport");
var SerialPort = serialport.SerialPort; // localize object constructor
var sp = new SerialPort("/dev/tty-usbserial1", {
parser: serialport.parsers.readline("\n")
});
To use the raw parser, you just provide the function definition (or leave undefined):
var serialport = require("serialport");
var SerialPort = serialport.SerialPort; // localize object constructor
var sp = new SerialPort("/dev/tty-usbserial1", {
parser: serialport.parsers.raw
});
You can get updates of new data from the Serial Port as follows:
serialPort.on("data", function (data) {
sys.puts("here: "+data);
});
You can write to the serial port by sending a string or buffer to the write method as follows:
serialPort.write("OMG IT WORKS\r");
Enjoy and do cool things with this code.
Create a new serial port on path
.
path
The system path of the serial port to open. For example, /dev/tty
on Mac/Linux or COM1
on Windows.
options (optional)
Port configuration options.
baudRate
Baud Rate, defaults to 9600. Should be one of: 115200, 57600, 38400, 19200, 9600, 4800, 2400, 1800, 1200, 600, 300, 200, 150, 134, 110, 75, or 50. Custom rates as allowed by hardware is supported.dataBits
Data Bits, defaults to 8. Must be one of: 8, 7, 6, or 5.stopBits
Stop Bits, defaults to 1. Must be one of: 1 or 2.parity
Parity, defaults to 'none'. Must be one of: 'none', 'even', 'mark', 'odd', 'space'rtscts
xon
xoff
xany
flowControl
bufferSize
Size of read buffer, defaults to 255. Must be an integer value.parser
The parser engine to use with read data, defaults to rawPacket strategy which just emits the raw buffer as a "data" event. Can be any function that accepts EventEmitter as first parameter and the raw buffer as the second parameter.encoding
dataCallback
disconnectedCallback
platformOptions
- sets platform specific options, see below.Note, we have added support for either all lowercase OR camelcase of the options (thanks @jagautier), use whichever style you prefer.
An object with the following properties:
vmin
(default: 1) - see man termios
vtime
(default: 0) - see man termios
openImmediately (optional)
Attempts to open a connection to the serial port on process.nextTick
. The default is true
. Set to false
to manually call open()
at a later time, but note you'll need to use factory error listener in the case of constructor errors.
callback (optional)
Called when a connection has been opened. The callback should be a function that looks like: function (error) { ... }
Opens a connection to the given serial port.
callback (optional)
Called when a connection has been opened. NOTE: Will NOT be called if openImmediately is set to false as open will not be performed. The callback should be a function that looks like: function (error) { ... }
Returns true
if the port is open.
Writes data to the given serial port.
buffer
The buffer
parameter accepts a Buffer
object, or a type that is accepted by the Buffer
constructor (ex. an array of bytes or a string).
callback (optional)
Called once the write operation returns. The callback should be a function that looks like: function (error) { ... }
Note: The write operation is non-blocking. When it returns, data may still have not actually been written to the serial port. See drain()
.
Pauses an open connection.
Resumes a paused connection.
Flushes data received but not read. See tcflush()
for Mac/Linux and FlushFileBuffers
for Windows.
callback (optional)
Called once the flush operation returns. The callback should be a function that looks like: function (error) { ... }
Waits until all output data has been transmitted to the serial port. See tcdrain()
for more information.
callback (optional)
Called once the drain operation returns. The callback should be a function that looks like: function (error) { ... }
Example
Writes data
and waits until it has finish transmitting to the target serial port before calling the callback.
function writeAndDrain (data, callback) {
sp.write(data, function () {
sp.drain(callback);
});
}
Closes an open connection.
callback (optional)
Called once a connection is closed. Closing a connection will also remove all event listeners. The callback should be a function that looks like: function (error) { ... }
@serialport/bindings@2.0.4 (2018-12-19)
FAQs
Node.js package to access serial ports. Linux, OSX and Windows. Welcome your robotic JavaScript overlords. Better yet, program them!
The npm package serialport receives a total of 0 weekly downloads. As such, serialport popularity was classified as not popular.
We found that serialport demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Security News
Node.js will be enforcing stricter semver-major PR policies a month before major releases to enhance stability and ensure reliable release candidates.