# Suggestion to handle serial over tcp using nodered?

**URL:** <https://discourse.nodered.org/t/suggestion-to-handle-serial-over-tcp-using-nodered/66867>\
**Category:** General\
**Created:** [24 August 2022 18:04 UTC](https://discourse.nodered.org/t/suggestion-to-handle-serial-over-tcp-using-nodered/66867 "2022-08-24T18:04:20Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![syma33](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/syma33/32/30665_2.png) [@syma33](https://discourse.nodered.org/u/syma33)\
**Post date:** [24 August 2022 18:04 UTC](https://discourse.nodered.org/t/suggestion-to-handle-serial-over-tcp-using-nodered/66867/1 "2022-08-24T18:04:20Z")

</div>

i suceeded to parse data using a rs232 adapter and node-red-node-serialport. However, the goal is to parse data over tcp, tried using tcp-node but then i cannot setup 7O1 in flow.... suggestion? virtualcom?

HOWEVER, this works and i got readings using python..  
sudo socat pty,link=/dev/ttyNET0,waitslave tcp:192.168.1.238:23  
sudo chmod 666 /dev/ttyNET0  
dmm read --connect /dev/ttyUSB8 --count 0  
sudo picocom -b 2400 /dev/ttyNET0

...but someone maybe have a flow that do that in node-red already? 🙂

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/3/2/322c95e12727728e98035e559d5f24c397395525.png)

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [24 August 2022 21:28 UTC](https://discourse.nodered.org/t/suggestion-to-handle-serial-over-tcp-using-nodered/66867/2 "2022-08-24T21:28:43Z")

</div>

I may be wrong here but I don't believe your Python example is reading over TCP - not directly, you set up a serial port that reads over TCP didn't you and then read from that serial port? Wouldn't that also work in node-red? You would still set up the port at the OS level.

---

<div class="post-metadata">

**Author:** ![Jean-Luc](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jean-luc/32/89996_2.png) [@Jean-Luc](https://discourse.nodered.org/u/Jean-Luc)\
**Post date:** [24 August 2022 21:55 UTC](https://discourse.nodered.org/t/suggestion-to-handle-serial-over-tcp-using-nodered/66867/3 "2022-08-24T21:55:19Z")

</div>

To read the serial port of my inverter via ethernet, I used this [gateway](http://www.hi-flying.com/elfin-ew10-elfin-ew11)  
and then I use a tcp node to retrieve or write to this port.  
And you which gateway do you use?

There are 2 versions, one wifi and the other rj45

---

<div class="post-metadata">

**Author:** ![syma33](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/syma33/32/30665_2.png) [@syma33](https://discourse.nodered.org/u/syma33)\
**Post date:** [26 August 2022 19:01 UTC](https://discourse.nodered.org/t/suggestion-to-handle-serial-over-tcp-using-nodered/66867/4 "2022-08-26T19:01:33Z")

</div>

oh, saw that dmn read --connect /dev/ttyUSB8 should be ttyNET0.. in my example byt my bad.  
And yes.. im sure it will work with node red.. im just wondering if i make it harder for myself...

---

<div class="post-metadata">

**Author:** ![syma33](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/syma33/32/30665_2.png) [@syma33](https://discourse.nodered.org/u/syma33)\
**Post date:** [26 August 2022 19:03 UTC](https://discourse.nodered.org/t/suggestion-to-handle-serial-over-tcp-using-nodered/66867/5 "2022-08-26T19:03:18Z")

</div>

i use raspberry pi, rs232 adapter and ser2net

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [25 October 2022 19:03 UTC](https://discourse.nodered.org/t/suggestion-to-handle-serial-over-tcp-using-nodered/66867/6 "2022-10-25T19:03:59Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.