# Not possible to communicate via com port with rfxcom

**URL:** https://discourse.nodered.org/t/not-possible-to-communicate-via-com-port-with-rfxcom/1909
**Category:** General
**Created:** [30 July 2018 21:06 UTC](https://discourse.nodered.org/t/not-possible-to-communicate-via-com-port-with-rfxcom/1909 "2018-07-30T21:06:02Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![koentje84](https://avatars.discourse-cdn.com/v4/letter/k/b9e5f3/32.png) [@koentje84](https://discourse.nodered.org/u/koentje84)
#### Post date: [30 July 2018 21:06 UTC](https://discourse.nodered.org/t/not-possible-to-communicate-via-com-port-with-rfxcom/1909/1 "2018-07-30T21:06:02Z")

</div>

Hi,  
I have an issue when I wan to use the node-red-contribit-rfcom node. It doesn't want to communicate with the RFXcom device.  
It complains over ReadIOCompletion.

If I use the software that comes with the RFXcom everything works. But nod in Node-red.

I'm running node red on an win7 64bit VM-ware machine.

![2018-07-30_22-59-16](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/2/2777ac7ae6da5f336e34297f81e1dde1ba8d3f90.jpg)

---

<div class="post-metadata">

### Author: ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)
#### Post date: [30 July 2018 21:13 UTC](https://discourse.nodered.org/t/not-possible-to-communicate-via-com-port-with-rfxcom/1909/2 "2018-07-30T21:13:33Z")

</div>

Do you mean node-red-contrib-rfxcom?

If so I'm not sure the author is on the forum very much. It's probably better to open up an issue on the guthub page for the node, [https://github.com/maxwellhadley/node-red-contrib-rfxcom/issues](https://github.com/maxwellhadley/node-red-contrib-rfxcom/issues)

---

<div class="post-metadata">

### Author: ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)
#### Post date: [31 July 2018 03:58 UTC](https://discourse.nodered.org/t/not-possible-to-communicate-via-com-port-with-rfxcom/1909/3 "2018-07-31T03:58:11Z")

</div>

Remember, you have to be sure that the other software (RFXmngr???) is really closed, otherwise the COM3 cannot be accessed from Node-RED

---

<div class="post-metadata">

### Author: ![koentje84](https://avatars.discourse-cdn.com/v4/letter/k/b9e5f3/32.png) [@koentje84](https://discourse.nodered.org/u/koentje84)
#### Post date: [31 July 2018 06:21 UTC](https://discourse.nodered.org/t/not-possible-to-communicate-via-com-port-with-rfxcom/1909/4 "2018-07-31T06:21:22Z")

</div>

sorry for the typo Ukmoose.  
I indeed mean node-red-contrib-rfxcom. But it can also be an issue related to serialport. Because that node also comes with the installation of node-red-contrib-rfxcom.

At this moment I have no clue where to look for and I was wondering if anyone has some experience with these kind of issues.

---

<div class="post-metadata">

### Author: ![koentje84](https://avatars.discourse-cdn.com/v4/letter/k/b9e5f3/32.png) [@koentje84](https://discourse.nodered.org/u/koentje84)
#### Post date: [31 July 2018 06:22 UTC](https://discourse.nodered.org/t/not-possible-to-communicate-via-com-port-with-rfxcom/1909/5 "2018-07-31T06:22:24Z")

</div>

I already double checked that Krambriw. And the RFXmngr is really closed.  
Anyway, thanks for the tip.

---

<div class="post-metadata">

### Author: ![koentje84](https://avatars.discourse-cdn.com/v4/letter/k/b9e5f3/32.png) [@koentje84](https://discourse.nodered.org/u/koentje84)
#### Post date: [31 July 2018 21:44 UTC](https://discourse.nodered.org/t/not-possible-to-communicate-via-com-port-with-rfxcom/1909/6 "2018-07-31T21:44:49Z")

</div>

I have found the code that throws the error. The error comes from serialport.(serialport\_win.cpp)

```
> void __stdcall ReadIOCompletion(DWORD errorCode, DWORD bytesTransferred, OVERLAPPED* ov) {
> ReadBaton* baton = static_cast<ReadBaton*>(ov->hEvent);
> 
> if (errorCode) {
> ErrorCodeToString("Reading from COM port (ReadIOCompletion)", errorCode, baton->errorString);
> baton->complete = true;
> return;
> }

```

Now I only need to find out why this error occurs. Anyone suggestions?

---

<div class="post-metadata">

### Author: ![maxwellhadley](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/maxwellhadley/32/7827_2.png) [@maxwellhadley](https://discourse.nodered.org/u/maxwellhadley)
#### Post date: [28 September 2018 21:18 UTC](https://discourse.nodered.org/t/not-possible-to-communicate-via-com-port-with-rfxcom/1909/7 "2018-09-28T21:18:18Z")

</div>

Are you still having problems? There was an update of the underlying node-rfxcom module to use the (then) latest Serialport module version 6.x.x on 8th July, which may have fixed this issue, as it looks like a Serialport problem. Try updating `node-red-contrib-rfxcom`, which should pull the latest versions in

---

<div class="post-metadata">

### Author: ![koentje84](https://avatars.discourse-cdn.com/v4/letter/k/b9e5f3/32.png) [@koentje84](https://discourse.nodered.org/u/koentje84)
#### Post date: [2 October 2018 21:52 UTC](https://discourse.nodered.org/t/not-possible-to-communicate-via-com-port-with-rfxcom/1909/8 "2018-10-02T21:52:41Z")

</div>

Hi Max,

Thanks for your reply.

Currently I’m running node red on an old pi. But I will definitely update the `node-red-contrib-rfxcom` see if there is any improvement/change on the situation.

I will let you know if anything is changed.
