![Zennio ZCL-MCC User Manual Download Page 8](http://html1.mh-extra.com/html/zennio/zcl-mcc/zcl-mcc_user-manual_3464852008.webp)
MCC
http://www.zennio.com
Technical Support:
http://support.zennio.com
8
Every time the master and the slave send the bus a
master / slave
role confirmation
notification
(see sections 2.2.1 and 2.2.2), they both will also re-send their
checksum
values
through a communication object with the writing and transmission flags
enabled, in order to transmit and receive information through it. If
the received
checksum is different from the one sent
(i.e., the one calculated internally):
Everything related to the thermostatic control will stop working
: no more
sendings will take place, even if the device is working as a master (see
section 2.2.1).
The role notification sending will stop
(master / slave).
The “Configuration error” communication object
will be transmitted with
value ‘1’ every 30 seconds.
The checksum calculated internally
will be transmitted with a one-second
delay, to make it possible to check at any time whether the two configurations
still do not match.
All LEDs will turn off except the configuration error LED
, which will bink
every one second.
The device will remain in the above state
until the
expected
checksum value
is
received (i.e., a value that matches with the one internally calculated), after which the
device will reboot as if it had just been programmed
.
Once the device reboots, it will operate as if it had never detected the wrong
configuration, thus, maintaining the same state it had before the configuration error
detection. Then, it will apply everything specified in section 2.5.
After a restart,
the object “
Configuration error
” is always transmitted with value ‘0’.