Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.arch.embedded > #32096

Re: Remote COM port

Show all headers | View raw

Il 27/11/2023 09:37, Arthur Erhardt ha scritto:
> pozz <pozzugno@gmail.com> wrote:
>> I have a proprietary device with a RS232 port controlled by a Windows
>> application that opens a standard COM port.
> 
>> Now I need to move the device in a remote position with Internet
>> connection. The user (and the Windows PC) will be in a different position.
> 
>> I want to develop an embedded Linux box with RS232 port connected to the
>> device and Internet.
> 
>> I know there are many commercial solutions, but before I'd search for an
>> open-source solution, if any. Here the big issue is the virtual COM
>> driver for Windows.
> Two devices would remove the need for any kind of special software on
> windows. For the sake of the argument, make it two raspberry pis with
> USB to RS232 adapters.
> 
> <windows pc.com1> <--> <raspberrypi1.ttyUSB0> <--> internet via your
> interface of choice <raspberrypi2.ttyUSB0> <--> <proprietary equipment>
> 
> The software you want on the linux systems is socat or netcat and
> should be part of any modern distribution, though not installed by
> default. For this to work, your windows software shouldn't do
> anything fancy with the status lines of RS232.
> 
> Any raspberry pi is grossly oversized for the task, so feel free to
> search for something smaller and cheaper.
> 
> This
> https://stackoverflow.com/questions/484740/converting-serial-port-data-to-tcp-ip-in-a-linux-environment
> might give some hints concerning how to use the software.

I was thinking about this solution, I see two drawbacks:

* The user PC, that is already connected to Internet, must be equipped 
with an additional box that must be connected to Internet

* Linux doesn't know anything about the serial port settings (baudrate, 
parity, and so on). The user should know the settings used by the 
third-party application and set them in the Linux box.


>> It's not a one-piece scenario, so it makes sense to develop my embedded
>> box that solves this problem. Moreover, I would stay generic regarding
>> RS232 baudrates, parity and so on.
> 

Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Remote COM port pozz <pozzugno@gmail.com> - 2023-11-27 08:55 +0100
  Re: Remote COM port Arthur Erhardt <usenet2023@erhardt-net.de> - 2023-11-27 08:37 +0000
    Re: Remote COM port pozz <pozzugno@gmail.com> - 2023-11-28 08:37 +0100
      Re: Remote COM port Arthur Erhardt <usenet2023@erhardt-net.de> - 2023-11-28 09:13 +0000
  Re: Remote COM port David Brown <david.brown@hesbynett.no> - 2023-11-27 09:44 +0100
  Re: Remote COM port Paul Rubin <no.email@nospam.invalid> - 2023-11-27 02:12 -0800
    Re: Remote COM port pozz <pozzugno@gmail.com> - 2023-11-28 08:38 +0100
  Re: Remote COM port Theo <theom+news@chiark.greenend.org.uk> - 2023-11-27 10:58 +0000
  Re: Remote COM port chrisq <devzero@nospam.com> - 2023-11-28 13:07 +0000

csiph-web