http://www.technologicalwanderings.co.uk/taxonomy/term/83 en http://www.technologicalwanderings.co.uk/node/42 <div class="field field-name-taxonomy-vocabulary-1 field-type-taxonomy-term-reference field-label-above"><div class="field-label">Keywords:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="/taxonomy/term/82">bu303</a></div><div class="field-item odd"><a href="/taxonomy/term/83">bu 303</a></div><div class="field-item even"><a href="/taxonomy/term/84">gpsd</a></div></div></div><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p>gpsd seems to be broken when talking to a BU303 GPS device. If the BU303 is put into NMEA mode, gpsd will think it sees SIRF data from it. When this happens, it will change its mode to SIRF which the triggers then BU303 to really go into SIRF. The BU303 is unreliable enough as it is.</p> <p>This is bad for me, as my Navigator software needs raw access to the device in NMEA mode and doesn't know how to switch it back over.</p> <p>The answer is compile gpsd from source without SIRF support:</p> <p>./configure --disable-sirf</p> <p>(As an aside, I would really like to write a 'fake' serial device which feeds data from gpsd as raw NMEA. That way I wouldn't need to have scripting which kills gpsd (and thus my tracking system) when I want to load Navigator 4).</p> </div></div></div> Sat, 27 Sep 2008 20:36:57 +0000 techuser 42 at http://www.technologicalwanderings.co.uk http://www.technologicalwanderings.co.uk/node/42#comments