Comfort Automation/ Security System Forums

I have a Comfort Ultra II running firmware 5.164 with a UCM Type 10 (CBUS) at 5.092 and the UCM Ethernet.

I had a power cut a couple nights ago and since then the keypad shows Communication Failure Slave 1.  I have tried the reset and the re-write of the .cclx file, but this only fixes the problem for about 10 seconds and then the issue returns.

What do I need to do?

I suspect I need to re-load the firmware, but to be honest I am lost as to what I can upgrade with my firmware and what I can\'t.

Please help!

Do you have a Slave? If not then the Number of Slaves in your cclx file should be 0
If you have no slave connected and the Number of slaves is 1, then you will get a Communications failure Slave 1

You do not need to upgrade firmware to fix this

My cclx file is showing a slave, always has done, but to be honest I am not sure what a slave is?

Given that I have one how do I fix the problem?

Thanks!

A Slave is an Expansion Module https://www.cytech.biz/slave_expansion_modules.html

If you do not have one and your cclx file does then it has been programmed wrongly
Set the number of Slaves to 0 in the Modules Tab

Programming with Comfigurator has all the details https://www.cytech.biz/programming_with_...rator.html

No, I have a slave, always have done so why would I suddenly have to tell Comfort I dont have one?

This has happened since the power cut so something has changed or been damaged, how do I check what that is?

Thanks.

I was replying  based on your information supplied

• If you do not have a slave  then you must set the number of slaves = 0
• If you DO  have a  slave as you now say, then you must set the number of slaves = 1.
  

If you get a message saying Slave 1 communications Failure, it means that Comfort is not getting any Communications  from Slave #1. Try resetting the Slave, or removing power from the slave and applying power again. if the problem still remains it means that the slave is probably faulty and needs to be replaced

Resetting the power to the SEM worked, thanks for correcting the problem.
Paul.