Datalogger recording

The KNX/EIB data are saved to a datalogger channel. A maximum of 20 datalogger channels can be inserted in the device project planning of the panel. New channels can be added by clicking the right mousebutton in the "Datalogger" parameter node in the plug-in. Each channel can be given a designation, so that it is easier to distinguish between the individual channels during later project planning work.

Communication object and data format:

Each datalogger channel possesses a communication object. The data format of this object can be specified using the "Data type" parameter in the parameter group of a channel. The following data formats are available...

DPT 9,001 ... 9,021 (2 byte value), DPT 5,001 ... 5,004 (1 byte value), DPT 14,000 ... 14,079 (4 byte float value),

DPT 8,001 (2 byte numeric value with plus/minus symbol), DPT 7,001 (2 byte numeric value), DPT 13,001 (4 byte numeric value with plus/minus symbol), DPT 12,001 (4 byte numeric value), DPT 6,010 (1 byte numeric value with plus/minus icon), 5,010 (1 byte numeric value).

Recording period:

Telegrams reaching the communication object are divided up within a recording period to vari-ous time intervals and assigned to them. At the end of each time period, the telegrams received are evaluated and a minimum and maximum interval value determined. In addition, an average value is calculated and saved.

The smallest and largest values are evaluated as the minimum and maximum values. To calcu-late the average, the recorded values are totalled and divided by the number of recorded val-ues. If, within a time period, only one telegram data value was received, then the minimum value = maximum value = average value.

The recording period specifies the visible time window of the value-time diagram (scaling of the X axis) in the on-screen display (see chapter 4.2.4.10.2. Datalogger display).

Using the parameter of the same name, the recording period can be configured separately in the datalogger channel in the ETS plug-in. The following recording periods can be configured with the appropriate time periods...

- "Hour (60 intervals of 1 minute)":

The recording period is set to one hour. Within this hour, 60 time intervals are formed, each 1 minute in length, meaning that the incoming telegrams are evaluated 60 times and the results saved.

- "Day (24 intervals of 1 hour)":

The recording period is set to one day. Within this day, 24 time intervals are formed, each 1 hour in length, meaning that the incoming telegrams are evaluated 24 times and the res-ults saved.

- "Week (7 intervals of 1 day)":

The recording period is set to one week. Within this week, 7 time intervals are formed, each 1 day in length, meaning that the incoming telegrams are evaluated 7 times and the results saved.

- "Month (31 intervals of 1 day)":

The recording period is set to one month. Within this month, 31 time intervals are formed, each 1 day in length, meaning that the incoming telegrams are evaluated 31 times and the results saved.

- "Year 1 (12 intervals of 1 month)":

The recording period is set to one year. Within this year, 12 time intervals are formed, each 1 month in length, meaning that the incoming telegrams are evaluated 12 times and the results saved.

- "Year 2 (52 intervals of 1 week)":

The recording period is set to one year. Within this year, 52 time intervals are formed, each 1 week in length, meaning that the incoming telegrams are evaluated 52 times and the res-ults saved.

i If, within a period of time, no telegram could be received and evaluated, then the corres-ponding interval is considered "invalid". The characteristic curve is thus interrupted in the value-time diagram of the on-screen display.

To prevent such behaviour, the data value sources - such as the room temperature control-ler, weather stations, etc. - should transmit the telegram data value cyclically to the bus with a cycle time which is considerably shorter than the set time period. At least two tele-gram data values should be received in a time interval. The evaluation of the minimum, maximum and average values becomes more accurate, the more telegrams are received in the time period.

Cyclic polling:

During data recording, regular incoming telegrams (ValueWrite) or value responses or a cyclic poll (ValueResponse) can be evaluated. Cyclical polling of the object value can be activated separately for each datalogger channel.

With activated cyclic polling, the panel transmits a value read telegram (ValueRead) to the bus regularly, after a period of time has elapsed. The data source must then return a value response telegram (ValueResponse) to the panel. The "Read" flag must be set on the transmitting object of the data source for this to function correctly.

The time period of a cyclic poll can be configured in the ETS plug-in. The setting options auto-matically align themselves to the configured recording period and the resulting time periods.

This ensures that at least one data value is requested within a time period.

i The panel makes a distinction between normal telegrams (ValueWrite) and value response telegrams. With activated cyclic polling, the minimum, maximum and average values are added to the value responses. In this case, additional spontaneous telegrams are only giv-en the maximum and minimum values.

i Cyclic polling is preferable for even average formation.

Saving the data:

When the day changes (jump to 0:00), the recorded time period data of the last recording period of all the data channels is backed up in the non-volatile flash memory of the panel. Only the data of all the completed time periods is taken into account. Temporary data for current, unfin-ished periods is not taken into account on saving to the flash data memory.

After a device reset (power failure or programming operation), the data backed up in the flash memory are rewritten to the normal memory of the panel and are thus available again to the datalogger display.

It should always be noticed that all the data of any day between 0:00 and the current time will not be available after a reset as it is not transferred to the flash data memory before the reset.

This property should especially be taken into account with the short recording periods "Hour"

and "Day" as, in these cases, whole recording periods could be lost if a device reset takes place without successful saving.

i On programming the device firmware, the entire flash data memory is deleted ad overwrit-ten. In this case the saved data of the datalogger no longer exists.

This matter should be particularly taken into account, if, for example, after an update of the ETS plug-in, the device firmware is also automatically updated during a new programming operation.

Differential calculation:

If the data source is a counter (e.g. electricity meter, people counter, etc.), data recording can be switched to differential calculation. In so doing, a differential between the last received value and the last value of the previous period is calculated and stored as a display data value in the panel. No calculation of minimum, maximum or average values take place. The calculated data value differentials then, in the case of an electricity meter, directly represent the consumed units of power within a recording period (e.g. month or year).

To ensure that the differential calculation produces useful display values, only those counter values should be used as data which are counted in one direction (either increasing or decreas-ing). In addition, differential calculation with data values not from counters is usually meaning-less and thus impracticable. Therefore, differential calculation should only be used for data channels which have "Counter" configured as the object data type.

After a device reset (power failure, programming operation), the differential calculation starts at a specified starting value. This is required to initialise the differential formation, so that a differ-ential value can be calculated in the first recording period after a reset. This means that, in addi-tion, there can be an adjustment to defined basic counter levels - for example after the installa-tion of a new electricity meter.

The system project planner must enter the starting value in the parameter of the same name in the ETS plug-in. This means that it is stored statically in the device project planning. A distinc-tion must be made between two different cases:

If a value is entered in the parameter box (standard value = "0"), the value then evaluates the last data value of the first time period after the reset directly and then shows the difference to the starting value in the display diagram (see chapter 4.2.4.10.2. Datalogger display). Alternat-ively, the parameter field of the start value in the ETS plug-in can be left empty. In this case, the panel automatically evaluates the first data value received as the start value. This value does not appear in the data display. Only the differential values calculated after this

(last value of 1st period <-> last value of 2nd period, etc.) are transferred to the display as dis-play values.

i With a set cyclic poll of the channel object, only the response telegrams (ValueResponse) of the data source are used to record the differential data. Additional spontaneous tele-grams (ValueWrite) are not taken into account in a differential evaluation.

e-mail at datalogger:

If the panel is connected to a network via an Ethernet connection and an e-mail mailbox is con-figured to send e-mail messages, the data values recorded by a datalogger channel can be send cyclically by e-mail. In this case, the panel prepares the data in a CSV file and sends it to a specified recipient in a standard e-mail. Both the e-mail function and the recipient address can be configured in the ETS plug-in in the parameter group of a datalogger channel.

The e-mail is sent automatically each time the configured recording period has elapsed. The data forwarded by e-mail thus take only the data values of one recording period into account.

i Irrespective of the sending of the e-mail message, the PC Client software can also read out and archive the data values of the datalogger (see chapter 4.3.1. Introduction, installation and program start).