Modbus-Tcp; Sending E-Mails - Smtp; Debugging - Novus fieldlogger Instruction Manual

The following services are available:

MODBUS-TCP

FieldLogger can be enabled to communicate through Modbus-TCP protocol, widely used in SCADA systems. By
enabling that functionality, FieldLogger will act as a Modbus-TCP server, allowing channel values, as well as status and
configuration information, to be read and written by external software applications. Enabling the gateway functionality
(assuming the device is configured as a Modbus-RTU/RS485 master), FieldLogger can forward Modbus requests to
slaves connected to the Modbus-RTU network.
FieldLogger must be accessed by the ID "255". Any other ID will be assumed to be targeting a Modbus-RTU/RS485
slave through FieldLogger by the gateway function. On this case, if this functionality is enabled, the data packet will be
forwarded to the RS485 bus.
From firmware version 1.40 on, FieldLogger also supports the "Modbus RTU over TCP" protocol.
The gateway functionality works as a multiplexer, receiving all the simultaneous Modbus-TCP connections and putting
them in a line to be sent to the Modbus-RTU network, one at a time. Due to this line, in a worst-case scenario, Modbus-
TCP clients timeout should be set as big or bigger than Modbus-RTU master timeout (configured in the Remote
Channels screen) multiplied by the number of the active Modbus-TCP connections. If the client Modbus-TCP timeout is
smaller than that value, a timeout must occur instead of an exception code "0Bh" (Gateway Target Device Failed to
Respond) in a missing slave situation.

SENDING E-MAILS - SMTP

FieldLogger can be configured to send e-mails to multiple receivers upon the occurrence of alarms or events. The
receivers must have been entered in the equipment through configuration. In alarms configuration, we must select which
receivers should be notified via e-mail on the occurrence of each alarm or event.
For this service, you must configure an e-mail server that will be accessed at the time of the alarm occurrence. On this
server, there obviously must be a valid e-mail account for the FieldLogger to login.
Note: SSL connections are not supported.
In the e-mail message bodies there are two parts: a constant part that is common to all messages, and a variable part
that is dependent on the alarm or event that originated the message. The constant part is defined by the user, as well as
the message subject. The variable part contains the FieldLogger tag, its serial number and a string describing the alarm
condition or event that caused the message.
Fig. 21 - Example of alarm message
IMPORTANT: E-mails do not have delivery or reading guarantees. Thus, in alarm cases, try to use some other ways to
report alarm or events.

DEBUGGING

In case of any problems during the start-up of the equipment when sending emails, you can use a Telnet client to view
messages that may help you to identify the problem. All you need do is point the Telnet client to the FieldLogger IP
address (port 23) and observe the messages posted.
NOVUS AUTOMATION www.fieldlogger.net 78/104