Table of Contents
Advertisement
Loopback Test
Total
Successful
Failures
Retries
Timeouts
Illegal Function
Illegal Address
Illegal Data
Slave Failure
No Gateway Path
Master Rejects
Reset
6.6.3 Modbus master data configuration
This is the area of configuration in which the individual data items are selected for transmission across the
Modbus master communications link. The configuration fields that appear depends on the parameter selected,
so the examples given here will probably not match those that appear to the user. The parameters that appear
in the 'Parameter List' scroll menu depends on the slave model.
EXAMPLE 1: TARGET SP1 WITH FEC920 SLAVE
Select configuration menu
Programmer
Modbus Master
EtherNet/IP
Digital I/O
User Lin
Custom Message
Zirconia
EXAMPLE 2 USER DEFINED PARAMETER
This allows the user to enter a Modbus address (decimal) and a data type in order to read the value of a
parameter from or write a parameter value to the slave. Modbus address and data types must be obtained from
September 18
FEC920: USER GUIDE
Illegal Code: The slave does not support the function code transmitted by the master.
Pending: The request is waiting to be sent, the most likely cause being that the slave
device has not been set to online.
If set to 'Yes', Sends a function code 8 transaction to the slave, and waits for a response.
A count of all the transactions sent to the slave including reads, writes both good and failed
transactions.
A count of all the successful transactions sent to the slave.
A count of all the unsuccessful (failed) transactions sent to the slave. May be caused by
Illegal Function, Illegal Address etc. failures, as detailed below.
The number of transactions that were re-sent because of timed out responses from the
slave devices.
A count of all the transactions sent to the slave for which no response was received within
the configured timeout period.
A count of all the transactions sent to the slave that the slave claimed contained an invalid
function code. Exception code (1).
A count of all the transactions sent to the slave that the slave claimed contained an invalid
Modbus register address. Exception code (2).
A count of all the transactions sent to the slave that the slave claimed contained an invalid
value. Exception code (3).
A count of all the times this slave device has failed to communicate. Exception code (4).
A count of all the times it has not been possible to access the slave device as it is on
another network that requires a gateway for access.
A count of all the transactions that the Modbus Master has refused to send to the slave
due to invalid configuration data.
A one shot action that immediately resets all diagnostics counts.
Data
Figure 83 Target Setpoint
A5E45696052A Rev-AA
Modbus Master.1.Data
Descriptor
Data Item 1
PV
0.00
Status
Success
Slave Device
FEC920
Parameter List
Target SP
Number
1
Priority
Medium
Page 93
Advertisement
Table of Contents
