For Example - uses for the serial port monitor may be interfacing to data loggers, "strange" log sources (e.g. PBX call logs) or out-of-band log retrieval (e.g. setting a router to log to the serial port instead to the network and then picking the data from that serial line). Out-of-band log retrieval can also be used to hide the fact that logging is actually taking place.
The serial port monitor works as follows: it listens to the configured port. With each received character, it checks if a configured "message end sequence" is received. If it isn't it continues listening until either another character is received or a timeout occurs.
If either the "message end sequence" is received or the timeout occured, the message is considered to be complete. In this case, an event is generated and that event is scheduled for processing.
Filter Conditions - Serial Port Monitor
Timeout Limit
This is the maximum amount of time the service waits to receive the "message end characters" from the attached device.
How the message is ended
This is the sequence that, when received, denotes the end of the message. Most often, this is either "\r\n" or "\n" ("\r" represents a CR characters, "\n" represents a LF character).
Which Port do you want to monitor
This is the port that the device is attached to. Most often, this is either COM1: or COM2:. All locally-existing ports can be used. When working locally, the configuration program enumerates the locally available ports. This can be one of the following values: