How to stop Date/Time announcement to CBus?

[Ingo]

Is there a way to stop the Date/Time announcement from Comfort to CBus? I had the strange case where lightning \'upset\' my system again. After I got home and reset the system it then proceeded to think it was still 5/3/2010 instead of 7/3/2010. This then changed my PAC time and date and all my nightly programs on CBus started to execute in the middle of the day.

Thanks,
Ingo

[slychiu]

You cannot stop the date and time sync betwen Comfort and Cbus
Make sure you have a TPB or APB surge arrestor oin the telephone line as that is the most susceptible to lightining surges

[Ingo]

I have no telephone connection on my system, I suspect the long cable runs to all my 64 zones to be the \'pickup\' for the EM interference. The rest of the system is well protected as per our previous discussion on lightning.

[slychiu]

Correct, the cable runs may cause high voltage to be picked up, especially from magnetic contact or sensors on the windows
Comfort is well protected so that it should not be damaged  unless there is a direct lightning strike on the sensors

One of the features to be implemented in a new generation UCM/CBus will be an option to send Comfort Time to Cbus just like the UCM/KNX

[Ingo]

Thanks Chiu,

I saw the KNX feature and that is why I asked about the CBus side.

Ingo.

[Pgordon]

[user=1]slychiu[/user] wrote:

One of the features to be implemented in a new generation UCM/CBus will be an option to send Comfort Time to Cbus just like the UCM/KNX

Is this \"new generation\" CBUS USM now available? if not is it imminent?

Is it new hardware, or just updated firmware? - trying to get a handle on whether I might want to upgrade my current CBUS UCM to a new one... I too have experienced \"issues\" with time synchronisation between Comfort & CBUS, especially around the DST changes... - FYI, I *HAVE* been able to stop time sync messages passing between them, so I now have isolated the date/time between them (they are currently running an hour apart due to the DST thing)....

Cheers.

Paul G.

[slychiu]

No it is not imminent, stil in the planning stages.
The main difference in the hardware will be the addition of an EEPROM IC. Current UCM/Cbus has an empty socket for the EEPROM so it can be upgraded easily by adding the IC and upgrading firmware.

You say you have a time synchronisation problem due to DST
Why is this a problem. Comfort\'s time should be correct as it automatically adjusts for DST, and it should update Cbus time so the times should be synchoriised. Why is your time not synchronised

[Pgordon]

[user=1]slychiu[/user] wrote:

No it is not imminent, stil in the planning stages.
The main difference in the hardware will be the addition of an EEPROM IC. Current UCM/Cbus has an empty socket for the EEPROM so it can be upgraded easily by adding the IC and upgrading firmware.

You say you have a time synchronisation problem due to DST
Why is this a problem. Comfort\'s time should be correct as it automatically adjusts for DST, and it should update Cbus time so the times should be synchoriised. Why is your time not synchronised

Thanks for the update Chiu. - the problem I had with DST was CBUS was constantly causing Comfort\'s time to be 1 hour out... - see here if you\'re interested in the details... http://www.cbusforums.com/forums/showthread.php?t=6434&highlight=wiser+time

and here as well: http://www.cbusforums.com/forums/showthread.php?t=5938&highlight=wiser+time

I \"fixed\" it by performing some black magic in the CBUS diagnostic utility, using some instructions that I was pointed at (which for the life of me I can\'t find now).... which I believe had the effect of filtering the CBUS messages passed through the UCM to specific applications.... (the date/time app NOT being one of them!) - thus blocking the passage of date/time sync messages between Comfort & CBUS, - and allowing me to set the time in comfort and have it stay set.... CBUS can do what the *** it likes with its time now, since I do no time-related functions there...

So, just to contradict the statement elsewhere in this thread, it *IS* possible to stop date/time sync between the two systems...


So if I\'ve understood correctly, you\'re saying the new UCM hardware isn\'t actually different from current since the current platform already has the IC socket?... - you\'re just actually making use of it with a new IC?... - so in theory my EXISTING UMC should be upgradeable when that IC becomes available?...


Cheers

Paul G.

[slychiu]

To upgrade the firmware you must have the \"new\" UCM/CBUS shown in the photo in the first post. This has a flashable processor. The firmware for this type is 5.100 and above

The 1st generation UCM/Cbus has a non-flash processor as shown in the photo below. Hence this type cannot be upgraded by firmware upgrade The firmware for the old type is 5.99 and below.

I have looked at the posts in the cbus forum about the non-conformance of Comfort UCM/Cbus to the time/date application. They say it is known and someone at Clipsal had been in communication with us, but this is the first time we have heard about it
http://www.cbusforums.com/forums/showthread.php?t=6434&highlight=wiser+time&page=2

It is true that we send a date and time message to Cbus with the DST field =0 even though the time has been changed in Comfort to Daylight saving. Basically Comfort ignores that field, historically because before the sunrise/sunset feature wwas implemented, Comfort did not know whether it was in Daylight saving or not.

However I dont think that is the cause of your problem because it is now December and there is no more daylight saving, so DST = 0 would be correct and would not cause Cbus to change its time

Anyway the next Cbus firmware will fix the DST issue
Admin Note: Fixed in UCM/Cbus 5.235, see http://www.comfortforums.com/forum85/2293.html