1 minute ago, unofix said:

Next you'll be trying to convince me that Scotland is still part of Britain 🤣

Well, it will be as soon as Queen Nicola vacates the premises LOL

On 3/26/2023 at 11:01 AM, unofix said:

Well here it is ..........

Indeed I can confirm that the clock on my Sync 3.4  did NOT go forward !!

It does have the option for GPS time which I have to keep turned off otherwise the time can jump forwards or backwards quite randomly.

So no Ford haven't fixed the problem, or at least not on my car. 🙄

I have MFD with Sync 1.1 and despite having GPS time enabled, there's still a checkbox for Summer Time... surely this can be automated fairly easily...!

The problem is that the date summer time changes can move. Internet connected devices regularly get updates for when particular countries are due to change to summer time. On something that doesn't receive regular updates, it's safer to let it be done manually.

That's fair.

I just wonder if it's something that could have been included in the GPS time functionality (obviously if summertime flags aren't part of the GPS data then obviously not possible!)

10 minutes ago, dontpannic said:

That's fair.

I just wonder if it's something that could have been included in the GPS time functionality (obviously if summertime flags aren't part of the GPS data then obviously not possible!)

There isn't really much data from GPS. It's just broadcasting a very accurate timestamp (time of transmission), which is based on the same time for all GPS satellites around the globe. Your device is doing all the calculation, working out the differences in the time signal sent from different satellites to work out your position and your timezone.

19 hours ago, unofix said:

Next you'll be trying to convince me that Scotland is still part of Britain

I think it still is....

But I'm not sure about Suffolk?  Some people say that it  might be part of Britain but it's definitely in a different century.

4 minutes ago, alexp999 said:

to work out your position and your timezone

I have to tell mine what time zone it's in (mine's currently set to Lisbon and Casablanca).

22 minutes ago, alanfp said:

I have to tell mine what time zone it's in (mine's currently set to Lisbon and Casablanca).

I didn’t word it very well. I meant the device has to know your time zone as it doesn’t get it from gps. Although it could in theory work it out but things like that can change too over time. 

2 minutes ago, alexp999 said:

I didn’t word it very well. I meant the device has to know your time zone as it doesn’t get it from gps. ..

I must be thick! I absolutely would think that one of the primary things a GPS signal could calculate, was what time zone you were in! LOL

26 minutes ago, StephenFord said:

I must be thick! I absolutely would think that one of the primary things a GPS signal could calculate, was what time zone you were in! LOL

The device could work out your position then it would have to look at map data that would need to contain time zones. It’s possible but not straight forward and relies on the device being kept up to date. GPS satellites are just broadcasting a radio time signal there is no back and forth communication. 

1 hour ago, alanfp said:

I think it still is....

But I'm not sure about Suffolk?  Some people say that it  might be part of Britain but it's definitely in a different century.

Do they not have webbed feet and hands down that way, a completely different country ?

1 minute ago, Jimpster said:

Do they not have webbed feet and hands down that way, a completely different country ?

Different country maybe, but you're describing a different species LOL 

There was a long running joke about people from Norfolk having webbed toes and 6 fingers as a result of rampant inbreeding.  Though I must admit there weren't many different surnames in the villages where I grew up.

 

8 hours ago, dontpannic said:

I have MFD with Sync 1.1 and despite having GPS time enabled, there's still a checkbox for Summer Time... surely this can be automated fairly easily...!

GPS time doesn't do daylight saving - they all run UTC (as far as I know) which is politically correct computer speak for GMT, so you get an option to choose to use  "I hope the daylight saving the car was once programmed with is still valid"

of course WNRO Apr 2019 might have thrown your car's GPS brain in a tail spin so it now thinks its 2006 or something regardless of daylight saving or not

3 minutes ago, Botus said:

GPS time doesn't do daylight saving - they all run UTC (as far as I know) which is politically correct computer speak for GMT..

I have a 10 year old standalone Garmin, I have never set the time on it as it's all automatic, clocks forward, and back...

3 minutes ago, StephenFord said:

I have a 10 year old standalone Garmin, I have never set the time on it as it's all automatic, clocks forward, and back...

Because the garmin is programmed that way. GPS is always the same time all year all around the globe. It will be wrong should summer time ever change or it runs out of it’s programmed lookup table. 

5 minutes ago, alexp999 said:

Because the garmin is programmed that way. GPS is always the same time all year all around the globe. It will be wrong should summer time ever change or it runs out of it’s programmed lookup table. 

Now, I did bring it with me to the USA when 1st got it years ago, and again, I never set the time, it was just 'right'.  Am I missing something?

2 minutes ago, StephenFord said:

Now, I did bring it with me to the USA when 1st got it years ago, and again, I never set the time, it was just 'right'.  Am I missing something?

It’s using map data or a lookup table. So it works out where you are on the globe then either the time zone is built in to the map data or it looks up your location in a time zone table to adjust the correct time. The problem is that if the data it’s using ever changes it will be wrong. 

Just to give you an example of needing to keep timezone data up to date, here is an extract of the changelog from Debian (a Linux distribution) that was released on Friday:

    - 16-greenland-dst.patch: Much of Greenland stops changing clocks after
      March 2023.
    - 17-mexico-dst-chihuahua.patch: The northern edge of Chihuahua changes to
      US timekeeping.
    - 18-no-leap-second-2023-06-30.patch: update leap-seconds.list, new
      expiration date on 28 December 2023.
    - 19-greenland-dst2.patch: Much of Greenland still uses DST from 2024 on.
    - 20-egypt-dst.patch: Egypt now uses DST again, from April through
      October.
    - 21-morroco-dst.patch: This year Morocco springs forward April 23, not
      April 30.
    - 22-palestine-dst4.patch: Palestine delays the start of DST this year.
    - 23-lebanon-dst.patch: Lebanon delays the start of DST this year.

 

These lists are very interesting - when selecting my time zone I was amazed to find a time zone that's 5 and 3/4 hours ahead of us (Kathmandu).

And a timezone called Nuku'alofa, wherever that is, but presumably it's the capital of somewhere.

1 hour ago, StephenFord said:

I have a 10 year old standalone Garmin, I have never set the time on it as it's all automatic, clocks forward, and back...

only if you applied a patch to make it tell the time correctly after april 2019 - and other updates to fix daylight saving changes around the world

tomtom's of that era no longer work for time and dates - unless you apply a third party patch - and I expect all the old fords in the same place - to save space they put a dim brain that ran a 19 year date cycle in satellites - most fall out of the sky before it ever matters... apr 2019 they all flipped to year zero and many devices that look for the sat signals didn't and thus got a muddle on

 

https://en.wikipedia.org/wiki/GPS_week_number_rollover

1 minute ago, Botus said:

only if you applied a patch to make it tell the time correctly after april 2019 - and other updates to fix daylight saving changes around the world

It does get a free map update every 3 months, Garmin may also apply a patch as well because I certainly have never applied one LOL 

On 3/26/2023 at 2:40 PM, mjt said:

I didn't but your comment prompted me to check and never mind the time -  I found the date was 01/01/2016 !! 

Obviously with the car standing unused for long periods the battery has expired. Needless to say it's a Nextbase. The same one that had not been recording when I had a near miss last year. Won't ever buy another one from them.

I might see if it's possible to open it up and change the battery myself pending getting something better.

Easy to change if you are any good at soldering wires. There are a few videos online.

 

Edited March 29, 20233 yr by PaterAnt
improved photo

I won't be changing the battery. I opened the cam up and couldn't see one so it looks as though it's on the other side of the pcb. The case back is connected to the pcb with some very small ribbon cables. I had to disconnect one to allow the back to swing open but that meant taking out the connector's tiny locking bar. Unlike other connectors of this type the locking bar is not captive and it was a real pita to get it back in whilst trying to keep the cable in place.

The cam gets the date and time from the gps when it's on the mount, although it takes a while for it to connect to the satellites, so the fact the battery doesn't maintain it between journeys isn't a major issue. However having uploaded all the files from the sd card, which is a Nextbase branded one, I've found several that are unreadable by any of my players and others that are jittery and freeze during playback. That's in spite of having reformatted the card as recommended before the latest journey so there's clearly a major problem with the cam.

37 minutes ago, mjt said:

... which is a Nextbase branded one, I've found several that are unreadable...

I too have had poor experience from my Nextbase. A lengthy exchange with their customer service (!) transpired it was all my fault by buying it from an Ebay seller rather than an 'authorised' one. It was brand new and factory sealed. Hard to recommend the brand...