View single post by Ingo | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Posted: Tuesday Oct 18th, 2016 09:15 pm |
|
||||||||||||
Ingo
|
Interesting... Being in a location that doesn't use DST I can't comment on the random changes but I must confess that I've never picked up anything like that on the Cbus forums. If you want Comfort to manage time on Cbus then all you have to do is to enable the SNTP setting in the Eth03 configuration and also enable the Timekeeping checkbox on the UCM/Cbus2 interface. Comfort will periodically broadcast the time but there is a limitation. The Cbus time protocol expects the Time Master to send time more regular than itself. With this I mean if a time broadcast is detected it will accept it as a Master only if the broadcasts are repeated more often than it's own internal clock. The limitation comes in where the Eth03 ONLY broadcasts the time if it's out by x seconds and if your Comfort clock is very stable it could be many hours before another broadcast is sent to the bus. If this time exceeds 60 minutes then Cbus reverts back to itself as the master and the cycle start again. My proposal to Cytech was to periodically send Time Broadcasts to Cbus irrespective if the Eth03 updates the time or not. Unfortunately this creates another problem. For the UCM/Cbus to detect a Time Broadcast it has to be sent on the bus. This then creates a Time Change entry in the log file and fills it up fairly quickly. Bit of a catch-22 situation if you ask me. Perhaps the UCM/Cbus2 can keep the time running local to the UCM and periodically send it to Cbus so no log entry will be made. This might or might not be possible, only time will tell. Ingo
|
||||||||||||
|