On Tue, Apr 23, 2013 at 11:22 AM, Eric S. Raymond
Pablo Rodriguez Monetti <address@hidden>:
> Is the dumping of this kind of messages completely supported now? I could
> read at
http://catb.org/gpsd/gpsd_json.html that it is not, but maybe that
> web page was not updated.
I lack test pairs for some RTCM3 packet types not all are yet supported.
The most useful thing you could do is give me test pairs for the
packet types you're concerned about.
A test pair includes (1) a binary RTCM3 packet, and (2) a labelled
dump of its fields (*all* the fields) in a readable format, made by
a decoder that is known good.
> I wrote a simple program, based on test_gpsmm (the test for libgpsmm that
> comes with the gpsd distribution), that uses a gpsd client in order to
> extract the RTCM information. I added a line of code to print the client
> buffer content (after checking that the PACKET_SET mask bit is on) and,
> when running the program, I could continually get JSON objects like the
> following:
Those look reasonable.
> However, against my expectations, the RTCM3_SET mask bit is never turned
> on.
Yes. That is because the client library doesn't support RTCM3 yet. It
reads the RTCM3 JSON structures off the wire but doesn't know how how
to unpack them into the rtcm3 menber of struct gps_data_t.
I haven't implemented that because I'm not confident about the daemon's
RTCM3 decoder. If you want it, you can either (a) find me enough test pairs
that I know it's really good, then wait until I have time to write the
library-side support, or (b) write it yourself. You could use the code in
rtcm2_json.c as a model.
--
<a href="" href="http://www.catb.org/~esr/" target="_blank">http://www.catb.org/~esr/">Eric S. Raymond</a>