After 2 months very busy at work, I'm back to correct some of the bugs of version 0.9.3. I hope to release a new version in a few days.
The same reason I didn't report my problems earlier, I'm struggling with it for quite a while, but didn't find the time to really dig into it.
Qpegps is communicating with gpsd (v2.34), showing sometimes the NMEA mode, sometimes SIRF mode. A while (varying from within 2 minutes to up to 5 minutes) after a fix is found qpegps hangs.
snip,..
When qpegps hangs, gpsd is still running fine and giving me positions.
I haven't experimented this problem but I'm trying another form to connect gpsd that doesn't involve the use of threads that could be the cause of your hangs.
I don't now if the changes between nmea and sirf mode are dued to qpegps or gpsd or even your gps hardware. Could you use cgps (the text based client included in the gpsd ipk) and tell me if you get the same mode changes?
Thanks for your feedback
[div align=\"right\"][a href=\"index.php?act=findpost&pid=156789\"][{POST_SNAPBACK}][/a][/div]
Some extra info:
I did run qpegps 0.9.3 on my former SL-C3000, with the same GPS (Billionton CF GPS), with the same result. When Qpegps freeze, some of the bearing/heading/velocity values show (sometimes!) "nan"
I tried to run cgps, but get an error message saying terminal vt100 not available or something like that.
Could you tell me how to run cgps?
When viewing gpsd in the terminal, I did not notice changes between NMEA mode and Sirf mode, but it was very cold outside, so maybe I didn't hang out long enough to be able to see it. Running qpegps it is also not a constant change between the 2 modes, I just noticed it changing now and then. In the old version, it only gave me questionmarks.
For what I've seen this version is quite an improvement on 0.9.2.3 so I really hope to be able to run it! I'm using it for geocaching mainly.
Thanks again