Carbolite nanodac - Manual (Page 48)

nanodac™
MC27 –EN– 1.04
46
Ethernet/IP Display Mode (Cont.)
An alternative to the click-drag technique is to right click on the required output (five in the example
below), and select ‘Edit Wire...’ from the context menu that appears. A browse window pops up, allowing
the user to navigate to the required parameter. This technique can be used both on previously empty
inputs or outputs and on those previously filled.
Figure 1.4.13d Context menu details
EXPLICIT DATA
As shown in table 3.4.13, when configured as a server, there is only one explicit application object, and
that has the class ID= A2 (162 decimal). The instance ID is the Modbus address of the parameter and the
Attribute is always = 1. Explicit service codes hex10 (decimal 16) and 0E (14) are both supported, for
writing and reading single attributes respectively.
Service code Class ID Instance ID Attribute
Hex Dec Hex Dec Decimal
0010 16 A2 162 1-65535 1
000E 14 A2 162 1-65535 1
Table 1.4.13 Explicit data specification
When configured as a client, two separate connections are available allowing the user to produce two
independent explicit read or write messages to different server devices.
Figure 1.4.13e below, shows an example of how to configure an explicit message request. The instance ID
and the data type are taken from the server manufacturer’s data. In this example a read request is
configured to determine the Group recording status of a nanodac server, and it can be seen from
table 5.3
that the decimal modbus address for this parameter is 4150 and the data type is int16. It is this address
which is used as the instance ID.
Once all the information has been entered, the read is requested by setting ‘Send’ to ‘Yes’. The Data field
changes to ‘3’ for this example and from table 5.3 it can be seen that the recording status is ‘Recording
enabled’.
Note: The nanodac supports only 16 bit data types for reading and writing of explicit messages.