HMS Anybus Edge Reference Manual page 90

Settings
• Could not initialise RTD module
The resistance temperature detector could not be initilaized. Values that are associated this
module are probably wrong.
• Portal communication error <error code>
A general error has occurred while exchanging data with the portal. Possible error codes:
-2
-3
If you see an error code that is not on the above list, please contact customer support.
Modbus Client/Master
The Modbus client/master can be configured through this form.
Devices and values
At the top there is a list of Modbus devices and their values. You can add, edit, delete or clone
devices and values (input or output) via the buttons below the list. For each device or value the
list shows a name, the communication parameters and an index. The name can be freely defined
and will e.g. be shown on the portal. The indexes are used internally to address the devices and
their values.
When adding or editing a device, a dialog will show up where you can configure the following
parameters:
Name
Type
Interface
Address
IP Address
Port
When adding or editing a value, another dialog will show up. Here you can configure the
following parameters:
Name
Unit identifier Only present for Modbus TCP servers For Modbus TCP/RTU gateways this is the address of the RTU
Function
Start address
Quantity
Data type
Swap words
Limits
You can define up to 128 devices and 4096 values. However, since values can become arrays
when reading/writing several registers/coils, there is another limit: The number of all scalar (non-
array) values plus the size of all arrays must not exceed 8192.
Anybus Edge Gateway Reference Guide
Out of memory
The internal data queue has overflown, because data was produced faster than it could be processed.
The device's name
Here you have to select whether the device will be accessed via Modbus TCP or RTU. The Modbus RTU
option will only be available after you have generally enabled Modbus RTU (see below).
Only present for Modbus RTU devices Serial interface the device is connected to
Only present for Modbus RTU devices Device's address
Only present for Modbus TCP devices Device's IP address (e.g. 192.168.0.3)
Only present for Modbus TCP devices Device's TCP port number - typically 502
The value's name
device to read/write from/to. For non-gateway devices this value should typically be 255.
Modbus function code used to read/write the value The function code also defines whether the value
is interpreted as an input or output.
Register/coil address to start reading/writing from/to Note that addresses start at 0.
Number of registers/coils to read/write If more registers/coils are read/written than fit into the
selected data type (see below), the value will become an array. For example 2 registers would fit into
one 32-bit unsigned integer value. The value would be scalar (no array). 4 registers would make up an
array with 2 32-bit unsigned integer elements.
Data type of the value
Modbus transmits the two bytes of one register in network byte order (big endian). Thus for multi-
register values, the registers are expected to be in the same order. However, some devices store multi-
register values in the opposite order. This option can be used to correct the word order.
88 (148)
SCM-1202-154 1.0 en-US