Managing Slave Devices Operating Modes
The operating modes of slave devices are managed by the protocol manager with the following scanners and their dedicated libraries:
oModbus TCP IOScanner: Modbus TCP IOScanner library
These libraries contain function blocks that allow you to:
oControl the Modbus TCP IOScanner,
oManage cyclic data exchanges (implicit messages),
oManage the status variables,
oSend non-cyclic data exchange requests (explicit messages).
Other libraries can be used depending on the devices.
Status Variables of the Modbus TCP IOScanner
There are two status variable types:
oHealth bits: variables to indicate the communication state of the channels. There is one health bit per channel.
oGlobal scanner status: variable to indicate the Modbus TCP IOScanner state.
This table presents the health bit values:
Health bit value |
Communication state of the channel |
---|---|
0 |
Health timeout expired without receiving a reply. |
1 |
No errors detected. Request and reply are received. |
The scanners collect and write data from/to the devices. These variables constitutes the I/O image.
Each variable gets its own address:
Variable |
Type |
Amount |
---|---|---|
I/O image variables |
%IW for inputs %QW for outputs |
A table of words is created per channel/connection. |
Health bit |
%IW |
Four consecutive words for Modbus TCP |
Global scanner status |
%IW |
One word for Modbus TCP |
Function Blocks to Control the Modbus TCP IOScanner
Modbus TCP IOScanner library contains function blocks used by the application to communicate with the controller and the Modbus TCP slave devices:
oCONFIGURE_OTB: Send the software configuration of the Advantys OTB
oIOS_GETSTATE: Read the state of the Modbus TCP IOScanner
oIOS_START: Launch the Modbus TCP IOScanner
oIOS_GETHEALTH: Read the health bit value
oIOS_STOP: Stop the Modbus TCP IOScanner
For more details, refer to Modbus TCP IOScanner.
Function Blocks to Control ATV and Lexium Devices
Use the PLC Open and other function blocks dedicated to drives to control ATV and Lexium devices. These function blocks can be accessed in the GMC Independent PLCopen MC library, GMC Independent Altivar library, and GMC Independent Lexium library. For more information, refer to the Motion Control Library Guide.
The protocol manager and the slave devices exchange data at each cycle of an application task.
The Bus Cycle Task parameter allows you to select the application task that manages the scanner:
oUse parent bus cycle setting: associate the scanner with the application task that manages the controller.
oMAST: associate the scanner with the MAST task.
oAnother existing task: you can select an existing task and associate it to the scanner.
For more information about the application tasks, refer to the EcoStruxure Machine Expert Programming Guide.