Sorry it took so long to post back, my day job has been keeping me pretty busy.
Martin, Thanks for the data. Not exactly what I was looking for but it got me started verifying what I thought was the case. With that data I made the following observations:
7 decimal places in the GPS number give you within ½” of accuracy for latitude or longitude; see table at
http://www.co.lincoln.wa.us/gis/gps.htm - The data I got from Martin was 7 decimal places and I think it was 10kz GPS. In my mind, 5 decimal places are sufficient.
Based on research I did, the maximum value possible Lat or Long numbers based on the Garmin format of DDDMM.sssss is 18090.99999 or -18090.99999.
I also figured out that the highest value accommodated in an ADL that I can find documented is 19000, with 11214 being the highest number I have seen.
The 19000 leads me to believe we can store lat and long in an ADL in 2 fields, one made up of whole number of Degrees and Minutes, and the second field holding the fractional seconds.
This all assumes the ADL can just store 18090.99999 or -18090.99999. Does anyone have documentation on what the data types are that are supported in the ADL? Is that documented anywhere?
I still need some data where I have to do the math to combine portions of the complete longitude or latitude reading in I2, then generate a track map. I don’t have that yet, so I can not test the combining using the I2 std math yet. Anyone that has that data, I would be happy to give it a try.
Another curious thing about Robins config. I took a close look at it. I determined that its using NEMA sentences, but using the delimited decimal format. Does anyone know how that works? I know how comma delimited works and based on that for the NEMA sentences Robin is using, you would get a value of DDDMM.sssss not separate fields of degrees minutes and seconds. I would be curious in finding out more how delimited decimal works and how a custom definition of fields from the NEMA sentence using delimited decimal format.
That’s the one thing I cant get straight in my mind, how is the lat and long extracted out of the NEMA $GPGGA in Robins config, and then how is that parsed into 3 user defined fields. I believe it works, I am just not sure how it works.
So all that being said, I understand what I am trying to do much better now. I still see no apparent reason why this can not be done.
However, I still need the data to try and put back together before I can say for sure it will.
FYI - found very interesting documentation - but have not had time to read yet convering how the RS232 comms settings work at:
download/file.php?id=7Mike.