It allows you to run the server and the client on linux or windows machines (and MACs I suppose, but haven't tested it). There are a lot of software that supports telnet+RFC2217 serial port forwarding. One of the solutions is using telnet with RFC2217 - Telnet Com Port Control Option. So now the application just works with serial port on the client machine, and doesn't even know that data is actually transmitted over the network. Virtual comport that mimics physical serial port and interface with the APP.SERVER that communicates with the DEVICE through physical serial port and then serves the data over network.So the diagram is: +-+ comport +-+ network +-+ virtual comport +-+ It is called "virtual serial port" or "virtual comport" as this is a software emulated bridge between a client and your application. Since the application (APP on diagrams) knows only how to communicate with the device by serial port (we suppose), the client machine has to have some virtual serial port that is used by the application. Real life example: a device is connected to raspberry pi (very small single-board machine) that is connected to a local network, and read the data on a desktop. Now what we want, is to have the device connected to one machine (server), and run the application on the remote machine (client) over the network. Suppose we have an application that works with some device using serial port (com port or comport - the same thing). You can read abut it in the Wiki article ) (Serial port or com port? - Serial ports are often refered as COM ports. Connecting to serial port (com port) over network
0 kommentar(er)
