[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gpsd-dev
Subject:    Re: [gpsd-dev] possible gpsd bug
From:       Roy Barkas <roy () rbdb ! net>
Date:       2015-02-17 10:29:07
Message-ID: CACEnT=fkadXZV+tLt0gr=9Qur3vTdXVhFKAcnmMnzLL9o1dnEQ () mail ! gmail ! com
[Download RAW message or body]

Sorry, my mistake.

On Tue, Feb 17, 2015 at 9:15 PM, Eric S. Raymond <esr@thyrsus.com> wrote:

> Roy Barkas <roy@rbdb.net>:
> > 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="http://www.catb.org/~esr/">Eric S. Raymond</a>
>

[Attachment #3 (text/html)]

<div dir="ltr">Sorry, my mistake.   <br></div><div class="gmail_extra"><br><div \
class="gmail_quote">On Tue, Feb 17, 2015 at 9:15 PM, Eric S. Raymond <span \
dir="ltr">&lt;<a href="mailto:esr@thyrsus.com" \
target="_blank">esr@thyrsus.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Roy Barkas &lt;<a \
href="mailto:roy@rbdb.net">roy@rbdb.net</a>&gt;:<br> &gt; For some reason I can&#39;t \
log in to the bug tracker, so as you&#39;re approaching<br> &gt; a release, here is \
what looks like a bug:   This behavior is from 3.11<br> &gt;<br>
&gt; When gpspipe is started with the options -wrSt (S=split24), the subsequent<br>
&gt; Watch message is:<br>
&gt;<br>
&gt; {&quot;class&quot;:&quot;WATCH&quot;,&quot;enable&quot;:true,&quot;json&quot;:tru \
e,&quot;nmea&quot;:true,&quot;raw&quot;:0,&quot;scaled&quot;:true,&quot;timing&quot;:false,<br>
 &gt; *&quot;split24&quot;:false,*&quot;pps&quot;:false}<br>
&gt;<br>
&gt; I am seeing some type 24 messages coming through from gpspipe but these all<br>
&gt; seem to be processed through the default method of processing part A and<br>
&gt; part B since the decoded messages contain data from both parts.<br>
&gt;<br>
&gt; If instead of using gpspipe I connect directly to gpsd on 2947 and send:<br>
&gt;<br>
&gt; ?WATCH={&quot;enable&quot;:true,<br>
&gt; &quot;json&quot;:true,&quot;scaled&quot;:true,&quot;split24&quot;:true,&quot;device&quot;:&quot;udp://localhost:46003&quot;}<br>
 &gt;<br>
&gt; Then it works as expected and the subsequent WATCH confirmation shows<br>
&gt; split24:true<br>
<br>
From the documentation:<br>
<br>
&lt;para&gt;-S sets the scaled flag.&lt;/para&gt;<br>
<br>
&lt;para&gt;-2 sets the split24 flag on AIS reports. Note: this option<br>
is experimental and may be changed or removed in a future release.&lt;/para&gt;<br>
<span class="HOEnZb"><font color="#888888">--<br>
                        &lt;a href=&quot;<a href="http://www.catb.org/~esr/" \
target="_blank">http://www.catb.org/~esr/</a>&quot;&gt;Eric S. Raymond&lt;/a&gt;<br> \
</font></span></blockquote></div><br></div>



[prev in list] [next in list] [prev in thread] [next in thread]