Comfort  Automation/ Security System Forums Home

 Moderated by: admin  
AuthorPost
cc_uk
Member
 

Joined: Friday Mar 28th, 2014
Location:  
Posts: 66
Status: 
Offline

  back to top

Hi,

I have just re-commissioned my Comfort system, which is running firmware 7.071  with a UCM with firmware 7.061 and ETH 03 running 2.14.

The ETH 03 is set to set the Comfort time via NTP   and in Comfigurator I have Comfort set to UTC - Dublin, Edinburgh, Lisbon, London  Which is correct since this system is in London.

However I notice that the Comfort time is 1 hour early now that the UK has moved to BST and the clocks went forward one hour.
I don't see any more places I can change this, so any help greatly received.


I should add that when I use server manager and look in SNTP settings the local time is correct.   GMT Time offset here is set to 0 and Readout also 0

Last edited on Wednesday Apr 8th, 2015 03:42 am by cc_uk

slychiu
Administrator


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

  back to top

Check your eth03 firmware should be at least 2.14, see http://www.comfortforums.com/forum113/3904.html as this firmware sets the time based on UTC and allows Comfort to do the daylight saving time change based on the Sunrise /sunset settings
Previous ETH03 firmware does not make the correct time changes for daylight saving

The Comfort server manager should also be the latest

cc_uk
Member
 

Joined: Friday Mar 28th, 2014
Location:  
Posts: 66
Status: 
Offline

  back to top

As mentioned I am running 2,14 firmware for Eth03

I do have sunrise and sunset times set to reflect london as my location yet still have the problem

slychiu
Administrator


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

  back to top

We are not able to duplicate the problem

does anyone else in the UK have the same time offset problem?

juwi_uk
Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1255
Status: 
Offline

  back to top

I'm in the UK too and mine reads as...

Attachment: Eth3Time.png (Downloaded 53 times)

cc_uk
Member
 

Joined: Friday Mar 28th, 2014
Location:  
Posts: 66
Status: 
Offline

  back to top

Thanks for posting this - my Read Out value is 0. Sounds like that could be the culprit... I wonder what that is that for.

slychiu
Administrator


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

  back to top

The READ-OUT value is actually the value of the GMT Time Offset on the left which has been submitted previously
For the UK the GMT Offset is 0
Hence if you have GMT Offset=0 and Submit, the next time you open CS Manager the value should be 0. For Julian's case, the READ OUT is +1, which means that he has not done a new submit after upgrading the CS Manager to 2.14, so the read out is the GMT offset which was last submitted


In ETH2.14, and CSM 2.06, the ETH03 will obtain the UTC time ie equivalent to GMT time from the designated NTP server, add the GST offset without any daylight saving offset and send it to Comfort with a parameter saying that the time does not include any Daylight saving adjustment.

Comfort will do the necessary DST adjustment based on the Sunrise/sunset time screen


eg currently it is 9 April, which has the time put forward 1 hour
Comfort will add 1 hour to the time received from ETH03 and display the correct time

If the date is 1st  march which is outside the DST period, then Comfort does not adjust the time from ETH03

To summarise, ETH03 gets the GMT time offset from the PC and saves it in the "readout". the time from the NTP server is added to the GMT offset and sent to Comfort, and Comfort makes an adjustment if during the DST period

Prior to CSM 2.06 and ETh03 2.14 a different scheme was used which resulted in incorrect time for daylight saving

Hence please ensure that ETH03 is 2.14 and above,  CSM software is 2.06 and above, then open CSM  and click SNTP. "Send Time to Comfort" must be checked.  submit again


Comfigurator Sunrise/Sunset time must be set to the correct city/country

If there is any error, please capture the DT command on the UCM IO monitor




juwi_uk
Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1255
Status: 
Offline

  back to top

Chiu

You are correct that I probably hadn't done a submit after upgrading CSM to 2.14 but where in any instructions does it say I had to do that?  ie not mentioned here for starters.

http://www.comfortforums.com/view_topic.php?id=4026&forum_id=113&highlight=2.14

Also CSM gets upgraded with comfigurator so people might not have even upgraded it separately anyway.

When I'm upgrading the CSM version either separately or implicitly via Comfigurator install you'd should tell me if I need to drill into other Eth3 card settings to do stuff as well.

YEP, my time on my keypad was +1 hour anyway (hadn't checked/noticed) but I've pressed "submit" now and it is correct.

Ta

Julian

slychiu
Administrator


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

  back to top

Yes, I did not realise that this was the way it works

cc_uk
Member
 

Joined: Friday Mar 28th, 2014
Location:  
Posts: 66
Status: 
Offline

  back to top

Thanks for this - once I also click on the Submit button the keypad display on Comfort now shows the correct time.

juwi_uk
Member


Joined: Friday May 25th, 2007
Location: Newbury, United Kingdom
Posts: 1255
Status: 
Offline

  back to top

So do we have to do that every time DST changes?

slychiu
Administrator


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

  back to top

You need to press Submit the first time that you use this SNTP function, r if you are upgrading from the old eth03 or CSM,  or if you change time zones, eg you bnng the system to Africa
Otherwise there is no need to submit again
Check that the READ field is the same as the GMT offset field


UltraBB 1.172 Copyright © 2007-2014 Data 1 Systems