Electronics > Projects, Designs, and Technical Stuff

Connecting Xport to a remote server

(1/2) > >>

Gandalf_Sr:
I have an embedded project where my PSoC6 processor talks to a Lantronix Xport over a 115,200 baud serial link - the PSoC6 code is quite far along with code that responds to 2-letter commands such as 'di' that gives a directory listing of the files my system has stored - this is all self-developed in C using Cypress Creator 4.2 and GCC C, no RTOS, no DOS, just Cypress-provided C drivers for stuff like the Quad SPI flash memory IC I'm using.

I have been successfully developing on this for a while simulating the UI by connecting to it from a remote PC using TeraTerm; when the initial TeraTerm connection window pops up, I chose the TCP/IP option, enter the IP address of the Xport, change the TCP port# to 10001 (default for the Xport), choose the 'other' radio button and set the Protocol: to IPv4.  TeraTerm then connects immediately and stays connected all day.  So far so good.

Now I need to make the Xport connect to a remote server which I don't have control over and the Server guy has no experience with Xport.  I have discovered (around p52/53 of the Xport UG) that I can configure the Xport so that it can be commanded to establish an Ethernet link by sending a command over the serial port something like C10.0.0.12/10001 and that is supposed to connect to the device at the other end and, if I configure it to respond, I can get a 1-letter response like Y or N to indicate success.

Sorry it's taken quite a while to get there but here is my question.  What needs to be set up at the Server end so that the incoming connection instigated by the Xport is successful?  Lantronix Tech Support tell me that they are assuming a second Xport at the other end but (disappointingly IMHO) they can't (or won't) provide information on a driver or setup of what the remote server would need to have configured to accept the incoming connection.  I think the server is Windows - I'll check.  Can anyone give me any help or advice on this?

2N3055:

--- Quote from: Gandalf_Sr on September 03, 2020, 02:29:03 pm ---I have an embedded project where my PSoC6 processor talks to a Lantronix Xport over a 115,200 baud serial link - the PSoC6 code is quite far along with code that responds to 2-letter commands such as 'di' that gives a directory listing of the files my system has stored - this is all self-developed in C using Cypress Creator 4.2 and GCC C, no RTOS, no DOS, just Cypress-provided C drivers for stuff like the Quad SPI flash memory IC I'm using.

I have been successfully developing on this for a while simulating the UI by connecting to it from a remote PC using TeraTerm; when the initial TeraTerm connection window pops up, I chose the TCP/IP option, enter the IP address of the Xport, change the TCP port# to 10001 (default for the Xport), choose the 'other' radio button and set the Protocol: to IPv4.  TeraTerm then connects immediately and stays connected all day.  So far so good.

Now I need to make the Xport connect to a remote server which I don't have control over and the Server guy has no experience with Xport.  I have discovered (around p52/53 of the Xport UG) that I can configure the Xport so that it can be commanded to establish an Ethernet link by sending a command over the serial port something like C10.0.0.12/10001 and that is supposed to connect to the device at the other end and, if I configure it to respond, I can get a 1-letter response like Y or N to indicate success.

Sorry it's taken quite a while to get there but here is my question.  What needs to be set up at the Server end so that the incoming connection instigated by the Xport is successful?  Lantronix Tech Support tell me that they are assuming a second Xport at the other end but (disappointingly IMHO) they can't (or won't) provide information on a driver or setup of what the remote server would need to have configured to accept the incoming connection.  I think the server is Windows - I'll check.  Can anyone give me any help or advice on this?

--- End quote ---
If other side is windows you can map remote xport to a virtual serial port and just use that.

Gandalf_Sr:

--- Quote from: 2N3055 on September 03, 2020, 03:49:53 pm ---If other side is windows you can map remote xport to a virtual serial port and just use that.

--- End quote ---
How do I do that?

2N3055:
There is a windows driver that creates virtual serial port that is tunneled to an IP adress of X-port on the other side.
It completely encapsulates serial port on windows trough TCP/IP to serial port on X-port. If you put MAX232 on X-port on the other side you get virtual RS232 cable...

So you map X-port to serial port on windows, and when you open COM port on windows, you create tunnel to serial interface on X-port. Your UART data goes there and back.

Gandalf_Sr:

--- Quote from: 2N3055 on September 03, 2020, 06:04:18 pm ---There is a windows driver that creates virtual serial port that is tunneled to an IP adress of X-port on the other side.
It completely encapsulates serial port on windows trough TCP/IP to serial port on X-port. If you put MAX232 on X-port on the other side you get virtual RS232 cable...

So you map X-port to serial port on windows, and when you open COM port on windows, you create tunnel to serial interface on X-port. Your UART data goes there and back.

--- End quote ---
Thanks. But doesn't one end of the link have to establish a connection with the other before data can be passed?

Navigation

[0] Message Index

[#] Next page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod