# 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:** cc100, docker, serial, 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:** 1
**Showing post:** 7

<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: [June 16, 2023, 4:06pm UTC](https://www.wago.community/t/using-rs485-port-on-cc100-with-nodered/202/7 "2023-06-16T16:06:01Z")

</div>

@Devlin_Hugo @WagoKurt  
I am experiencing a similar issue on my wago CC100 running node red in docker. I’ve spent the last couple of days trying to solve this but with no positive outcome. Even with only one modbus serial read node and a debugger, after configuring the modbus read node, node red immidiately crash and goes into infinite boot-loop. I finally managed to find the flows.json via FTP and remove the modbus node from the flow and node red started back up on its own, as it should.

Same thing happens (serial only, TCP works fine) with node-red-contrib-serialport and node-red-contrib-modbus.

I’ve found some older info about this being an issue in the past as well, but on raspberry pi. In this case I would assume this is either a firmware or a node issue 😕

I don’t have any logs available just now. FYI, I have two Wago CC100 installed docker and node-red exactly the same way, both are acting the same way.

Any tips and tricks to solve this?

---

_[View the full topic](https://www.wago.community/t/using-rs485-port-on-cc100-with-nodered/202)._