Using an array instead of a message structure - intrepidcs API
In some programming environments (such as LabVIEW) it maybe inconvenient for you to access the message with a structure. In these cases you may use a 64 byte array in place of the structure. Table 1 below lists the locations of message items in the byte array.
With LabVIEW, items that are 4 bytes long can be read with neoGetLong.vi and set with neoPutLong.vi SubVIs.
Table 1 - Position of Message Elements in the Byte Array
| Item | Bytes | Byte (s) Location |
| StatusBitField | 4 | 0-3 |
| StatusBitField2 | 4 | 4-7 |
| TimeHardware | 4 | 8-11 |
| TimeHardware2 | 4 | 12-15 |
| TimeSystem | 4 | 16-19 |
| TimeSystem2 | 4 | 20-23 |
| TimeStampHardwareID | 1 | 24 |
| TimeStampSystemID | 1 | 25 |
| NetworkID | 1 | 26 |
| Protocol | 1 | 28 |
| NumberBytesHeader | 1 | 31 |
| NumberBytesData | 1 | 32 |
| Header(1 To 4) | Array Length 4 | 36-39 |
| ArbIDOrHeader | 4 | 36-39 |
| Data(1 To 8) | Array Length 8 | 40-47 |
| intrepidcs API Documentation - (C) Copyright 2000-2012 Intrepid Control Systems, Inc. (www.intrepidcs.com) |
Last Updated : Monday, April 23, 2001