Raw Device Status Message - Intrepidcs API
Main - Compatibility - Example

Raw Device Status message sends out this report every timestamp clock rollover. This is used for larger than 16 bit time-stamping and to detect a neoVI disconnection or reset.

The sequence of the message stream allows this message to act as a most significant roll over for time-stamping. Each rollover for a neoVI device indicates a ( NEOVI_TIMESTAMP_2 = 0.1048576 ) count. Each rollover for a neoVI Blue or ValueCAN device is a ( NEOVIPRO_VCAN_TIMESTAMP_2 = 0.065536) count.

You can detect a disconnection by watch the SYNC_COUNT. This is a modulus 255 counter that is incremented every time the message is sent. Your application can monitor this for consecutive numbers for connection detection.

The RESET_STATUS should not change. If there was a device reset or a watchdog reset these bits will change. 

The message format is shown below in Table 1.  The 0xAA and the check sum of the Raw Communications Packet are left out of the table.

Table 1 - Message Format

BYTE 1 BYTE 2 BYTE 3 BYTE 4
 NETID_DEVICE 0x01 SYNC_COUNT RESET_STATUS

Compatibility

Hardware Present Notes
neoVI Yes Message period is 0.1048576 seconds
ValueCAN Yes Message period is 0.065536 seconds
neoVI PRO/neoVI Blue Yes Message period is 0.065536 seconds


Example

Message : "0xAA - 0x30 - 0x01 - 0xEE - 0x0C - 0xD5" 

0xAA = Start Byte

0x30 = Length / Target Byte : Length is 3 Bytes To Follow and Target is 0 which is the Device

0x01 = Identifies the status message within the device network

0xEE = Current Sync Count

0x0C = Reset Status

0xD5 = Checksum 

 

 

intrepidcs API   Documentation - (C) Copyright 2000-2009 Intrepid Control Systems, Inc.

Last Update: Thursday, May 22, 2003