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

NOVUS AUTOMATION www.fieldlogger.net 84/103
From firmware version 1.40 on, there is the possibility to download data directly in the CSV (comma-separated values)
format. When selecting this option for the client FTP download, the files created in the download folder will be in the CSV
format instead of the binary (standard) format.
The created CSV file will have the equipment tag in its first row. In the second row, there will be the column names. From
the third row on, there are the dates, times and channel values for eack log. If the logging rate was configured in
milliseconds, this extra column will be placed before the values columns. All fields are between quotation marks (“) and
the field separator used is the semi-colon (;).
Due to the extra processing to transform the files to the CSV format, this option may cause a delay in the download.
Note: Due to a limited size of FieldLogger internal buffer, it is recommended that FTP server welcome message
should have sentences no longer than 60 characters (each sentence must necessarily be finished with “car return” and
“new line” characters, or “0Dh” and “0Ah” in hexadecimal).
Server
To use FTP server on FieldLogger, simply enable this feature in the Configurator application and set up a username
and password. In this way, the user will have access to the data files for read-only purposes.
The standard used for the FTP is the "Unix" type.
Note: There is no support for simultaneous connections. Therefore, the used client will have to be configured to just
use one connection. In addition, the client must be configured to use the passive mode.
NETWORK MANAGEMENT - SNMP
All of the enabled channels for reading, as well as several status information, have their values available via SNMP
protocol (read-only, there is no writing implemented on the equipment via SNMP).
Standard MIBs are not available in FieldLogger. Available SNMP information is listed below, besides the
following OIDs of the “System” group:
•
sysDescr
•
sysObjectID
•
sysUpTime
The available MIB is described below. A MIB file is available in the product CD. The branch “Enterprise” of MIB is used,
where the “Enterprise number” is 34590. The sub-branch assigned to FieldLogger is 1. Thus, all information will have
the OID starting in 1.3.6.1.4.1.34590.1.
Here follows the available OIDs:
•
1.3.6.1 .4.1.34590.1.0 = Device tag. [OCTET STRING]
•
1.3.6.1 .4.1.34590.1.1 = Device serial number. [OCTET STRING]
•
1.3.6.1.4.1.34590.1.2 = Firmware version. [OCTET STRING]
•
1.3.6.1 .4.1.34590.1.3 = Device date year. [INTEGER]
•
1.3.6.1.4.1.34590.1.4 = Device date month. [INTEGER]
•
1.3.6.1.4.1.34590.1.5 = Device date day. [INTEGER]
•
1.3.6.1.4.1.34590.1.6 = Device time hour. [INTEGER]
•
1.3.6.1.4.1.34590.1.7 = Device time minute. [INTEGER]
•
1.3.6.1.4.1.34590.1.8 = Device time second. [INTEGER]
•
1.3.6.1.4.1.34590.1.9 = RS485 interface enabling and configuration (0 = disabled; 1 = master; 2 = slave).
[INTEGER]
•
1.3.6.1.4.1.34590.1.10 = Selected logging memory (0 = internal memory; 1 = SD card). [INTEGER]
•
1.3.6.1.4.1.34590.1.11 = Logging status (0 = logging stopped; 1 = logging in progress). [INTEGER]
•
1.3.6.1.4.1.34590.1.12 = Available memory for logging in internal memory, in bytes. [INTEGER]
•
1.3.6.1.4.1.34590.1.13 = Presence of SD card (0 = no card; 1 = card present). [INTEGER]
•
1.3.6.1.4.1.34590.1.14 = Available memory for logging in the SD card, in kilobytes. [INTEGER]
•
1.3.6.1.4.1.34590.1.15 = Presence of USB flash drive (0 = no USB flash drive; 1 = USB flash drive present).
[INTEGER]
•
1.3.6.1.4.1.34590.1.16 = Presence of HMI (0 = no HMI; 1 = HMI present). [INTEGER]
•
1.3.6.1.4.1.34590.1.17 = Total number of enabled channels. [INTEGER]
•
1.3.6.1.4.1.34590.1.18.X.Y
o X = Sequential channel number, starting with analog channels and followed by the digital, remote and
virtual ones: