MCC
http://www.zennio.com
Technical Support:
http://support.zennio.com
11
Note
:
the time to wait before reporting the
‘missing slave’ notification starts counting on
the last reception of a slave notification (the first time, the count begins once the device
adopts the master role).
2.2.2
SLAVE
When MCC operates as a slave, its internal thermostats listen to the communication
objects being written to the KNX bus, and update their states and communication
objects. The main difference is that a
slave MCC
doesn’t send any communication
objects (related to thermostats)
to the bus. Thus, master thermostats and slave
thermostats will always have the same state (at least after a certain time, in case both
MCCs were not put in operation simultaneously).
While the device is operating as a slave, the slave LED indicator is on.
2.2.2.1
SENDING READ REQUESTS
After a reboot, as long as MCC is operating as a slave (i.e., when the device state is
not
“master” nor “undefined”), the device may send
requests to read certain objects
in order to update the statuses of its thermostats
, provided that such requests have
been enabled by parameter. Specifically, the following communication objects are read:
Transition Time: comfort to default mode
Transition Time: standby to economy
Comfort Setpoint Reset Time
User Setpoint Control (Cooling and Heating)
Comfort Setpoint (Cooling)
Standby Setpoint (Cooling)
Economy Setpoint (Cooling)
Protection Setpoint (Cooling)
Comfort Setpoint (Heating)
Standby Setpoint (Heating)
Economy Setpoint (Heating)
Protection Setpoint (Heating)
