DOCA0142EN-10

Device Logging

Introduction

The Device Logging page provides the graphic and table representations of the log data of the circuit breaker connected to the IFE interface. For more details on configuring device logging, refer to Device Logging.

Single Device Pages

Step

Action

Result

1

From the IFE menu bar, click Monitoring .

Opens the Monitoring menu.

2

From the Monitoring menu, click Device Logging .

Displays the available device logging choices.

3

From the Device Logging , click Single Device Pages .

Displays the available device with logged data available for viewing.

4

Select the device from the Device List .

Displays the device log for the selected device.

5

To view a data range, select a period range from the period range drop-down list:

  • Last Full Day

  • Last Full Week

  • Last Full Month

  • All

Plots the selected period range.

6

Hold the left mouse button and drag a selection box around a graph area to zoom in on it.

Zooms in on the selected graph area.

7

To return to the original full view, enter Z on your keyboard, or double-click the graph.

The view zooms out.

8

Click Data Points to view the selected interval data log table.

Opens the selected Interval Data Log table.

9

To view different topics, click New Topic(s) . Enable the check boxes of the topics to be displayed, and click Apply .

Enables the display of the selected topics.

The data logged from the circuit breaker is displayed in a webpage in a time-trend chart format. The time-trend chart is preconfigured to display data from the Last Full Day , Last Full Week , Last Full Month , or All .

Energy parameters are logged as accumulating values but are displayed as incremental values on an interval basis. All other parameters are logged and displayed as the actual value recorded.

Retrieving a Data Log

Interval data logs can be retrieved using the methods given in the following table:

Retrieval Method

File Format Retrieved

IFE FTPS server

Comma-separated variable (CSV)

Export to an external FTPS server

CSV

Data point option

HTML

Email

CSV

To view the list of all the available log files, follow steps 2 to 4 in the section Getting an Interval Data Log using FTPS . Files are in the format: Device Name.csv where the device name is the name given to the device. For example, a device named building 1 utility entrance is Building 1 Utility Entrance.csv.

When the log files are exported, the date and time are appended to the file name in the following format: _YYYYMMDDHHMMSS. For example, Building 1 Utility Entrance_20100218115216.csv. This indicates that the file was exported on 2010 February 18 at 11:52:16 AM.

NOTE:
  • The circuit breaker status in log file is coded by numbers. For information on circuit breaker status, refer to the description of the Modbus register 12001 in the Modbus Communication Guides in Related Documents.

  • The device log file may contain invalid values (-9999, -99999, 32768) for electrical parameters based on the data read from the device.

Log Format

Data is logged in the CSV file with the following format:

Row

Data in CSV Format

Description

1

IFE name, IFE serial number, IFE address, device name, device local ID, device type name, logging interval.

This row contains the column headings for the information in row 2.

2

IFE 555, 23227,157.198.184.116, building1 utility entrance, 893, MasterPacT MTZ ,15

This row contains the information about the IFE interface and the logged device.

3

This row is blank.

4

,,,topic id 1,topic id 2,topic id 3

This row contains the column headings for the topic IDs in row 5. A topic ID is a numerical reference to the quantity being logged. Topic IDs are used to identify the quantity, regardless of the device or language. The first three commas are used for layout purposes in a spreadsheet application.

5

,,,1617,1621,1625

This row contains the topic IDs of the values logged.

6

This row is blank.

7

Error, UTC offset (Minutes), local time stamp, apparent energy (kVAh), real energy (kWh), reactive energy (kVARh)

This row contains the column headings for the data logged in rows 8 and higher.

8 and higher

These rows contain the logged data.

0,-300,2008-10-09 14:15:00,1400738.219,1201962.707,647069.906,15

0,-300,2008-10-09 14:20:00,1400758.260,1201980.725,647078.602,15

0,-300,2008-10-09 14:25:00,1400778.198,1201998.661,647087.233,15

If a spreadsheet application is used to view the CSV file, data should look similar to the interval data log opened in a spreadsheet application.

Error Codes for Data Logs

The following error codes may be seen when troubleshooting data logs:

Error Code

Definition

19

Communication error occurred (for example: CRC, protocol, or exception).

25

Timeout occurred when a request was sent without receiving a corresponding response within the allowed time.

38

Invalid data.

100

Interval time expired before data could be recorded.

101

Invalid local time stamp. IFE is not set with absolute time.

Contact technical support if you need assistance in resolving these or other error conditions.

Retrieving Data Log Using IFE FTPS Server

You can use IFE FTPS server to retrieve a data log file by connecting to the IFE interface via FTPS and transferring the .csv file, as shown in the following steps:

NOTE: If you want the IFE interface to send the data log file via FTPS automatically, the device log export must be configured for FTPS.

Step

Action

Result

1

Create a folder on your PC, such as C\:file_logs.

Creates a folder to store the IFE data log.

2

Launch Windows Explorer, enter ftps:// and the IP address of the IFE interface in the address text box (for example, ftps://169.254.0.10), press Enter .

Opens the Log On As dialog box.

3

Enter the user name as Administrator and password as Gateway in the text boxes, click Log On .

Opens an FTPS session with the IFE interface and displays the files stored in the IFE interface.

4

Navigate to the directory/logging/data on the IFE interface.

Opens the data logging directory on the IFE interface.

5

Copy the log file and paste it into the folder created in step 1.

Copies the data log to the folder.

Retrieving Data Log Using the Data Points Option

Step

Action

Result

1

From the Device Logging webpage, click Data Points .

Opens a new window displaying the logged data.

2

Press CTRL+A, then press CTRL+C.

Selects all of the data and copies the data to the clipboard.

3

Open Excel, then press CTRL+V.

Pastes the data into an Excel spreadsheet.

Retrieving Data Log Using Email

The IFE interface must be configured to deliver data logs to an email address. For more information, refer to Email Export.

Summary Device Pages

The summary device view provides the summary of the circuit breaker connected to the IFE interface.

Step

Action

Result

1

From the Monitoring menu, click Device Logging .

Displays the available device logging choices.

2

Under Device Logging , click Summary Device Page .

3

Under Summary Device Pages , click Single Topic, Multiple Devices .

Opens the setup page for selecting the device and topics.

4

Select the device from the Available Devices list.

Displays the available topics for the selected device.

5

Select a topic from the Available Topics list.

Displays the selected topic for the selected device.

6

Hold the left mouse button and drag a selection box around a graph area to zoom in on it.

Zooms in on the selected graph area.

7

To return to the original full view, enter Z on the keyboard, or double-click the graph.

The view zooms out.

8

Repeat steps 3 through 7 to display other topics of the selected device.

Displays the selected topic for the selected device.

The topic logged from the selected device is displayed in a webpage in a time-trend chart format. The time-trend chart is preconfigured to display data from the last full day, last full week, and last full month.

Energy parameters are displayed as incremental values on an interval basis. All other parameters are logged and displayed as the actual value recorded.

QR Code is a registered trademark of DENSO WAVE INCORPORATED in Japan and other countries.

Was this helpful?