# Serial Port Management Features?
**URL:** https://discourse.nodered.org/t/serial-port-management-features/5587
**Category:** General
**Created:** [8 December 2018 16:25 UTC](https://discourse.nodered.org/t/serial-port-management-features/5587 "2018-12-08T16:25:05Z")
**Posts on this page:** 3
**Page:** 2
### Author:  [@tree-frog](https://discourse.nodered.org/u/tree-frog)
#### Post date: [5 April 2021 19:00 UTC](https://discourse.nodered.org/t/serial-port-management-features/5587/21 "2021-04-05T19:00:43Z")
Julian,
Thanks for your advice and input. I'm working with VSCOM devices. Upon investigation, (and I will need to test this on our devices when I get the chance) There is a TCP Raw Server Mode. There is a setting for "max clients". The question that needs an answer is does this mode work the same way with the serial port devices connected? The VSCOM units are a set which have an IP address to each unit. The "driver" applies a virtual port for the unit I/O.
---
### Author:  [@tree-frog](https://discourse.nodered.org/u/tree-frog)
#### Post date: [15 April 2021 20:24 UTC](https://discourse.nodered.org/t/serial-port-management-features/5587/22 "2021-04-15T20:24:59Z")
As it turns out you can use the VSCOM in "Raw TCP Server" mode. You can specify how many connections you want to limit to the port. You can access the TCP data by the devices IP address and the TCP port assigned to each physical RS232 port. So using these devices allows me to split the messages and allow more connections. The Microscan ESP software will allow you to connect to certain devices in TCP mode, only if there is an option on the device to talk TCP in the first place. You may be able to cheat it by connecting to one and switching the device type. I will need to experiment with it. Fortunately, the majority of the devices we use that are serial have options for TCP on those models.
I did try com0com and it works pretty well. You can use other programs which need to be running on startup to monitor and pass information to the virtual ports.
**com0com** is used for creating and maintaining virtual serial port pairs allowing you to connect software to software and eliminate real ports between devices.
**com4port** is a means to multiplex and connect real serial ports to one of the pairs such that you can send a real serial ports data to many virtual serial port pairs etc.
**com2TCP** is a means to connect a virtual serial port to TCP. So you use these programs in concert with one another to create the monster you desire.
---
### Author:  [@Fizzo](https://discourse.nodered.org/u/Fizzo)
#### Post date: [15 November 2022 12:04 UTC](https://discourse.nodered.org/t/serial-port-management-features/5587/23 "2022-11-15T12:04:06Z")
There was no reaction on this comment on DTR, RTS, CTS Pins.
I would like to dynamicly change these pins on the fly.
It is very useful, how it is realised with the buadrate (msg.baudrate = 2400) ...
Wouldn´t it be ok to control the pins as well with e.g. mgs.DTR = low / high / auto ... ?
[Previous page](https://discourse.nodered.org/t/serial-port-management-features/5587.md?page=1)