SENA Serial_IPTM Redirector 4.3 - Manual (Page 26)

3.1 Checking for Special Application Requirements
3.2
Modifying Application Settings
3.3 Troubleshooting Application Problems
3.4 Monitoring Serial/IP COM Port Activity
3.5 Tracing Serial/IP COM Port Data
3.1 Checking for Special Application Requirements
Nearly all Windows applications can use Serial/IP COM ports and serial servers instead of local COM ports. The
exceptions mostly fall into two general categories.
●
Does the application require serial line control and/or status?
Most Windows applications perform only the common read/write operations that all serial servers
support. Some applications, however, also require some of the features provided by the COM Port
Control protocol specified by IETF RFC 2217. For these applications, the serial server must
support the COM Port Control protocol and provide at least the serial port control and status
functions that the application requires.
Generally, applications requiring COM Port Control are of two types:
1. Applications that must programmatically change serial port settings like baud rates and
framing. A common workaround is to manually make these settings on the serial server. If
an application must change these settings on the fly, COM Port Control will be required.
2. Applications that require serial line status signals.
●
Is the application a DOS application?
Some DOS applications are not able to access Windows COM ports (including the virtual COM
ports created by the Serial/IP Redirector) without additional software to bridge the gap between
DOS and Windows COM ports. If you plan to use the Serial/IP Redirector with a DOS application,
refer to the technical note
Using Tactical Software Redirectors with DOS Applications .
3. Using the Serial/IP Redirector