Getting the latitude and longitude out of the M800 and into the logger was easy, but the maths has proven complex (at least it was complex to me, I got a kind friend to help out a lot...). Jamie Augustine at Motec was very helpful and felt that it should be straightforward. Negative latitudes didn't seem to be accounted for though, which at one stage I put down to Motec being in Oz and them not having to worry about certain latitudes further north
Here is what he felt would be the required format into the logger viewing software:
"You just need to place the high word to the left of the Low word, without
any multiplication, division or anything.
You can then put the decimal place at the 7th number in from the right.
Example:
The GPS Lat and GPS Long are just split in 2, nothing more challenging that
that.
GPS LON HW is the High word component.
GPS LON LW is the Low Word component.
Eg
144.9688203
Is
HW is 0101011001101000
LW is 0111110010001011
Put them together
01010110011010000111110010001011
= 1449688203
Divide by
10000000
Gives you
144.9688203
This is the GPS Long value."
I was getting wild results for coordinates until I added maths into the logger, to combine HW and LW so:
Combine GPS Longitude: ((if('GPS LON HW'>32767,('GPS LON HW'-65536),'GPS LON HW')*65536)+if('GPS LON LW'<0,('GPS LON LW'+65536),'GPS LON LW'))/10000000
Combine GPS Latitude: ((if('GPS LAT HW'>32767,('GPS LAT HW'-65536),'GPS LAT HW')*65536)+if('GPS LAT LW'<0,('GPS LAT LW'+65536),'GPS LAT LW'))/10000000
GPS Latitude: if(('GPS LAT COMBINE'>0.0),((('GPS LAT COMBINE'-floor('GPS LAT COMBINE'))/0.6)+(floor('GPS LAT COMBINE'))),((('GPS LAT COMBINE'-ceil('GPS LAT COMBINE'))/0.6)+(ceil('GPS LAT COMBINE'))))
GPS Logitude: if(('GPS LON COMBINE'>0.0),((('GPS LON COMBINE'-floor('GPS LON COMBINE'))/0.6)+(floor('GPS LON COMBINE'))),((('GPS LON COMBINE'-ceil('GPS LON COMBINE'))/0.6)+(ceil('GPS LON COMBINE'))))
Without these functions negative values were incorrectly shown, and Google Earth overlays were thousands of miles off.
Now, tell me I have missed something obvious and all this was unnecessary
I can only assume i2 does something similar, plus some neat filtering, under the covers? Unfiltered the above data is a bit ragged when viewed as a track map. Unfiltered overlay, taken via GPS CAN from my M800 and rendered in my GEMS DA99L2 logger and GEMS GDA software, the maths functions were done in the software, but now I am doing them in the logger itself, same result:
http://www.gatesgarth.com/GDA/newrock.kml