NOVUS V1.5x A - Manual (Page 77)

NOVUS AUTOMATION www.fieldlogger.net 77/103
Throughout the FieldLogger operation, while not downloading data to the USB flash drive, all different types of errors
generate 3 blinks on the status led. When the USB flash drive is connected for download and an error occurs, it is
indicated as shown in the table below:
BLINK NUMBER ERROR
1 Not enough space on the USB flash drive
2 File not found
3 USB flash drive disconnected before the end of the download
4 Writing error in USB flash drive
5 Error in creating the path in the USB flash drive
6
Error in the opening of the download session: there is already an open
session (configuration or download)
ETHERNET INTERFACE
Interface not available in models “FieldLogger – USB, 512k logs, RS485” and “FieldLogger – USB,
512k logs, RS485, 24 V”.
The FieldLogger Ethernet interface allows the connection of the equipment in Ethernet 10/100 Mbps networks. There
are several services available for this interface, all enabled and configured individually, which gives FieldLogger a high
degree of versatility.
Note: It is always recommended that when not needing an interface or a service anymore, these should be disabled.
For connection to the TCP-IP network, we can set a fixed IP or use DHCP (dynamic host configuration protocol, the
protocol that allows for FieldLogger to have an IP number assigned by the network server). Furthermore, if desired, you
can enable the DNS service, where in some services, instead of the IP number of the servers, you can configure your
name (URL).
Note: FieldLogger does not have the processing capability of computers; therefore the switch port where it is
connected (especially in data center monitoring applications) configuration should be as basic as possible, avoiding
exaggerated traffic in the network where it is. This will greatly increase its performance, avoiding potential packet
losses.
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.