NOVUS Web Server – WS10 - Manual (Page 26)

Web Server – WS10
NOVUS AUTOMATION 26/33
PARAMETERS
ModbusTCP function is enabled when file MODBTCP.CFG is included in the WS10. Follows an example of this file:
[General]
ServerPort = 502
ServerID = 255
IdleTimeOut = 300
MaxConnections = 4
MultipleConnections = true
[Rules]
Allow 10.1.1.0 mask 255.255.255.0
Allow 200.200.200.200
Deny 192.168.0.0 mask 255.255.255.0 Connection parameters are defined in section [General]. Values shown
for ServerPort and ServerID parameters are specified by the protocol,
and should not be modified.
In section [Rules] the allowed and blocked IP addresses are listed. Deny
clauses have higher priority than Allow clauses. By defining an IP mask,
one can allow or deny access for an IP range. To allow access from any
IP, use Allow All.
Section Parameter Values Description
ServerPort 1 to 65535 TCP port for the ModbusTCP connection. Always set to 502.
ServerID 1 to 255 Unit identifier for the WS10. Always set to 255.
IdleTimeOut 0 to 65535
Maximum time with no data flow in seconds. After this time the connection is aborted by the
WS10. If value 0 is defined, the connection will not be aborted due to inactivity. It is strongly
recommended to set a non-zero value.
MaxConnections 1 to 10 Maximum number of clients that can be simultaneously connected to the WS10.
General
MultipleConnections True or False
Permission for multiple connections from the same IP address, If true, a single client may
establish multiple ModbusTCP connections to WS10. If false, a single connection is allowed
from each client.
Rules
Allowed Syntaxes:
Allow xxx.xxx.xxx.xxx
Allow xxx.xxx.xxx.xxx mask yyy.yyy.yyy.yyy
Allow all
Deny xxx.xxx.xxx.xxx
Deny xxx.xxx.xxx.xxx mask yyy.yyy.yyy.yyy
Deny all
Rules for connection authorization. Allow clauses define external IP addresses from which
ModbusTCP connections will be allowed. Deny clauses define external IP addresses from
which no connections will be allowed. By using a mask clause, an IP range can be defined.
All clause means all IP values. Deny rules have higher priority. If no rule is defined, all IP
addresses are blocked and ModbusTCP function can’t be used by any client. At least one
Allow clause must exist.
xxx.xxx.xxx.xxx and yyy.yyy.yyy.yyy are IP and mask values, respectively.
REGISTERS ADDRESS MAP FOR MODBUS TCP AND MODBUS RTU-SLAVE
WS10 registers are defined by its device and tag name. To externally access these registers using ModbusTCP or ModbusRTU-Slave, numerical
addresses must be assigned. These addresses correspond to Holding Registers Addresses, as defined in Modbus specifications.
All Modbus registers defined in this map can contain values up to 16 bits long. To address an WS10 register containing a 32 bits value, it is
necessary to create 2 Modbus registers, one associated to the upper 16 bits and the other to the lower 16 bits of the WS10 register, as in the
following example:
_INTERNAL_/IN1CNT.Hi = 5
_INTERNAL_/IN1CNT.Lo = 6
by doing this, the Modbus register with address 5 is associated to the upper 16 bits of the IN1CNT register of the device _INTERNAL_, and the
Modbus register with address 6 is associated to the lowest 16 bits.
Assignment of addresses to these registers is only necessary if one of the above protocols is in use, and is implemented in file MAP.CFG, to be
included in the WS10. Follows an example for this file.
[RegMap]
TT101/PV = 0
TT201/PV = 1
_ALARMS_/ALARM1 = 2
_INTERNAL_/IN1 = 3
_INTERNAL_/OUT1 = 4
_INTERNAL_/IN1CNT.Hi = 5
_INTERNAL_/IN1CNT.Lo = 6 In section [RegMap] addresses are associated to already defined register
names. Physical Modbus addresses are used (zero based). Addresses
don’t need to be contiguous, but it is recommended to improve
performance and allow block operations. All addresses are Holding
Registers, accessible using Modbus commands 3, 6 and 16.