Chat about Node-Serialport and projects using node serialport for specfic problems or bugs please open a github issue.
I would say no it don't works but I could get it working that's sure!
We will only need to fix some os related stuff.
But when docker runs I would say use that
has anyone used this library to talk to a scale? I'm curious if scale manufacturers generally implement the same sort of protocol (ie do they just stream weight values constantly with delimiting characters, etc)
@frank-dspeed i'm not going to have a lot of control over the targets, which are school-owned chromebooks
running stock chromeOS
my ultimate goal is to write an electron application that can run on a stock chromebook that can talk to an Arduino using serialport
Yo Yo. totaly having problems here
i'm pretty new to johnny five and node.js
after i run npm blink it looks like serial port didnt compile properly.
whats wierd is it used to work until i got interchange to work for me
hello ... just to let you know (if you don't), there is no prebuild for windows 10 with the following parameter : target=10.0.0 runtime=node arch=x64 platform=win32
seems standard for me .. it's a nodejs 10 version
is it possible to force the use of a prebuild ?
id love to try
how would i do that or a link to it?
i think you are saying that the node.js is too new
whice i found out doing the goingnative tutorial i found
the only thing i couldnt finish to go native was getting windows 2013 visual studios. So, if you are asking if my node js has been built us an earlier version i Installed node.js 6.14.2
so, in order for me to get interchange to work i went to the node_modules in my command line. and i NPM install serialport
this got interchange to work for me. but then when i went to run a normal blink.js that i knew worked thats when the serial port started to act up.
im starting to think you are talking about pre-gyp
sry for the hassle. I'm finding out its my serialport.h file for arduino
include# softwareserial.h threw the error. im re installing arduino ide to see if my missing serialport.h will be back
it didnt fix the problem but definetly told me serialport.h is needed and i dont have it or its in the wrong place
arduino IDE debug that is
got arduino IDE to compile again. didnt fix the johnny five
NOde blink problem. sry to ramble on . ill just wait and keep searching for answers. I know were on the topic of "there is not pre build for windows 10"
I want to stop emmiting data from serialport
how can I do it
Cowboy close the port
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'm trying to bundle it with webpack – sorry for giving all the info in the wrong order)
Looks like this just isn't doable and it's not a good idea to use webpack with node-serialport
Hello! Anybody used serialport together with socket.io? I have some weird behaviour when i try to write to the serialport in the socket message callback.
Hi all! I'm developing an app on OSX, but trying to also build for Windows and Linux, using electron-builder. Most stuff "just works", but I'm having problems with serialport
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
@Dealerpriest I don't monitor this regularly and just get a weekly digest. If you are still having issues, I may be able to help. We have developed a working system using socket.io and serialport
If anyone cares, I figured it out...electron-rebuild wasn't necessary. electron-builder handles it with a postinstall script: "electron-builder install-app-deps"
Hello everyone, I am trying to install node-serialport on an embedded platform running arm linux. Is there any good way？ Not RaspberryPi Thank you！
@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.