Comfort  Automation/ Security System Forums Home
Home Search search Menu menu Not logged in - Login | Register

Date issue
 Moderated by: admin Page:    1  2  Next Page Last Page  
 New Topic   Reply   Printer Friendly 
 Rate Topic 
AuthorPost
 Posted: Tuesday Jan 3rd, 2017 07:47 pm
   PM  Quote  Reply 
1st Post
Craig Robins
Member
 

Joined: Monday Mar 3rd, 2014
Location:  
Posts: 43
Status: 
Offline

  back to top

I'm currently having a problem where the date shown on keypads and reported in email alerts is 24 hours in the future.
Using the Set Comfort Date/Time feature in Comfigurator corrects this, only for the problem to recur on the next automatic date/time update from the UCM/ETH03. This can be clearly seen in the log.
Looking through the emails received from Comfort, I can see that the problem started happening between 1726 and 1808 on 31st December.
I seem to recall there was a similar issue last year which was fixed by upgrading the UCM/ETH03 firmware to v2.20. That is the firmware that I am currently running.



 Posted: Wednesday Jan 4th, 2017 06:09 am
   PM  Quote  Reply 
2nd Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 5493
Status: 
Offline

  back to top

We have discovered a problem with the ETH03. In 2017 the date is wrong by + 1 day
Please hold on we are testing a fix for this



 Posted: Wednesday Jan 4th, 2017 06:20 am
   PM  Quote  Reply 
3rd Post
Craig Robins
Member
 

Joined: Monday Mar 3rd, 2014
Location:  
Posts: 43
Status: 
Offline

  back to top

Thanks, Chiu. I'll keep an eye out for developments.



 Posted: Monday Jan 9th, 2017 12:04 pm
   PM  Quote  Reply 
4th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 5493
Status: 
Offline

  back to top

Please see http://www.comfortforums.com/view_topic.php?id=4596&forum_id=113&jump_to=21406#p21406 for info on the new ETH03 firmware 2.22 to fix this bug



 Posted: Monday Jan 9th, 2017 08:07 pm
   PM  Quote  Reply 
5th Post
Craig Robins
Member
 

Joined: Monday Mar 3rd, 2014
Location:  
Posts: 43
Status: 
Offline

  back to top

This has certainly fixed the date issue on the keypads. However, it has not done so for the C-Bus edlts in my set-up.

With V2.20 the date and time would be correct on the edlts after a manual setting of Comfort date/time, as would the keypads, but both would jump forward a day on the next automatic update from the UCM/ETH03. With V2.22 the keypads are now correct but the date on the edlts has stayed 1 day ahead, even following a manual setting of Comfort date/time.

To verify this was an issue with the new firmware, I downgraded to V2.20 and found I could now manually change the date on the edlts as before. I immediately upgraded to V2.22 again and waited to see what would happen on the next automatically date/time change from the UCM. The date on the edlt was unaffected. The logical conclusion is that the new firmware is not sending the updates to C-Bus at all, just Comfort.



 Posted: Tuesday Jan 10th, 2017 06:26 am
   PM  Quote  Reply 
6th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 5493
Status: 
Offline

  back to top

what do you mean by Cbus Edits?

ETH03 firmware does not affect Cbus, it just sends the time to Comfort
UCM/Cbus handles Cbus communications so one should not have anything ot do with the other



 Posted: Tuesday Jan 10th, 2017 08:19 am
   PM  Quote  Reply 
7th Post
Craig Robins
Member
 

Joined: Monday Mar 3rd, 2014
Location:  
Posts: 43
Status: 
Offline

  back to top

The C-Bus eDLT is a switch which uses extended dynamic labelling technology. Mine are programmed to show the date and time which is sent to them by Comfort via the UCM02.

Prior to the firmware update, they displayed the same date and time as the keypads. If you did a manual setting of Comfort date/time, both the eDLTs and the keypads would show the correct date until the next auto update when the date on both would jump ahead by a day, as you are aware.

After the firmware upgrade to V2.22, the date on the keypads was correct but the eDLTs were still displaying one day ahead.

By downgrading and upgrading the UCM/ETH03 firmware, I have established conclusively that the eDLTs are no longer receiving date and time info from Comfort with V2.22 whereas they were with V2.20. Nothing else has changed apart from the firmware. Downgrading back to V2.20 results in the eDLTs being updated once again, albeit with a date that is one day ahead, which clearly points to a bug in V2.22 causing the latest issue.



 Posted: Tuesday Jan 10th, 2017 08:29 am
   PM  Quote  Reply 
8th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 5493
Status: 
Offline

  back to top

Please send your cclx file to support@cytech.biz so we can investigate thios strange issue



 Posted: Tuesday Jan 10th, 2017 04:50 pm
   PM  Quote  Reply 
9th Post
Craig Robins
Member
 

Joined: Monday Mar 3rd, 2014
Location:  
Posts: 43
Status: 
Offline

  back to top

Will do



 Posted: Wednesday Jan 11th, 2017 05:20 pm
   PM  Quote  Reply 
10th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 5493
Status: 
Offline

  back to top

The cclx file seems OK
However your comfigurator version seems to be 3.11.0? Is there any reason you did not upgrade to the latest 3.11.10 Sometimes this can affect some of the features

We cannot see any reason the ETH03 would affect the date setting

can you try this test>?

In Comfort Server Manager, disable SNTP setting so Comfort does not get any time updates from ETH03

Then change the time on Comfort
Does the time change crrectly on the eDLT?



 Posted: Wednesday Jan 11th, 2017 09:02 pm
   PM  Quote  Reply 
11th Post
Craig Robins
Member
 

Joined: Monday Mar 3rd, 2014
Location:  
Posts: 43
Status: 
Offline

  back to top

Before I could perform your test I had to temporarily downgrade to V2.20 so that the date would be wrong again. Having achieved that, I immediately reupgraded to V2.22.

I then did as you advised. As before, the date on the keypads changed but not on the eDLTs.

I noticed that I didn't have the latest firmware for the controller so I upgraded from V7.099 to V7.116. Unfortunately, that made no difference either.

To summarise where we are:

V2.20 I can manually change the date on both Comfort and the eDLTs to be correct but with SNTP enabled this will jump a day ahead on the next auto date/time update.

V2.22 I can manually change the date on Comfort only. Having SNTP enabled or disabled makes no difference.

I agree with you that it seems odd that a firmware update on the UCM/ETH03 should have this effect but I can only report what I am observing. Under V2.22, there is some interaction between the UCM and the controller which is preventing time updates on the eDLTs which wasn't the case with V2.20 or earlier.

Last edited on Thursday Jan 12th, 2017 03:50 pm by Craig Robins



 Posted: Thursday Jan 12th, 2017 11:25 am
   PM  Quote  Reply 
12th Post
Ingo
UCM Pi Users


Joined: Sunday Jan 21st, 2007
Location: South Africa
Posts: 557
Status: 
Offline

  back to top

Craig,
I don't have an eDLT but did some testing on my Cbus system and couldn't find anything wrong with the format of the Date/Time updates received from Comfort. Please elaborate on your statement below:
V2.20 I can manually change the date on Comfort only. Having SNTP enabled or disabled makes no difference.

Do you mean that you can't change time on the eDLT at all? Strange. Remember also that the Eth03 only provides updates to Comfort, it's the function of the UCM/Cbus2 that propagates the update to Cbus if the checkbox is selected. If you uncheck this checkbox then time updates from Comfort will not be sent to Cbus at all.
Ingo



 Posted: Thursday Jan 12th, 2017 04:09 pm
   PM  Quote  Reply 
13th Post
Craig Robins
Member
 

Joined: Monday Mar 3rd, 2014
Location:  
Posts: 43
Status: 
Offline

  back to top

There was an error in my previous post. It should have read:

V2.20 I can manually change the date on both Comfort and the eDLTs to be correct but with SNTP enabled this will jump a day ahead on the next auto date/time update.

V2.22 I can manually change the date on Comfort only. Having SNTP enabled or disabled makes no difference.

I've now edited it accordingly.

No, Ingo, I cannot change the time at all on the eDLTs with V2.22 whereas I can with V2.20. I am aware that the Eth03 only updates Comfort which then passes the info to Cbus via the UCM/CBus2. That's what makes this so odd. You wouldn't expect a firmware update to the Eth03 to be able to cause this but the fact remains that I only have this problem with V2.22 (if I revert to V2.20 the problem goes away but then I habe the problem of the date being a day out again!) which suggests there is a curious interaction between the new firmware and Comfort which prevents it passing the time to the UCM/Cbus2.

And yes, the checkbox you refer to is ticked, as has been verified by Cytech who looked at my cclx. Without that, it wouldn't work under V2.20 either.



 Posted: Thursday Jan 12th, 2017 04:22 pm
   PM  Quote  Reply 
14th Post
Ingo
UCM Pi Users


Joined: Sunday Jan 21st, 2007
Location: South Africa
Posts: 557
Status: 
Offline

  back to top

It is very curious. I did a packet capture on the Cbus network and both 2.20 and 2.22 have the same format so it shouldn't affect it unless I missed something. Perhaps another user with an eDLT can do some testing on their side as well. Just to make sure, check that your UCM/Cbus2 is on the latest firmware and also the eDLT. I know there is a way to upgrade it but don't know the specifics.

PS. Cbus firmware 7.068 is the latest, not 7.054 what is shown in Comfigurator.

Last edited on Thursday Jan 12th, 2017 04:26 pm by Ingo



 Posted: Thursday Jan 12th, 2017 05:19 pm
   PM  Quote  Reply 
15th Post
Craig Robins
Member
 

Joined: Monday Mar 3rd, 2014
Location:  
Posts: 43
Status: 
Offline

  back to top

Ingo, I think I will have difficulty upgrading the UCM/Cbus2 firmware. It is currently 7.054 and I believe that cannot be upgraded with Comfigurator. Although, I have the Eth03 so in theory I could use the programming cable methgod, they are in separate panels in different parts of the house.



 Posted: Thursday Jan 12th, 2017 05:21 pm
   PM  Quote  Reply 
16th Post
Ingo
UCM Pi Users


Joined: Sunday Jan 21st, 2007
Location: South Africa
Posts: 557
Status: 
Offline

  back to top

Nope, it would be quite easy. Just download the file and use Comfigurator to upgrade From Local file.



 Posted: Thursday Jan 12th, 2017 05:28 pm
   PM  Quote  Reply 
17th Post
slychiu
Administrator


Joined: Saturday Apr 29th, 2006
Location: Singapore
Posts: 5493
Status: 
Offline

  back to top

I checked your cclx file, it  is Cbus2 7.054 firmware, and it can be upgraded without ucm firmware cable. Only ucms firmware 5 need firmware upgrade cable



 Posted: Thursday Jan 12th, 2017 05:40 pm
   PM  Quote  Reply 
18th Post
Craig Robins
Member
 

Joined: Monday Mar 3rd, 2014
Location:  
Posts: 43
Status: 
Offline

  back to top

I just tried and I get a "product number or type doesn't match" error. I think that's because it isn't the specific version for Cbus2. Where can I download that from please as Comfigurator will only let me download 7.054 as it thinks that is the latest?

Last edited on Thursday Jan 12th, 2017 05:44 pm by Craig Robins



 Posted: Thursday Jan 12th, 2017 05:47 pm
   PM  Quote  Reply 
19th Post
Ingo
UCM Pi Users


Joined: Sunday Jan 21st, 2007
Location: South Africa
Posts: 557
Status: 
Offline

  back to top

http://www.cytech.biz/ucmcbus2_firmware.html



 Posted: Thursday Jan 12th, 2017 05:51 pm
   PM  Quote  Reply 
20th Post
Craig Robins
Member
 

Joined: Monday Mar 3rd, 2014
Location:  
Posts: 43
Status: 
Offline

  back to top

Sorry, I've found the Cbus2 firmware now and I'm installing it.



 Current time is 03:44 pmPage:    1  2  Next Page Last Page  
Top




UltraBB 1.172 Copyright © 2007-2014 Data 1 Systems