User Manual MN032006EN
Effective May 2018
415U Condor-long-range wireless I/O and gateway
Data logging
The data logging feature allows you to record the status of I/O registers on a regular basis. Data is saved to non-volatile memory, and can be retrieved at a later time.You can enable data logging on 415U modules with the purchase of a feature key license (see
“Feature license keys” on
page 51
).
Data is logged to an internal data file in “.csv” format. Each row of the file is a single record, consisting of a timestamp and values of all of the configured log items at that time. When the file reaches a configured maximum number of rows, the file is “rolled,” that is, the file is compressed and archived and a new log file is created.
The amount of memory available for storing logged data depends on the device type. The available data logging memory is indicated in the log files. When the memory is full, the oldest data log file is deleted.
The 415U series supports up to 500KByte of data log memory in compressed files.
Configuring data logging
To configure data logging, you need to specify how frequently the data is to be stored, what data is to be stored, and the maximum number of records stored in each log file. Click
Data and Event
Log
on the home page of the Web-based configuration utility to
configure these settings (see
Figure 86
).
Note
: You need Administrator or Manager privileges to configure data and event logging
.
Data Log
Record
Enable
Name
Each entry in this table specifies a block of registers to be included in the log. To add an entry, click Add
Entry and fill in the Name, First Register, and Count information. Select the Enable checkbox to enable data logging for the block. You can configure up to 100 register blocks. Use Delete to remove an entry that you no longer want.
For a configuration example, see
Figure 87
and
Table
11
.
When this checkbox is selected, data logging is enabled for this block of registers. When it is cleared, a placeholder symbol “-” is stored to the log file.
Name to appear in the column heading within the log file to identify data for this entry. If no name is entered, the register number is used as the column heading.
First
Register
Count
Address of the first register to be logged.
Number of registers to be logged.
Event Log
Config uration
These settings apply only to modules that have the
915U-AT (Audit Trail) feature key enabled. Event Logging is discussed in a separate document.
The configuration example in see
Figure 87
will log six registers in
each log record.
Table 111
shows an example of the logged data for this configuration.
Figure 86. Data and Event log Configuration
Data log configuration
Scan Rate Enter the rate that you want data to be recorded
(fastest rate is every 5 seconds).
Records per
File
Enter the maximum number of records you want in a file (up to 3,000 records per file). When the maximum is reached, the file is archived and a new data log file is created.
62 EATON
www.eaton.com
Figure 87. Data log record
Table 11. Data log example
Time stamp
Analog
01
2018-04-08 03:43:47 10476
2018-04-08 03:43:47 10623
Analog
02
33921
33923
2018-04-08 03:43:47 13923
2018-04-08 03:44:02 10451
2018-04-08 03:44:07 10773
33918
33922
33927
0
0
0
0
1
Discrete
01
1
1
1
0
1
Discrete
02
1
1
0
0
0
Discrete
03
1
0
0
1
1
Discrete
04
Viewing current data
To view the latest logged data, click
Logs and Archives
on the home page of the Web-based configuration utility. The latest data is shown in a “.csv” format on the screen.
415U Condor-long-range wireless I/O and gateway
User Manual MN032006EN
Effective May 2018 recognize the USB drive, check to make sure that the drive is formatted with FAT file system and that it contains a directory named “logs”.
When the USB drive is recognized, the module copies the data log files to the USB drive. Once all files are copied, the OK LED turns solid green. The data log files are not deleted from the module when they are copied to USB drive.
If the module encounters an error or if the USB drive does not have sufficient space to fit all of the files, the OK LED turns solid red to indicate a failure. Remove the USB drive and try another one until the files are successfully transferred and the OK LED turns green.
Figure 88. Log information
Retrieving logged data
The module supports remote retrieval of files via HTTP, as well as local retrieval of files via USB flash drive.
To retrieve logged data files via HTTP
1. Click
Logs and Archives
on the home page of the Web-based configuration utility.
2. Click the link “Click to download data log files.”
This displays a listing of all of the stored data log files. Files are named with the time and date created and the module serial number, in the format yyyymmddhhmmss-nnnnnnnnnnn-DAT.log.
Figure 90. USB port
5. Remove the USB drive from the module USB port.
The log files are contained in a directory under the “logs” directory. This subdirectory is named with the module device name, or the module serial number if no device name was configured for the module. The device name is configured on the
Module Information configuration page. The following example shows the contents of a USB drive after retrieving log files from a module. In this example, the module serial number is
01234567837.
Figure 89. Data log listing
3. Right-click the file that you want to retrieve.
4. Click
Save Target as
to save the file to your local computer.
To retrieve logged data files using a USB drive
1. Make sure that the USB drive is formatted for a FAT file system.
This is the normal file system on USB drives.
2. Create a directory named “logs” (all lowercase) on the
USB drive.
3. Using a small screwdriver, open the hatch on the side of the module.
4. Plug the USB drive into the USB Host port (see
Figure 900
).
Within 10 seconds, the module should recognize the USB drive and the OK LED should flash red-green. If the module does not
Figure 91. Log file directory on USB drive
You can leave the files on the USB drive. The next time you plug in the USB drive, only the new files are retrieved from the module.
You can also use the same USB drive to retrieve data from multiple modules. The data for each module is stored in a separate directory.
If you configure your modules with a device name, the data is stored in a directory with that name. Take care that each module has a unique device name. Data from modules with the same device name will be stored in the same directory.
Retrieving stored log file data
The log files are stored in comma-separated-value (.csv) format.
To increase storage space, each log file is compressed using the
Tar-Gzip method when it is stored to internal flash memory. The log files can be opened and the compressed .csv files recovered using an archive manager, such as 7-Zip, that can operate with Tar-Gzip
(.tgz) files.
EATON
www.eaton.com
63
