Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 111
|
201
o
Third word: data in PV (lower).
•
2 – for all other data types (i.e. attributes without a status byte), with the status byte being
auto-generated; in this case, the ISA100.11a entity is mapped onto the chunk of registers
starting at address <start_address>+1. At address <start_address> there is a
device status
register
generated by the Modbus server which reflects the state of the ISA100.11a
communication, just like for value 1.
This should
not
be used for mapping ISA100.11a
attributes of types 65 and 66
.
Example:
169,3,6202030405060C04,2,1,66,0,0,0,
2
In the above holding register line, DEVICE_ATTRIBUTE is 4 bytes data, no data status
byte. When mapping to Modbus registers, it can have the Modbus status byte type set
to 2; three words will be needed, as follows:
o
First word: 0x00 + status (U8);
o
Second word: DEVICE_ATTRIBUTE (upper);
o
Third word: DEVICE_ATTRIBUTE (lower).
3.
If the address range of a register line overlaps an existing register line in the same group, or if it
does not fit in the range 0-65535, it will be ignored.
Loading a List of Registers
You can import the register map from a file that includes the input and holding registers lines with their
parameters which are expressed as comma separated values.
To load the list, you must perform the following actions:
1.
in the Manage Host list section click on
Browse
to locate the text file that you wish to load, and
click
Upload
;
2.
click
Activate
, to load the new host list into Modbus; the current
Modbus_gw.ini
file will be
overwritten.
Exporting the Registers
This page also enables to export the registers, by clicking
Save
in the Manage Host list section.
