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

NOVUS AUTOMATION www.fieldlogger.net 86/103
Open Authentication
After the connection, in a time frame of up to 5 seconds, the FieldLogger will send an authentication package with the
following format:
String “NOVUS-”. Serial number of
AirGate-GPRS
(8
digits) in ASCII.
Code “-0500-” in
ASCII. Firmware version for
FieldLogger (4 characters)
Example: “1.40”.
As an example, a FieldLogger with a serial number 12546890 and firmware version 1.40 would have an authentication
package equal to “NOVUS-12546890-0105-1.40”.
FieldLogger awaits an “OK” response (ASCII) from the server. If this answer does not arrive in one second, the
authentication package will be resent.
NAP
NAP is a proprietary authentication protocol of NOVUS. Since it is reinforced by cryptography and with other security
features, it is the level of authentication suggested to be used with NOVUS remote server.
DATA LOGGING AND DOWNLOAD
Data logging can be done in the internal memory of FieldLogger or, optionally in a SD card (not included), which must
be inserted into the proper compartment behind the cover (or HMI), as shown in Fig. 20. The internal memory capacity is
up to 532,480 loggings, while SD card logging capability will depend on its storage capacity (size), assuming that the
card is empty.
Note: Poor quality of the card can compromise data logging, causing missed logging periods at higher logging rates
or being more susceptible to data write corruption. Therefore, it is always recommended the usage of high-speed
(class 4 or higher) SD cards of established brands.
SD Card logging not available in models “FieldLogger – USB, 512k logs, RS485” and “FieldLogger –
USB, 512k logs, RS485, 24 V”.
Any kind of channels (analog, digital, remote and virtual ones) can be written into the memory. Logging is periodic and
has its period (rate) set through the Configurator software. After each time interval, the current values of the configured
channels are logged in the selected memory.
There are several ways to start and stop the loggings, and many of them can be freely combined. During the logging, all
the selected channels will be recorded in the requested memory (internal flash or SD card) based on the interval
between loggings configured.
Depending on the start and stop modes selected, there may be "snippets" of logs in memory, and therefore, periods
without any data recorded. This is fully compatible with the equipment and means no problem at all.
The start modes available are the following:
• Immediate start: Loggings will be started right after the equipment reconfiguration.
• By date/time: Loggings will be started on the configured date/time.
• By alarm: When the alarm condition is met (alarm active), loggings will be started.
• Only by Modbus commands: Loggings will be started only when a specific command is sent to the Modbus
equipment.
The stop modes available are the following:
• Full memory: The loggings will be stopped only when the selected memory (internal flash or SD card) has no
more available space.
• Never stop (circular memory): Loggings will be continually done in the selected memory. When filling up the
memory, the oldest data are erased so that the most recent data may be saved.
• By date/time: Loggings will be started on the configured date/time.
• By alarm: If loggings were started by the same alarm, when the alarm condition is no longer met (alarm inactive),
loggings are stopped. If loggings were started for some other reason, as soon as the alarm condition takes place
(alarm active), loggings will be stopped.
• By Modbus command: A specific Modbus command can be sent to stop loggings. This command is independent
of the selected stop mode and has priority over it.