Serial over TCP Thema ist als GELÖST markiert

[detlef]

Does Paul use a TW39/serial card with USB option?
Then a Serial-over-Ethernet adapter is the wrong device. An USB-over-Ethernet would fitt.

[PaulHeller]

Thank you for the helpful replies. My objective is to create a stand-alone system for remote I-telex access which does not require a dedicated PC. I did this in Arvada and it works very well. The setup In Arvada is using a serial RS-232 connection and a serial over Ethernet adapter. I am using the I-telex Usb serial interface card at my new location in Austria. It sounds like the best for me now would be to swap this card for an I-telex rs-232 serial interface card. I will do that and report back here.

I wish you all a nice day.

[PaulHeller]

Update: I switched over to using a raspberry PI for the TCP/Serial interface. All works fine now. Fred, you were right in your assessment.

I am very pleased with the setup. I use a VPN so that the direct port for the TCP communication is not on the internet. The only port open to the internet is port 134 for i-Telex (and of course the VPN port). I'm using noip to deal with any changes to my ipaddress for the vpn.

I am using a raspberry Pi 3B+ running Raspberry PI OS (formerly Raspbian) running the following software:

• ser2net

• pivpn

• noip update client

The Raspberry PI is connected via USB cable to the i-Telex serial port.

In windows I am using Johannes' very fine i-Telex USB Terminal program, com0com, and com2tcp

With this setup I can VPN into my network from anywhere in the world and check for i-Telex messages on the serial port.