gpsd-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gpsd-dev] ✘NMEA_MAX


From: Chris Kuethe
Subject: Re: [gpsd-dev] ✘NMEA_MAX
Date: Mon, 28 Mar 2016 16:10:29 -0700

http://www.trimble.com/OEM_ReceiverHelp/V4.44/en/NMEA-0183messages_GGA.html
 admits that their sentence exceeds the maximum length, so there is a
maximum and vendors violate it.

http://www.visualgps.net/whitepapers/nmeaparser/nmeaparserdesign.html
says "the maximum number of characters shall be 82"... and they sound
like they've actually seen the standard.

The 86 comes from me, back in SVN r4303. I, too, have one of those
standards-violating receivers. I think it's safe to increase the limit
since there is a fairly robust structure detector.


On Mon, Mar 28, 2016 at 3:54 PM, Gary E. Miller <address@hidden> wrote:
> Yo All!
>
> I have a nice new Skyrtaq S2525F8-BVD-RTK.  It seems to work out of the box
> with gpsd head.
>
> I'm trying to decode their proprietary $PSTI sentence, which looks like this:
>
> $PSTI,030,224352.000,A,4404.1219937,N,12118.8480255,W,1131.250,0.01,-0.02,0.05,280316,D,0.0,0.0*1C
>
> Yeah, that is 100 chars, with the \r\n.
>
> gpsd defines NMEA_MAX as 91.  gpscat defines it as 86.
>
> Q's:
>
> Does NMEA 0183 have a defined max length?  If so, what is it?
>
> Anyone have a problem with me making NMEA_MAX equal to 100?
>
> Will I need to special case $PSTI to be 100 nforce 91 for all other NMEA
> sentences?
>
> RGDS
> GARY
> ---------------------------------------------------------------------------
> Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
>         address@hidden  Tel:+1 541 382 8588



-- 
GDB has a 'break' feature; why doesn't it have 'fix' too?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]