# Using RS485 port on CC100 with NodeRED

**URL:** <https://www.wago.community/t/using-rs485-port-on-cc100-with-nodered/202>\
**Category:** Node-RED\
**Tags:** serial, docker, cc100, nodered\
**Created:** [August 3, 2022, 5:00pm UTC](https://www.wago.community/t/using-rs485-port-on-cc100-with-nodered/202 "2022-08-03T17:00:03Z")\
**Posts on this page:** 14\
**Page:** 2

<div class="post-metadata">

**Author:** ![WagoKurt](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/wagokurt/32/11_2.png) [@WagoKurt](https://www.wago.community/u/WagoKurt)\
**Post date:** [August 11, 2023, 4:33pm UTC](https://www.wago.community/t/using-rs485-port-on-cc100-with-nodered/202/21 "2023-08-11T16:33:25Z")

</div>

Please check the FW for both CC100’s. In the short term, it may be necessary to install older FW.

---

<div class="post-metadata">

**Author:** ![StefSoma](https://avatars.discourse-cdn.com/v4/letter/s/a3d4f5/32.png) [@StefSoma](https://www.wago.community/u/StefSoma)\
**Post date:** [August 11, 2023, 5:15pm UTC](https://www.wago.community/t/using-rs485-port-on-cc100-with-nodered/202/23 "2023-08-11T17:15:04Z")

</div>

@WagoKurt Thanks for you reply. Both my CC100 have 03.09.07(21) firmware. So that is not the issue it seems.

---

<div class="post-metadata">

**Author:** ![WagoKurt](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/wagokurt/32/11_2.png) [@WagoKurt](https://www.wago.community/u/WagoKurt)\
**Post date:** [August 11, 2023, 5:48pm UTC](https://www.wago.community/t/using-rs485-port-on-cc100-with-nodered/202/24 "2023-08-11T17:48:58Z")

</div>

Interesting. Can you please check the versions of the node-red-contrib-modbus and Node-RED?

---

<div class="post-metadata">

**Author:** ![StefSoma](https://avatars.discourse-cdn.com/v4/letter/s/a3d4f5/32.png) [@StefSoma](https://www.wago.community/u/StefSoma)\
**Post date:** [August 11, 2023, 6:02pm UTC](https://www.wago.community/t/using-rs485-port-on-cc100-with-nodered/202/25 "2023-08-11T18:02:41Z")

</div>

11 Aug 18:00:19 - [info] Node-RED version: v3.0.2  
11 Aug 18:00:19 - [info] Node.js version: v16.20.1  
11 Aug 18:00:19 - [info] Linux 5.10.21-rt34w03.01.06 arm LE

node-red-contrib-modbus 5.26.0

---

<div class="post-metadata">

**Author:** ![StefSoma](https://avatars.discourse-cdn.com/v4/letter/s/a3d4f5/32.png) [@StefSoma](https://www.wago.community/u/StefSoma)\
**Post date:** [August 11, 2023, 9:28pm UTC](https://www.wago.community/t/using-rs485-port-on-cc100-with-nodered/202/26 "2023-08-11T21:28:39Z")

</div>

I suspect this might actually caused by incorret permission for node red to use the serial port.

(Dont mind the date, but I get the same return)

docker exec -it wago-node-red /bin/bash  
ls -l /dev/ttySTM1  
crw-rw---- 1 root 106 247, 1 Jun 15 10:04 /dev/ttySTM1

Should it not be lrwxrwxrwx?

I also have to make the permissions persisten somehow. Will test this ASAP.

Docker is installed by uploading the docker ipk in the wbm. node red run command:  
docker run -d --restart unless-stopped --name wago-node-red -d --privileged=true --user=root -p  
1880:1880 --device=/dev/ttySTM1:/dev/serial:rw --security-opt=seccomp=unconfined -v  
node\_red\_user\_data:/data nodered/node-red

I dont think this procedure automatically grants all the neccessary permissions for node red to access the serial port and then throws node red into infinate reboot loop when using a modbus node.

I think I’ve might been a bit confused by the initial post in this thread, where it says that node red should have the correct permissions by default.

---

<div class="post-metadata">

**Author:** ![WagoKolcz](https://avatars.discourse-cdn.com/v4/letter/w/47e85d/32.png) [@WagoKolcz](https://www.wago.community/u/WagoKolcz)\
**Post date:** [June 17, 2024, 9:47pm UTC](https://www.wago.community/t/using-rs485-port-on-cc100-with-nodered/202/27 "2024-06-17T21:47:19Z")

</div>

hi, do we have a solution to the problem of the serial port not working properly?

---

<div class="post-metadata">

**Author:** ![slawekberok](https://avatars.discourse-cdn.com/v4/letter/s/a88e57/32.png) [@slawekberok](https://www.wago.community/u/slawekberok)\
**Post date:** [August 8, 2024, 6:34pm UTC](https://www.wago.community/t/using-rs485-port-on-cc100-with-nodered/202/28 "2024-08-08T18:34:05Z")

</div>

Hello WAGO community,

Did anyone solve this issue with serial port and Node Red on Wago CC-100 ?  
I had exactly the same issue with Node-RED stuck in infinite crash loop after trying to set up modbus connection through serial port.  
The only solution that works for me is using older Node-Red version (v 3.0.2) installed with container from the image:  
docker run -d   
–name node-red   
–restart always   
–privileged=true   
–user=root   
-p 1880:1880   
-p 505:505   
-v node\_red\_user\_data:/data   
-v /dev/ttySTM1:/dev/serial   
**wagoautomation/node-red-cc100:1.0.0**

rather than from image:  
docker run -d --name node-red --restart=always   
-d --privileged=true --user=root   
-p 1880:1880   
-p 505:505   
-v node\_red\_user\_data:/data   
-v /dev/ttySTM1:/dev/serial   
**nodered/node-red**  
where with version 3.1 serial port will not work with modbus nodes in NodeRed 😕

---

<div class="post-metadata">

**Author:** ![ygdrasil](https://avatars.discourse-cdn.com/v4/letter/y/d78d45/32.png) [@ygdrasil](https://www.wago.community/u/ygdrasil)\
**Post date:** [August 21, 2024, 7:31am UTC](https://www.wago.community/t/using-rs485-port-on-cc100-with-nodered/202/29 "2024-08-21T07:31:49Z")

</div>

You might want to try using `modbus@5.25.0` along with dependencies `serialport@10.5.0` and `modbus-serial@8.0.8`.

I’m hoping WAGO releases a new cc100 image that supports Node.js \> 18 and Node-RED 4, along with a fully functional CC100 serial port. Dashboard 1 is depreceated and dashboard 2 can’t be used with current wago CC100 image

---

<div class="post-metadata">

**Author:** ![WagoIcard](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/wagoicard/32/1508_2.png) [@WagoIcard](https://www.wago.community/u/WagoIcard)\
**Post date:** [August 26, 2024, 2:35am UTC](https://www.wago.community/t/using-rs485-port-on-cc100-with-nodered/202/30 "2024-08-26T02:35:27Z")

</div>

Hello,  
In the vanilla node-red installation, does the problem came from the serial node ?  
Last time I was able to make it work by using this work around:

> - I you don’t have Portainer:  
> Login in the PFC100/PFC200/CC100 with SSH then go to elevated user by using the command `su -`  
> Then use the command `docker exec -ti --user root <containername> /bin/bash` to open the container console as root.
> - If you have Portainer, use it to log in the container console in root.
> - In the container console, go to the node-red data folder `cd /data/`
> - Execute the command `npm rebuild --build-from-source`
> 
> This will rebuild the serial node from source to the specific of the system.

---

<div class="post-metadata">

**Author:** ![WAGOAnVe](https://avatars.discourse-cdn.com/v4/letter/w/ed8c4c/32.png) [@WAGOAnVe](https://www.wago.community/u/WAGOAnVe)\
**Post date:** [September 18, 2024, 3:21pm UTC](https://www.wago.community/t/using-rs485-port-on-cc100-with-nodered/202/31 "2024-09-18T15:21:25Z")

</div>

NodeRed CC100 Modbus RTU:

please do the following steps:

1. stop the container
2. delete the container and volume
3. start the container new
4. enter the container and build node-red-contrib-modbus new

docker stop node-red  
docker rm   
docker volume rm node\_red\_user\_data  
docker run --name wago-node-red --privileged=true --user=root --network=host --device=/dev/ttySTM1:/dev/ttySTM1:rw -v node\_red\_user\_data:/data nodered/node-red  
docker exec -it wago-node-red /bin/bash

npm install node-red-contrib-modbus  
npm rebuild --build-from-source

---

<div class="post-metadata">

**Author:** ![WagoKolcz](https://avatars.discourse-cdn.com/v4/letter/w/47e85d/32.png) [@WagoKolcz](https://www.wago.community/u/WagoKolcz)\
**Post date:** [October 1, 2024, 10:36am UTC](https://www.wago.community/t/using-rs485-port-on-cc100-with-nodered/202/32 "2024-10-01T10:36:23Z")

</div>

Works Perfect! 🙂 THX

---

<div class="post-metadata">

**Author:** ![WagoDamRud](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/wagodamrud/32/258_2.png) [@WagoDamRud](https://www.wago.community/u/WagoDamRud)\
**Post date:** [November 4, 2024, 4:04pm UTC](https://www.wago.community/t/using-rs485-port-on-cc100-with-nodered/202/33 "2024-11-04T16:04:39Z")

</div>

Hey, I pushed to my repository working image ( [damrudwago/node-red-cc100 - Docker Image | Docker Hub](https://hub.docker.com/r/damrudwago/node-red-cc100))

You can run it with command:  
`docker run -d --restart always --name wago-node-red --privileged=true --security-opt seccomp:unconfined --user=root --network=host -p 1880:1880 -v node_red_user_data:/data -v /dev/ttySTM1:/dev/serial damrudwago/node-red-cc100:1.0.0`

---

<div class="post-metadata">

**Author:** ![MikePsaltis](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/mikepsaltis/32/47_2.png) [@MikePsaltis](https://www.wago.community/u/MikePsaltis)\
**Post date:** [January 7, 2026, 3:20pm UTC](https://www.wago.community/t/using-rs485-port-on-cc100-with-nodered/202/34 "2026-01-07T15:20:53Z")

</div>

Thanks, Damian. I just tried this on a 751-9301 (FW28) with your image and it worked!

---

<div class="post-metadata">

**Author:** ![HANIBAL](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/hanibal/32/2084_2.png) [@HANIBAL](https://www.wago.community/u/HANIBAL)\
**Post date:** [October 1, 2026, 8:20pm UTC](https://www.wago.community/t/using-rs485-port-on-cc100-with-nodered/202/35 "2026-10-01T20:20:33Z")

</div>

Hi, does it allow my application to share the same Modbus RTU ports?  
My problem is that the runtime seems not to allow sharing resources.

[Previous page](https://www.wago.community/t/using-rs485-port-on-cc100-with-nodered/202.md?page=1)
