Nomenclature in the documentation

This documentation is a copy of the programmed functions in a plain text description. In the process, all functionalities are basically described and the parameters as well as optional capabilities like for instance BACnet or historic data logging are also listed.

Font sizes and their significance

Significance	Example
Heading of an independent function and/or of an encapsulated programme component	Heading
Title of an area within a function. This area includes detailed information and parameters	Parameter/Option
General descriptive text	Description of the function

Specialised functions and their parameters

A typical application can include specialised functions and options. These are partially listed in tables to assign the data more easily. Moreover, these tables have a coloured title line to immediately recognise the function/option/parameter listed here. Up to 4 specialised functions are described:

· General parameters of the function, e.g. limit value, set points. These tables have a table heading in grey colour.

Designation

Value

· Data points that are autonomously and historically logged in the control. These tables have a table heading in green colour.

Reserved memory

0 KB

                                                           &nb

· Alarm data points that are integrated in an alarm management in the control. These tables have a table heading in orange colour.

Alarm designation

Number

· Data points that are provided by the control as BACnet objects. These tables have a heading in blue colour.

Opt.

Data point

Object information

Historic data logging in the control

The control can autonomously record historic data. These data can then be accessed in a web operation, and where applicable these data can be read out from a control station and processed there.

The control provides a part of the memory for these historic data. As the programme, texts and historic data have to share the same memory, the capacty of the available memory depends on these values. Theoretically a maximum of 640 KB can be used, but this depends on the control type and the previously mentioned data.

The 1 KB memory is the parameter in a cyclical recording of 60 seconds which can save a over the last 2 hours. A maximum assignment of 640 KB * 2 hours/KB results in a theoretical recording time of 1280 hours (=53 days) for one value.

Instead of a cyclical recording, a recording only with a value modification can be alternatively parameterised. This usually extends the data reaching back in time, but does not allow for an accurate statement how far back these data go. Here it is only possible to state the minimum guaranteed data to be saved.

Generally 4 different data types are distinguished which have their own recording rules. These 4 data types are set points, measurement readings, continuous signals and feedbacks.

Here only recording rules are defined. The detailed descriptions contain the values of the system which are in fact recorded.

Recording rules for set points

Parameter	Value
Recording in a value modification of at least	0.5 (Einheit)
Delay between 2 recordings	6.0 s
Enforced cyclical recording after (0 seconds deactivates this option, then only recording in value modification)	0.0 s
Recording (0=Fill&Stop, 1=Ring memory)	1

Recording rules for actual values

Parameter	Value
Recording in a value modification of at least	0.5 (Einheit)
Delay between 2 recordings	6.0 s
Forced cyclical recording after (0 seconds deactivates this option, then only recording in value modification)	0.0 s
Recording (0=Fill&Stop, 1=Ring memory)	1

Recording rules for continuous values

Parameter	Value
Recording in a value modification of at least	2.0 (Einheit)
Delay between 2 recordings	6.0 s
Enforced cyclical recording after (0 seconds deactivates this option, then only recording in value modification)	0.0 s
Recording (0=Fill&Stop, 1=Ring memory)	1

Recording rules for feedbacks

Parameter	Value
Delay between 2 recordings	6.0 s
Forced cyclical recording after (0 seconds deactivates this option, then only recording in value modification)	0.0 s
Recording (0=Fill&Stop, 1=Ring memory)	1

Central function of the control

The control provides several standard functions which are used in the entire programme. These are:

• Monitoring of the control for errors like for instance "Division durch 0" and alarming in the case of an error
• Activation of the WatchDog function. Depending on the application, it can be used to activate a signal light or switch to a redundant control.
• Monitoring of the battery status and alarm indication if it has to be replaced
• Central error acknowledgement for all error signals that have to be acknowledged manually. This can be done with a mechanical button in the switching system or with the virtual button, if a terminal (WebPanel/control technology) is present
• Central acknowledgement of pending maintenance messages and restart of all meters for the maintenance intervals

Anti-block protection of drives

The anti-block protection protects drives from pollution in case of long downtimes. Heating pumps can for example become so soiled in summer by the accumulation of dirt in the pump that they break down. A frequent switch-on of the pump for a short while can prevent this from happening. Anti-block protection can in principal

• Switching drives, e.g. pumps and 2-point flap drives (Open/Close)
• Continuous drives, e.g. valves and butterfly valves

Thereby a differentiated form of anti-block protection can be set for the switching and continuous drives. The principal operation modes are:

• After down time, i.e. each drive monitors itself and switches on autonomously, if it has completed the specified downtime, i.e. was not switched on during the specified period. This has the effect that during the operation of a system, the drives carry out the anti-block protection function at entirely different times.
At a precisely specified time of the week. Thereby all drives are for instance activated to perform an anti-block protection function every Sunday at 12:00 hours. This might be desirable in case of maintenance processes.

One can find out from the settings of the individual drives, if an anti-block protection function of the relevant drive is carried out or disabled. The anti-block protection only provides the operation mode centrally.

The anti-block protection can be deactivated for switching and continuous drives respectively, to prevent a potential switch-on of pumps with emptied pipes in case of maintenance work. This might be realised e.g. by a mechanical switch, at the display or via a building management system switch.

Settings for switching drives

Parameter	Value
Preselection operation mode (1=Off, 2=Downtime, 3=Weekly)	3
In operation mode "Stillstand" always after	24 hours
In operation mode "Wöchentlich" always on (1=Mo, 7=Su)	7
and at	12.00 Uhr

Settings for continuous drives

Parameter	Value
Preselection operation mode (1=Off, 2=Downtime, 3=weekly)	3
In operation mode "Stillstand" always after	24 Std
In operation mode "Wöchentlich" always on (1=Mo, 7=Su)	7
and at	12.00 Uhr

Voltage monitoring FuseGuard

Monitoring of control voltages and/or fuses. With this function, ghost signals can be rejected, if a fuse is blown. In functions that create error signal, the correpsonding fuse can be selected.

For the signals phase monitoring and control voltage, it can be additionally set whether the signals 230 VAC, 24 VAC and 24 VDC are also internally alerted.

Parameter	Value
Group name of the function	FuseGuard
Fuse 230 VAC, normal status (0=NO, 1=NC)	0
Fuse 230 VAC, requiring acknowledgement (0=No, 1=Yes)	0
Fuse 24 VAC, normal status (0=NO, 1=NC)	0
Fuse 24 VAC, requiring acknowledgement (0=No, 1=Yes)	0
Fuse 24 VDC, normal status (0=NO, 1=NC)	0
Fuse 24 VDC, requiring acknowledgement (0=No, 1=Yes)	0
Phase monitor, normal status (0=NO, 1=NC)	0
Phase monitor, requiring acknowledgement (0=No, 1=Yes)	0
Phase monitor: In case of activation, fuses can be emulated as blown (0=No, 1=Yes)	1
Control voltage loop, normal status (0=NO, 1=NC)	0
Control voltage loop, requiring acknowledgement (0=No, 1=Yes)	0
Control voltage loop: In case of activation, fuses can be emulated as blown (0=No, 1=Yes)	1