Capture Settings are set-up separately for each capture channels. Once these settings have been specified, OK or Apply should be clicked. This tab specifies Echo UDP (Syslog), TCP Server and TCP Client settings.
Echo to Network Overview
ComCap can echo any captured data to the network, using UDP (syslog), TCP Server or TCP Client protocols, which are detailed in the Networking Tutorial. Effectively, this allows ComCap to convert serial data to network protocols, to be captured on remote PCs for viewing or redundancy.
Using TCP Server, data may be echoed to a maximum of five remote PCs (using TCP Client) that connect to the Local IP Address and Port. Connections are refused for connections in excess of five. TCP Client and UDP need a remote IP address to be specified, and are thus limited to a single remote PC.
Add Syslog Headers, Priority (Facility/Severity) Text
Specifies that syslog headers should be added to echoed lines:
Priority Only |
<14> is a Priority value where the first 7 bits of the number are a facility code and the last 3 bits are severity, selected from the drop down Facility Priority and Severity Priority lists. The Actual Priority text that will be added is show, |
Priority, Time and Host |
Also add the time and host and program name, similar in format to: <14>Mar 25 17:03:04 PC09 ComCap |
Note that Syslog headers are normally only used with UDP.
Add CRLF End of Line (UDP only)
This tick box specifies whether echoed UDP lines should have CRLF added to the end of each captured line. The TCP protocols always have CRLF added for end of line.
Remote IP Address and Port, Retry Attempts, Wait Seconds
For UDP and TCP Client, these fields allow the Remote IP Address and Remote IP Port to be specified, to which captured data will be echoed. They may not left blank or zeros. For UDP Syslog, the port is usually 514, for TCP Client it should be above 1,024, the same as that of the remote TCP Server which is listening.
UDP is an unreliable protocol where data is sent blind with no confirmation it has been received by the remote computer, which might not even exist.
TCP Client is reliable, and also needs Retry Attempts and Wait Seconds to be specified, so that connection attempts are repeated if they fail. Setting Retry Attempts to zero causes indefinite attempts to be performed.
Local IP Address and Port
For TCP Server, this is the Local IP Address for server, selected from a drop down box, usually 0.0.0.0 and the IP Port on which the server will listen for remote TCP clients, usually higher than 1,024. For UDP and TCP Client, the IP address should usually be 0.0.0.0 and the port set to zero so that Windows selects port randomly. A fixed port may be used to identify multiple UDP or TCP sessions from the same PC, but when a connection is lost there may be delay of several minutes before the port can be re-used.