PDA

View Full Version : PICED sets wrong Date on Comfort


Ingo
01 Oct 09, 04:27 AM
Hi,

I noticed a few times that my Comfort system sometimes changes to the wrong date. Tonight I actually simulated this after a project download via PICED.

When doing a project download, one of the options are to set the Date & Time. Usually you set this to make sure that your PAC is running the right time and date.

After a transfer my Comfort panel changed from year 09 to year 29. The output below is from Comfigurator's Monitor window showing, firstly, setting the time & date back to normal using Comfigurator and then doing a Date & Time setting using PICED connected via USB to the PAC.

Setting Date & Time via Comfigurator.

> DT20090930184247
< DT20090930184247


Doing a Set Date & Time from PICED 4.7.1.
< DT51290930194326
< DT51290930194300
< DT51290930194300

Am I the only one time travelling to the year 5129??? Seems a lot like 2009 to me :-) I don't know if this is an incorrect command sent to Comfort via PICED or is the command interpreted wrong by the UCM/CBus connecting the two units together. I presume it's the UCM/CBus because below is the log entry for PICED (running on a second PC for capture purposes)

2009/09/30 19:43:31 Date/Time: Received C-Bus message to set date to 2009/09/30
2009/09/30 19:43:31 Date/Time: Received C-Bus message to set time to 19:43:31
2009/09/30 19:43:31 Date/Time: Received C-Bus message to set time to 19:43:31
2009/09/30 19:43:32 Date/Time: Received C-Bus message to set time to 19:43:32
2009/09/30 19:43:32 Date/Time: Received C-Bus message to set time to 19:43:32

Can anyone confirm my findings?

Thanks,
Ingo

NickD
01 Oct 09, 10:30 AM
Can't confirm as I don't have a Comfort system.. however I suspect what is happening is that the PAC broadcasts the time on C-Bus when it is set during the upload, and that the Comfort is not handling this message properly.

Nick

Ingo
01 Oct 09, 03:13 PM
Nick,

I am going to test an older Comfort UCM/CBus firmware tonight and post the results.

Ingo

Ingo
02 Oct 09, 03:58 PM
I found the problem, it's the UCM/Cbus that seems to wrongly interpret a Date setting. This is only in a Beta firmware and all released UCM/CBus firmware should be fine. Results below:

Setting Date & Time using Comfigurator and monitoring with Diag Tool.
2009/10/02 07:19:29 Rx : Local Network, Source Unit 18, Time, Date Friday 2/10/2009

Setting with PICED via PAC.
2009/10/02 07:24:25 Rx : Local Network, Source Unit 19, Time, Date Friday 2/10/2009, Time 07:24:14