Rockwell Automation GMLC Reference Manual - Manual (Page 779)

Publication GMLC-5.2 - November 1999
742 Using the RIO Adapter Option
Data Table Report PLC-5/30
Address 0 1 2 3 4
F16:0 -511.4872 0.0 0.0 0.0 0.0
F16:0 0.0 0.0 0.0 0.0 0.0
F16:0 0.0 0.0 0.0 0.0 0.0
F16:0 0.0 0.0 0.0 0.0 0.0
F16:0 0.0 0.0 0.0 0.0 0.0
F16:0 0.0 0.0 0.0 0.0 0.0
F16:0 0.0 0.0
Sending or Getting Data Bit Values
Individual data bit values for any of the motion controller axes can be sent
to or taken from the motion controller using a block transfer. To send or
get multiple data bit values, multiple block transfers (one for each value)
must be used. The bit number of the parameter to be transferred must be
put in word 1 of the BTW data file for the transfer.
• Put the bit number from the table (just the number, not the B) of the
bit to be transferred in word 1.
• Put 01 for the number of bits to be transferred in the low byte of word
2 of the BTW data file for the transfer.
Use the Data Bits table in the Appendix A of this manual to determine the
appropriate bit number. In all cases, block transfers affect only the
working data bit value.
Note: An axis must always be specified (low byte of word 0), even for
data bits that are not axis-specific.
Data bit values sent to the motion controller must always be either 1 or 0
or unpredictable operation can result. In addition, since these values are
integers, 16-bit integer format with zero decimal digits should always be
specified in the high byte of word 2 in the BTW data file.
For example, the integer data file shown below (in hexadecimal format)
sets the overtravel switch polarity (data bit 5) for axis 2 to NC (normally
closed) when specified in a BTW as shown in Sending Data to the Motion
Controller in this chapter. Word 0 specifies that this block transfer is
sending (7Bxx) data bits for axis 2 (xx22). Word 1 specifies the item as