[danner]

Noticed a glitch in the matrix.

This morning at 0200 the clocks were supposed to go back 1 hour. My RPI3 and Cumulus MX went back to 0100 but the Pro2+ receiver didn't go back 1 hour until 0300. It appears Cumulus MX handled the time change fine for uploading to wunderground and logging.

Is there a setting where can I tell it to go back 1hr at 0200 instead of 0300? And on March 11 the time change comes at 0200, is there a setting for that as well?

I noticed my WirelessDisplay had the incorrect time at ~0230. When I went to the receiver I noticed there was no green indicator for the RTC. I stopped Cumulus MX and rebooted the Pro2+ and the RTC green dot came back. At 0300 it went back 1hr.

I'm still running v320_b002 because it has been raining and cold and I'm not changing the software on the TX until spring so I haven't changed the receiver software either.


TIA

[danner]

OK that's not good. When 0300 came the time went forward 1 hour. It should read 0316 but it now says 0416. The RTC green dot is present on the receiver.

[danner]

now the clock says 0337. LOL. I don't know what is going on.

[AllanG]

Hi Danner.

Clocks here in the UK went back an hour (so we revert to UTC) last weekend and as far as I know, things happened as they should though I wasn't around at 2-3am to check exactly what time it all happened...!!

Are the settings correct in the "Timezone" section of your RX software "Config_RX_Pro2PLUS.h" tab?? If you need it there's an explanation of the settings by Werk_AG in the third post here:

http://www.meteocercal.info/forum/Thread...t=timezone


Allan.

[danner]

The clock hasn't changed since the last change around 0330 so it's good now. Don't know why it was switching back and forth. That was strange for sure.

And Werk was the one who configured my time zone info in a post a while back so I'm pretty sure it's ok.

For what it's worth here's the code.

Code:

// --------------------------------------------------------------------------------------
//   Define rules for Auto Summer Time Display, and clock adjustment
// --------------------------------------------------------------------------------------
// Example for Australia Eastern Time Zone (Sydney, Melbourne)
// TimeChangeRule aEDT = {"AEDT", First, Sun, Oct, 2, 660};    //UTC + 11 hours
// TimeChangeRule aEST = {"AEST", First, Sun, Apr, 3, 600};    //UTC + 10 hours
// Timezone myTZ(aEDT, aEST);

TimeChangeRule usEDT = {"USEDT", Second, Sun, Mar, 11, -240};   //UTC - 4 hours
TimeChangeRule usEST = {"USEST", First, Sun, Nov, 5, -300};    //UTC - 5 hours
Timezone myTZ(usEDT, usEST);

[hornychz]

The clock hasn't changed since the last change around 0330 so it's good now. Don't know why it was switching back and forth. That was strange for sure.

And Werk was the one who configured my time zone info in a post a while back so I'm pretty sure it's ok.

For what it's worth here's the code.

Code:

// --------------------------------------------------------------------------------------
//   Define rules for Auto Summer Time Display, and clock adjustment
// --------------------------------------------------------------------------------------
// Example for Australia Eastern Time Zone (Sydney, Melbourne)
// TimeChangeRule aEDT = {"AEDT", First, Sun, Oct, 2, 660};    //UTC + 11 hours
// TimeChangeRule aEST = {"AEST", First, Sun, Apr, 3, 600};    //UTC + 10 hours
// Timezone myTZ(aEDT, aEST);

TimeChangeRule usEDT = {"USEDT", Second, Sun, Mar, 11, -240};   //UTC - 4 hours
TimeChangeRule usEST = {"USEST", First, Sun, Nov, 5, -300};    //UTC - 5 hours
Timezone myTZ(usEDT, usEST);

Hi danner,

I think you have bad definition of the hour in which the change should occur:

11 = eleven o'clock ... should be 2 (maybe? - two o'clock in the morning)
5 = five o'clock ... should be 3 (maybe? - three o'clock in the morning)

Try it. 

[werk_ag]

And Werk was the one who configured my time zone info in a post a while back so I'm pretty sure it's ok.

Alma, Michigan is GMT/UTC - 5h during Standard Time
Alma, Michigan is GMT/UTC - 4h during Daylight Saving Time


Alma, Michigan started Daylight Saving Time on
Sunday March 12, 2017 at 2:00 AM local time

Alma, Michigan ends Daylight Saving Time on
Sunday November 5, 2017 at 2:00 AM local time.


If the info above is right, these settings are correct. Note that you have 11 instead of 12 on first rule.
Edited: This info is wrong!

Correct settings should be:

// --------------------------------------------------------------------------------------
//   Define rules for Auto Summer Time Display, and clock adjustment
// -------------------------------------------------------------------------------------

TimeChangeRule usEDT = {"USEDT", Second, Sun, Mar, 2, -240};   //UTC - 4hours
TimeChangeRule usEST = {"USEST", First, Sun, Nov, 2, -300};    //UTC - 5hours
Timezone myTZ(usEDT, usEST);

This morning at 0200 the clocks were supposed to go back 1 hour. My RPI3 and Cumulus MX went back to 0100 but the Pro2+ receiver didn't go back 1 hour until 0300.

...

The clock hasn't changed since the last change around 0330 so it's good now. Don't know why it was switching back and forth. That was strange for sure.

Never saw it happens, however I took note of it for further investigation.

[danner]

If the info above is right, these settings are correct. Note that you have 11 instead of 12 on first rule.

DST in 2018 is 11 Mar, no? Unless I'm misunderstanding what the 12 is for? Should the 11 be 2? for 2am?

[danner]

So is this correct? The "2" meaning change the time at 0200?

Code:

// --------------------------------------------------------------------------------------
//   Define rules for Auto Summer Time Display, and clock adjustment
// --------------------------------------------------------------------------------------
// Example for Australia Eastern Time Zone (Sydney, Melbourne)
// TimeChangeRule aEDT = {"AEDT", First, Sun, Oct, 2, 660};    //UTC + 11 hours
// TimeChangeRule aEST = {"AEST", First, Sun, Apr, 3, 600};    //UTC + 10 hours
// Timezone myTZ(aEDT, aEST);

TimeChangeRule usEDT = {"USEDT", Second, Sun, Mar, 2, -240};   //UTC - 4hours
TimeChangeRule usEST = {"USEST", First, Sun, Nov, 2, -300};    //UTC - 5hours
Timezone myTZ(usEDT, usEST);

[werk_ag]

So is this correct? The "2" meaning change the time at 0200?

Code:

// --------------------------------------------------------------------------------------
//   Define rules for Auto Summer Time Display, and clock adjustment
// --------------------------------------------------------------------------------------
// Example for Australia Eastern Time Zone (Sydney, Melbourne)
// TimeChangeRule aEDT = {"AEDT", First, Sun, Oct, 2, 660};    //UTC + 11 hours
// TimeChangeRule aEST = {"AEST", First, Sun, Apr, 3, 600};    //UTC + 10 hours
// Timezone myTZ(aEDT, aEST);

TimeChangeRule usEDT = {"USEDT", Second, Sun, Mar, 2, -240};   //UTC - 4hours
TimeChangeRule usEST = {"USEST", First, Sun, Nov, 2, -300};    //UTC - 5hours
Timezone myTZ(usEDT, usEST);

Yes, that is correct! The info on my previous post is wrong, sorry...
Please refer to the readme file, included in the TimeZone library