Instruction manual

53
specification, registers have two different indices at which they can be
referenced: their “known as” value (which starts at number 1) and their
“addressed as” value (which is always 1 less than the “known as” value).
The “known as” value is typically the number that is presented for human
entry or consumption, while the “addressed as” value is the number that
appears “on the wire” when the Modbus packet is sent from master to
slave. This gateway follows this generally-accepted industry paradigm,
where a point’s configured Modbus master “register” value is decremented
by 1 before it is placed “on the wire”. Some vendors, however, will
document their slave device’s “addressed as” values in their literature,
which means that these register indices must have 1 added to them when
entered into the gateway’s “Modbus master register” field.
For example, the Toshiba VF-AS1/G9 drive’s Modbus RTU slave protocol
implementation & corresponding user’s manual references all internal ASD
parameters using “addressed as” values. This means that (in addition to
the required conversion from Toshiba’s native hexadecimal radix to the
Modbus protocol’s natural decimal radix) these parameter values must
have 1 added to them when they are to be accessed via an ICC gateway
executing the Modbus RTU master protocol.
e.g
VF-AS1/G9 “command 1” parameter is documented to be FA00 in the
Toshiba literature. Converting this to decimal, we arrive at a value of
64000. To allow a point in the gateway’s database to correctly access the
“command 1” parameter via Modbus RTU, therefore, that point’s Modbus
master “register” attribute must be set to 64001 (which will result in an
address value of 64000 (0xFA00) “on the wire”).
16.1.4 Modbus TCP/IP Slave
The gateway supports Schneider Electric’s Modbus TCP/IP protocol, release
1.0. The unit is conformance class 0 and partial class 1 and class 2 compliant,
and allows up to 4 simultaneous Modbus TCP/IP client connections (sockets).
• The “unit identifier” (UI) field of the request packets is ignored.
• Standard socket timeouts are set to 30s, which means that if a particular
open socket experiences no activity for more than 30s, then the gateway
assumes that the client or network has experienced some sort of
unexpected problem, and the gateway will close that socket.
• A “master” IP address and timeout time can be assigned to the unit. Each
point defined in the point database has the capability to be assigned an
optional failsafe timeout value. When an unexpected socket failure from
the “master” client occurs, all points with timeout processing enabled will
be written with their failsafe values. This provides an additional level of
process security in the event of a network or master device disturbance.