You stated:
"> Since I don't own the Dire Wolf code, I must defer to the author.
And where is he? Does he not care to get this fixed?
Are we giving you all this help and the upstream code will not get fixed??"
You will have to ask the code developer. gpsd is a minor part of the code functionality and there are other bugs which need resolution. I have been copying him on the emails.
You ask:
"I'm still waiting for a deinition of "high rate of messages"?
Most gpsd clients consider that a good thing."
I don't have a rate but it is fast enough that we are filling the message queue much faster than it can be handled and we are dropping messages due to an over filled queue. It looks like we have dropped something on the order of at least 100 messages during the transient: I will try to get a count form a log file.
You stated:
":> I can of course monitor the output of the
> MT3333, but I have already been monitoring this and it basically is
> the messages every two seconds.
Which would be very weird. Most GNSS receivers default to a fix
every second"
You are correct and I am in error: it is one message every second. My apologies.
You asked:
"> Thoughts on a command line client to capture output of gpsd into say
> a log?
To see the raw from the MT3333, with gpsd running: gpspipe -R
To see the JSON from gpsd: gpspipe -w"
Checked and that looks like it will work. Back with the data probably tomorrow.