User Manual

26/90
Building Technologies Integration von DESIGO™ RXC in VISONIK CM2Z8338en_01
Building Automation Integration functions 12.06.2006
3.2.6 Displaying the actual controller operating mode
All RXC applications
VISONIK BPS NIDES.RX RXC controller
DP.Parameter Function/Range NV name / element Function/Range
BT
User designation NV name NV element
@TCRn.AOPST
See table of bindings ←
nviEffectOccup
2)
See table of bindings ←
1
Effect Occup
nvoEffectOccup
2)
2)
In the RXC Application Library V2, the NV element EffHvacMode.op_mode is used instead of NV EffectOccup.
Table of bindings
Effect Occup @TCRn.AOPST
0 = Occupied 0 = Comfort
3 = Standby 1 = Pre-comfort
2 = Economy 1 = Unoccupied
1)
3 = Standby
1)
The NV “Effect Occup” does not distinguish between the
TEC operating states Economy and Standby.
The effective operating state is therefore determined by the
CFE-SW in accordance with the following flow chart.
In order for this to work properly, either the window contact
(nvoEnergyHoldOff) or the basic setpoints (nciSetpoints)
must be integrated (see further below).
If neither of these is integrated, then ensure that the basic
setpoints, set in the controllers with the RXT tool match
those in the BPS.
Note: From CFE Version 2.1 on, there is no longer a
"Setpoint change" test. Refer to the V2.1 release
notes (Intranet).
Effect Occup
= Unoccupied
@TCRn.SOPST=3
(Standby)
@TCR.AOPST=2
(Economy)
@TCR.AOPST=3
(Standby)
nvoEnergyHoldOff
(window contact)
integrated
Setpoint change:
ASPH-SPEH/=0 or
ASPC-SPEC/=0
@TCRn.WINO=1
(window open)
yes
yes
yes
yes
01138en