I don't own this product, but this https://www.eztcp.com/en/download/pds_files/an_telcom_en.pdf is the quality of the gibberish I've seen on RFC 2217.
RFC 2217: https://tools.ietf.org/html/rfc2217
https://datatracker.ietf.org/doc/html/rfc855
pyserial: https://pythonhosted.org/pyserial/
ser2net: https://manpages.debian.org/testing/ser2net/ser2net.8.en.html
<network port>:<state>:<timeout>:<device>:<options>
CONTROLPORT:<port spec>
DEVICE:<name>:<device>
these make some sense.
socat(): https://linux.die.net/man/1/socat
It's my understanding that RFC 2217 generally provides out of band signalling for serial ports:
a) e.g. DTR, DSR, RTS, CTS, CD, RI etc.
b) allows reading and writing of the serial port parameters.
c) The serial port is accessed via a TCP port.
The other option is to use something like Real Port or True Port. These solutions put hardware flow control in the OS. With Linux it requires rebuilding the Kernel with that support.
generally, instructions don't even mention the control port.
This, https://www.elmark.com.pl/amfile/file/download/file/133827/product/24215 is just as bad.
I just don't get how control is implemented AND not sure how to take a given RFC 2217 port, e.g. 5500 and turn it into a /dev/tty or /dev pseudoterminal device.
The intent is to communicate to a serial server (possibly Perle, MOXA or Advantek) from a Rasberry PI 4. Either using the LabView community edition with WXG (web) and Linx (extensions) or use Python.
Besides communicating with the two serial devices, I need some I/O from a webpage. Serial port messages to one device will be outgoing only. The other will have both solicited and unsolicited messages.
RFC 2217: https://tools.ietf.org/html/rfc2217
https://datatracker.ietf.org/doc/html/rfc855
pyserial: https://pythonhosted.org/pyserial/
ser2net: https://manpages.debian.org/testing/ser2net/ser2net.8.en.html
<network port>:<state>:<timeout>:<device>:<options>
CONTROLPORT:<port spec>
DEVICE:<name>:<device>
these make some sense.
socat(): https://linux.die.net/man/1/socat
It's my understanding that RFC 2217 generally provides out of band signalling for serial ports:
a) e.g. DTR, DSR, RTS, CTS, CD, RI etc.
b) allows reading and writing of the serial port parameters.
c) The serial port is accessed via a TCP port.
The other option is to use something like Real Port or True Port. These solutions put hardware flow control in the OS. With Linux it requires rebuilding the Kernel with that support.
generally, instructions don't even mention the control port.
This, https://www.elmark.com.pl/amfile/file/download/file/133827/product/24215 is just as bad.
I just don't get how control is implemented AND not sure how to take a given RFC 2217 port, e.g. 5500 and turn it into a /dev/tty or /dev pseudoterminal device.
The intent is to communicate to a serial server (possibly Perle, MOXA or Advantek) from a Rasberry PI 4. Either using the LabView community edition with WXG (web) and Linx (extensions) or use Python.
Besides communicating with the two serial devices, I need some I/O from a webpage. Serial port messages to one device will be outgoing only. The other will have both solicited and unsolicited messages.