FS-RA-CLX_SlotServer_Instruction_Manual_(T17011) Page 25 of 34
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Tel: (408) 262-2299 Fax: (408) 262-2296 Toll_Free: 888-509-1970 email: support@fieldServer.com
Appendix A.2. The IO image header
The IO image header appears at the start of every block of image data that is transferred to
or from the SlotServer to the Logix CPU. It consists of 4 items of data:
Offset into image
data block
Item Description
0
Protocol
Type
The value specified under the Map Descriptor’s
Protocol_Type_ID field is transferred to the Logix CPU
and can be used to decode the protocol. The same
value has to be transferred back to the SlotServer to
indicate the protocol.
1
Node
Status
This field is automatically filled in by the SlotServer if a
Node Status Data Array with the name
SlotServerNodes is declared. Its value can be used in
the Logix CPU to check the status of Nodes connected
to the SlotServer.
2
Block
Number
The number of the Data Array for which the IO image
data is valid for, e.g. a block number of 1 will indicate
the data is to or from DataArray_1
3 Reserved Not used
Appendix A.3. How to obtain Node Status from the SlotServer
By declaring the following Data Array, the Node Status field in the IO image header will be
filled in with the Node Statuses of all Nodes declared on the SlotServer:
// Data Arrays
Data_Arrays
Data_Array_Name, Data_Format, Data_Array_Length, Data_Array_Function
SlotServerNodes, Bit, 256, Node_Status
Note: The Data Array Name must be as shown for this function to work correctly.