On Sat, January 20, 2007 18:31, Hal Murray said:
>
>> Is PM messages not short for Proprietary Message? Ie its not
>> documented by the NMEA, and you need the manufacturer documentation to
>> know whats in that string.
>
> I found a NMEA FAQ that says $P is proprietary and the next 3 characters
> a
On Sat, January 20, 2007 17:29, Bruce Lane said:
> Good day,
>
> *** REPLY SEPARATOR ***
>
> On 20-Jan-07 at 14:08 [EMAIL PROTECTED] wrote:
>
>>On Sat, January 20, 2007 4:16, Hal Murray said:
>>>
I have discovered that the receiver, on one of its ports (the aux
port), is
> Is PM messages not short for Proprietary Message? Ie its not
> documented by the NMEA, and you need the manufacturer documentation to
> know whats in that string.
I found a NMEA FAQ that says $P is proprietary and the next 3 characters are
the manufacturer code. MGL seems reasonable for Mage
Good day,
*** REPLY SEPARATOR ***
On 20-Jan-07 at 14:08 [EMAIL PROTECTED] wrote:
>On Sat, January 20, 2007 4:16, Hal Murray said:
>>
>>> I have discovered that the receiver, on one of its ports (the aux
>>> port), is putting out Magellan ASCII strings prefixed with $PMGLK.
>>
>>
On Sat, January 20, 2007 4:16, Hal Murray said:
>
>> I have discovered that the receiver, on one of its ports (the aux
>> port), is putting out Magellan ASCII strings prefixed with $PMGLK.
>
> Looks like NMEA stuff.
>
> I haven't found the NMEA specs on line. Looks like they (nmea.org) want
> BIG$
> I have discovered that the receiver, on one of its ports (the aux
> port), is putting out Magellan ASCII strings prefixed with $PMGLK.
Looks like NMEA stuff.
I haven't found the NMEA specs on line. Looks like they (nmea.org) want BIG$
for it. I have found various pieces in specs from variou
Fellow clock-tickers,
I'm delving into the secrets of my Odetics 325 in an effort to
understand if the GPS receiver can be replaced with something a little more
modern than the Magellan OEM 5000. In the course of this investigation, I have
discovered that the receiver, on one of its por
