# Modbus RTU node red UART issue

**URL:** <https://discourse.nodered.org/t/modbus-rtu-node-red-uart-issue/75866>\
**Category:** General\
**Created:** [28 February 2023 08:47 UTC](https://discourse.nodered.org/t/modbus-rtu-node-red-uart-issue/75866 "2023-02-28T08:47:02Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![DSongra11\_forum.com](https://avatars.discourse-cdn.com/v4/letter/d/f04885/32.png) [@DSongra11\_forum.com](https://discourse.nodered.org/u/DSongra11_forum.com)\
**Post date:** [1 March 2023 11:02 UTC](https://discourse.nodered.org/t/modbus-rtu-node-red-uart-issue/75866/9 "2023-03-01T11:02:22Z")

</div>

Hello Colin,

Basically, Node-red is perfectly running my Modbus TCP node is also working perfectly, but the only issue is with the Serial UART interface. I have seen this kind of issue many developers are facing, with this same error/problem.

you can refer this kind of issue - [Segment fault error occurs when deploy node-red-node-serial in openWRT](https://discourse.nodered.org/t/segment-fault-error-occurs-when-deploy-node-red-node-serial-in-openwrt/63842)

> <https://github.com/serialport/node-serialport/issues/2438>
>
> \### SerialPort Version
> 
> 10.3.0
> 
> \### Node Version
> 
> v14.19.0
> 
> \### Electron Version…
> 
> \_No response\_
> 
> \### Platform
> 
> Linux raspberrypi 5.10.92-v7+ #1514 SMP Mon Jan 17 17:36:39 GMT 2022 armv7l GNU/Linux
> 
> \### Architecture
> 
> ARM
> 
> \### Hardware or chipset of serialport
> 
> QinHeng Electronics CH340
> 
> \### What steps will reproduce the bug?
> 
> I've created a repository at https://github.com/avakarev/serialport-docker-rpi to reproduce the issue.
> 
> Clone it and then:
> 
> \`make run-v9 # v9.2.8 on rpi\`
> 
> Using serialport ^9.2.8
> serialport/stream opening path: /dev/ttyUSB0 +0ms
> serialport/binding-abstract open +0ms
> serialport/bindings/poller Creating poller +0ms
> serialport/stream opened path: /dev/ttyUSB0 +10ms
> port successfully opened
> 
> \`make docker-run-v9 # v9.2.8 on rpi in docker container\`
> 
> Using serialport ^9.2.8
> 2022-02-23T17:19:07.255Z serialport/stream opening path: /dev/ttyUSB0
> 2022-02-23T17:19:07.256Z serialport/binding-abstract open
> 2022-02-23T17:19:07.266Z serialport/bindings/poller Creating poller
> 2022-02-23T17:19:07.267Z serialport/stream opened path: /dev/ttyUSB0
> port successfully opened
> 
> \`make run-v10 # v10.3.0 on rpi\`
> 
> Using serialport ^10.3.0
> serialport/stream opening path: /dev/ttyUSB0 +0ms
> serialport/bindings-cpp open +0ms
> serialport/bindings-cpp/poller Creating poller +0ms
> serialport/stream opened path: /dev/ttyUSB0 +11ms
> port successfully opened
> 
> \`make docker-run-v10 # v10.3.0 on rpi in docker container\`
> 
> Using serialport ^10.3.0
> 2022-02-23T17:20:48.142Z serialport/stream opening path: /dev/ttyUSB0
> 2022-02-23T17:20:48.144Z serialport/bindings-cpp open
> make\[1\]: \*\*\* \[Makefile:8: \_docker\_run\] Error 139
> 
> \### What happens?
> 
> \`serialport\` exits with 139 and have no stacktrace despite \`DEBUG=serialport\*\`
> 
> \### What should have happened?
> 
> \`serialport\` should successfully open given port
> 
> \### Additional information
> 
> The alpine base image v12 used in demo repo is kinda outdated, but same behavior is met with alpine v14 and v15
> 
> Original discussion started at https://github.com/Koenkk/zigbee2mqtt/issues/11545

for this, I am able to use a Simple Serial interface node node-red-node-serialport@0.15.0 version, without any issue. But my problem is with Modbus RTU serial UART node i am facing this issue.

In case you need any further information from my side please let me know.

Br,  
Devendra

---

_[View the full topic](https://discourse.nodered.org/t/modbus-rtu-node-red-uart-issue/75866)._