Slave comm failure and then instant recovery after upgrade to 7.207

[freak69]

HI, I have just upgraded firmware on my slave to 7.207.Now every time I reset the system I get:

Code:

07/06 00:00 Reset Comfort Controller0
7/06 00:00 Comm. failure # Slave 1
07/06 00:00 Comm. restore # Slave 1
02/11 18:22 Date/Time Change UCM 1
02/11 18:24 Sign in - User # 10
2/11 18:36 Sign in - User # 1
02/11 18:37 Sign in - User #1
02/11 18:38 Sign in - User # 1
02/11 18:39 Reset Comfort Controller
02/11 18:39 Sign in - User # 1
02/11 18:40 Sign in - User # 1
02/11 18:40 Comm. failure # Slave 1
02/11 18:40 Comm. restore # Slave 1

 
Seems stable after the restore - is this a reported bug or smoothing else? FYI, controller is 7.201Thanks!

[slychiu]

I believe this is a timing issue at reset and should not affect the operation of the slave. Let me know if you encounter any problems

[freak69]

Hi,It seems fine apart from the alarm going off every time I reset, and my wall panel constantly telling me there is or was a slave communication issue. It was fine before I upgraded and has never happened before, should I try and downgrade? Is this a reported bug that can be looked at in a new version?Thanks

[slychiu]

Sure, we will check if it happens on other systems

[Guest]

I had exactly the same issue. The comms failure rectifies itself but it was extremely annoying getting these warnings after any reset. I have now downgraded the slave firmware to stop this happening again.

[eborges]

I\'m also having this same communications failure to Slave when I reset the ystem. I\'m runing firmware 7.201 on the controller and 7.207 on the slave board

[slychiu]

It looks like the slave is slow to respond to a initial poll by Comfort. we shall check it further

[timop001]

I have just updated to the latest firmware - Updated ULT (7.201) UCM (7.176) and SEM (7.207) firmware and am relieved to see that others have encountered the same problem. Comms error to Slave after reset and Comfigurator transfer.

[slychiu]

We have not encountered this but will check again

[timop001]

It looks like the same issue as mentioned by others in this thread...

Is there a fix or shall I downgrade the slave (SEM02-M2) to the previous version ?
Can one downgrade via the ETH03 connection or does it require a cable upload ?