For support you can open a github issue, for discussions, designs, and clarifications, we recommend you join our Gitter Chat room. We have two related projects Browser Serialport "just like Node Serialport but for browser apps", and Serialport Test Piliot which helps us test serialport.
If you'd like to contribute please take a look at contribution guide and code of conduct. You also might want to see the road map. We also have issues tagged "good first PR" if you'd like to start somewhere specific. We'll do our best to support you until your PR is merged.
You're reading the README for the master branch of serialport. You probably want to be looking at the README of our latest release. See our change log for what's new and our upgrade guide for a walk through on what to look out for between major versions.
[email protected]
docs are here it is the latest4.x
releases.[email protected]
docs are here it is the latest3.x
releases.[email protected]
docs are here it was the last2.x
release[email protected]
docs are here it was the last1.x
release
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:
- Johnny-Five - The Johnny-Five Robotics and IoT platform's 6 line "Hello World" (awesome).
- Arduino Node Security Sensor Hacking - A great all around "how do I use this" article.
- NodeBots - The Rise of JS Robotics - A survey article of why one would want to program robots in JS and how this all started.
- Platform Support
- Installation
- Installation Special Cases
- License
- Usage
- SerialPort ⏏
new SerialPort(path, [options], [openCallback])
- instance
- static
- inner
~errorCallback
:function
~openOptions
:Object
~listCallback
:function
- Command Line Tools
serialport
supports and tests against the following platforms, architectures and node versions.
Platform / Arch | Node v0.10.x | Node v0.12.x | Node v4.x | Node v5.x | Node v6.x |
---|---|---|---|---|---|
Linux / ia32 | ☑ | ☑ | ☑ | ☑ | ☑ |
Linux / x64 | ☑ | ☑ | ☑ | ☑ | ☑ |
Linux / ARM v6¹ | ☐ | ☐ | ☐ | ☐ | ☐ |
Linux / ARM v7¹ | ☐ | ☐ | ☐ | ☐ | ☐ |
Linux / ARM v8¹ | ☐ | ☐ | ☐ | ☐ | ☐ |
Linux / MIPSel¹ | ☐ | ☐ | ☐ | ☐ | ☐ |
Linux / PPC64¹ | ☐ | ☐ | ☐ | ☐ | ☐ |
Windows² / x86 | ☑ | ☑ | ☑ | ☑ | ☑ |
Windows² / x64 | ☑ | ☑ | ☑ | ☑ | ☑ |
OSX³ / x64 | ☑ | ☑ | ☑ | ☑ | ☑ |
¹ ARM, MIPSel and PPC64¹ platforms are known to work but are not currently part of our test or build matrix. #846 ARM v4 and v5 was dropped from NodeJS after Node v0.10.
² Windows 7, 8, 10, and 10 IoT are supported but only Windows Server 2012 R2 is tested by our CI.
³ OSX 10.4 Tiger and above are supported but only 10.9.5 Mavericks with Xcode 6.1 is tested in our CI.
For most "standard" use cases (node v4.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.
- Windows 7, Windows 8.1, and Windows 10 are supported.
- Might just download and install with no extra steps. If the downloaded binary fails you'll have to build it with the following steps.
- Install Visual Studio Express 2013 for Windows Desktop.
- If you are hacking on an Arduino, be sure to install the drivers.
- Install node.js matching the bitness (32 or 64) of your operating system.
- Install Python 2.7.6 matching the bitness of your operating system. For any questions, please refer to their FAQ. Default settings are perfect.
- Open the 'Visual Studio Command Prompt' and add Python to the path.
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. To compile node-serialport
with Node.js 4.x+, you will need to use g++ v4.8 or higher.
The best way to install any version of NodeJS is to use the NodeSource Node.js Binary Distributions. Older versions of Ubuntu install nodejs with the wrong version and binary name. If you node binary is nodejs
not node
or if your node version is v0.10.29
then you should follow these instructions.
The package build-essential
is necessary to compile serialport
. If there's a binary for your platform you won't need it. Keep rocking!
# Using Ubuntu and node 6
curl -sL https://deb.nodesource.com/setup_6.x | sudo -E bash -
sudo apt-get install -y nodejs
# Using Debian and node 6, as root
curl -sL https://deb.nodesource.com/setup_6.x | bash -
apt-get install -y nodejs
Alpine is a (very) small distro, but it uses the musl standard library instead of glibc (that most other Linux distros use), so it requires compilation.
# If you don't have node/npm already, add that first
sudo apk add --no-cache nodejs
# Add the necessary build and runtime dependencies
sudo apk add --no-cache make gcc g++ python linux-headers udev
# Then we can install serialport, forcing it to compile
npm install serialport --build-from-source=serialport
Follow the instructions for setting up a Raspberry pi for use with Johnny-Five and Raspi IO. These projects use Node Serialport under the hood.
Revision | CPU | Arm Version |
---|---|---|
A, A+, B, B+ | 32-bit ARM1176JZF-S | ARMv6 |
Compute Module | 32-bit ARM1176JZF-S | ARMv6 |
Zero | 32-bit ARM1176JZF-S | ARMv6 |
B2 | 32-bit ARM Cortex-A7 | ARMv7 |
B3 | 32-bit ARM Cortex-A53 | ARMv8 |
The pre-compiled binaries assume a fully capable chip. The Galileo 2 for example lacks a few instruction sets from the ia32
architecture. A few other platforms have similar issues. So if you get Illegal Instruction
when trying to run serialport you'll need to rebuild the serialport binary by asking npm to rebuild it.
# Will ask npm to build serialport during install time
npm install serialport --build-from-source
# If you have a package that depends on serialport you can ask npm to rebuild it specifically.
npm rebuild serialport --build-from-source
# Or leave out the package name to rebuild everything.
npm rebuild --build-from-source
SerialPort is MIT licensed and all it's dependencies are MIT or BSD licensed.
Opening a serial port:
var SerialPort = require("serialport");
var port = new SerialPort("/dev/tty-usbserial1", {
baudRate: 57600
});
When opening a serial port, you can specify (in this order).
- Path to Serial Port - required.
- Options - optional and described below.
Constructing a SerialPort
object will open a port on nextTick
. You can bind events while the port is opening but you must wait until it is open to write()
to it. (Most port functions require an open port.) You can call code when a port is opened in three ways.
- The
open
event is always emitted when the port is opened - The constructor's openCallback is passed to
.open()
when theautoOpen
option hasn't been disabled, if you have disabled it the callback is ignored. - The
.open()
function takes a callback that is called after the port is opened. This can be used if you disabled theautoOpen
option or have previously closed an open port.
var SerialPort = require('serialport');
var port = new SerialPort('/dev/tty-usbserial1');
port.on('open', function() {
port.write('main screen turn on', function(err) {
if (err) {
return console.log('Error on write: ', err.message);
}
console.log('message written');
});
});
// open errors will be emitted as an error event
port.on('error', function(err) {
console.log('Error: ', err.message);
})
This could be moved to the constructor's callback.
var SerialPort = require('serialport');
var port = new SerialPort('/dev/tty-usbserial1', function (err) {
if (err) {
return console.log('Error: ', err.message);
}
port.write('main screen turn on', function(err) {
if (err) {
return console.log('Error on write: ', err.message);
}
console.log('message written');
});
});
When disabling the autoOpen
option you'll need to open the port on your own.
var SerialPort = require('serialport');
var port = new SerialPort('/dev/tty-usbserial1', { autoOpen: false });
port.open(function (err) {
if (err) {
return console.log('Error opening port: ', err.message);
}
// write errors will be emitted on the port since there is no callback to write
port.write('main screen turn on');
});
// the open event will always be emitted
port.on('open', function() {
// open logic
});
You can get updates of new data from the Serial Port as follows:
port.on('data', function (data) {
console.log('Data: ' + data);
});
You can write to the serial port by sending a string or buffer to the write method as follows:
port.write('Hi Mom!');
port.write(new Buffer('Hi Mom!'));
Enjoy and do cool things with this code.
Kind: Exported class
Emits: open
, data
, close
, error
, disconnect
Properties
Name | Type | Description |
---|---|---|
path | string |
The system path or name of the serial port. Read Only. |
isOpen | boolean |
true if the port is open, false otherwise. Read Only. |
Create a new serial port object for the path
. In the case of invalid arguments or invalid options when constructing a new SerialPort it will throw an error. The port will open automatically by default which is the equivalent of calling port.open(openCallback)
in the next tick. This can be disabled by setting the option autoOpen
to false.
Throws:
TypeError
When given invalid arguments a TypeError will be thrown.
Param | Type | Description |
---|---|---|
path | string |
The system path of the serial port to open. For example, /dev/tty.XXX on Mac/Linux or COM1 on Windows. |
[options] | openOptions |
Port configuration options |
[openCallback] | errorCallback |
Called when a connection has been opened. If this is not provided and an error occurs, it will be emitted on the ports error event. The callback will NOT be called if autoOpen is set to false in the openOptions as the open will not be performed. |
Opens a connection to the given serial port.
Kind: instance method of SerialPort
Emits: open
Param | Type | Description |
---|---|---|
[callback] | errorCallback |
Called when a connection has been opened. If this is not provided and an error occurs, it will be emitted on the ports error event. |
Changes the baud rate for an open port. Throws if you provide a bad argument. Emits an error or calls the callback if the baud rate isn't supported.
Kind: instance method of SerialPort
Param | Type | Description |
---|---|---|
[options] | object |
Only baudRate is currently supported |
[options.baudRate] | number |
The baud rate of the port to be opened. This should match one of commonly available baud rates, such as 110, 300, 1200, 2400, 4800, 9600, 14400, 19200, 38400, 57600, 115200. There is no guarantee, that the device connected to the serial port will support the requested baud rate, even if the port itself supports that baud rate. |
[callback] | errorCallback |
Called once the port's baud rate has been changed. If .update is called without an callback and there is an error, an error event will be emitted. |
Some devices like the Arduino reset when you open a connection to them. In these cases if you immediately write to the device they wont be ready to receive the data. This is often worked around by having the Arduino send a "ready" byte that your node program waits for before writing. You can also often get away with waiting around 400ms.
Kind: instance method of SerialPort
Param | Type | Description |
---|---|---|
data | string | array | buffer |
Accepts a Buffer object, or a type that is accepted by the Buffer constructor (ex. an array of bytes or a string). |
[callback] | errorCallback |
Called once the write operation returns. |
Pauses an open connection (unix only)
Kind: instance method of SerialPort
Resumes a paused connection (unix only)
Kind: instance method of SerialPort
Closes an open connection
Kind: instance method of SerialPort
Emits: close
Param | Type | Description |
---|---|---|
callback | errorCallback |
Called once a connection is closed. |
Sets flags on an open port. Uses SetCommMask
for windows and ioctl
for mac and linux.
Kind: instance method of SerialPort
Param | Type | Default | Description |
---|---|---|---|
[options] | object |
All options are operating system default when the port is opened. Every flag is set on each call to the provided or default values. If options isn't provided default options will be used. | |
[options.brk] | Boolean |
false |
|
[options.cts] | Boolean |
false |
|
[options.dsr] | Boolean |
false |
|
[options.dtr] | Boolean |
true |
|
[options.rts] | Boolean |
true |
|
[callback] | errorCallback |
Called once the port's flags have been set. |
Flush discards data received but not read and written but not transmitted. For more technical details see tcflush(fd, TCIFLUSH)
for Mac/Linux and FlushFileBuffers
for Windows.
Kind: instance method of SerialPort
Param | Type | Description |
---|---|---|
[callback] | errorCallback |
Called once the flush operation finishes. |
Waits until all output data has been transmitted to the serial port. See tcdrain()
or FlushFileBuffers() for more information.
Kind: instance method of SerialPort
Param | Type | Description |
---|---|---|
[callback] | errorCallback |
Called once the drain operation returns. |
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);
});
}
The data
event's callback is called with data depending on your chosen parser. The default raw
parser will have a Buffer
object with a varying amount of data in it. The readLine
parser will provide a string of a received ASCII line. See the parsers section for more information.
Kind: event emitted by SerialPort
The error
event's callback is called with an error object whenever there is an error.
Kind: event emitted by SerialPort
The open
event's callback is called with no arguments when the port is opened and ready for writing. This happens if you have the constructor open immediately (which opens in the next tick) or if you open the port manually with open()
. See Useage/Opening a Port for more information.
Kind: event emitted by SerialPort
The disconnect
event's callback is called with an error object. This will always happen before a close
event if a disconnection is detected.
Kind: event emitted by SerialPort
The close
event's callback is called with no arguments when the port is closed. In the event of an error, an error event will be triggered
Kind: event emitted by SerialPort
Parsers will process incoming data in a variety of ways and are meant to be passed to a port during construction.
Kind: static property of SerialPort
Properties
Name | Type | Description |
---|---|---|
raw | function |
emits a raw buffer as a data event as it's received. This is the default parser. |
readline | function |
returns a function that emits a string as a data event after a newline delimiter is received. |
byteLength | function |
returns a function that emits a data event as a buffer after a specific number of bytes are received. |
byteDelimiter | function |
returns a function that emits a data event each time a byte sequence (an array of bytes) is received. |
Example
To use the readline parser, you must provide a delimiter as such:
var SerialPort = require('serialport');
var port = new SerialPort('/dev/tty-usbserial1', {
parser: SerialPort.parsers.readline('\n')
});
To use the raw parser don't specify any parser, however if you really want to you can:
var SerialPort = require('serialport');
var port = new SerialPort('/dev/tty-usbserial1', {
parser: SerialPort.parsers.raw
});
Note that the raw parser does not guarantee that all data it receives will come in a single event.
To use the byte sequence parser, you must provide a delimiter as an array of bytes:
var SerialPort = require('serialport');
var port = new SerialPort('/dev/tty-usbserial1', {
parser: SerialPort.parsers.byteDelimiter([10,13])
});
To use the byte length parser, you must provide a delimiter as a length in bytes:
var SerialPort = require('serialport');
var port = new SerialPort('/dev/tty-usbserial1', {
parser: SerialPort.parsers.byteLength(5)
});
Retrieves a list of available serial ports with metadata. Only the comName
is guaranteed, all the other fields will be undefined if they are unavailable. The comName
is either the path or an identifier (eg COM1
) used to open the serialport.
Kind: static property of SerialPort
Param | Type |
---|---|
callback | listCallback |
Example
// example port information
{
comName: '/dev/cu.usbmodem1421',
manufacturer: 'Arduino (www.arduino.cc)',
serialNumber: '757533138333964011C1',
pnpId: undefined,
locationId: '0x14200000',
vendorId: '0x2341',
productId: '0x0043'
}
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);
});
});
A callback called with an error or null.
Kind: inner typedef of SerialPort
Param | Type |
---|---|
error | error |
Kind: inner typedef of SerialPort
Properties
Name | Type | Default | Description |
---|---|---|---|
autoOpen | boolean |
true |
Automatically opens the port on nextTick |
lock | boolean |
true |
Prevent other processes from opening the port. false is not currently supported on windows. |
baudRate | number |
9600 |
The baud rate of the port to be opened. This should match one of commonly available baud rates, such as 110, 300, 1200, 2400, 4800, 9600, 14400, 19200, 38400, 57600, 115200. There is no guarantee, that the device connected to the serial port will support the requested baud rate, even if the port itself supports that baud rate. |
dataBits | number |
8 |
Must be one of: 8, 7, 6, or 5. |
stopBits | number |
1 |
Must be one of: 1 or 2. |
parity | string |
"none" |
Must be one of: 'none', 'even', 'mark', 'odd', 'space' |
rtscts | boolean |
false |
flow control setting |
xon | boolean |
false |
flow control setting |
xoff | boolean |
false |
flow control setting |
xany | boolean |
false |
flow control setting |
bufferSize | number |
65536 |
Size of read buffer |
parser | function |
Parsers.raw |
The parser to transform read data, defaults to the raw parser that emits data as it's received. |
platformOptions | object |
sets platform specific options | |
platformOptions.vmin | number |
1 |
see man termios |
platformOptions.vtime | number |
0 |
see man termios |
This callback type is called requestCallback
and is displayed as a global symbol.
Kind: inner typedef of SerialPort
Param | Type | Description |
---|---|---|
error | error |
|
ports | array |
an array of objects with port info. |
If you install serialport
globally. (eg, npm install -g serialport
) you'll receive two command line tools.
serialport-list
will list all available serial ports in different formats.
$ serialport-list -h
Usage: serialport-list [options]
List available serial ports
Options:
-h, --help output usage information
-V, --version output the version number
-f, --format <type> Format the output as text, json, or jsonline. default: text
$ serialport-list
/dev/cu.Bluetooth-Incoming-Port
/dev/cu.usbmodem1421 Arduino (www.arduino.cc)
$ serialport-list -f json
[{"comName":"/dev/cu.Bluetooth-Incoming-Port"},{"comName":"/dev/cu.usbmodem1421","manufacturer":"Arduino (www.arduino.cc)","serialNumber":"752303138333518011C1","locationId":"0x14200000","vendorId":"0x2341","productId":"0x0043"}]
$ serialport-list -f jsonline
{"comName":"/dev/cu.Bluetooth-Incoming-Port"}
{"comName":"/dev/cu.usbmodem1421","manufacturer":"Arduino (www.arduino.cc)","serialNumber":"752303138333518011C1","locationId":"0x14200000","vendorId":"0x2341","productId":"0x0043"}
serialport-term provides a basic terminal interface for communicating over a serial port.
ctrl+c` will exit.
$ serialport-term -h
Usage: serialport-term -p <port> [options]
A basic terminal interface for communicating over a serial port. Pressing ctrl+c exits.
Options:
-h, --help output usage information
-V, --version output the version number
-l --list List available ports then exit
-p, --port, --portname <port> Path or Name of serial port
-b, --baud <baudrate> Baud rate default: 9600
--databits <databits> Data bits default: 8
--parity <parity> Parity default: none
--stopbits <bits> Stop bits default: 1
--echo --localecho Print characters as you type them.
$ serialport-term -l
/dev/cu.Bluetooth-Incoming-Port
/dev/cu.usbmodem1421 Arduino (www.arduino.cc)