Configuring Explicit Messaging Using DATA_EXCH
Original instructions
About us
Overview
Use the DATA_EXCH function block to configure Modbus TCP explicit messages.
The Management_Param, the Data_to_Send, and the Received_Data parameters define the operation.
EN and ENO can be configured as additional parameters.
FBD Representation
Input Parameters
Parameter
Data type
Description
EN
BOOL
This parameter is optional. When this input is set to one, the block is activated and can solve the function blocks algorithm. When this input is set to zero, the block is deactivated and won’t solve the function block algorithm.
Address
Array [0...7] of INT
The path to the destination device, the content of which can vary depending on the message protocol. Use the Address function as an is input to the block parameter ADR.. Refer to a description of the Address parameter
ActionType
INT
The type of action to perform. For Modbus TCP protocols, this setting = 1 (transmission followed by await reception).
Data_to_Send
Array [n...m] of INT
The content of this parameter is specific to the protocol.
Refer to Control Expert online help.
Input/Output Parameters
The Management_Param array is local:
Parameter
Data type
Description
Management_Param
Array [0...3] of INT
The management parameter, consisting of four words
Do not copy this array during a switchover from a primary to a standby CPU in a redundant system. De-select the Exchange On STBY check bocx in Control Expert when you configure a redundant system.
NOTE: Refer to the description of redundant system data management and the T_M_ECPU_HSBY DDT in the M580 Hot Standby System Planning Guide.
Output Parameters
Parameter
Data type
Description
ENO
BOOL
This parameter is optional. When you select this output you also get the EN input. ENO output is activated upon successful execution of the function block.
Received_Data
Array [n...m] of INT
the Modbus TCP response, of which the structure and content depends upon the specific protocol