Chat about Node-Serialport and projects using node serialport for specfic problems or bugs please open a github issue.
I want to stop emmiting data from serialport
how can I do it
I'm getting errors when trying to use SerialPort. I installed it with npm i serialport
I'm getting lots of "Module not found: Error: Can't resolve 'child_process' in '...\node_modules\serialport\lib\bindings'"
same with trying to resolve 'fs'. I'm on Windows 10
I've looked at electron-rebuild... It seems like I'm on the right track, but I'm not actually seeing any options for platform (win, linux) there... just electron version and arch
@AgileDog Thx for the offer! I eventually got it working. The issue was apparently related to the socket code. Actually I didn't get to the bottom of it. But it was somehow related to my client code creating two sockets while my socket-to-serial server only expects one socket connection. When I made sure the client only inititated one socket, everything worked as expected.
@Dealerpriest Our application allows for multiple browser tabs/windows connected to multiple serial ports. The way we handle this is to use the "rooms" feature of socket.io. The server creates one socket and the clients connect up to individual "rooms" which are, in fact, one socket to one room. This way we can have one socket on the server and as many as we like on the client. Then we keep an array of serial port to client socket on the server side so we can direct serial communications to the correct socket.
Hello, I am having issues downloading serialport. I have node v10.3.0. I have seen many more of install issues with serialport but none of the fixes I found worked for me. Here is the code of me trying to install serialport above. Any help is much appreciated.
Hi everyone, first time question asker here. created a vue cli 3 app. vue added. added the vue-cli-plugin-electron-builder plugin. in the main rendering thread of electron i tried to add "var SerialPort = require('serialport')" and I receive this message "TypeError: Path must be a string. Received undefined" and a confusing stacktrace. Might be a problem with the plugin might be a problem with the cli. I dont know. Hoping someone may have happened the same problem and have come with a solution. vue-cli 3.0.1 , electron ^2.0.2 and serialport ^6.2.2
I'm trying to interface with some hardware where order matters. Messages are new line delimited. I tried to read in only one byte at a time (by setting the highWaterMark to 1) and then send my responses once I see a new line. However I noticed that 10 bytes are read in at once when looking at an EZ-Tap serial port sniffer, so my responses are instantly out of order. Is there a way to read in one byte at a time from the level of the port?
//Start
port.on('open', function(){
console.log('Port Opened');
port.write('ATE1');
});
port.on('data', function(data){
data = data.toString();
console.log(data);
});
thats all im trying to do
@Vercellotti
const SerialPort = require('serialport')
const Readline = require('@serialport/parser-readline')
const port = new SerialPort('/dev/tty-usbserial1')
const parser = new Readline()
port.pipe(parser)
// Here we wait for data and do console.log
parser.on('data', console.log)
// Here we send data and do nothing else
port.write('ROBOT PLEASE RESPOND\n')
this example uses the searl port stream interface
into the parser Stream that is write only
the parser stream processes the data of the port stream
Adding on to @Vercellotti 's question (I'm a bit new to streams): I need be able to keep track of which command I write triggered the response I read. Is pairing each port.write(...) with a corresponding port.once('data',...) function a reasonable way to do this, or is there a more sensible / direct way?
I also considered having my write commands set a "lastCommandSent" flag and having a port.on("data",...) function that checks the flag before processing the response, but that felt like a bad pattern.
``` const SerialPort = require('serialport')
const port = new SerialPort('/dev/ttyAMA0', {
baudRate: 9600,
autoOpen: false
},function(err){
console.log(err);
})
setTimeout(function(){
port.open(function (err) {
if (err) {
return console.log('Error opening port: ', err.message)
}
})
},5000);
// The open event is always emitted
port.on('open', function() {
// open logic
console.log('opened ')
var buf = new Buffer([ 0xC1, 0xC1, 0xC1 ]);
port.write(buf, function(err,n) {
if (err) {
return console.log('Error on write: ', err.message)
}
console.log('message written')
})
}) ```