Communications Status Log Format

Each record in the communications status log includes two fields in addition to the timestamp and device name:

  • Severity – A single character code that indicates the type of message. The following values are legal:

    • “S” (Status) Indicates that the identified operation has successfully completed.

    • “W” (Warning) Indicates that the server has attempted to retry the operation with the identified device.

    • “F” (Fault) Indicates that the identified operation has failed and that the server has stopped retrying.

  • Description – text providing more details about the event.

Communications Status Log Example

"2009-04-15 16:41:05.367","IPPort","S","Device dialed"
"2009-04-15 16:41:05.382","PakBusPort_ip","S","sending message","src: 4094","dest: 2","proto: PakCtrl","type: 0x09","tran: 214"
"2009-04-15 16:41:05.398","PakBusPort_ip","S","received message","src: 2","dest: 4094","proto: PakCtrl","type: 0x89","tran: 214"
"2009-04-15 16:41:05.398","CR1000","S","PakCtrl message received","89"
"2009-04-15 16:41:05.413","PakBusPort_ip","S","sending message","src: 4094","dest: 2","proto: BMP5","type: 0x17","tran: 213"
"2009-04-15 16:41:05.429","PakBusPort_ip","S","received message","src: 2","dest: 4094","proto: BMP5","type: 0x97","tran: 213"
"2009-04-15 16:41:05.429","CR1000","S","BMP5 message received","type: 0x97","check/set clock"
"2009-04-15 16:41:06.367","PakBusPort_ip","S","sending message","src: 4094","dest: 2","proto: BMP5","type: 0x09","tran: 217"
"2009-04-15 16:41:06.382","PakBusPort_ip","S","received message","src: 2","dest: 4094","proto: BMP5","type: 0x89","tran: 217"
"2009-04-15 16:41:06.382","CR1000","S","BMP5 message received","type: 0x89","table poll","CR1000.TestFast"
"2009-04-15 16:41:06.382","PakBusPort_ip","S","sending message","src: 4094","dest: 2","proto: BMP5","type: 0x09","tran: 218"
"2009-04-15 16:41:06.492","PakBusPort_ip","S","received message","src: 2","dest: 4094","proto: BMP5","type: 0x89","tran: 218"
"2009-04-15 16:41:06.492","CR1000","S","BMP5 message received","type: 0x89","table poll","CR1000.TestFast"
"2009-04-15 16:41:06.523","PakBusPort_ip","S","sending message","src: 4094","dest: 2","proto: BMP5","type: 0x17","tran: 219"
"2009-04-15 16:41:06.523","PakBusPort_ip","S","received message","src: 2","dest: 4094","proto: BMP5","type: 0x97","tran: 219"

Communication Status Log Messages
Message Text Message Meaning User Response to Message
Serial packet X exchanged The low level serial BMP1 communication framing packet was sent and the response received from the device. (CR10X-TD table based type devices)  
Classic;;Cmd The listed command was sent to an array based datalogger. For a list of the commands and their meanings see the datalogger operator’s manual.
BMP1 packet received A BMP1 packet was received from the device. (CR10X-TD type devices only)  
RPC packet exchanged A BMP3 packet was exchanged. (CR5000, CR9000 dataloggers only)  
Datalogger did not respond to end command The computer tried to terminate the connection but the datalogger did not acknowledge the shutdown. This is an indication that there is a communications problem between the computer and the datalogger. Check the cables and connectors and make sure the datalogger has power.
PakBus framing error LoggerNet received data from the link that cannot be verified to be part of a PakBus packet. Some possible causes: the datalogger program or its settings are configured to write data on the port on which you are attempting to connect, there is a mismatch in baud rates between your computer serial port and the datalogger, the link is dropping sequences of characters from transmission because the CPU on the computer is heavily loaded or because of faulty USB drivers. Possible solutions: change the port you are using to communicate, try using a slower baud rate to communicate with the datalogger, use Windows Task Manager to determine whether there are processes that are loading down your CPU, check to see if there is an updated driver for your USB/RS232 adapter.
Invalid low level signature The packet received from the device got corrupted and the packet signature doesn’t match the packet contents. Check to find out where in the communications link noise or signal corruption is causing the data to be disrupted.
Provider opened The serial communications port has been initialized.  
Device dialed The communications link has been initialized to transfer data packets.  
Provider closed The serial communications port has been closed.  
Unable to Locate Serial synch byte The low level communications synchronization byte was not received after the computer sent out a serial packet. This indicates that the device is either not responding or responding with an invalid communications protocol. This message would appear if trying to talk to an array based datalogger that is set up as a table based datalogger in the network map.