![](/images/new-backgrounds/1195197/195197147x1.webp)
6. Configuring the Gateway
Please see chapter 2.12 Command editor in the AbcConf user manual, entitled AnyBus Communicator – User Manual, for further information about creating standard Modbus commands. This manual can be found on the CD LU9CD1 : “ABC_User_Manual.pdf”.
6.11.3.2. Modbus Commands which Can Be Completely Changed by the User
In AbcConf, these commands are known as “Transactions”. Unlike in the previous case, the whole structure of the query and response frames associated with these commands correspond to an association of input or output data in the gateway’s memory (“Data” fields), constants in Byte, Word or DWord format and a final “Checksum” field.
All of the data contained in the query and response “Data” fields of a “Transactions” command are managed by the DeviceNet master, including the “Slave address” and “Function” fields if these are placed in a “Data” field. For instance, this allows you to manage all of the Modbus frame fields from the DeviceNet master if all of the query and response fields of a “Transactions” element (excluding “Checksum”) are “Data” type fields.
N.B. You must not place more than one “Data” field in any Modbus frame. This guarantees that all of the data involved will be processed by the gateway at the same time.
Constants in Byte, Word or DWord format allow you to relieve the DeviceNet master by placing the values of these constants in Modbus query frames (constants in “Query” elements) or by comparing them to the values located in the Modbus responses (constants in “Response” elements). These comparisons are used to accept (identical values) or reject (different values) the Modbus responses in the same way as for standard Modbus commands. The DeviceNet master does not have access to these constants. They are mainly used to replace fields such as “Slave address”, “Function”, “Starting Address,” etc.
Please see the section on “Actions on query/response” in chapter 2.6.4 Transaction and in chapter 2.6.6 Frame objects in the AbcConf user manual, entitled AnyBus Communicator – User Manual, for further information about how to handle “Transaction” commands. This manual can be found on the CD LU9CD1 :
“ABC_User_Manual.pdf”.
74