On 12/30/20 8:19 AM, RobertoA wrote:
> Having to control devices via uart (for example gps receivers,
> electronic scales, etc.) it would be useful to create a device that,
> communicating with the control computer via ethernet, would allow the
> computer to 'see' the virtual com ports, corresponding to the uart of
> the card Raspberry

Do you /need/ (raw) Ethernet specifically?  Or are you simply wanting
the ability to use a physical serial port on one computer from another
computer across a network (be it Ethernet, WiFi, PPP, etc.)?

> So it will be necessary to program the Raspberry so that it has a tcp /
> ip server inside, which will pass the information to the uart ports
> On the computer side it will be necessary to install programs to
> 'virtualize' the com port and connect it to the tcp / ip server on the
> Raspberry

There is a standard that has been used in the past:  RFC 2217 - Telnet
Com Port Control Option.  It is an extension to the telnet protocol to
allow controlling various aspects about the serial port across the
network from the client.

> How to proceed?

It's been about 15 years since I've used this.  But the last time I did
so, I installed one of the handful of programs that supported RFC 2217
on a Linux machine, and a separate / independent client program on a
Windows VM that also supported RFC 2217.  The client made a virtual COM
port on Windows that any program could use just like a physical COM
port.  The only caveat was some programs didn't know how to deal with
COM ports numbered higher than 4.

I've messed with a few different RFC 2217 servers for Linux.  I remember
messing with a couple of different RFC 2217 clients for Windows.  One
was free and limited function.  Another was a reasonable price to
license with more functions.  The names of all of them have long since
been lost to me.

Search for things related to RFC 2217.  I think that will get you close
to what you want.



--
Grant. . . .
unix || die

--- SoupGate-Win32 v1.05