Generic FTP/email gateway

Follow

DEXCell Energy Manager allows inserting data from other systems through an FTP server, where these files are processed and inserted through the platform. This article includes the following sections:

  1. Available file formats
  2. How to register the gateway in DEXCell Energy Manager
  3. How to import historical data


1. Available file formats 

In this section, it is explained all the different file parsers available. If you want to send data through FTP using a different file format, contact with support@dexma.com.

The included formats in this article are the following:

  1. DEXMA Default CSV format 
  2. DEXMA Default 15min shifted
  3. Roquetude
  4. Carlo Gavazzi SH2WEB24
  5. Schneider StruxtureWare
  6. Synetica
  7. Trend v1
  8. Trend v2
  9. Capfile PME PMI
  10. OPTIMISED
  11. Fleetsolve - Wipulse
  12. Smonitor
  13. UNIWIN32
  14. ELComponent
  15. Solarlog
  16. Wit
  17. WONDERWARE
  18. HWM RT:Wi5
  19. ICF-STRUXTUREWARE
  20. AquaLogic
  21. Lora
  22. ND Meter
  23. Sedical
  24. Synapsis SIP
  25. Desigo
  26. HH Read Data
  27. Schneider Com'X-510
  28. Satel DL


    NOTE: Please follow the exact formatting of  any of the following file types used to insert data in DEXCell EM 
     (exact time stamp, valid time zone, etc.)
     
  • It is important to know that regarding FTP in passive mode we have a defined range of ports: 49152 - 49260.

 


1.1 DEXMA Default CSV format 

DEXCell Energy Manager allows sending data through email/FTP using a standard CSV file. Values must be separated by semicolons. The name of each file sent must be unique.

The format is the following:
Column 1: Time zone
Column 2: Date in the following format: YYYY/MM/DD HH:MM:SS (local time related to Column1, not UTC)
Column 3: Name of the device (DeviceID) - Limited to 64 characters.
Column 4: Parameter
Column 5: Value

Example:

"

Europe/Madrid;2013/07/07 12:15:00;enfriadora;401;188.23
Europe/Madrid;2013/07/07 12:15:00;enfriadora-fase1;401;44.5
Europe/Madrid;2013/07/07 12:15:00;enfriadora-fase2;401;43.5
Europe/Madrid;2013/07/07 12:15:00;enfriadora-fase3;401;100.23
Europe/Madrid;2013/07/07 12:30:00;enfriadora;401;198.23
Europe/Madrid;2013/07/07 12:30:00;enfriadora-fase1;401;44.5
Europe/Madrid;2013/07/07 12:30:00;enfriadora-fase2;401;43.5
Europe/Madrid;2013/07/07 12:30:00;enfriadora-fase3;401;110.23

"

Daylight savings changes should be set on the gateway that is sending the data to the FTP server, so that the hour that is doubled appears only one time in the file, but having the consumption of the repeated hour or latest hour. For example, if the hourly consumption is a steady 100 kWh:

Europe/Madrid;2018/10/28 01:00:00;E-01;40211;100
Europe/Madrid;2018/10/28 02:00:00;E-01;40211;200
Europe/Madrid;2018/10/28 03:00:00;E-01;40211;100

 

Disclaimer: When creating the CSV file, double check that there are no extra quotation marks in the fields (for instance with a plain text editor such as Notepad or TextEdit), as some software for editing CSV will add them as field delimiters.

 

1.2 DEXMA Default 15min shifted

This format is exactly the same as the previous one, but subtracting 30 minutes on the timestamp due to other considerations on the beginning/end of the period. DEXMA understand that the consumption between 04:00 to 04:15 is put on 04:00h

Example:

"

Europe/Madrid;2013/07/07 12:00:00;enfriadora;401;188.23
Europe/Madrid;2013/07/07 12:00:00;enfriadora-fase1;401;44.5
Europe/Madrid;2013/07/07 12:00:00;enfriadora-fase2;401;43.5
Europe/Madrid;2013/07/07 12:00:00;enfriadora-fase3;401;100.23
Europe/Madrid;2013/07/07 12:15:00;enfriadora;401;198.23
Europe/Madrid;2013/07/07 12:15:00;enfriadora-fase1;401;44.5
Europe/Madrid;2013/07/07 12:15:00;enfriadora-fase2;401;43.5
Europe/Madrid;2013/07/07 12:15:00;enfriadora-fase3;401;110.23

"

 

Disclaimer: When creating the csv file, double check that there are no extra quotation marks in the fields, as some software for editing CSV will add them as field delimiters. 

1.3 Roquetude

File format: .csv​
Timezone;Timestamp(Y/m/d H:M:S);Device_name(DeviceID);Parameter_ID;Value;    
"Europe/Paris";"2014/06/03 16:00:00"; "PCPT";401;48;

 
 

1.4 Carlo Gavazzi SH2WEB24

File format: .zip, which includes all the .csv

The .csv must have the following format:

"Position" ; "Timestamp" ; "Date"; "Hour" ; "Part Number" ; "Object Name" ; "Location Name"  "Sin" ; "Subnet" ; "Modbus Address" ; "Com Port" ; "kWh AC [kWh]" ; "DMD W [W]"; ; ; ;.....


To keep in mind:

  • Timestamp (in seconds from 01/01/1970 (epoch)
  • Com Port (If that field is empty, we take only the data from the mono_service_dict column),
  • Compatible variables:  


service_dict = { 'Temperature 1 (ºC)' ,  'Temperature 2 (ºC)' ,  'Humidity (%)' , 'Light (Lux)' , 'Input1 0-10V' ,  'Input2 0-10V' , 'VL1N(V)' , 'VL2N(V)' , 'VL3N(V)' ,  'AL1(A) ,  'AL2(A)', 'AL3(A)' ,  'WL1(kW)' , 'WL2(kW)' ,  'WL3(kW)' ,  'VAL1(VA)' ,  'VAL2(VA)' ,  'VAL3(VA)',
'VarL1(Var)' ,  'VarL2(Var)' ,  'VarL3(Var)' ,  'PFL1' ,  'PFL2' ,  'PFL3' ,  'kWh AC (kWh)', 'DMD W sys (W)' ,  'Counter 1' ,  'Counter 2' ,  'Counter 3' ,  'Counter 4' ,  'Co2', 'Temperature' ,  'VLN sys [V]' ,  'VL1N [V]' ,  'VL2N [V]' ,  'VL3N [V]' , 'VLL sys [V]' ,  'VL1L2 [V]' ,  'VL2L3 [V]' ,  'VL3L1 [V]' , 'AL1 [A]' ,  'AL2 [A]' ,  'AL3 [A]' ,  'W sys [kW]' ,  'WL1 [kW]', 'WL2 [kW]' ,  'WL3 [kW]' ,  'kVA sys [VA]' ,  'kVA L1 [VA]' ,  'kVA L2 [VA]' ,  'kVA L3 [VA]', 'Var sys [Var]' ,  'kVar L1 [Var]' ,  'kVar L2 [Var]' ,  'kVar L3 [Var]' ,  'PF sys' ,  'PF L1' ,  'PF L2' ,  'PF L3' ,  'FREQUENCY [Hz]' ,  'kWh AC [kW]' ,  'KWh L1 [kW]' ,  'KWh L2 [kW]' , 'KWh L3 [kW]' ,  'Kvarh [kVarh]' ,  'KWh ACN [kWh]' , 'kWh AC [kWh]' ,  'COUNTER 1' ,  'COUNTER 2' ,  'COUNTER 3' ,  'COUNTER 4' , 'THDAl1' ,  'THDAl2' ,  'THDAl3', 'THDVl1' ,  'THDVl2' , 'THDVl3' }


mono_service_dict = { 'WL1 [kW]' , 'WL1(kW)' , 'kVar L1 [Var]' , 'VL1N [V]' , 'AL1 [A]' , 'kVA L1 [VA]' , 'PF L1' }


1.5 Schneider StruxtureWare

File format: .csv
TL_Instance , object , year-month-day hour:min:sec,value

tl1,AV1,2014-05-08 14:00:31,21

That parser takes the timezon configured in the gateway registered on DEXCell Energy Manager

 

1.6 Synetica

File format: .csv

UTCTimeStamp, LocalTimeStamp, device1, device2, device3, ..
21/05/2014 11:30:00 , 21/05/2014 12:30:00, 4250, 212.23, 12.4,...

As timeStamp, we take the first value in UTC and is applied the timezone configured on the gateway registered in DEXCell Energy Manager.

On the header, we indicate the name of the devices (which is the ID), with all the values in the rows. The values are inserted using the "503" parameter ID (a generic one). Then, we have to derive that "503" to the corresponding parameters. In order to create a derived parameter, see this article.

 


1.7 Trend v1


File format: .csv
The .csv header is the following:

UTCTimeStamp, Asset_ID, Value, DeviceID

06/04/2014 13:16 ,   21_11_S1_Real Energy Total ,  27363.976562 , Meter 51

That parser takes the timezone configured in the gateway registered on DEXCell Energy Manager

 

1.8 Trend v2


File format: .csv
The .csv header is the following:

LabelsFromController UTCTimeStamp value.

1stFlrTop    2015-04-03 12:45:00    84707.
1stFlrTop    2015-04-03 13:00:00    84707.
1stFlrTop    2015-04-03 13:15:00    84707.
1stFlrTop    2015-04-03 13:30:00    84708.

That parser takes the timezone configured in the gateway registered on DEXCell Energy Manager

 



1.9 Capfile PME PMI

 

That parser receives a XML file saved on a .csv inside the <PointConso> labels

The csv inside the xml has the following format:

Date      SouP    SouQ    InjP    InjQ    Tens    PuisSous    Period    Etat

20/11/2012 06:10:00    0    0    0    0    0    148    HPH    

The bold columns are the data which takes the parser

Date = 20/11/2012 06:10:00 (timezone configured on the gateway registered on DEXCell Energy Manager)

Soup = serviceid 40271

InjP = serviceid 45271

Separator = tabulator

 

1.10 OPTIMISED

 

File format: .csv

The csv has the following format:

-- x Chiltern School Energy Meters 10/10/2014 08:24:27 AM

DATE, H02_022,                   W01_05 ,  E059_064 , PoolKwh,  GW01_05,      BioMass,  SolarPV,  M006

10/10/2014 07:30:00 AM, 289966 , 7220.24,      131318,   1.0055e+006, 1539.66, 684340, 13193,589.5

10/10/2014 07:00:00 AM, 289960 , 7220.05,      131292 , 1.0055e+006, 1539.64, 684340, 13193,589.5

 

The first line is not taken into account.
The second line is the Header of the CSV, where the position of the DATE and the Device IDs are defined.
The rest of the lines contain the TimeStamp at the first column and the measures of each Device.

Date =
10/10/2014 07:30:00 AM (timezone configured on the gateway registered on DEXCell Energy Manager)

Separator = ","

The values are inserted using the "503" parameter ID (a generic one). Then, we have to derive that "503" to the corresponding parameters. In order to create a derived parameter, see that article.

 

1.11 Fleetsolve - Wipulse


The xls has the following format:


Name

Firmware ver.

Application

Date

App. ver.

Ser. num.

       

EMA

IS-NT-2.5 R:14.01.2011

SPI

6/2/2014

2.5

101161E0

       
                   

Num

Reason

Date

Time

RPM

Pwr

A2-2

A2-3

A2-4

A2-5

-29

Time stamp

01/06/2014

23:30:00.1

0

0

20

22

71

72

-30

Time stamp

01/06/2014

23:00:00.1

0

0

20

22

64

63

-31

Time stamp

01/06/2014

22:30:00.1

0

0

20

21

69

69

-32

Time stamp

01/06/2014

22:00:00.0

0

0

21

22

70

70

-33

Time stamp

01/06/2014

21:30:00.0

0

0

21

22

64

65

-34

Time stamp

01/06/2014

21:00:00.0

0

0

21

22

71

72


First three rows are not taken into account.
The parser starts working on the 4th row where the Device IDs are defined at the Header (A2-2, A2-3,...)
Rows are ordered by the Timestamp in descendant order.


The values are inserted using the "503" parameter ID (a generic one). Then, we have to derive that "503" to the corresponding parameters. In order to create a derived parameter, see that article.

Cells with #### or null values are not taken into account.

 

1.12 Smonitor

 

File format: .csv

The csv has the following format:
 

Data; Hora; 301-Temp; 419-GasCoz; 419-GasCald; 402-TorreG; 901-AF; 901-AQS; 402-Geral; 402-Chiller

23-09-2014; 14:30:45; 24,6; 5995,0; 32506,0; 19987,3; 0,0; 5974,0; 845143,9; 66820,7; 43072,3 ;

 
At the Header on the first Row, the type of measure and the Device ID are defined (301-Temp).
Measures are located in the second row.

The parser takes the timezone configured in the gateway registered on DEXCell Energy Manager

 

1.13 UNIWIN32

 

This parser process SIEMENS Temperature probes DATA coming in files with the following structure:

 

5

Histórico             : HISTO_PL02_DEXMA

Elemento     1        : C-201 Temperatura

Elemento     2        : C-202 Temperatura

Elemento     3        : C-203 Temperatura

Elemento     4        : C-204 Temperatura

Elemento     5        : C-205 Temperatura

Tiempo de muestreo    : 00:15:00

Intervalo muestreo    : 30/09/2014 0:07:30 --- 30/09/2014 23:52:30

Número de muestras    : 96

Estado actual         : ACTIVO    

Valor máximo          :   22.8    24.1    20.6    40.7    24.1  

Valor mínimo          :   22.3    23.0    19.9    40.7    23.4  

Valor medio           :   22.4    23.4    20.3    40.7    23.7  

                       ,,,°C,°C,°C,°C,°C

    1,30/09/2014 0:07:30, 22.8, 23.6, 20.5, 40.7, 24.0

    2,30/09/2014 0:22:30, 22.8, 23.6, 20.5, 40.7, 24.0

    3,30/09/2014 0:37:30, 22.8, 23.6, 20.5, 40.7, 24.0

    4,30/09/2014 0:52:30, 22.8, 23.6, 20.5, 40.7 24.0

    5,30/09/2014 1:07:30,22.8,23.5,20.5,40.7,24.0

    6,30/09/2014 1:22:30,22.6,23.6,20.5,40.7,24.0

    7,30/09/2014 1:37:30,22.6,23.6,20.5,40.7,23.9

    8,30/09/2014 1:52:30,22.6,23.6,20.4,40.7,23.9

    9,30/09/2014 2:07:30,22.6,23.5,20.4,40.7,23.9

   10,30/09/2014 2:22:30,22.6,23.5,20.4,40.7,23.9

   11,30/09/2014 2:37:30,22.6,23.5,20.3,40.7,23.9

   12,30/09/2014 2:52:30,22.6,23.5,20.3,40.7,23.9


At first, the parser obtains the number of devices that are sending DATA (5 in this example) and the Device ID of each device (C-201,C-202,..).
Then, the parser obtains the DATA at the table below, where the measure for device 1 is on the 3rd column, the measure for device 2 on the 4th column, and so until the last column.

The parser takes the timezone configured in the gateway registered on DEXCell Energy Manager
 

 

1.14 ELComponent

 

File format: .csv

The csv has the following format:
 

"DeviceName(deviceID)","DataItem","Units","Date","Time","Value","Status"

"Pulse-3-EGGG-CL","Channel 1 counter","","2014-09-07","00:30",42281322.00,0

"Pulse-3-EGGG-CL","Channel 1 counter","","2014-09-07","01:00",42281455.00,0

"Pulse-3-EGGG-CL","Channel 1 counter","","2014-09-07","01:30",42281585.00,0

"Pulse-3-EGGG-CL","Channel 1 counter","","2014-09-07","02:00",42281713.00,0

"Pulse-1-WWGG-OH","Channel 1 Pulse Count","","2014-09-07","00:30",1922752.00,0

"Pulse-1-WWGG-OH","Channel 1 Pulse Count","","2014-09-07","01:00",1922752.00,0

"Pulse-1-WWGG-OH","Channel 1 Pulse Count","","2014-09-07","01:30",1922752.00,0


"DeviceName" is taken as the Device ID but in case of pulse counters, a prefix PC0 or CC0 is added, depending on the type of pulse counter.
Units recognized at this moment are:

{

       "kWh" : 402,

       "kVArh" : 404

}

Pulse measures are inserted using the  "502" parameter ID ant the rest of values are inserted using the "503" parameter ID (a generic one).
The timestamp is modified by subtracting 30 minutes.

 

 

1.15 Solarlog

 

File format: .csv

The csv has the following format:
 

Date;Time;INV;Pac;DaySum;Status;Error;Pdc1;Pdc2;Udc1;Udc2;Temp;Uac;INV;Pac;DaySum;Status;Error;Uac;Iac;Pac1;Pac2;Pac3;Uac1;Uac2;Uac3
 

14/12/14; 23:55:00; 1; 0; 8943; 0; 0; 0; 0; 0; 0; 0; 0; 2;6262;235110;1;0;230;27;2018;2418;1826;230;230;230

14/12/14; 23:50:00; 1;0;8943;0;0;0;0;0;0;0;0;2;5829;234582;1;0;230;25;1981;2201;1645;230;230;230

14/12/14; 23:45:00; 1;0;8943;0;0;0;0;0;0;0;0;2;6334;234098;1;0;230;27;2228;2248;1858;230;230;230

 
This parser receives information from n devices that in this example are called "INV". Each device sends information of various types of counters that are identified at the Header as:

INV; Pac; DaySum; Status; Error; Pdc1; Pdc2; Udc1; Udc2; Temp; Uac

Parameters taken into account are:

 

{

                  'Pac' :401,

                  'Uac': 405,

                  'Iac': 406,

                  'Temp' : 301,

                  'Pdc' : 461,

                  'Udc' : 465

}

At the DaySum Column, Produced Energy (DEXCell Service 502) is shown, except on the last INV of the list where the consumed Energy (DEXCell Service 402) is shown instead.
Rows are ordered by the Timestamp in descendant order.
The INV called "N3", if that exists, is not taken into account.


 

1.16 Wit


File format: .xml

The xml has the following format:

 

<dset>

<tagdset id="WT1015-1" var="TENERGYMWH-FRIO" time="201504201115" value="1749.1"/>

<tagdset id="WT1015-1" var="OUTTEMP" time="201504201115" value="9.05"/>

<tagdset id="WT1015-1" var="INTEMP" time="201504201115" value="9.74"/>

<tagdset id="WT1015-1" var="TPOWER" time="201504201115" value="37"/>

<tagdset id="WT1015-1" var="MASSFLOW" time="201504201115" value="47.37"/>

<tagdset id="WT1015-2" var="GASVOLUME" time="201504201115" value="191882.1"/>

<tagdset id="WT1015-3" var="GASVOLUME" time="201504201115" value="254632"/>

<tagdset id="WT1015-4" var="TENERGYMWH" time="201504201115" value="0"/>

<tagdset id="WT1015-4" var="OUTTEMP" time="201504201115" value="90.02"/>

<tagdset id="WT1015-4" var="INTEMP" time="201504201115" value="61.13"/>

</dset>


At this structure, you can find two xml tags: "dset" and "tagset".
​Inside "tagset" tag, you'll find the information of a device that is sending data.

The "id" attribute defines the Device ID.
The "var" attribute defines the type of measure. The parser recognizes these:
 

{

       "TENERGYMWH":(802,1000),

       "TENERGYCMWH":(810,1000),

       "OUTTEMP": (806,1),

       "INTEMP": ( 805,1),

       "TPOWER": (801,1),

       "MASSFLOW": (804,1),

       "TENERGY": (802,1),

       "GASVOLUME":(419,1),

       "EAENERGY":(402,1),

       "EAPOWERKW":(401,1000),

       "LOADFACTOR":(812,1),

       "TENERGYC":(810,1),

       "TOU":(161,1),

       "IO":(501,1)

   }


The "time" attribute defines the timestamp of the measure in UTC.
The "value" attribute defines the value of the measure.
The parser takes the timezone configured in the gateway registered on DEXCell Energy Manager
 


1.17 WONDERWARE

 

File format: .csv

The csv has the following format:

 

FECHA HORA;        VAP_CT-01_CNT;   VAP_CT-02_CNT;  VAP_CT-03_CNT

18/10/2014 0:00:00;      985789.1;               278382.5;                  8171.1

18/10/2014 1:00:00;       987133.9;              278491.6;                  8175.9

18/10/2014 2:00:00;       988619.3;              278602.1;                  8186.1

18/10/2014 3:00:00;       990061.7;              278708.3;                  8191.5

18/10/2014 4:00:00;       991509.4;              278816.7;                  8194.5

18/10/2014 5:00:00;       993070.4;              278934.9;                  8197.5

18/10/2014 6:00:00;       994572.3;              279052.8;                  8202.3

18/10/2014 7:00:00;       995975.4;              279167.3;                  8204.7

18/10/2014 8:00:00;       997378.9;              279285.1;                  8213.7


At the Header of the csv you can find the Device ID.
All measures are inserted using the "503" parameter ID (a generic one). 



 

1.18 HWM RT:Wi5

 

File format: .txt

The txt has the following format:
 

20150401094449810217D802051C03474C03

20150401094454810217F80218D75B3B06D0

20150401094459810217F80218D75B9C476A


This txt file contains sequences of Hexadecimal digits, where the first 14 digits indicate the timestamp. At this example:

2015 04 01 09 44 49

Next two digits indicate the parameter:

81

The parser recognizes the next parameters:


{'81': 502,

'82': 301,

'92':301,

'83': 302,'93': 302,                            }

The next 6 digits indicate the name of the device to which the data belongs to.
 
Let's take as an example a file called E4T5_20150509104539 with a line to import saying as follows:
20150401094449810217D802051C03474C03
  • Date: 20150401
  • Time: 094449
  • Parameter: 81
  • 6 digits for Device name: 0217D8 (The device ID that's going to be generated is E4T5_0217D8) 

Obtaining the value of the measures:
The digits from the 26th to the end (51C03474C03) contain the value of the measure and depending on the type of measure, the digits are structured in different ways.
Temperature measures:
The first 2 digits indicate the sign, and the next 3 digits indicate the value.
If the sign is negative (0F), the parser substracts 256 and then the value is divided by 2. If it is not negative, the parser just divides by 2.
Pulse measures:
The parser obtains the 7 first digits and converts it into decimal.

Humidity measures:
The parser obtains the 5 first digits and converts it into decimal (value).
Then a caculation is done:
Humidity= (value* value )*-0.0000028) + (value*0.0405) -4



 

1.19 ICF-STRUXTUREWARE

 

File format: .csv

The csv has the following format:

 

Sonda temperatura tuberia; Temperatura Retorn ;25.298 ;2015-06-04 13:07:52;

Sonda temperatura tuberia; Temperatura Impulsio ;25.14 ;2015-06-04 13:07:52;

Sonda temperatura humitat interior SHO101-T5 ; Humitat Interior ;65.16 ;2015-06-04 13:07:52;

Sonda temperatura humitat interior SHO101-T5 ; Temperatura Interior ;24.468 ;2015-06-04 13:07:52;

Sonda temperatura humitat exterior SHR-510-T ; Temperatura Exterior ;30.639 ;2015-06-04 13:07:52;

Sonda temperatura humitat exterior SHR-510-T ; Humitat Exterior ;48.187 ;2015-06-04 13:07:52;

iEM3255 ; Total Consum ;342.487 ;2015-06-04 13:07:52;

iEM3255 ; Consum de gas ;0 ;2015-06-04 13:07:52;

 

The first column indicates the Device ID, and the second column indicates the parameter type.
The parser recognises the following types:


 

' Temperatura Retorn ' : 301,

' Temperatura Impulsio ': 301,

' Humitat Interior ': 302,

' Temperatura Interior ': 301,

' Temperatura Exterior ': 301,

' Humitat Exterior ': 302,

' Total Consum ': 402,

' Consum de gas ': 419,



Last two columns indicate the timestamp and the value.

 

1.20 Aqualogic 

File format: .csv


The csv has the following format:

Third column –> deviceID
Fourth column –> timestamp in LOCAL
Fifth column –> value

All the values are inserted as water volume using the 901 divided by 1000 (Value information in CSV interpreted a water liter [l]) in the DEXCell EM service.


Example:
AB CLIENTS IMETER;13060110;D13XK047959C;28/10/2013 07:00:00;7403300;
AB CLIENTS IMETER;13060110;D13XK047959C;28/10/2013 06:45:00;7403300;
AB CLIENTS IMETER;13060110;D13XK047959C;28/10/2013 06:30:00;7403300;
AB CLIENTS IMETER;13060110;D13XK047959C;28/10/2013 06:15:00;7403300;
AB CLIENTS IMETER;13060110;D13XK047959C;28/10/2013 06:00:00;7403300;
AB CLIENTS IMETER;13060110;D13XK047959C;28/10/2013 05:45:00;7402200;
AB CLIENTS IMETER;13060110;D13XK047959C;28/10/2013 05:30:00;7395600;

 

1.21 Lora
 

File format: .csv, separated with semicolons (";")

CSV file name sent by the concentrator is composed of the sensor (deviceID) identification.

The parser creates as many devices (channels) as data columns you specify in column 5 of the file in the .CSV file. All the Values are introduced using the 503 DEXCell service.

The csv has the following format:

First column –> Timestamp in ISO 8601 format.

Columns, 2, 3 and 4: Not used

Fifth column: number of channels

6th to nth column –> different channels Values

Values must be separated by semicolons (";").
 

Example:
2015-06-12T00:15:56+00:00 -9 0 8000 2 989 547
2015-06-12T00:26:13+00:00 -9 0 8000 2 989 547
2015-06-12T00:36:13+00:00 -9 0 8000 2 989 547
2015-06-12T00:45:56+00:00 -9 0 8000 2 989 547
2015-06-12T00:56:13+00:00 -9 0 8000 2 989 547
2015-06-12T01:06:13+00:00 -9 0 8000 2 989 547
2015-06-12T01:16:13+00:00 -9 0 8000 2 990 547
2015-06-12T01:26:13+00:00 -9 0 8000 2 990 548
2015-06-12T01:35:56+00:00 -9 0 8000 2 990 548



 

1.22 ND Meter
 

File format: .txt

“001BE5101010_110817_073000”

txt file name (001BE5101010_110817_073000) sent by the concentrator is composed of the sensor (deviceID) identification followed by the date and time.

The parser creates as many subdevices (channels) as data columns you have in the .CSV file. All the Values are introduced using the 503 DEXCell service.


The csv has the following format:

First ROW –> ND meter Service ID
Second ROW –> Values
 

Example:
 

SES XXXXX 7702 7703 7704 7736 7681 7680 7737 7688 7689 7690 7733 7701 7697 7686 7687 7691 7692 7693
160404_133000 65031 65205 65080 4 5357 3 5 235 160 211 2 954 500 0 37983 2230 2233 2239


ND Meter services implemented in the parser are the following:

6656, 6657, 6658, 6659, 6660, 6661, 7680, 7681, 7682, 7683, 7684, 7685, 7686, 7687, 7688, 7689, 7690, 7691, 7692, 7693, 7694, 7695, 7696, 7697, 7698, 7699, 7700, 7701, 7702, 7703, 7704,  7705, 7706, 7707, 7708, 7709, 7710, 7711, 7712, 7713, 7714, 7715, 7716, 7717, 7718, 7719, 7720, 7721, 7722, 7723, 7724, 7725, 7726, 7727, 7728, 7729, 7730, 7731, 7732

 

1.23 Sedical
 

File format: .csv

The csv has the following format:

Column A: Timestamp in UTC

Column C: deviceID

Column I: value

Column J: parameter:

Services implemented in the parser are the following:

- If the parameter is m3 > 419 (Gas DEXCell service)

- If the parameter is Wh > 402 (Active Energy DEXCell service). Convert the Units to kWh in DEXCell EM.

- If the parameter is kWh > 402 (Active Energy DEXCell service)


Example:
14/04/2016 00:00:01 11 1022001 REL 65 Gas 149 0 791 m3 14/04/2016 01:58:00   15/09/1914   0 m3 31/12/1916   C0010A0C




1.24 Synapsis SIP
 

File format: .csv

The csv has the following format:

First column: timestamp in LOCAL
2nd column:  Value
3rd columnd: deviceID
 

Services implemented in the parser are the following:

 

All values will be inserted as 40261 (Half Hourly Discretized Active Energy)

Example:

UoW M,16-10-2016 00:00,MBRMetering
Timestamp,Value,Label
15-10-2016 00:30,1,10th Floor kWh
15-10-2016 01:00,0,10th Floor kWh



1.25 Desigo
 

Description Name Unit Value TimeStamp
Contador de Gas B1'Cald'Gas m3 236939,7 18/07/2016 17:30
Total Posit Active Energy B1'Ene'EL'00'Pot kWh 82513 18/07/2016 17:30
Reactive Energy B1'Ene'EL'00'PotA kVAr 29310 18/07/2016 17:30
Active Power Phase 1 B1'Ene'EL'00'PotR kW 29,2 18/07/2016 17:30
Active Power Phase 2 B1'Ene'EL'00'PotR2 kW 11,1 18/07/2016 17:30
Active Power Phase 3 B1'Ene'EL'00'PotR3 kW 11,3 18/07/2016 17:30
  • 5th column: timestamp in LOCAL
  • deviceID: (cell B1) + _ + Description. Examples: Location1_Total Active Energy //  Location1_Gas Meter
  • 4th column: Value
  • Parameter > We just parse 2 devices: Total Active Energy XXX (*402*) and Gas Meter XXX (*419*). The other devices are discarded.

 

1.26 HH Read Data
 

- Format: .csv
- Comma Separated
- deviceID: column A
- date and time: column B. Time in UTC. IMPORTANT. In the file, 00:15 represents the consumption between 00:00 to 00:15, so we substract one period to the timestamp, as DEXCell EM represents the consumption at the beginning of the period (00:00)
- data: column D
-
parameter: 40261


Example:

mtr/2376551956116_41060652 2017/03/12 00:30 0 1934 0
mtr/2376551956116_41060652 2017/03/12 01:00 0 1972 0
mtr/2376551956116_41060652 2017/03/12 01:30 0 1908 0
mtr/2376551956116_41060652 2017/03/12 02:00 0 1941 0
mtr/2376551956116_41060652 2017/03/12 02:30 0 1964 0
mtr/2376551956116_41060652 2017/03/12 03:00 0 1931 0
mtr/2376551956116_41060652 2017/03/12 03:30 0 1909 0

 

1.27 Schneider Com'X-510
 

File name: DeviceName_AAAAMMDDhhmmss.csv

Format: .csv
Comma Separated

 

deviceID: column E row 2 .

Timestamp: column C (Date_Time) in Local

Values (except device ID)
  - start at row 8
  - column D, E, F, etc

Dexcell service: depending on the "tags" located at each column header. Tags available:

Parameter Service Applicable Factor Subdevice
'Active energy (Wh)' 402 1000  
'Active Power (W)' 401 1  
'Reactive Power (VAr)' 403 1  
'Active energy delivered (Wh)' 402 1000  
'Reactive energy delivered (VArh)' 404 1000  
'Gasoil (l)' 432 1000  
'Temperature (ºC)' 301 1  
'CO2 Level ()' 307 1  
'Humidity Rate ()' 302 1  
'Litros (l)' 901 1000  
'Iluminancia (lx)' 303 1  
'Producción (Units)' 131 1  
'CO2 (ppm)' 307 1  
'Active energy delivered A (Wh)' 402 1000 'A'
'Active energy delivered B (Wh)' 402 1000 'B'
'Active energy delivered C (Wh)' 402 1000 'C'
'Active energy delivered rate 1 (Wh)' 402 1000 '1'
'Active energy delivered rate 2 (Wh)' 402 1000 '2'
'Active energy delivered rate 3 (Wh)' 402 1000 '3'
'Active energy delivered rate 4 (Wh)' 402 1000 '4'
'VLNAvg' 405 1  
'Agua (l)' 901 1000  
'Agua (m3)' 901 1  
'Gas (m3)' 419 1  
'Gas (l)' 419 1000  
'Caudal Agua (m3/h)' 902 1  
'Agua (m3) (m3)' 901 1  
'Consumo E0 ()' 503 1 'E0'
'Consumo E1 ()' 503 1 'E1'
'Consumo E2 ()' 503 1 'E2'
'Temperatura Impulsion ()' 806 100  
'HeatEnergy ()' 802 1  
'Temperatura Retorno ()' 805 100  
'WaterFlowRate' 804 1  
'Active Power ()' 801 1  
'Energia Reactiva Recibida (kVArh)' 404 1 'ENTRADA'
'Energia Activa recibida (kWh)' 402 1 'ENTRADA'
'Energia Reactiva Entregada (kVArh)' 404 1  
'Energia Activa Entregada (kWh)' 402 1  
'Frequency (Hz)' 414 1  
'Current A (A)' 406 1 'A'
'Current B (A)' 406 1 'B'
'Current C (A)' 406 1 'C'
'Voltage A-N (V)' 405 1 'A'
'Voltage B-N (V)' 405 1 'B'
'Voltage C-N (V)' 405 1 'C'
'Power Factor ()' 412 1  
'Apparent Power (VA)' 409 1  
'Temperature (°C)' 301 100  
'Compressed air massflow (m3/h)' 436 1  
'Flujo de aire comprimido (m3/h)'
436 1  
'Compressed air massflow (m3/min)' 436 1/60  
'Flujo de aire comprimido (m3/min)' 436 1/60  
'Compressed air volume (m3)' 435 1  
'Volumen de aire comprimido (m3)' 435 1  
'Dew Point' 312 1  
'Punto de rocio' 312 1  
'Generic Volume (m3)' 504 1  
'Volumen generico (m3)' 504 1  
'Mass flow (m3/h)' 804 1  
'Mass flow (m3/min)' 804 1/60  
'Mass flow (l/min)' 804 1000/60  
'Flujo masico (m3/h)' 804  1  
'Flujo masico (m3/min)' 804 1/60  
'Flujo masico (l/min)' 804  1000/60  



Example:
 

Gateway Name Gateway SN Gateway IP Address Gateway MAC Address Device Name Device Local ID Device Type ID Device Type
Name
Logging Interval Historical Intervals
ComX510_F965D0 DN16020SE 192.16.23.50 00:80:67:F9:65 Device_XXXX 2 10000 PM3250    15 4
                   
      Topic ID1 Topic ID2          
      1042 1046          
                   
Error UTC Offset (minutes) Local Time Stamp Active Power (W) Reactive Power (VAr)          
0 120 2017-07-11 01:00:00 76.8382 -7.3920          
0 120 2017-07-11 01:15:00 6.2608 -6.2291          
0 120 2017-07-11 01:30:00 6.2847 -6.7508          
0 120 2017-07-11 01:45:00 6.469 -6.8538          

 

1.28 Satel DL

Satel DL format has the following columns:

date time id devname Parámetro 1 Parámetro 2 (...)

 

  • The date needs to be in the format YYYY/MM/DD 
  • The time needs to be in the format HH:MM:SS
  • The id is optional
  • The devname is compulsory, and will tell the software the device in which we are inserting data
  • The parameters can be the following:
    • EAct imp (kWh): It will correspond to quarter-hourly active energy
    • ERInd imp (kvarh): It will correspond to quarter-hourly reactive energy

(Note that the parser will suppress the spaces and convert capital letters to low-case letters in the headers).

The file should be saved as a csv semicolon-separated columns.

Please check the file attached: SatelDL.csv

 

2. How to register the gateway to DEXCell Energy Manager

In order to register this gateway, follow these steps:

  1. Go to Settings > Gateway > Register a new Gateway and select "Generic FTP" or "Generic email"01_06044fa22a06de2809de785f6acd810e80e5fbb16f1544c1b84f4dd1d3878e01.png
  2. Write a distinctive name for the gateway and click on "Save". Here you will be able to download an example file to check the format of the file02_8e65ed5ce1afa28eec403e50a186d1e80908694a3ba569e336add84005fb9e8b.png
  3. Now it's time to send data using a FTP program, such as FileZilla. You have to indicate the server (ftp.dexcell.com), and the FTP user and FTP password obtained on step number 2. Then, you will have to select the corresponding file from your computer and send it to the server. 03_144e09352fc3dbfbe9aa27edbdcd3b35216bcedecad96ebab69c951ce3486bca.png  
  4. Remind that files take about 15 minutes to be processed and be sent to the server. After that, you will be able to select your devices and see them on the analysis screen.

3. How to import historical data

DEXCell Energy Manager allows inserting data from other systems through a FTP server, where these files are processed and inserted through the platform. 

It is very common that people want to insert historical data into the platform and they follow the former process to do it, the problem is that they are processed as many times as the data is inserted (which can be many times) and this means using more space and resources than the strictly necessary. For this reason, we are going to explain in this article how the insertion must be performed in this case.
 

If it is time to send the historical data using a FTP program, such as FileZilla. Here you must indicate the server (ftp.dexcell.com) and the user and password of the FTP that you could see on the former image. Then click Quickconnect.
 
04_3b3b02883064866250a83e8b8e168088b2823e6229e7c5e78c3b5a96e0b68993.png

Once connected to the server, you can see that it appears a new folder called historic. There is where you will have to insert all your historical data, so it won't be double processed.
 
05_fc22e6d63270bc9bcb52c661aebbdac000749d15210982dd9e0d4e74b5c6385d.png

After this, you will be able to select your devices and see their data on the analysis screen.
 
1 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.