E!c ApplicationNote WagoAppDatalogger

e!
COCKPIT Application note
Building
Automation
WAGO-I/O-SYSTEM 750
WagoAppDatalogger
Version 1.0.0
2 e!COCKPIT Application Note – WagoAppDatalogger
WAGO-I/O-SYSTEM 750
© 2017 by WAGO Kontakttechnik GmbH & Co. KG

All rights reserved.
WAGO Kontakttechnik GmbH & Co. KG
Hansastraße 27
D-32423 Minden
Phone: +49 (0) 571/8 87 – 0

Fax: +49 (0) 571/8 87 – 1 69
Email: info@wago.com
Online: http://www.wago.com
Technical Support
Phone: +49 (0) 571/8 87 – 5 55

Fax: +49 (0) 571/8 87 – 85 55
Email: support@wago.com
Every conceivable measure has been taken to ensure the accuracy and
completeness of this documentation. However, as errors can never be fully
excluded, we always appreciate any information or suggestions for improving the
documentation.
We wish to point out that the software and hardware names, as well as the
trademarks of companies used and/or mentioned in the present document, are
generally protected by trademark or patent.
Version 1.0.0
e!COCKPIT Application Note – WagoAppDatalogger 3
WAGO-I/O-SYSTEM 750 Description
Information about This Documentation
Copyright
This documentation, including all figures and illustrations contained therein, is
subject to copyright protection. Any use of this documentation that infringes upon
the copyright provisions stipulated herein is prohibited. Reproduction, translation,
electronic, photo-technical filing/archiving and any amendments require the
written consent of WAGO Kontakttechnik GmbH & Co. KG, Minden, Germany.
Non-observance will entail the right of claims for damages.
WAGO is a registered trademark of WAGO Verwaltungsgesellschaft mbH.
Number Notation
Table 1: Number Notation
Number System Example Comment
Decimal 100 Normal notation
Hexadecimal 0x64 C notation
Binary '100' In single quotes,
'0110.0100' nibble separated by a period
Font Conventions
Table 2: Font Conventions
Font Type Explanation
italic Names of paths and files are shown in italics, e.g.:
C:\Programs\WAGO-I/O-CHECK
Menu Menu options are shown in bold, e.g.,:
Save
> A “greater than” symbol between two names denotes the selection of
a menu option, e.g.:
File > New
Input Names of input or selection fields are shown in bold, e.g.:
Start of measurement range
“Value” Input or selection values are shown in quotation marks, e.g.:
Enter the value “4 mA” under Start of measurement range.
[Button] Button labels within the dialogs are bold and enclosed in square
brackets, e.g.:
[Input]
[Key] Key labels on the keyboard are shown in bold and enclosed in square
brackets, e.g.:
[F5]
Version 1.0.0
Description WAGO-I/O-SYSTEM 750
Symbols
DANGER Warning against personal injury!

Indicates a high-risk, imminently hazardous situation which, if not avoided,
will result in death or serious injury.
DANGER Do not work on components while energized!

Indicates a high-risk, imminently hazardous situation which, if not avoided,
will result in death or serious injury.
WARNING Warning against personal injury!

Indicates a moderate-risk, potentially hazardous situation which, if not
avoided, could result in death or serious injury.
CAUTION Warning against personal injury!

Indicates a low-risk, potentially hazardous situation which, if not avoided,
may result in minor or moderate injury.
ATTENTION Warning against damage to property!

Indicates a potentially hazardous situation which, if not avoided, may result
in damage to property.
ESD Warning against damage to property caused by electrostatic discharge!

(Electrostatic Indicates a potentially hazardous situation which, if not avoided, may result
Discharge) in damage to property.
Note Important note!

Indicates a potential malfunction, but one which will not result in damage to
property if not avoided.
Information Additional information

Refers to additional information which is not an integral part of this
documentation (e.g., the Internet).
Version 1.0.0
Legal Principles
Subject to Change
WAGO Kontakttechnik GmbH & Co. KG reserves the right to make any
alterations or modifications that serve the purpose of technical progress. WAGO
Kontakttechnik GmbH & Co. KG owns all rights arising from granting patents or
from the legal protection of utility patents. Third-party products are always
mentioned without any reference to patent rights. Thus, the existence of such
rights cannot be excluded.
Personnel Qualification
The use of the product described in this document is exclusively geared to
specialists having qualifications in PLC programming, electrical specialists or
persons instructed by electrical specialists who are also familiar with the
appropriate current standards.
Moreover, the persons named here must also be familiar with all of the products
cited in this document, along with the operating instructions. They must also be
capable of correctly predicting any hazards which may not arise until the products
are combined.
WAGO Kontakttechnik GmbH & Co. KG assumes no liability resulting from

improper action and damage to WAGO products and third-party products due to
non-observance of the information contained in this document.
Limitation of Liability
This documentation describes the use of various hardware and software
components in specific example applications. The components may represent
products or parts of products from different manufacturers. The respective
operating instructions from the manufacturers apply exclusively with regard to
intended and safe use of the products. The manufacturers of the respective
products are solely responsible for the contents of these instructions.
The sample applications described in this documentation represent concepts, that

is, technically feasible applications. Whether these concepts can actually be
implemented depends on various general conditions. For example, different
versions of the hardware or software components may require different handling
than that described here. Therefore, the descriptions contained in this
documentation do not form the basis for assertion of a particular product
characteristic.
Responsibility for safe use of a specific software or hardware configuration lies

with the party that produces or operates the configuration. This also applies if one
of the concepts described in this document was used for implementation of the
configuration.
WAGO Kontakttechnik GmbH & Co. KG assumes no liability for the realization
of these concepts.
Version 1.0.0
Description WAGO-I/O-SYSTEM 750
Table of Contents
Table of Contents................................................................................................... 6
1 Description .................................................................................................... 7
2 Material Used ............................................................................................... 7
2.1 Required Libraries ..................................................................................... 7
2.2 Devices ...................................................................................................... 7
2.3 Tools .......................................................................................................... 7
3 Structure ....................................................................................................... 8
4 Commissioning and Use .............................................................................. 9
4.1 Variable Declaration ............................................................................... 12
4.2 Important Notes about the Storage Medium ........................................... 12
4.3 Offline Parameterization ......................................................................... 14
4.4 Connection of Function Block ................................................................ 15
4.5 Use and Important Information ............................................................... 16
4.6 Setting the CSV Formats ......................................................................... 17
4.6.1 Standard Format ................................................................................. 17
4.6.2 Econ Format ....................................................................................... 17
4.6.3 Dataplotter Format.............................................................................. 18
4.7 Setting Up the FTP Connection .............................................................. 20
5 Diagnostics .................................................................................................. 21
6 Visualizations.............................................................................................. 22
6.1 Setting Up the Visualizations .................................................................. 22
6.2 Explanations of the Visualizations .......................................................... 25
Version 1.0.0
1 Description
The WagoAppDatalogger library makes data logging of up to 160 channels
possible. At the desired interval and/or if an event occurs, the measured values of
the channels are written to a CSV file in three different formats. The main element
of the library is the FbDatalogger function block. This executes the required
operations and controls the “Datalogger_Compact” visualization element also
contained in the library.
2 Material Used
2.1 Required Libraries
Library Description
WagoAppDatalogger Library with the data logger functionality
Util Library with various ancillary functions; used in this

application note to generate different signals.
2.2 Devices
Supplier Quantity Designation Item No.
WAGO 1 PFC200 Controller; 750-8202

2 x ETHERNET, RS-232/-485
WAGO 1 8-channel analog input; 0/4 … 20 mA; 750-496

single-ended
WAGO 1 16-channel digital input; 24 VDC; 3 ms 750-1405
WAGO 1 16-channel digital output; 24 VDC; 0.5 A 750-1504
WAGO 1 End module 750-600
2.3 Tools
Designation Item No.
2759-101/
e!COCKPIT workstation license
1110-2002
Version 1.0.0
Structure WAGO-I/O-SYSTEM 750
3 Structure
Figure 1: Sample Node Configuration
Note Node configuration

No specific node configuration is required for use of the
WagoAppDatalogger library. The configuration illustrated above is
selected as an example. The modules may be exchanged and expanded as
required by the respective application.
Version 1.0.0
WAGO-I/O-SYSTEM 750 Commissioning and Use
4 Commissioning and Use

Pos: 34 /Dokumentation allgemein/Muster/Inbetriebnehmen - Konfigurieren - Parametrieren/Strukturmuster Hauptkapitel "Inbetriebnehmen" @ 12\mod_1339747278173_6.doc @ 97667 @ @ 4
The following eight steps are simplified instructions for integrating the function
block in the project. Starting in Section 4.1, some of these steps are described in
detail, and other noteworthy features of the library explained.
1) Integration of the WagoAppDataplotter library:

Program Structure > Applications > select target application > Library
Manager > [Add Library]
Search for WagoAppDatalogger in the dialog and confirm the selection

with [OK].
Figure 2: Library Integration
2) Adding the FbDatalogger function block
Figure 3: Adding the Function Block
Version 1.0.0
Commissioning and Use WAGO-I/O-SYSTEM 750
3) Set up the function block connection.
Declaration of the required variables of type FbDatalogger and
typConfigDatalogger
Figure 4: Function Block Connection
Note RETAIN PERSISTENT

The data array on the “aValues” input and the block configuration on the
“typConfigParameters” input should be declared as RETAIN
PERSISTENT so the data will be retained after a controller reset, and also
after a download.
4) Log in and start the program.
5) Set channel and base settings online via the “typConfigDatalogger” type
structure (alternative: see Sec.4.3).
a. Set the desired CSV format as follows:
1
i. .bDatalogger_type = 1 for default data logger
1
ii. .bDatalogger_type = 2 for the Econ format
1
iii. .bDatalogger_type = 3 for the Dataplotter format: specific to
the “Dataplotter” Web application
A detailed description of the various CSV formats is provided in Sec.
4.6.
b. Channel is ignored by FbDatalogger unless 2.xChannelExists =
“TRUE.”
1
c. .sFilename must end with “.csv.”
1
typConfigParameters
2
typConfigParameters.atypChannelConfig[…]
Version 1.0.0
1
d. .sPath should be an existing directory (“/media/sd/” corresponds to
the SD card of the 750-820x controller)
Figure 5: Set up Channels and Configure Settings
6) Apply changes with “xActivate” = “FALSE” > “xActivate” = “TRUE”

(function block reset).
Figure 6: Function Block Reset
7) To start cyclic data logging, set 1.xCyclicLogging to TRUE. Event-controlled

data logging is always available and triggered by a positive edge on the
“xEvent” input.
Version 1.0.0
Figure 7: Activation of Cyclic Logging
8) The function block is now in operation. If necessary, the library contained in

the visualization can also be integrated. Section 6 explains how to set up and
integrate the visualization.
Pos: 35 /Alle Serien (Allgemeine Module)/Überschriften für alle Serien/Inbetriebnehmen - Konfigurieren - Parametrieren/Konfigurieren - Überschrift 2 @ 12\mod_1339747993273_6.doc @ 97679 @ 2 @ 1
4.1 Variable Declaration

Note The library contains the required data types. The data types are described in
the function block description (open help with [F1]) and in the library itself.
The latter description can be viewed via the library manager.
To have the right settings after power failures and reloading the program, it is
recommended that you declare the two following variables as VAR RETAIN
PERSISTENT (see Step 3 above).
The input of the “aValues” function block requires an ARRAY
[1..MAX_CHANNELS] OF REAL as a variable. This variable contains all input
values for the channels to be logged, of which there can be up to 80.
Note The MAX_CHANNELS parameter can be set to a value ≤ 160 via the
library parameter list according to the number of channels used. Advantage:
A smaller global constant results in lower memory requirements and a
shorter internal sequence for the function block. For example, if only
channels 1 to 20 are required, the MAX_CHANNELS parameter can be set
to 20.
The input of the “typConfigParameters” function block requires a variable of

type typConfigDatalogger. This variable contains the basic information for the
FbDatalogger module and ensures usability without visualization.
4.2 Important Notes about the Storage Medium

The default value of the typConfigDatalogger.sPath parameter is “/media/sd”
and corresponds to the SD card directory of the 750-8x0x controller.
Note Use SD card

Only save data to removable media, because permanently saving to the
internal Flash memory destroys the controller!
The possible paths for the storage medium are listed in the table below according
to the controller used:
Version 1.0.0
Table 3: Path for the Storage Medium According to the Controller

Controller Path for the Storage Medium
750-88x “s:\”
750-8x0x (PFC) “/media/sd/”
Due to the limitation on the maximum number of files in the root directory of the
storage medium, the FbDatalogger function block forces a subdirectory called
“CSV_Files” in which the CSV files are stored. If the 1.sPath file path already
contains a subdirectory, it remains unchanged. The 1.sPath file path specified is
adjusted automatically.
Examples:
Table 4: Automatic Adaptation of the Specified Path (Standard and Econ Format)
Specified Path Adapted Path
“/media/sd/logfile.csv” “/media/sd/CSV_Files/logfile.csv”
“/media/sd/Day1/logfile2.csv” “/media/sd/Day1/logfile2.csv”
“s:\Temp.csv” “s:\CSV_Files\Temp.csv”
“s:\Logging\logfile.csv” “s:\Logging\logfile.csv”
If the Dataplotter format is selected (1.bDatalogger_type = 3), the “CSV_Files”

directory is always used as the subdirectory in 1.sPath:
Table 5: Automatic Adaptation of the Specified Path (Dataplotter Format)
Specified Path Adapted Path
“/media/sd/logfile.csv” “/media/sd/CSV_Files/logfile.csv”
“/media/sd/Day1/logfile2.csv” “/media/sd/CSV_Files/Day1/logfile2.csv”
“s:\Temp.csv” “s:\CSV_Files\Temp.csv”
“s:\Logging\logfile.csv” “s:\CSV_Files\Logging\logfile.csv”
Note:
The FbDatalogger function block checks whether a folder with the adapted
1
.sPath file path already exists. If not, the FbDatalogger function block creates
this folder automatically.
Version 1.0.0
4.3 Offline Parameterization

Assignments must be created to set up the channels and make settings without
first starting the program. The assignments should be organized as shown below
to avoid blocking changes via the visualization.
1) Creation of an action via: right-click on program > Add a New Element >
Action > Enter Name > [ST] > [Add]
Figure 8: Create Action
2) Entering the required assignments

a. Creating an IF statement for one-time initialization of the values
i. Initial value of the Boolean variable = “TRUE”
ii. After processing, set variable to “FALSE.”
iii. Assignments within the statement are only executed after the
program is restarted.
iv. Measurement values must be assigned outside the IF statement
to ensure continuous updating.
b. Creating assignments as required
Version 1.0.0
Figure 9: Assignment for typConfigParameters
3) Integrating the action into the parent program (before FbDatalogger):
Figure 10: Open Action in Program
4.4 Connection of Function Block

To use the function block, the signal on the “xActivate” input must be set to
“TRUE.” The “xEvent” and “typConfigParameters” input/output variables also
have to be connected with their associated variables The data to be logged must be
created on the “aValues” input. Cyclic logging at a specific interval and/or event-
based logging (triggering via events) can be used if needed.
Version 1.0.0
4.5 Use and Important Information

After the program starts, the channel parameterization can be processed. If you
open the variable of type “typConfigDatalogger,” you can edit all channels as
needed. For the function block to detect a channel, the included 2.xChannelExists
variable of the respective channel must be set to“TRUE.” The function block
always has to be reset after adding and removing channels with that variable for
the changes to apply. The “xActivate” input variable must be set to “FALSE” and
then back to “TRUE.”
The header of the LOG file in which the channels are named is only created once.
If the number of channels or their names change, a new file must be created to
ensure proper formatting. The same applies to the channel-specific 2.xLogAlarm
option. The header includes an alarm column, which is created only once. If
2
.xLogAlarm changes without a new file being created, the entries move through
the unexpected, added or removed alarm column. It follows that a new file must
be created when there are changes to the 2.xChannelExists, 2.sChannelName and
2
.xLogAlarm channel variables. A new file is created if no file of this name
exists. Consequently, either the old file must be deleted or the file name must be
changed to allow a new file and header to be generated.
The logging operation of the function block can be executed at a fixed time
interval or by means of trigger event. If you set the 1.xCyclicLogging variable to
“TRUE,” writing to the file occurs at the specified interval. The interval factor is
stored in the 1.uiIntervalFactor variable and the associated unit in the 1.bInterval
variable (hours = 1, minutes = 2, seconds = 3). Even during cyclic writing, the
“xEvent” trigger (block input) can be set and can trigger a logging operation if
necessary. It is necessary to ensure that “xEvent” is only set if “xReady” outputs a
“TRUE” to avoid possible complications with an open file. The shortest possible
interval setting is one second. The only time limit for logging via Event is the
“xReady” output. If the intervals for the channels differ, the function block must
be instantiated. Several function blocks writing to one file is not recommended;
therefore, an individual file name should be used for each function block.
If you set 1.xAppendDate to “TRUE,” the controller date is automatically
appended to the file name entered. Because the file name changes daily, a new file
is generated every day.
Pos: 36 /Dokumentation allgemein/Muster/Inbetriebnehmen - Konfigurieren - Parametrieren/Strukturmuster Hauptkapitel "Inbetriebnehmen", Unterkapitel "Konfigurieren" @ 12\mod_1339747405738_6.doc @ 97671 @ @ 4
Pos: 37 /Alle Serien (Allgemeine Module)/Überschriften für alle Serien/Inbetriebnehmen - Konfigurieren - Parametrieren/Parametrieren - Überschrift 2 @ 5\mod_1249376820406_6.doc @ 40252 @ 2 @ 1
Pos: 39 /Dokumentation allgemein/Gliederungselemente/---Seitenwechsel--- @ 3\mod_1221108045078_0.doc @ 21808 @ @
Information Block description

The meanings of the variables available for each channel can be found in the
function block description (open help with [F1] or see description in the
library manager).
Version 1.0.0
4.6 Setting the CSV Formats

The formatting of the entries in the file is designed for a tabular view. The “.csv”
file format can be opened in editor programs such as Notepad, MS Word and MS
Excel. When the storage media is removed from the controller, the write process
must first be stopped to prevent file errors.
The CSV file can be opened in Excel via: File > Open… > select the respective
file.
The FbDatalogger function block can create the CSV file in three different
formats.
4.6.1 Standard Format

This format can be selected by setting the 1.bDatalogger_type input of the
FbDatalogger function block to “1” (default).
Figure 11 shows the CSV file format. Channels 1 (Sinus Curve) and 2 (sawtooth)
are expanded with alarm columns. Channel 37 (CH – 37) was paused at the time
of saving, so the associated cells were marked with “OFF.” The column separator
in the CSV file can be adjusted using the 1.sColumnSeparator variable. The
semicolon “;” is used in this format by default. The decimal separator can be
adjusted using the 1.sDecimalSeparator variable. The comma “,” is used by
default.
Figure 11: Example of the CSV File in Standard Format
4.6.2 Econ Format

This format can be selected by setting the 1.bDatalogger_type parameter to “2.”
Compared to the standard format (see Section 4.6.1), the Econ format lacks the
Alarm column. As shown in Figure 12, the unit of each channel is entered once
with the channel name. Channel 4 was paused at the time of saving, so the
corresponding cells were labeled with a space.
The column separator in the CSV file can be adjusted using the
1
.sColumnSeparator variable. The semicolon “;” is used in this format by
Version 1.0.0
default. The decimal separator can be adjusted using the 1.sDecimalSeparator
variable. The comma “,” is used by default.
Note Special features of the Econ format
If the Econ format is selected, the minimum time interval for the logging
operation is one minute. Then the “Seconds” selection option is no longer
shown in the visualization.
The file name entered in the 1.sFileName variable is adjusted automatically:

The date is always added at the beginning of the file name, and only upper
case letters are used, e.g.: 2015_11_28_LOGFILE.CSV.
Figure 12: Example of the CSV File in Econ Format
4.6.3 Dataplotter Format

This format is specific to the “Dataplotter” Web application and can be selected
by setting the 1.bDatalogger_type parameter to “3.”
Compared to the standard format (see Section 4.6.1), the Dataplotter format lacks
the alarm column. As shown in Figure 13, the unit of each channel is entered once
with the channel name. Channel 4 was paused at the time of saving, so the
corresponding cells were labeled with a space. The comma “,” is used in this
format as the column separator. The period “.” is used as the decimal separator.
The 1.sColumnSeparator and 1.sDecimalSeparator parameters are ignored in
this format.
Version 1.0.0
Figure 13: Example of a CSV file in Dataplotter Format
“_dp” is always added to the file name. This prevents any confusion between
different CSV formats in a file (usually due to setting the 1.bDatalogger_type
during the write operation without changing the file name).
Note Maximum file size
A new file is always generated when the specified size of 25 MB is reached.
Version 1.0.0
4.7 Setting Up the FTP Connection

To open the completed files, an FTP connection via ETHERNET is recommended
in addition to removing the storage media. Setting up “FileZilla,” the free FTP
client, to read the SD card is explained in Figure 14.
Figure 14: FTP SD Card, 750-8202

Pos: 40 /Alle Serien (Allgemeine Module)/Überschriften für alle Serien/Diagnose - Service/Diagnose - Überschrift 1 @ 4\mod_1240831069471_6.doc @ 31370 @ 1 @ 1
Version 1.0.0
WAGO-I/O-SYSTEM 750 Diagnostics
5 Diagnostics
Pos: 41 /Dokumentation allgemein/Muster/Diagnose - Service/Strukturmuster Hauptkapitel "Diagnose" @ 12\mod_1339747130109_6.doc @ 97663 @ @ 4
The “xReady” output outputs a “TRUE” provided that no file is open for writing
at the respective time. This output is critical when using the trigger via event
option, because a pulse should only be sent if the previous write operation has
been completed.
The “sStatus” output outputs the status of the function block as a string. If
problems arise during processing of the function block, error messages are output
to the “sStatus” output.
Version 1.0.0
Visualizations WAGO-I/O-SYSTEM 750
6 Visualizations
The visualization object contained in the library provides a simple overview of the
current channels and some settings options for ongoing operation. This object is
only for support and makes it possible to change only part of the existing settings
of the function block.
6.1 Setting Up the Visualizations

The WagoAppDatalogger library contains the Datalogger_Compact
visualization object for the FbDatalogger block. To integrate it into a project, the
following steps are necessary:
1) Creating a visualization page. To do this, right-click on the application and

then select [Visualization].
Figure 15: Create Visualization Page
Version 1.0.0
WAGO-I/O-SYSTEM 750 Visualizations
2) Integrate configuration interface:
Open the visualization page created previously. Then open the [Tools] tab on
the right edge of the screen.
Click [WagoAppDatalogger] to view the visualization elements contained in
the library.
In the selection window, select the Datalogger_Compact element and drag
and drop it onto the visualization page.
After you place it there, a dialog opens, which can be closed by clicking the
[Cancel] button.
Figure 16: Integrate Configuration Interface
Version 1.0.0
3) After the visualization element is placed, it should be linked to the
FbDatalogger function block. To do so, select the visualization element and
open the [Properties] tab.
Elements to be linked are displayed under “Referenced visualizations.” Here
the required variables and blocks (in this case, the FbDatalogger function
block) can be selected with the Input Assistant ([...] button) and assigned to
the configuration interface (see Figure 17).
Figure 17: Placeholder Setup
4) After successful assignment, the application can be loaded and started.
Version 1.0.0
6.2 Explanations of the Visualizations

The Datalogger_Compact visualization element displays up to 160 channels with
their current measurement values. Only active channels are displayed. Besides the
visual display, the user interface can be used to modify some parameters of the
data logger that are stored in the “typConfigParameters” type variable. The
functions in the user interface are explained below.
1 2 3 4
Channel
overview
5
Figure 18: Datalogger_Compact Visualization Interface
1 Cyclic Logging In this section, the cyclic logging interval can be

adjusted. A factor can be entered, and the
associated unit (hour/minute/second) can be
selected. The [Start/Stop] button makes it
possible to activate/deactivate cyclic logging.
2 Manual Logging The [Trigger] button triggers a one-time logging of

the current data.
Version 1.0.0
3 CSV Settings Clicking the [Configuration] button opens the

following dialog:
Figure 19: CSV Settings Dialog
General settings of the CSV file can be edited in

the upper section of the dialog. Besides the target
format (Standard/Econ/Dataplotter), the column
and decimal separators and the date/time format
can be set here.
The lower table lists the active channels. The name,
unit, number of decimal places, alarm monitoring
activation and upper and lower alarm limits of each
channel can be parameterized.
The two buttons in the upper right corner can be
used to save (green symbol) or discard (red
symbol) the changes and close the dialog.
4 File Information The storage path and CSV file name can be
adjusted in this section. It is also possible to specify
whether the current date should be appended to the
file name.
Version 1.0.0
Channel overview The tabular overview displays the most important

information for up to 160 channels. The current
log status is visualized in the first column (logging
active/inactive). The following columns display
the channel name, current measurement value and
unit.
The last three columns show the alarm monitoring
status (active/inactive) and the alarm limit
settings. If a channel value outside the alarm value
range has occurred, the entire channel row is
highlighted in red.
Clicking on a channel opens the following dialog
with detailed information.
Figure 20: Channel Details Dialog
In the dialog, the [Pause/Resume] button above

the data table can be used to pause/reactivate the
channel logging. The most recently logged
measurement values (together with their time and
date stamps) are visualized in the table.
The red symbol in the upper right corner can be
used to close the dialog.
5 Status bar Besides the current time and storage path of the
CSV file, the status bar indicates the current status
of the cycling logging process (in plain text and
symbolically).
Version 1.0.0
WAGO Kontakttechnik GmbH & Co. KG
PO Box 2880 • D-32385 Minden
Hansastraße 27 • D-32423 Minden
Phone: +49 (0) 571/8 87 – 0
Fax: +49 (0) 571/8 87 – 1 69
Email: info@wago.com
Web: http://www.wago.com

E!c ApplicationNote WagoAppDatalogger

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

E!c ApplicationNote WagoAppDatalogger

Uploaded by

Copyright:

Available Formats

e!

COCKPIT Application note

© 2017 by WAGO Kontakttechnik GmbH & Co. KG

WAGO Kontakttechnik GmbH & Co. KG

Phone: +49 (0) 571/8 87 – 0

Phone: +49 (0) 571/8 87 – 5 55

Information about This Documentation

DANGER Warning against personal injury!

DANGER Do not work on components while energized!

WARNING Warning against personal injury!

CAUTION Warning against personal injury!

ATTENTION Warning against damage to property!

ESD Warning against damage to property caused by electrostatic discharge!

Note Important note!

Information Additional information

WAGO Kontakttechnik GmbH & Co. KG assumes no liability resulting from

The sample applications described in this documentation represent concepts, that

Responsibility for safe use of a specific software or hardware configuration lies

WagoAppDatalogger Library with the data logger functionality

Util Library with various ancillary functions; used in this

WAGO 1 PFC200 Controller; 750-8202

WAGO 1 8-channel analog input; 0/4 … 20 mA; 750-496

WAGO 1 16-channel digital input; 24 VDC; 3 ms 750-1405

WAGO 1 16-channel digital output; 24 VDC; 0.5 A 750-1504

WAGO 1 End module 750-600

Figure 1: Sample Node Configuration

Note Node configuration

4 Commissioning and Use

1) Integration of the WagoAppDataplotter library:

Search for WagoAppDatalogger in the dialog and confirm the selection

Figure 2: Library Integration

2) Adding the FbDatalogger function block

Figure 3: Adding the Function Block

Figure 4: Function Block Connection

Note RETAIN PERSISTENT

4) Log in and start the program.

Figure 5: Set up Channels and Configure Settings

6) Apply changes with “xActivate” = “FALSE” > “xActivate” = “TRUE”

Figure 6: Function Block Reset

7) To start cyclic data logging, set 1.xCyclicLogging to TRUE. Event-controlled

Figure 7: Activation of Cyclic Logging

8) The function block is now in operation. If necessary, the library contained in

4.1 Variable Declaration

The input of the “typConfigParameters” function block requires a variable of

4.2 Important Notes about the Storage Medium

Note Use SD card

Table 3: Path for the Storage Medium According to the Controller

750-8x0x (PFC) “/media/sd/”

If the Dataplotter format is selected (1.bDatalogger_type = 3), the “CSV_Files”

4.3 Offline Parameterization

Figure 8: Create Action

2) Entering the required assignments

Figure 9: Assignment for typConfigParameters

3) Integrating the action into the parent program (before FbDatalogger):

Figure 10: Open Action in Program

4.4 Connection of Function Block

4.5 Use and Important Information

Information Block description

4.6 Setting the CSV Formats

4.6.1 Standard Format

Figure 11: Example of the CSV File in Standard Format

4.6.2 Econ Format

Note Special features of the Econ format