User manual . concentrate on what is most important for you – your business.

Data logging with ORION

Our InD, OutD and HelpD series are designed to

complement each other. InD stands for indoor power
systems, while OutD solutions are created for demanding
outdoor use. HelpD is our global support team; its task is
to make everything easy for you.

www.deltapowersolutions.com
3791363100_00
Table of contents
1 About this document ........................................................................................... 2
2 Description of the log function ............................................................................ 3
2.1 Running criteria ........................................................................................ 3
2.1.1 Continuous log ........................................................................... 3
2.1.2 Event controlled log ................................................................... 3
2.1.3 Energy log .................................................................................. 4
2.2 Sampling .................................................................................................. 4
2.3 Logged measurements ............................................................................ 5
2.4 Logged events .......................................................................................... 5
2.5 Dynamically captured events ................................................................... 5
2.6 Dynamically captured system messages ................................................. 5
2.7 File splitting ............................................................................................ 17
2.8 File naming ............................................................................................. 18
2.9 File export............................................................................................... 18
2.10 Behaviour in case not having enough storage memory available ......... 18
3 Using the log function ....................................................................................... 19
3.1 Setting up a new log ............................................................................... 19
3.1.1 Adding a new log configuration................................................ 19
3.1.2 Adding a description to the new log configuration ................... 19
3.1.3 Selecting the logged measurement and logged events .......... 19
3.1.4 Configuring the sampling criteria ............................................. 20
3.1.5 Configuring the dynamic event capturing ................................ 20
3.1.6 Configuring the log files ........................................................... 21
3.1.7 Configuring the control events ................................................. 21
3.1.8 Starting up the log .................................................................... 21
3.2 Editing a log configuration ...................................................................... 22
3.3 Viewing a log .......................................................................................... 22
3.3.1 Viewing the content of a log file ............................................... 22
3.3.2 Viewing the setup of a log configuration .................................. 22
3.4 Exporting a log file to PC ........................................................................ 23
3.5 Deleting a log ......................................................................................... 23
3.5.1 Deleting a single log file ........................................................... 23
3.5.2 Deleting a log configuration ..................................................... 23

Data logging with ORION Table of contents

1 About this document
This document has been created for ORION software version V5.10. The document is
updated only when necessary when new software versions are released.

This document provides information to assist in using the versatile and advanced data
and event log function of the controller ORION.

The first part of the document, the chapter 2 "Description of the log function", provides an
overview about the logging function, its capabilities and the configuration possibilities.
The latter part provides step by step instruction to the usage of the log function.

2 Data logging with ORION About this document

2 Description of the log function
The log function is used to store the system history in a persistent way. This functionality
writes measurements, events and inbuilt system messages to log files. The user has the
possibility to create several different log configurations. Each log configuration has a
name, a description, a set of measurements and events to be logged as well as the
sampling criteria and rules for the log files management.

The ORION can handle up to 18 user defined log configurations and additionally there is
a Default Log to store system messages.

2.1 Running criteria

The running criteria define the start and stop conditions for a log configuration. The user
can choose from three alternatives: “Continuous”, “Event controlled” and “Energy”.

2.1.1 Continuous log

The “Continuous” log runs always, except if manually paused or stopped by the user.
After a controller reset or configuration upload, a stopped log restarts automatically. As
long as the file splitting condition is not met the log entries are stored in the same file.

This type of log can be used to record the system voltage or battery temperature
variations along the system life.

2.1.2 Event controlled log

The event controlled log runs and records entries when the chosen control event is active
(true) unless it is manually stopped or paused by the user. When the event is inactive
(false), then the log is idle, and no entries will be recorded.

The user must select a control event from the available configured events, in order to
command the running or idle state of a log.

Useful control events are for example “battery test active” and timer and latch type of
events.

In addition to the control event, the user can define a save event. If the save event is
used, the recorded data is saved only in case the save event is activated while the log is
running. In other words, all the log entries that have been recorded when the log was
running will be discarded if the save event has not been active (true) during this time.

A save event can be used for example with the natural battery test, where the log entries
need to be stored only if the “S NaturalBT” event changes to true during the mains failure.

Every time the control event is activated and a log state changes to “running”, it is
considered as a new log sequence. The user can define where the log entries of a new
sequence will be stored:

Data logging with ORION Description of the log function 3

 • Append to existing file means that the new log entries will be saved in the
same file as the last sequence. Note that it is not possible to select this option
when a save event is configured.

• Overwrite existing file means the log file of the last sequence will be deleted
and the log entries of the new sequence will be written into a new log file.

• Start new file means the new log entries will be saved into a new file, the files
of the older sequences will remain in the storage memory.

The option “Start new file” is useful with battery test data in order to separate the test
results into different log files.

When the ORION restarts and the configured control events are active at this time, then it
is considered as a new log sequence, not as a continuation of the preceding sequence
before the ORION was restarted. As a consequence, if the file management condition
“Start new file” is selected, a new log file is created for the new log entries, or if the file
management condition “Overwrite existing file” is selected, the latest log file is cleared
and a new log file is created for the new log entries.

2.1.3 Energy log

In some countries the operators share the basic infrastructure of the sites including the
power supply system. A tower operating company or one of the operators owns the
power supply system and sells energy to the other users. Therefore, the energy supplied
to each load string needs to be measured separately by the system controller.

Some power systems contain renewable energy components like solar converters and/or
wind turbines. To monitor the obtained energy, the respective visualization and statistics
functions are implemented. Following values are logged:

• Energy today
• Energy of the last 30 days. Each day is listed separately.
• Energy this month
• Energy of the last 12 months. Each month is listed separately.
• Energy this year
• Energy of the last years. Each year is listed separately.

All of these values are logged separately per energy measurement.

2.2 Sampling
The sampling criteria define when to generate a log entry. There are two sampling criteria
to choose from and they can also be used at the same time.

• When Fixed interval sampling is chosen, the log entries are captured based
on the time interval defined in the log configuration.

• When Measurement based sampling is chosen, the log entries are captured
whenever the change in a selected measurement exceeds the delta-threshold
defined in the log configuration.

4 Data logging with ORION Description of the log function

 For an energy log, the sampling type cannot be chosen.

2.3 Logged measurements

The user can select any of the available measurements in the ORION to be logged. The
number of Logged Measurements selected plus the number of Logged Events selected
cannot be more than 32.

2.4 Logged events

The user can select any of the defined events to be logged. The status of the event is
stored as “True” or “False”. The number of Logged Measurements selected plus the
number of Logged Events selected cannot be more than 32.

2.5 Dynamically captured events

The user can select up to 128 events that will be captured immediately as their state
changes. This happens dynamically and independently from the sampling.

2.6 Dynamically captured system messages

System messages are automatically captured to the default log, but the user has a
possibility to define that they are also recorded in a user defined log. The system events
will be recorded in the same way as the captured events.

The following table gives an overview about the existing system messages and their
meaning:

Name Description

OTA: Invalid URL

OTA: Unable to resolve Address

OTA: Server not reachable

OTA: HTTP Error

OTA information
OTA: File Too Big

OTA: Nothing transferred

OTA: Request accepted

Check file failed

Load file aborted

Load file successfully terminated

File Transfer information
Load file successfully, ORION
will reboot.

Data logging with ORION Description of the log function 5

 Process file failed

Load file aborted. Reason: write

access denied

Load file aborted. Reason:

Modem disconnected

File transfer rejected. Already a

transfer running.

System restart Always done after power up of ORION

Buzzer HW Failure If Buzzer is configured, but no UIM is present

Recharge Failed

Loss of Backup Time detected

Equalize Started

Equalize Finished

Equalize Aborted Battery string information

Boost Charge Started

Boost Charge Finished

Boost Charge Failed

Battery Test Successful – Final

Voltage = xx

Battery Test Ok Final Volt. = xx

Battery Test Ended –

Discharged Capacity = xxx

Battery Test Failed - Idiff

Battery Test Failed – Middle

Point Battery Test information

Battery Test Failed – Usupport

Battery Test Started – Manual

Battery Test Started – Periodic

Battery Test Aborted – Manual

Battery Test Aborted – Load

Failure

6 Data logging with ORION Description of the log function

 Battery Test Aborted – Event
Ctrl Charge

Battery Test Aborted – Inhibit

Event

Natural Battery Test Failed –

Time = xxx

Natural Battery Test Successful

– Voltage = xxx

Natural Battery Test – Voltage

Reached = xxx

Natural Battery Test – Duration

Expired = xxx

Middle Point Measurement Battery Middle point information

Failed

Tdiff Failed

Idiff Charge Failed Battery measurements

Idiff Discharge Failed

Separate charge mode entered

Separate discharge started

Separate charge started

Separate Charge information
System voltage reached

Separate charge mode left

Event controlled charge started

Event Controlled Charge information
Event controlled charge finished

Battery Life prediction information

Life Prediction Warning, The battery life has reached the notification limit.
Remaining Days < Notification

Life Prediction Failure, The battery life is coming to an end.

Remaining Days = 0

Life Prediction Reset The battery installation date has been reset.

Life Prediction Disabled The battery life prediction has been disabled.

CAN Error IMBUS I – HW Imbus information

Failure

Data logging with ORION Description of the log function 7

 APOSYS information
APOSYS HW Failure Communication with APOSYS has failed

APOSYS HW Failure – ok Communication with APOSYS is ok again

APOSYS Real Time Clock

RTC present but not operational
Failure

APOSYS Incompatible with the

configuration System Interface Board HW failures

APOSYS Digital Inputs Nbr not

compatible

APOSYS Temp Meas Nbr not

compatible

APOSYS Middle Point Meas

Nbr not compatible

APOSYS Digital Output Nbr not

compatible

APOSYS Open Collector Nbr

not compatible

APOSYS LVD Output Nbr not

compatible

APOSYS Shunt Meas Nbr not

compatible

APOSYS Shunts not available

for NGS

BIST HW Failure Built In Self Test failure

RM Power Limitation Started Rectifier Functions information

RM Power Limitation Finished

RM Redundancy lost

RM Redundancy restored

RM Lack of Power

RM Recharge Power OK

Current Sharing Error <RFM Rectifier current sharing information

name>

Current Sharing Error <RFM

name> -ok

8 Data logging with ORION Description of the log function

 Time changed System time has been changed

Setup information
Setup cleared Setup has been cleared

Setup saved Setup has been saved

Invalid License Key entered

SNMP Feature activated with

License Key License Keys information

SMS Alarming Feature activated

with License Key

TOC: Failed to build up GPRS

connection.

TOC: DNS-Address is empty

TOC: DNS-Address not

reachable.

TOC: Domain-Name not

resolved.

TOC: Server not reachable.

TOC: Data not sent

TOC: Data sent successfully.

TOC protocol information
TOC: Mapping Table empty.

TOC: Incompatible mapping

entry

TOC: SMS sent

TOC: SMS received

TOC: Invalid SMS received

TOC: Mapping File Invalid

TOC: No TOC Protocol active

TOC: Authentication Failed

SMS protocol information

An action requiring the SMS protocol to be active has
SMS: No SMS Protocol active been performed, but the SMS protocol was not

Data logging with ORION Description of the log function 9

 SMS Received: <phone
number>;<SMS text>
SMS: Incompatible mapping
entry: <text>
SMS: Mapping File Invalid:
<text>
Modbus Slave: No Modbus
Protocol active
Modbus Slave: Mapping File
Invalid: <text>
Modbus Slave: Incompatible
mapping entry: <text>
Low storage memory
Out of storage memory
[MEASX] Symmetry Failure
[MEASX] Symmetry Failure – ok
DCDC Redundancy lost
DCDC Redundancy restored
MODBUS Com Failure
Dial-out Connection Established
Dial-out Connection Terminated
Dial-out Connection Failure
GPRS Connection Established
GPRS Connection Terminated
GPRS Connection Failure
Dial-in Connection Established
Dial-in Connection Terminated
Dial-in Connection Failure
PPP Connection Failure
10
active.
This log contains a validated SMS that received by
the system and was modifying the local setup.
The SMS mapping file contains an invalid entry. The
text contains details of the incompatible entry.
The SMS mapping file is invalid. The text gives
details on the reason for invalidity.
Modbus Slave protocol information
An action requiring the Modbus Slave protocol to be
active has been performed, but the Modbus Slave
protocol was not active.
The Modbus Slave mapping file is invalid. The text
gives some details on the reason for invalidity.
Indicates that the Modbus Slave mapping file
contains an invalid entry. The text contains details of
the incompatible entry.
More than 80 % of the storage memory is used.
More than 96 % of the storage memory is used.
Symmetry information
DCDC information
GWM module information
Modem information
Data logging with ORION Description of the log function
 PPP Connection Ok

Send SMS Failure

Send SMS Buffer Full

Receive SMS Buffer Full

Initialization Modem Failure

PIN Code Modem Failure

Initialization Modem Ok

PIN Code Modem Ok

GSM NITZ Synchronisation

Failure

GSM FITZ Synchronisation Ok

Hardware Failure information

[element] HW Failure Element is missing or not properly connected

[element] HW Failure – ok Element is ok again

Name Description

OTA: Invalid URL

OTA: Unable to resolve Address

OTA: Server not reachable

OTA: HTTP Error

OTA information
OTA: File Too Big

OTA: Nothing transferred

OTA: Request accepted

Check file failed

Load file aborted

Load file successfully terminated

File Transfer information
Load file successfully, ORION
will reboot.

Process file failed

Load file aborted. Reason: write

access denied

Load file aborted. Reason:

Modem disconnected

Data logging with ORION Description of the log function 11

 File transfer rejected. Already a
transfer running.

System restart Always done after power up of ORION

Buzzer HW Failure If Buzzer is configured, but no UIM is present

Recharge Failed

Loss of Backup Time detected

Equalize Started

Equalize Finished

Equalize Aborted Battery string information

Boost Charge Started

Boost Charge Finished

Boost Charge Failed

Battery Test Successful – Final

Voltage = xx

Battery Test Ok Final Volt. = xx

Battery Test Ended –

Discharged Capacity = xxx

Battery Test Failed - Idiff

Battery Test Failed – Middle

Point Battery Test information

Battery Test Failed – Usupport

Battery Test Started – Manual

Battery Test Started – Periodic

Battery Test Aborted – Manual

Battery Test Aborted – Load

Failure

Battery Test Aborted – Event

Ctrl Charge

Battery Test Aborted – Inhibit

Event

Natural Battery Test Failed –

12 Data logging with ORION Description of the log function

 Time = xxx

Natural Battery Test Successful

– Voltage = xxx

Natural Battery Test – Voltage

Reached = xxx

Natural Battery Test – Duration

Expired = xxx

Middle Point Measurement Battery Middle point information

Failed

Tdiff Failed

Idiff Charge Failed Battery measurements

Idiff Discharge Failed

Separate charge mode entered

Separate discharge started

Separate charge started

Separate Charge information
System voltage reached

Separate charge mode left

Event controlled charge started

Event Controlled Charge information
Event controlled charge finished

Battery Life prediction information

Life Prediction Warning, The battery life has reached the notification limit.
Remaining Days < Notification

Life Prediction Failure, The battery life is coming to an end.

Remaining Days = 0

Life Prediction Reset The battery installation date has been reset.

Life Prediction Disabled The battery life prediction has been disabled.

CAN Error IMBUS I – HW Imbus information

Failure

APOSYS information
APOSYS HW Failure Communication with APOSYS has failed

APOSYS HW Failure – ok Communication with APOSYS is ok again

APOSYS Real Time Clock

Data logging with ORION Description of the log function 13

 Failure RTC present but not operational

APOSYS Incompatible with the

configuration System Interface Board HW failures

APOSYS Digital Inputs Nbr not

compatible

APOSYS Temp Meas Nbr not

compatible

APOSYS Middle Point Meas

Nbr not compatible

APOSYS Digital Output Nbr not

compatible

APOSYS Open Collector Nbr

not compatible

APOSYS LVD Output Nbr not

compatible

APOSYS Shunt Meas Nbr not

compatible

APOSYS Shunts not available

for NGS

BIST HW Failure Built In Self Test failure

RM Power Limitation Started Rectifier Functions information

RM Power Limitation Finished

RM Redundancy lost

RM Redundancy restored

RM Lack of Power

RM Recharge Power OK

Current Sharing Error <RFM Rectifier current sharing information

name>

Current Sharing Error <RFM

name> -ok

Time changed System time has been changed

Setup information
Setup cleared Setup has been cleared

14 Data logging with ORION Description of the log function

 Setup saved
Setup has been saved

Invalid License Key entered

SNMP Feature activated with

License Key License Keys information

SMS Alarming Feature activated

with License Key

TOC: Failed to build up GPRS

connection.

TOC: DNS-Address is empty

TOC: DNS-Address not

reachable.

TOC: Domain-Name not

resolved.

TOC: Server not reachable.

TOC: Data not sent

TOC: Data sent successfully.

TOC protocol information
TOC: Mapping Table empty.

TOC: Incompatible mapping

entry

TOC: SMS sent

TOC: SMS received

TOC: Invalid SMS received

TOC: Mapping File Invalid

TOC: No TOC Protocol active

TOC: Authentication Failed

SMS protocol information

SMS: No SMS Protocol active
SMS Received: <phone
number>;<SMS text>
SMS: Incompatible mapping
entry: <text>
An action requiring the SMS protocol to be active has
been performed, but the SMS protocol was not
active.
This log contains a validated SMS that received by
the system and was modifying the local setup.
The SMS mapping file contains an invalid entry. The
text contains details of the incompatible entry.

Data logging with ORION Description of the log function 15

 SMS: Mapping File Invalid:
<text>
Modbus Slave: No Modbus
Protocol active
Modbus Slave: Mapping File
Invalid: <text>
The SMS mapping file is invalid. The text gives
details on the reason for invalidity.
Modbus Slave protocol information
An action requiring the Modbus Slave protocol to be
active has been performed, but the Modbus Slave
protocol was not active.
The Modbus Slave mapping file is invalid. The text
gives some details on the reason for invalidity.

Modbus Slave: Incompatible Indicates that the Modbus Slave mapping file
mapping entry: <text> contains an invalid entry. The text contains details of
the incompatible entry.

Low storage memory More than 80 % of the storage memory is used.

Out of storage memory More than 96 % of the storage memory is used.

[MEASX] Symmetry Failure Symmetry information

[MEASX] Symmetry Failure – ok

DCDC Redundancy lost DCDC information

DCDC Redundancy restored

MODBUS Com Failure GWM module information

Dial-out Connection Established

Dial-out Connection Terminated

Dial-out Connection Failure

GPRS Connection Established

GPRS Connection Terminated

Modem information
GPRS Connection Failure

Dial-in Connection Established

Dial-in Connection Terminated

Dial-in Connection Failure

PPP Connection Failure

PPP Connection Ok

Send SMS Failure

Send SMS Buffer Full

16 Data logging with ORION Description of the log function

 Receive SMS Buffer Full

Initialization Modem Failure

PIN Code Modem Failure

Initialization Modem Ok

PIN Code Modem Ok

GSM NITZ Synchronisation

Failure

GSM FITZ Synchronisation Ok

Hardware Failure information

[element] HW Failure Element is missing or not properly connected

[element] HW Failure – ok Element is ok again

Any not listed system message may indicate an internal error.

2.7 File splitting

In order to limit a log file to an acceptable size, the log files will be split into several files
when defined criteria are met. The user can choose from two different strategies for
splitting a log files:

• If circular buffer is selected, the log file splitting is deactivated. Therefore the
Log is limited to one log file. When the limit is reached, the newest log entry
overwrites the oldest one, as it would be the case for a ring buffer.

• If limit number of entries is selected, the number of log entries per log file
will be limited by a set parameter Max Entries per file. As soon as the limit is
reached, the log entries recording is continued in a new log file. The older log
file is kept in storage memory.

For an energy log file splitting cannot be chosen. Everything is stored in one file.
Exceptions:

• User stops and starts an energy log.

• The selected measurements don’t match the measurements stored in log file,
e.g. after restore setup.

A log configuration can have up to 20 log files. When this limit is reached, the oldest log
file will be deleted before creating a new one.

Data logging with ORION Description of the log function 17

2.8 File naming
The log file names are generated based on the log name and six digit number. The log
file extension is set to “.csv”.

Every time a new log file for a log configuration is created, six digit number in its name is
increased by one. When no log file exists, then the first number is the number 000001.

2.9 File export

The user can export any log file to a PC. The log file is exported in CSV format; therefore
it can be imported in any spreadsheet program.

2.10 Behaviour in case not having enough storage memory

available
The ORION monitors the available storage memory used to store the files. Out of that,
ORION calculates the usage ratio in %. This value is shown on the log overview page. If
the memory usage exceeds 80 % a system message “Low storage memory” is
generated. If the memory usage exceeds 96 %, the event “S Storage Out of Memory” will
be activated, and a system message “Out of storage memory” is generated.

During the “Out of storage memory” state, most of the log configurations will not be able
to record new log entries. Nonetheless, Default Log and Log which overwrites older
samples still continue recording as long there is still some storage memory left.

In order to free up some storage memory, the user may delete some old log files, or
delete running log files having a big size. Some other unnecessary files may also be
deleted from the file manager web page.

If the information in the file is important to the user, then the file may be uploaded to an
external storage before deleting it from the ORION storage memory.

18 Data logging with ORION Description of the log function

3 Using the log function

3.1 Setting up a new log

Use this procedure to add and configure the functionality of a new log configuration.

3.1.1 Adding a new log configuration

Use this procedure to add a new log configuration

Step 1 Go to Home → Log → Setup.

Step 2 Select the log type “Event controlled” or “Continuous” or “Energy” from drop-
down list.

Step 3 Click “Add”.

Step 4 Give name for the log.

Step 5 Select the control event from drop-down if “event controlled” is used.

Step 6 Click “Accept Changes”.

3.1.2 Adding a description to the new log configuration

Use this procedure to add a description of the log configuration.

Step 1 Click “Edit” button of the new log configuration on the page Home → Log →
Setup.

Step 2 Write the description of the log in the Description field on the Log Editor page
that has automatically opened.

Step 3 Click “Accept Changes” to save the description.

3.1.3 Selecting the logged measurement and logged events

Use this procedure to select the logged measurements and events.

Step 1 Click “Logged Measurement Selection”.

Step 2 Select the measurements to be logged and click “Add”.

Step 3 Click “Back” when the selection is done.

Step 4 Click “Logged Events Selection”.

Step 5 Select event to be logged and click “Add”.

Data logging with ORION Using the log function 19

 Step 6 Click “Back” when the selection is done.

3.1.4 Configuring the sampling criteria

Use this procedure to define when the samples are recorded.

Step 1 Enable either Measurement Based Sampling or Fixed Interval Sampling or both
of them.

Step 2 Click “Accept Changes” to save the selection.

Step 3 If Measurement Based Sampling is enabled, click “Change” to select the

measurement to be used for triggering the sampling from drop-down list.

Step 4 Click “Accept Changes” to confirm the selection and return to Log Editor page.

Step 5 Set the value for the delta threshold in the field “When Changed at least”.

Step 6 If the Fixed Interval Sampling is enabled, set the value for the sampling interval.

Step 7 Click “Accept Changes” to save the sampling parameters.

3.1.5 Configuring the dynamic event capturing

Use this procedure to define which events are captured immediately when their status
changes.

Step 1 Click “Capture Events Selection”.

Step 2 Select the events from the list and click “Add”.

Step 3 Click “Back” when all desired events are visible in the list of Selected Captured
Events.

Step 4 Select “Capture all System Messages” if you want to include all system
messages in this log.

Step 5 Click “Accept Changes”.

Note! The system messages are automatically logged into the Default Log.

20 Data logging with ORION Using the log function

3.1.6 Configuring the log files

Use this procedure to select the language, to define how many entries are stored in a file
and what happens when the limit is reached.

Step 1 Select the language from the drop-down list.

Step 2 Select either “circular buffer” or “limit entries” to the File Splitting strategy.

Step 3 Set the value for “Max Entries per File”.

Step 4 Click “Accept Changes”.

3.1.7 Configuring the control events

Use this procedure to select the start and save events and to define what happens when
the log restarts.

Note! This procedure is not needed if the log type is “Continuous”.

Step 1 Select the Control Event from the drop-down list.

Step 2 Select the Save event from the drop-down list.

Step 3 Select either “append to existing file”, “overwrite existing file” or “start new file” to
define the behaviour when the log restarts.

Step 4 Click “Accept Changes”.

Note! If no Save Event is selected, the log file will be automatically saved.

3.1.8 Starting up the log

Use this procedure to start the new log configuration.

Step 1 Go to Home → Log → Setup.

Step 2 Click “Start” button of the new log configuration.

Data logging with ORION Using the log function 21

3.2 Editing a log configuration
Use this procedure to change some of the settings of a log configuration.

Step 1 Go to Home → Log → Setup.

Step 2 Click “Stop” to stop the log configuration you need to edit.

Step 3 Click “Edit” to open the editor page.

Step 4 Click “Accept Changes” when all the changes are done.

Step 5 Click “Back” to return.

Step 6 Click “Start” button on the page Home → Log → Setup.

3.3 Viewing a log

3.3.1 Viewing the content of a log file

Use this procedure to view the content of a log file.

Step 1 Go to Home → Log → Status.

Step 2 Click “Files” of the log configuration you are interested in.

Step 3 Click “View” to see the content of the selected file.

Step 4 Click “Back” to return to the file list.

3.3.2 Viewing the setup of a log configuration

Use this procedure to view the setup of a log configuration.

Step 1 Go to Home → Log → Status.

Step 2 Click “Setup” of the log configuration you are interested in.

Step 3 Click “Back”.

22 Data logging with ORION Using the log function

3.4 Exporting a log file to PC
Use this procedure to export a log file to PC.

Step 1 Go to Home → Log → Status.

Step 2 Click “Files” of the log configuration you are interested in.

Step 3 Click the link “Save to PC” of the log file you want to export.

Step 4 Follow the instructions on the screen.

3.5 Deleting a log

3.5.1 Deleting a single log file

Use this procedure to delete a single log file.

Step 1 Go to Home → Log → Status.

Step 2 Click “Files” of the log configuration you are interested in.

Step 3 Check the “Delete” box beside the file you want to delete.

Step 4 Click “Accept Changes”.

3.5.2 Deleting a log configuration

Note! You need to delete all the files of a log configuration first before the log
configuration can be deleted.

Use this procedure to delete the files of a log configuration.

Step 1 Go to Home → Log → Setup.

Step 2 Click “Stop” button of the log configuration you want to delete.

Step 3 Go to Home → Log → Status.

Step 4 Click “Files” of the log configuration you want to delete.

Step 5 Check the “Delete” box beside each file.

Step 6 Click “Accept Changes”.

Use this procedure to delete the log configuration.

Data logging with ORION Using the log function 23

 Step 1 Go to Home → Log → Setup.

Step 2 Select the check box “Delete” of the log configuration you want to delete.

Step 3 Click “Accept Changes”.

Note! It is not possible to delete the Default Log.

24 Data logging with ORION Using the log function

 Our mission is to provide
innovative, clean and
energy-efficient solutions
for a better tomorrow.

5010740800_00
*5010740800*