[Top][All Lists]

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

Re: [gpsd-dev] possible gpsd bug

From: Roy Barkas
Subject: Re: [gpsd-dev] possible gpsd bug
Date: Tue, 17 Feb 2015 21:29:07 +1100

Sorry, my mistake. 

On Tue, Feb 17, 2015 at 9:15 PM, Eric S. Raymond <address@hidden> wrote:
Roy Barkas <address@hidden>:
> For some reason I can't log in to the bug tracker, so as you're approaching
> a release, here is what looks like a bug:  This behavior is from 3.11
> When gpspipe is started with the options -wrSt (S=split24), the subsequent
> Watch message is:
> {"class":"WATCH","enable":true,"json":true,"nmea":true,"raw":0,"scaled":true,"timing":false,
> *"split24":false,*"pps":false}
> I am seeing some type 24 messages coming through from gpspipe but these all
> seem to be processed through the default method of processing part A and
> part B since the decoded messages contain data from both parts.
> If instead of using gpspipe I connect directly to gpsd on 2947 and send:
> ?WATCH={"enable":true,
> "json":true,"scaled":true,"split24":true,"device":"udp://localhost:46003"}
> Then it works as expected and the subsequent WATCH confirmation shows
> split24:true

>From the documentation:

<para>-S sets the scaled flag.</para>

<para>-2 sets the split24 flag on AIS reports. Note: this option
is experimental and may be changed or removed in a future release.</para>
                <a href="" href="" target="_blank">">Eric S. Raymond</a>

reply via email to

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