rishabht1 / gmapcatcher

Automatically exported from code.google.com/p/gmapcatcher
0 stars 0 forks source link

GPS and gpsd recognized, no gps marker shown on the map #170

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
 1. Initializer bluetooth connection with GPS unit
 2. Start gpsd "gpsd -b /dev/rfcomm0"
 3. Start gmapcatcher

The GPS options are shown in the menu as if gpsd and a GPS is connected, there 
is however no GPS marker shown on the map.

Using Arch Linux i686 with latest svn version of gmapcatcher

Original issue reported on code.google.com by stefanaf...@gmail.com on 20 Jun 2010 at 11:13

GoogleCodeExporter commented 9 years ago
I'm getting the same problem here. I've installed this program to get an icon 
"GPSd for Windows" which launches this command prompt but it doesn't display 
the GPS points. I was actually expecting something like the one on google map 
as shown below.

Original comment by tjoolfoo on 21 Jun 2010 at 6:22

Attachments:

GoogleCodeExporter commented 9 years ago
On these cases the GPSd daemon is running but not getting a GPS lock.
Most GPS receivers come with a testing tool, where you can see if the GPS is 
getting valid data.
That is a way of testing, the other will be to test the GPSd daemon, I'm not 
sure about linux but in windows you could run one of the batch files 
(Test_gpsd.bat) to see if it outputs data.

I hope that helps

Original comment by heldersepu on 21 Jun 2010 at 2:45

Attachments:

GoogleCodeExporter commented 9 years ago
I can confirm that my gpsd is recieving data, tangogps and xgps shows that the 
gps unit has a lock.

Original comment by stefanaf...@gmail.com on 21 Jun 2010 at 3:00

GoogleCodeExporter commented 9 years ago
In that case we will need to do some debugging in GMapCatcher...
The program detects a valid GPSd Daemon that is way the GPS menu is shown, but 
in some how is not getting a valid response.

You will need to modify the file where we draw the GPS location:
http://code.google.com/p/gmapcatcher/source/browse/trunk/src/widDrawingArea.py
to output the result of gps.get_location() 
that could be a starting point

Original comment by heldersepu on 21 Jun 2010 at 3:24

GoogleCodeExporter commented 9 years ago
The second step debugging could be to add some output right where we make the 
reading form the GPS device:
http://code.google.com/p/gmapcatcher/source/browse/trunk/src/mapGPS.py
output the fix = self.gps_session.fix

Original comment by heldersepu on 21 Jun 2010 at 3:39

GoogleCodeExporter commented 9 years ago
I'll report back in a few days.

Original comment by stefanaf...@gmail.com on 21 Jun 2010 at 8:19

GoogleCodeExporter commented 9 years ago
I wish I could do more for you guys, but unfortunately to troubleshoot this 
case I will have to setup identical system to what you have.

If there is anything else I can do let me know, I will be happy to help

Original comment by heldersepu on 21 Jun 2010 at 8:25

GoogleCodeExporter commented 9 years ago
I just want to share couple of things regarding this new GPS feature on windows 
platform, I use been using Garmin 18 sensor for GPS data, since Garmin outputs 
a property data i used a 'Franson GpsGate??' to convert Garmin data format to 
NMEA sentences and bridged the data to virtual COM2 port so that gpsd can read 
the data from the COM2, Every thing is fine till now and the gpsd is 
successfully getting data from COM2, when i launched GMapcatcher it 
successfully connected to gpsd but there after i don't see any location 
tracking in the map, i have configured GPS mode = 'GPS center' in the GPS 
options but still not location shown up in the map, any one please let me know 
if i have missed any thing. Find the gpsd log below:

gpsd: launching (Version 2.37)
gpsd: listening on port 2947
gpsd: Unable to start ntpshm. gpsd must run as root.
gpsd: running with effective group ID 401
gpsd: running with effective user ID 400
gpsd: opening read-only GPS data source at '/dev/com2'
gpsd: speed 9600, 8N1
gpsd: garmin_gps not active.
gpsd: gpsd_activate(0): opened GPS (4)
gpsd: client 127.0.0.1 (0) connect on fd 5

Note that even the gpsd documentation claims that it supports Garmin GPS 18 USB 
sensor i dont not it dint worked for me so i have chosen GpsGate to bridge the 
gap between my sensor and gpsd.

Original comment by krishnak...@gmail.com on 15 Jul 2010 at 5:40

GoogleCodeExporter commented 9 years ago
Same problem here with GMapCatcher 0.7.5.3 (Linux, gpsd 2.95)
My GPS works well with gpsd/viking so it's definitly something to fix here.
gps.get_location() returns 'None' even if gpsd is detected.
I guess the problem is in the gpsd API: it has changed in gpsd 2.90.
You should read 
http://gpsd.berlios.de/protocol-transition.html#_python_client_library_changes 
Here is a small python test code that works for me.

Original comment by ngc...@gmail.com on 24 Dec 2010 at 1:42

Attachments:

GoogleCodeExporter commented 9 years ago
Created a patch for this, also includes the fix for mistace I made in the last 
patch... A quick fix, so not much of testing yet.
REQUIRES DELETION OF "gps.py" (and gps.pyc, if you're updating)

http://paste.ubuntu.com/1202813/

Original comment by kipenros...@gmail.com on 13 Sep 2012 at 3:17

GoogleCodeExporter commented 9 years ago
And that last one of course doesn't mean that it doesn't need python-gps, I 
just couldn't be bothered to update it locally ;P

Original comment by kipenros...@gmail.com on 13 Sep 2012 at 3:20

GoogleCodeExporter commented 9 years ago
Fixed in r1253

Original comment by kipenros...@gmail.com on 13 Sep 2012 at 6:06

GoogleCodeExporter commented 9 years ago
The problem was that the old version of GPSd library couldn't get data from 
newer GPSd
So, the fix basically updates to newer version of GPSd library and updates 
mapGPS.py to use new style of GPSd-data.

Original comment by kipenros...@gmail.com on 13 Sep 2012 at 7:19

GoogleCodeExporter commented 9 years ago
Of course, I didn't check this on Windows etc. GPSd is available on Windows 
only as version 0.20, so the fix doesn't apply to Windows.

It should however fix problems on GPSd version 2.90 and above.

Original comment by kipenros...@gmail.com on 13 Sep 2012 at 7:40

GoogleCodeExporter commented 9 years ago

Original comment by heldersepu on 29 Sep 2012 at 12:28

GoogleCodeExporter commented 9 years ago
Fixed (also works with GPSd for Windows).

Original comment by kipenros...@gmail.com on 8 Oct 2012 at 2:50

GoogleCodeExporter commented 9 years ago
Released in 0.8

Original comment by heldersepu on 16 Oct 2012 at 6:06