Dataloggers Configuration Manual - v1.1

Table of contents
1. INVENTIA MT-723 DATALOGGER..................................................

1.1.
DESCRIPTION......................................................................................1
1.2.
CONFIGURATION..................................................................................2
2. FTP TRANSFERS......................................................................
2.1.
SERVER
CONFIGURATION......................................................................12
2.2.
CLIENTS
CONFIGURATION.....................................................................12
2.3.
MANUAL
EXECUTION...........................................................................13
2.4.
AUTOMATIC
2.5.
LOG
EXECUTION........................................................................13
FILE.........................................................................................14
3. DLFILECONV...........................................................................
3.1.
DESCRIPTION....................................................................................16
3.2.
CONFIGURATION FILES........................................................................16
3.3.
MANUAL STARTUP..............................................................................18
3.4.
AUTOMATIC STARTUP..........................................................................19
3.5.
LOG
FILE.........................................................................................20
4. SCADA...................................................................................
4.1.
OBJETIVES........................................................................................21
4.2.
GRAPHIC
4.3.
FACEPLATES (GRAPHICS).......................................................................22
4.4.
FILE DL_STUDY_VXX..........................................................................23
4.5.
REAL TIME DATA................................................................................23
4.6.
IAS APPLICATION OBJECTS....................................................................24
4.7.
HISTORICAL
OBJECTS IN THE PHYSICAL NET....................................................21
DATA...............................................................................24
Dataloggers configuration manual v1.0
1.
INVENTIA MT-723 DATALOGGER
1.1. DESCRIPTION
This type of datalogger is managed by 2 software applications: MT Manager (which includes
MT Spooler) and MT DataProvider.
MT Manager is used to read/write the usual settings (e.g. GPRS configuration,

inputs/outputs to be read, counters and timers) to the datalogger. Especially for the battery
modules MT Spooler application is used for reading/writing to the dataloggers. This spooler
waits for the moment when the datalogger wakes up and in this moment it makes the
wanted changes.
MT DataProvider can run as an application or as a service. The main settings are contained
in the .xml file named in our case OPCconfig.
Usually all settings are done locally, by a laptop with a USB cable attached to the
datalogger.
For Gorj Project, initial settings were made locally, after that we read all the setting in MT
Manager.
It is important to have in Startup the MTManager and is good to be assured that the
MT_OPC (MT Data Provider) and MTSsWinService4 (MTspooler4) services are started in
automatic mode.
ApaRegio Supervizare si control colectare date (SCADA)
1.2. CONFIGURATION
To configure the datalogger the following steps should be done:
1. Creating a new module
2. Introducing the module IP
3. Reading the dataloggers configuration
All the following print scripts are made in the moment in which we have a report at every
1 h (CT3) and the reading is made at every 5 min (CT1).
The final value of CT3 (the time period for sending the .csv files) was set at 24 hours.
For the .csv files configuration we will need to complete 3 files from C:\Program Files
(x86)\InVentia\MTopc2: mt_aliases where we can change the syntax of the variales,
mt_log_filter where we can introduce only the variables we need to receive into .csv files,
OPCconfig.xml file which contains all parameters regarding the dataloggers (module IP,
module serial number). Also we must complete the startfile with C:\Program Files
(x86)\InVentia\MTopc2\OPCconfig.xml.
mt_aliases file contents (an example from Trgu Crbuneti):
PM18--DL.REGL2,lIndexFwd
PM18--DL.REGL4,lIndexRev
PM18--DL.AIL2,lRTC_HMS
PM18--DL.AI7,iMT_ALM
PM18--DL.AI10,iDebitFwd
PM18--DL.AI11,iDebitRev
PM18--DL.AI15,iPresiune
PM18--DL.AIL18,lALM_LH
PM18--DL.AI21,iBattVolt
PM18--DL.AI24,iGSM_STATE
mt_log_filter file contents (an example from Trgu Crbuneti):
PM18--DL.lIndexFwd
PM18--DL.lIndexRev
PM18--DL.lRTC_HMS
PM18--DL.iMT_ALM
PM18--DL.iDebitFwd
PM18--DL.iDebitRev
PM18--DL.iPresiune
PM18--DL.lALM_LH
PM18--DL.iBattVolt
PM18--DL.iGSM_STATE
PM19--DL.lIndexFwd
PM19--DL.lIndexRev
PM19--DL.lRTC_HMS
PM19--DL.iMT_ALM
PM19--DL.iDebitFwd
PM19--DL.iDebitRev
PM19--DL.iPresiune
PM19--DL.lALM_LH
PM19--DL.iBattVolt
PM19--DL.iGSM_STATE
PM20--DL.lIndexFwd
PM20--DL.lIndexRev
PM20--DL.lRTC_HMS
PM20--DL.iMT_ALM
PM20--DL.iDebitFwd
PM20--DL.iDebitRev
PM20--DL.iPresiune
PM20--DL.lALM_LH
PM20--DL.iBattVolt
PM20--DL.iGSM_STATE
OPCconfig.xml file contents (an example from Trgu Crbuneti):
<?xml version="1.0"?>
<opc>
<configure net_mode="dynamic" udp_port="7110" timestamp="system"

csv_log="true"
csv_path="D:\DATA\Dataloggers\Files\"
odbc_log="false"
odbc_source="myodbc" odbc_user="" odbc_password="" odbc_write="1" log_filter="true"
aliases="true"
debug_file_type="daily_log"
updateable="false" debug="false"/>
restore="true"
backup_time="5"
<network
name="PM18"
ip_receiver=""
udp_port=""
ip_header_receiver="023.012.014.004"
ip_header_sender="255.255.255.255"
timeout="12"
retries="3"
module_type="mt723"
update="false"
add_crc="true"
csv_msg_log="logger" odbc_msg_log="false" dreg_order="lo_hi" expire_time="11000"
debug="false" enable="true">
<modbus name="DL"
id="1" type="analog_inputs"
format="long4" interval="0" debug="false" enable="true"/>
address="2"
size="1"
<modbus name="DL"
format="int2" interval="0" debug="false" enable="true"/>
address="7"
size="1"
<modbus name="DL"
address="10"
size="2"
<modbus name="DL" id="1" type="analog_inputs" address="15" size="1"

<modbus name="DL"
address="21"
size="1"
<modbus name="DL"
address="24"
size="1"
<modbus
name="DL"
id="1"
type="registers"
address="2"
size="2"
</network>
<network
name="PM19"
ip_receiver=""
udp_port=""
timeout="12"
retries="3"
module_type="mt723"
update="false"
add_crc="true"
<modbus name="DL"
address="2"
size="1"
<modbus name="DL"
address="7"
size="1"
<modbus name="DL"
address="10"
size="2"

<modbus name="DL"
address="21"
size="1"
<modbus name="DL"
address="24"
size="1"
<modbus
name="DL"
id="1"
type="registers"
address="2"
size="2"
</network>
<network
name="PM20"
ip_receiver=""
udp_port=""
timeout="12"
retries="3"
module_type="mt723"
update="false"
add_crc="true"
<modbus name="DL"
address="2"
size="1"
<modbus name="DL"
address="7"
size="1"
<modbus name="DL"
address="10"
size="2"

<modbus name="DL"
address="21"
size="1"
<modbus name="DL"
address="24"
size="1"
<modbus
name="DL"
id="1"
type="registers"
address="2"
size="2"
</network>
</opc>
10
If we are using MT Data provider to set up the dataloggers, the use of MT Manager is not
necessary. The only task that is needed is starting mt_opc as Service and File as shown
below:
Anyway, the OPC configuration from MT Manager may look as follows:
11
2.
FTP TRANSFERS
2.1. SERVER CONFIGURATION

Administrative Tools > Internet Information Services (IIS) Manager
The FTP server was already configured to transfer files between SCADA and BI modules,
using the folder C:\GorjTraspaso as the working directory. To transfer datalogger files, the
DL_Inbox virtual directory has been added pointing to the path D:\DATA\DL\Inbox. This
path is where the datalogger driver program DLFileConv expects to find the datalogger files
to load.
2.2. CLIENTS CONFIGURATION

To transfer files the Windows command line FTP client is used. Because it will be running
periodically in an unattended manner, a batch process has been written to manage the files
upload and log the results.
The following folder structure has been created on every workstation under D:\DATA\FTP:
12
backup: stores the original files sent to the server
log: log file (ftp.log) with all the FTP transfers and its result
shells: scripts including the batch process (uploadTgJiu1.bat) and the FTP commands
(tgjiu1.ftp)
2.3. MANUAL EXECUTION

Can be started from the Windows Command Processor or from the Windows Explorer.
2.4. AUTOMATIC EXECUTION

An automatic task has been configured in the Task Scheduler to run every 5 minutes:
13
2.5. LOG FILE

Whether executed manually or automatically the following log file is created.
ftp.log:
Sat 12/01/2012
1:38:04.52 - Process start: 546 files will be uploaded
Sat 12/01/2012
1:38:07.12
D:\DATA\FTP\backup\
Sat 12/01/2012
Process
stop:
File/s
uploaded
succesfully,
moving
file/s
14
to
Sat 12/01/2012
1:43:04.36
D:\DATA\FTP\backup\
Sat 12/01/2012
Process
stop:
File/s
uploaded
succesfully,
moving
file/s
15
to
3.
DLFILECONV
3.1. DESCRIPTION
This module has been implemented as an independent application that should be always
running. Their functions are:
-
Parse files located in the folder defined in the InboxPath setting: at program startup and when a file is uploaded by the scripts described in the previous chapter, it
parses the contents of the file
Generate an historical file with the format expected by Wonderware Historian at

folder defined in the HistoryOutboxPath setting
Update the real-time file with the values obtained from the last parsed history
records at the folder defined in the RealtimeOutboxPath setting
If the above steps success move the original file to the folder defined in the
BackupPath setting and otherwise move it to the folder defined in the BadPath
setting
3.2. CONFIGURATION FILES

By default the program
(x86)\Adasa\DLFileConv
is
installed
in
the
following
path:
C:\Program
files
The application loads configuration from the following files:

-
DataloggerFilesConversor.exe.config: settings related to the folders that the application

will use which are described above
NLog.config: log-related settings such as the log file path
datalogger-location.lst: settings to configure the datalogger list linked with its location
The default contents of the configuration files are copied below.
16
DataloggerFilesConversor.exe.config:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<configSections>
<sectionGroup name="userSettings" type="System.Configuration.UserSettingsGroup,
System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" >
<section name="DataloggerFilesConversor.Properties.Settings"
type="System.Configuration.ClientSettingsSection, System, Version=2.0.0.0,
Culture=neutral, PublicKeyToken=b77a5c561934e089"
allowExeDefinition="MachineToLocalUser" requirePermission="false" />
</sectionGroup>
</configSections>
<userSettings>
<DataloggerFilesConversor.Properties.Settings>
<setting name="InboxPath" serializeAs="String">
<value>D:\DATA\DL\inbox</value>
</setting>
<setting name="RealtimeOutboxPath" serializeAs="String">
<value>D:\DATA\DL\outbox_RT</value>
</setting>
<setting name="HistoryOutboxPath" serializeAs="String">
<value>D:\DATA\DL\outbox_HIST</value>
</setting>
<setting name="BackupPath" serializeAs="String">
<value>D:\DATA\DL\backup</value>
</setting>
<setting name="BadPath" serializeAs="String">
<value>D:\DATA\DL\bad</value>
</setting>
</DataloggerFilesConversor.Properties.Settings>
</userSettings>
</configuration>
NLog.config:
<?xml version="1.0" encoding="utf-8" ?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">


<targets>
<target name="logfile"
xsi:type="File"
layout="${longdate}|${level:uppercase=true}|${message}"
fileName="D:\DATA\DL\log\DLFileConv.log"
archiveFileName="D:\DATA\DL\log\archives\DLFileConv.{#}.log"
archiveEvery="Month"
archiveNumbering="Rolling"
maxArchiveFiles="12"
concurrentWrites="true"
keepFileOpen="false"
encoding="iso-8859-2" />
</targets>
<rules>
<logger name="*" minlevel="Info" writeTo="logfile" />
</rules>
</nlog>
17
datalogger-location.lst:
PM12|BUMDT
PM25|TICDT
PM13_1|BUMDT
PM26|TICDT
PM13_2|BUMDT
PM27|MOTDT
PM14|BUMDT
PM28|MOTDT
PM15_1|BUMDT
PM29|MOTDT
PM15_2|BUMDT
PM1|TJ1DT
PM15_3|BUMDT
PM2|TJ1DT
PM16|BUMDT
PM3_1|TJ1DT
PM17|BUMDT
PM3_2|TJ1DT
PM18|CARDT
PM3_3|TJ1DT
PM19|CARDT
PM4|TJ1DT
PM20|CARDT
PM5|TJ1DT
PM21|CARDT
PM6|TJ1DT
PM22_1|TICDT
PM7|TJ1DT
PM22_2|TICDT
PM8|TJ1DT
PM23|TICDT
PM9|TJ1DT
PM24|TICDT
PM10|TJ1DT
PM11|TJ1DT
3.3. MANUAL STARTUP

To manually start the application, the application installer has been configured to place a
shortcut in the desktop. Once clicked that shortcut the application opens the main form and
informs about the files converted and the result of the conversion.
18
3.4. AUTOMATIC STARTUP

An automatic task has been configured in the Task Scheduler to run the application on
Startup:
19
3.5. LOG FILE

The same information that the applications shows on the main form and a more detailed
description of the errors will be stored in the log file.
DLFileConv.log:
2012-11-16 09:48:36.1718|INFO|------ Application start -----2012-11-16 09:48:41.7179|INFO|Converting file "log (PM24--DL) 2012_11_12_00_01_17.csv"
2012-11-16
09:48:41.8116|INFO|File
"log
(PM24--DL)
converted. The file will be moved to the backup folder
2012_11_12_00_01_17.csv"
succesfully
2012-11-16 09:48:41.8116|INFO|Converting file "log (PM25--DL) 2012_11_12_00_01_02.csv"

2012-11-16 09:48:41.8897|INFO|An exception has occurred while converting file "log (PM25--DL)
2012_11_12_00_01_02.csv" probably due to a bad format. The file will be moved to the bad folder.
To get detailed information about the exception review the log file
2012-11-16 09:48:41.9678|ERROR|Datalogger not configured in "datalogger-location.lst" file
DataloggerFilesConversor.HistoryRecord.getId()
en
en DataloggerFilesConversor.FileParser.createRealtimeFile()
en DataloggerFilesConversor.MainForm.convertFile(String filePath)
2012-11-16 09:48:41.9835|INFO|Converting file "log (PM26--DL) 2012_11_12_00_01_23.csv"
2012-11-16
09:48:42.0303|INFO|File
"log
(PM26--DL)
converted. The file will be moved to the backup folder
2012_11_12_00_01_23.csv"
succesfully
20
4.
SCADA
4.1. OBJETIVES
It have been developed the objects that represent de Dataloggers of Gorjs Project
(Rumania), this Dataloggers are connected to flowmeters. It have been developed the
objects that represents the physical datalogger in the distribution net and the faceplates
that displays the information.
4.2. GRAPHIC OBJECTS IN THE PHYSICAL NET

Distribution: Showed in the screen GR_Main.The features are:
When pushed brings to the corresponding distribution area (Targu Jiu, Bumbesti
Jiu..)
Its displayed in grey if it dont have active alarms.
Its displayed in red if it have active alarms.
It blinks if any alarm is unacknowledged.
DL001: Is the basic object to show in the different distribution areas.

DL001_1: Its just the graphic DL001 embeded and configured to use in the DL001Emb.
DL001Emb: Its just the graphic DL001_1 embeded to apply over it the StrMe technique.
21
The DL001 graphic have the following features in the SCADA:
Its displayed in grey color if the point is represented in the map but it is not linked
to a datalogger.
Its displayed in green if the point is linked to a datalogger and It isnt in alarm.
Its displayed in red if It is linked to a datalogger and It is in alarm.
It blinks if it have any unacknowledged alarm.
When pushed shows a faceplate with the datalogger information (DL001Fac).
It display the Datalogger identifier
The DL001xxx graphic is used in the different distribution areas and the specific graphic
used is:
DL001: To represent dataloggers that are not linked to a physical one.

DL001Emb: To represent dataloggers that are linked to a physical one.
4.3. FACEPLATES (GRAPHICS)

DL001Fac: Shows the information specified in the DL_Study_Vxx file, in the sheet
Flowmeter and in the column Faceplate. In the button alarm is a resume of the alarm,
pushing this button the DL001Alr is opened.
DL001Alr: Displays the Dataloggers alarms, if any alarm is active its round led is in red, if
the alarm is unacknowledged the round led blinks.
22
In the forlder \DLFac_Objects are done the objects needed to do the faceplates.
4.4. FILE DL_STUDY_VXX

This file is composed of four main sheets:
Datalogger information: Here is the information processed by the SCADA It is

marked if the information comes from the Datalogger or if it is processed in the
SCADA, it specifies which signals are logged, which are alarms, the descriptions, the
subitem
Datalogger Identifier: It is specified the name of the datalogger and the name of the
dataloggers area
File_DataRT: It is explained the meaning of each row of the DL_RTime file.
File_Hst: It is explained the meaning of each row of the Historical files.
4.5. REAL TIME DATA

The SCADA read the Real time data from one file called DL_RTime.csv in the fold
D:\Data\DL\outbox_RT and it is generated by an intermediate program that process
the files recived by the datalogger and generate one row with the last information for each
datalogger. The values writed in this file are equal to the values received from the
datalogger.
In the sheet File_DataRT of the
column of the file DL_RTime.csv.
DL_Study_Vxx is explained the meaning of each
The file DL_RTime.csv is a valid example of this file.
23
4.6. IAS APPLICATION OBJECTS

DL_Gen: Reads the DL_RTime.csv file and copy the values to the corresponding variable
of the DL001 instance. If the processed value is numeric and is not valid it pass -1 to the
corresponding variable of DL001. If the processed value is string and is a null string it pass
Bad Value. It is needed only one DL_Gen instance for all Datalogger.
DL001: Its needed one DL001 instance for each datalogger. It process the values writed
by DL_Gen instance.
In the instances of DL001 is needed to configure the UDA ObjDesc that defines the
description of the object. It have been done a file to charge the values of this variable in all
the instances named DL001_Configuration.csv
4.7. HISTORICAL DATA

An intermediate program process the information arrived from the datalogger an makes a
file to charge diretly into Historian.
The file must be charged in the
C:\Historian\Data\DataImport folder.
The file DL_Hst.csv is a valid example of file.
In the file DL_Study_Vxx in the sheet File_Hst is an explanation with the meaning for
each row.
The file DL_Hst_Info.txt have included a query to excute over Runtime database that
return the value introduced by the file DL_Hst.csv
In historian have been defined the historical variables of the dataloggers, these variables
are not related with any variable defined in IAS. They have been created charging a file
with the application Database configuration export and import of historian. The file is
DL_Hst_Charge.txt
24

Dataloggers Configuration Manual - v1.1

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Dataloggers Configuration Manual - v1.1

Hochgeladen von

Copyright:

Verfügbare Formate

Table of contents

1. INVENTIA MT-723 DATALOGGER..................................................

REAL TIME DATA................................................................................23

IAS APPLICATION OBJECTS....................................................................24

OBJECTS IN THE PHYSICAL NET....................................................21

Dataloggers configuration manual v1.0

INVENTIA MT-723 DATALOGGER

MT Manager is used to read/write the usual settings (e.g. GPRS configuration,

ApaRegio Supervizare si control colectare date (SCADA)

Dataloggers configuration manual v1.0

2. Introducing the module IP

ApaRegio Supervizare si control colectare date (SCADA)

Dataloggers configuration manual v1.0

3. Reading the dataloggers configuration

ApaRegio Supervizare si control colectare date (SCADA)

Dataloggers configuration manual v1.0

ApaRegio Supervizare si control colectare date (SCADA)

Dataloggers configuration manual v1.0

ApaRegio Supervizare si control colectare date (SCADA)

Dataloggers configuration manual v1.0

mt_aliases file contents (an example from Trgu Crbuneti):

ApaRegio Supervizare si control colectare date (SCADA)

Dataloggers configuration manual v1.0

mt_log_filter file contents (an example from Trgu Crbuneti):

ApaRegio Supervizare si control colectare date (SCADA)

Dataloggers configuration manual v1.0

OPCconfig.xml file contents (an example from Trgu Crbuneti):

<configure net_mode="dynamic" udp_port="7110" timestamp="system"

ApaRegio Supervizare si control colectare date (SCADA)

Dataloggers configuration manual v1.0

<modbus name="DL" id="1" type="analog_inputs" address="15" size="1"

ApaRegio Supervizare si control colectare date (SCADA)

Dataloggers configuration manual v1.0

<modbus name="DL" id="1" type="analog_inputs" address="15" size="1"

<modbus name="DL" id="1" type="analog_inputs" address="15" size="1"

ApaRegio Supervizare si control colectare date (SCADA)

Dataloggers configuration manual v1.0

Anyway, the OPC configuration from MT Manager may look as follows:

ApaRegio Supervizare si control colectare date (SCADA)

Dataloggers configuration manual v1.0

2.1. SERVER CONFIGURATION

2.2. CLIENTS CONFIGURATION

ApaRegio Supervizare si control colectare date (SCADA)

Dataloggers configuration manual v1.0

backup: stores the original files sent to the server

2.3. MANUAL EXECUTION

2.4. AUTOMATIC EXECUTION

ApaRegio Supervizare si control colectare date (SCADA)

Dataloggers configuration manual v1.0

2.5. LOG FILE

1:38:04.52 - Process start: 546 files will be uploaded

1:43:04.35 - Process start: 0 files will be uploaded

ApaRegio Supervizare si control colectare date (SCADA)

Dataloggers configuration manual v1.0

1:48:04.35 - Process start: 0 files will be uploaded

ApaRegio Supervizare si control colectare date (SCADA)

Dataloggers configuration manual v1.0

Generate an historical file with the format expected by Wonderware Historian at

3.2. CONFIGURATION FILES

The application loads configuration from the following files:

DataloggerFilesConversor.exe.config: settings related to the folders that the application

NLog.config: log-related settings such as the log file path

The default contents of the configuration files are copied below.