feature request: built-in support for serialport

[cnotch]

No description provided.

[Fishrock123]

Is this a feature request?

This stuff lives quite happily already in user-land: https://github.com/voodootikigod/node-serialport

Is there a good reason that should change?

[mikeal]

not that happily, but we may need more work in libuv before talking about taking this in to core. @voodootikigod

[voodootikigod]

I'd rather node/io get proper ability to provide SOCK_OPTS on file descriptors for many reasons not JUST serial port and then serial port can be only JS.

[Qard]

I don't think serialport should be in core, but I'm 👍 on including the functionality needed to be able to do a userland module in pure JS.

[Fishrock123]

but isn't this like the entire "websocket support" in core then?

[Qard]

I'd think using websockets would be somewhat more common than using serialport though. I think it's mostly a concern of if there'd be enough people committed to maintaining it. I'm not firmly against serialport in core, but I'm not convinced it should be there.

[cnotch]

I use IO.js developing desktop software, need access to a lot of serialport-based devices. If I used a third-party module(https://github.com/voodootikigod/node-serialport), It has version matching problem and installation problem ...
IO.js version changes so often!

[voodootikigod]

i blame io.js.

Chris Williams

@voodootikigod http://twitter.com/voodootikigod | GitHub
https://github.com/voodootikigod

The things I make that you should check out:
SaferAging http://www.saferaging.com/ | JSConf http://jsconf.com/ |
RobotsConf http://robotsconf.com/ | RobotsWeekly
http://robotsweekly.com/

Help me end the negativity on the internet, share this
http://jsconf.eu/2011/an_end_to_negativity.html.

On Tue, Apr 28, 2015 at 9:01 PM, yrushi75 [email protected] wrote:

I use IO.js developing desktop software, need access to a lot of
serialport-based devices. If I used a third-party module(
https://github.com/voodootikigod/node-serialport), It has version
matching problem and installation problem ...
IO.js version changes so often!

—
Reply to this email directly or view it on GitHub
#1546 (comment).

[rvagg]

@yrushi75 the current goal is that within any major-version of io.js, compiled addons should still work regardless of minor and patch version number. We're going to hit 2.0.0 soon which, amongst other things, indicates a need to recompile addons but beyond that you shouldn't need to and if you are then perhaps you could file a bug report so we can look at it.

[kyriosli]

I think it easy to interpret a serial port in unix/linux/darwin with module tty, but difficult to port on windows.

So if you are working under *nix, there is no worry about io.js's version change, just do it yourself, write your own serial port interpreter:

input = require('tty').ReadStream(require('fs').openSync('/dev/tty.usbserial', 'r'));
// since io.js does not support both read and write on same fd, we need to open the device twice

[saghul]

FWIW: libuv/libuv#19

[Fishrock123]

See libuv/libuv#379

[livesankp]

This will be so great to have built in support of serialport for nodejs!

[ekryski]

Keeping this thread up to date. 379 is closed in favour of libuv/libuv#484.

[Fishrock123]

Another update: libuv/libuv#484 seems to have good traction.

[Trott]

It appears that libuv/libuv#484 may have sorta kinda stalled out. If someone with the right skill set is motivated to jump in there and offer to help, that might be A Good Thing..

[Trott]

This issue has been inactive for sufficiently long that it seems like perhaps it should be closed. Feel free to re-open (or leave a comment requesting that it be re-opened) if you disagree. I'm just tidying up and not acting on a super-strong opinion or anything like that.

(Perhaps N-API will make this less of a pain-point?)