Messages

1

Software / Updating Qpegps - New Gpsd And More

« on: October 31, 2006, 03:14:37 pm »

Ah, I seem to get speed and heading, only the speed doesn't seem to be correct, I was thinking I may not have got the correct units somewhere - perhaps something had changed between old and new gpsd.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=144953\"][{POST_SNAPBACK}][/a][/div]

I worked out the speed problem I was having - gpsd used to report in Knots, it now reports in metres/second.

2

Software / Updating Qpegps - New Gpsd And More

« on: October 28, 2006, 04:20:26 pm »

But the inclusion of two interfaces on qpegps will increase its size
[div align=\"right\"][a href=\"index.php?act=findpost&pid=145016\"][{POST_SNAPBACK}][/a][/div]

Well, not by enough to bother about since it will be a pretty small amount of glue code. The major part is the bit copying data from gpsd structures to the qpegps store.

Do any of the other apps which use gpsd start it themselves? Or do they expect it to be running already? I think we should be following the same arrangement as them regarding starting gpsd.

Starting and stopping and external app seems more risky/complex that an internal interface which can talk direct to the device.

Anyway, the main thing is to have qpegps working with the latest gpsd with other new features.
And it sounds like it will be before too long.

3

Software / Updating Qpegps - New Gpsd And More

« on: October 28, 2006, 01:48:32 pm »

That is if you have gpsd running and use the low-level interface (the one used by grahamj) it probably cause 'confusion'. So I'd prefer my approach using the high level interface.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=144998\"][{POST_SNAPBACK}][/a][/div]

Actually, I have been thinking about that - I think we can have the best of both worlds.

For my purposes and possibly many who simply want to use qpegps and aren't interested in how the communication with the device happens, the direct method is nice in the sense that nothing is left running when qpegps has quit.

For those with more complex requirements, having gpsd running in the background is fine and the only option because of the need for other apps to use it.

Why don't we do something like:

1. Start qpegps
2. Check if gpsd is running
3. If yes, connect to the gpsd daemon using the high-level interface
4. If no, use the low-level interface

We can use the same function to transfer data from gpsd to qpegps, since the same structures are used by the high and low level interfaces. Sub-classing Client to provide the two methods of connection should be relatively simple, and we link with the same library so code size is the same.

Qpegps is released of the need to start (and preferably stop, which it doesn't do at the moment) a separate gpsd process just for itself, which I have never liked anyway.

4

Software / Updating Qpegps - New Gpsd And More

« on: October 27, 2006, 10:47:03 am »

...
I am interested to learn more about any other improvements people are planning for qpegps.

After the message from hvontres about gpsd 2.xx I have read the documetation and thinking as you that linking with libgpsd was a good idea and quite easy I have been working this week on that task.

Looks like we have been doing the same work almost simultaneously!

I have compiled gpsd 2.33 and modified client.cpp to use libgpsd interface and at this moment I have a (more or less) working implementation. Tha main problems I have had until now are:
- gpsd 2.33 does not seen to give speed/heading information to qpegps ....

Ah, I seem to get speed and heading, only the speed doesn't seem to be correct, I was thinking I may not have got the correct units somewhere - perhaps something had changed between old and new gpsd.

Sounds like you have found a better fix to the problem - is this the "J" fix talked about in the gpsd forums, looking like a versino of it is due to be added to the next release?

- Instead of a timer like in the current version of qpegps, I want to use the watcher mode and a QSocketNotifier to know when there is new information from gpsd <....> Do you use QSocketNotifier or how do you detects new information?

At present I am using a simple timer to call gpsd_poll, and the raw_hook function to handle the data. I was planning on aiming for the asynch version (can't remember the name off the top of my head). Since I am linking directly with libgpsd and not running a separate gpsd executable I don't have any sockets (not local network sockets anyway).

By the way, in order to work together we should coordinate our codes to work with the same files. <....> Any other idea about how to work together?

That sounds like a good idea. Somebody would have to transfer the 0.9.2.3.3 code to the CVS server (assuming everybody is happy with that as the current version). I think that code only made it to the download page, not CVS.
We will need to be careful not to check conflicting versions into CVS so some separate discussion by e-mail might be good to get things going.

Anyway I would like to see your modifications. (I think that the multiple folder for maps is a good idea, I used to have several folders and manualy switch between several maps.txt files) and how it can be mixed with mines to make a better version.

The multiple folders helps me a lot, it is so easy to drop new maps in and remove old maps without altering other files.

Other question, I have the same GPS than you but qpgs recognize it as 'Generic NMEA' and use NMEA messages <....> Do you know how to change to sirf mode with gpsd 2.xx?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=144950\"][{POST_SNAPBACK}][/a][/div]

Hmm, I haven't tried switching to Sirf mode yet, but was ewondering about trying the sirf program which is part of gpsd.

5

Software / Updating Qpegps - New Gpsd And More

« on: October 27, 2006, 08:32:24 am »

Following the discussion started in the topic about kdepim development ....

... I am in the process of testing Qpegps (0.9.2.3.3 codebase) updated to use the latest gpsd (currently V 2.33).

Not everything is working at the moment so I plan to wait having anything ready for wider testing (currently it crashes viewing the map, probably due to not updating everything regularly enough, and the reported speed seems to be out).

I have chosen to statically link with libgpsd to avoid having to start and stop the gpsd daemon. A few minor changes were needed to gpsd to get it to compile for the Zaurus, but nothing which should alter its behaviour.

I am able to test on Zaurus SL-C series with Sharp ROM only, and one GPS device (SysOnChip CF Plus III).

I have also added a way to add new folders holding maps, as subfolders of the main map folder, without editing the main maps.txt file. Each sub-folder has its own maps.txt with info only on those maps. I can use some of the off-line map capture tools and then drop in or remove sets of maps very easily.

The previous discussion suggests that other work is being done on qpegps as well.

More news from me later, when the code looks like it is ready.

I am interested to learn more about any other improvements people are planning for qpegps.

6

Software / Korgnanizer Pim / Kopi Still Alive?

« on: October 26, 2006, 04:18:14 pm »

The same question about qpegps
http://sourceforge.net/projects/qpegps/]http://sourceforge.net/projects/qpegps

nothing since 2006-02-02

Currently, I'm working on some modifications on qpeGPS (mainly support to tiled maps). I think that in 4-6 weeks I will release a new version.

If you have a new feature or bug to be corrected post it, and I will look if I can solve it.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=144160\"][{POST_SNAPBACK}][/a][/div]

Interestingly I have just been working on updating Qpegps to use gpsd 2.3X, and just about have something ready for testing.

With the new features in later gpsd versions it will be possible to add new information to that produced by qpegps. At the moment I am worrying about getting the basic software working - my current test is directly linking with the gpsd library, avoiding the need to start and stop gpsd all the time.

I haven't seen anybody else comment about having tried this recently - am I the only one?