GMT to local time

picprogrammer · Joined: 10 Sep 2003 Posts: 35

Does some made a routine to calculate the local time from GMT. The GMT is from a GPS receiver.

Basic it is only calculate the minute of year, plus timezone and convert back to date and time.

temtronic · Posted: Wed Mar 07, 2012 10:03 am

Your GPS doesn't have an option to change the time to 'local'?

Ttelmah · Joined: 11 Mar 2010 Posts: 19535

You should already have what is needed.
Key is that you need to calculate the 'offset' between UTC (no longer GMT), and the local time. time.h, has routines to convert a 'time', into a tick count (mktime), and back to a string (ctime). So you just take the UTC time, convert it to a 'tick' count, then add or subtract the offset, and convert it back to a string. If you do a search online, you will find dozens of examples, normally with the 'offset' called something like GMT_OFFSET. All you need to calculate this is the timezone, and a flag for DST.

Best Wishes

gpsmikey · Joined: 16 Nov 2010 Posts: 588 Location: Kirkland, WA

If this is a stationary application (home etc), then the above answers work. If this is mobile, you have the added issue of having to periodically figure out which time zone you are in (and if DaylightSavings applies). My older Magellan hand-held gps doesn't know which time zone it is in which surprised me since it knows where it is - I would have thought they would have put that feature in, but nope. So if you are mobile (at least to the extent of crossing time zones), then you will also need to figure out how to determine which time zone you are in before you can correct for it.
_________________
mikey
-- you can't have too many gadgets or too much disk space !
old engineering saying: 1+1 = 3 for sufficiently large values of 1 or small values of 3

JamesW · Joined: 23 Apr 2007 Posts: 91 Location: Rochester, England

Funnily enough, I am doing exactly the same at the moment.

I have tried the above method, and get some weird results

My data from the satellite is reporting in perfectly, and displaying OK on the terminal - however when converting to ticks using mktime and then back to a string using ctime - I am getting an incorrect date (time is OK).

At the moment I am not introducing an offset into the ticks, to cater for local time. (But when I do - the hours adjust fine!)

It did occur to me, that maybe I needed to add 2000 to the year, as the satellite data is only 2 digits - but this crashed the PIC.

MY RESULTS (CAPTURED FROM HYPERTERMINAL) :
SATELLITE TIME : 18:24:13 09/03/12
SECONDS SINCE EPOCH 8706253
LOCAL TIME : Sat Apr 11 18:24:13 1970

Ttelmah · Joined: 11 Mar 2010 Posts: 19535

The most likely thing is a variable is being destroyed/overwritten.
In C, It is _not_ legal to declare variables in the middle of the code. CCS does not complain about this, and sometimes seems to accept it, but most normally it results in variables that overwrite one another. Variables can be declared in a function, but _must_ be declared at the start of the function section.
Second, it is not legal in CCS, to declare a variable and initialise it from a function in the same line.

Best Wishes

picprogrammer · Joined: 10 Sep 2003 Posts: 35

My own way was the quickest:

ckielstra · Joined: 18 Mar 2004 Posts: 3680 Location: The Netherlands

Just some minor remarks.

1) You are calculating the leap year correction for number of days with two different methods. Once using two different arrays and once by adding +1.
Both methods are correct, but your code is larger and more difficult to understand because you use two methods.

2) You can save some code space by using a year calculation that is limited to the year span 1901 - 2099. Sufficient for most applications: