Notices


Reply
Thread Tools
Posts: 33 | Thanked: 5 times | Joined on Nov 2007
#41
Originally Posted by gnuite View Post
"/dev/pgp", not "/dev/pgps" ? Or is the display cut off? I guess you can try "/dev/pgp" in the "File Path" field instead of "/dev/pgps" - I doubt it will work, but it's worth a try.

display cut off, pgp doesn't exist
 
gnuite's Avatar
Posts: 1,245 | Thanked: 421 times | Joined on Dec 2005
#42
Originally Posted by haokah View Post
I'm sure I got some giggle from linux veterens, I didn't realize enable was only for printers. Anyway, I did some searching and reading, and I think I'm getting closer. I started reading the gpsd commands, after gnuite's grep request.

I did the following:

/etc/init.d/gpsdriver start
Is this command necessary to actually "enable" the internal GPS receiver? How does Maemo Mapper do the equivalent programmatically? Is there a DBUS interface? Does libgpsmgr not handle it automatically? Can you PM to me the contents of that "/etc/init.d/gpsdriver" file?

Originally Posted by haokah View Post
then

gpsd -n -N -D5 -F /tmp/gps.sock


the term shows it running, and a client connect on 6 when I start mapper, next it says channel assignment failed going to raw mode,

I've tried configuring mapper with /dev/pgps and with gpsd local host server

with /dev/pgps it keeps asking to retry,
Specifying a "File Path" causes Maemo Mapper to use libgpsmgr to try and start and GPSD server using the given path. If GPSD is already running, then libgpsmgr may return a failure (but I thought it was supposed to do nothing - maybe that's libgpsbt I'm thinking of, though). In any case, you already have a GPSD server running, so you shouldn't use "File Path", you should use "GPSD Host", as you did in your second try....

Originally Posted by haokah View Post
with gpsd it keeps searching until you stop it
( this is inside an office building, with no signal )
Hm. If it doesn't produce an error, then it sounds like you've connected to the GPS receiver, but have not yet received an NMEA sentence. Usually, GPS receivers will send NMEA sentences even when they don't have a fix (i.e. with satellite info). If you're not getting any NMEA sentences at all, it sounds like the connection isn't really working that well. In fact, you really should be getting an error after about 10-15 seconds.


I found this header file that reveals the internal GPS receiver is indeed "/dev/pgps", and there are no other API mechanisms by which to "enable" the GPS receiver. One would assume from that API that you should give "/dev/pgps" to the libgps_start() function, which causes the GPS receiver to be enabled and the GPSD server to be started. But it seems as though it doesn't actually handle the "enabling" part.
 
Posts: 33 | Thanked: 5 times | Joined on Nov 2007
#43
Is this command necessary to actually "enable" the internal GPS receiver? "
Doesn't look like it is. I'm new to linux, so I tried it from seeing it on some articles for getting a gps to work with a wifi app.

Specifying a "File Path" causes Maemo Mapper to use libgpsmgr to try and start and GPSD server using the given path. If GPSD is already running, then libgpsmgr may return a failure (but I thought it was supposed to do nothing - maybe that's libgpsbt I'm thinking of, though). In any case, you already have a GPSD server running, so you shouldn't use "File Path", you should use "GPSD Host", as you did in your second try....
I was thinking the server wasn't running, since ps |grep gps didn't show gpsd once waypoint was closed.

Hm. If it doesn't produce an error, then it sounds like you've connected to the GPS receiver, but have not yet received an NMEA sentence. Usually, GPS receivers will send NMEA sentences even when they don't have a fix (i.e. with satellite info). If you're not getting any NMEA sentences at all, it sounds like the connection isn't really working that well. In fact, you really should be getting an error after about 10-15 seconds.
I'm not getting an error from mapper, but debug info from gpsd shows the clients actually enumerating after it can't create a channel, so something isn't right.

The reason I was trying to start gpsd manually, was that mapper would grab if you choose localhost gpsd server in settings, as long as waypoint had activated the gps, and you left it open.
( as Tuxedosteve posted )
 
Posts: 33 | Thanked: 5 times | Joined on Nov 2007
#44
kept playing around, and am able to start the gpsd server using the navicore helper, without having to launch wayfinder

in xterm ( no root needed ) type:

/usr/libexec/navicore-gpsd-helper



once it's running, launch mapper and it will find the gps if you have it set to gpsd on 127.0.0.1
 

The Following 2 Users Say Thank You to haokah For This Useful Post:
frethop's Avatar
Posts: 283 | Thanked: 60 times | Joined on Nov 2005 @ It's dark in here. I hear laughing.
#45
Perfect! That works! Now I'm wondering how much battery life is chewed up!
 
Posts: 264 | Thanked: 28 times | Joined on May 2006
#46
Hi Gnuite,
Version 2.2 doesn't find my gps (Nokia LD-1W) on my 770 w/2007HE running on mmc.
The GPS and 770 are pairing, the bluetooth LED on the GPS shows it's connected, I get a bluetooth logo in the status bar (which I had not noticed before).

Version 2.0 was working fine.
 
Posts: 148 | Thanked: 20 times | Joined on Sep 2007
#47
I am getting an error on my 770 with 2007he edition also. The GPS pairs fine but I get a GPSD error when Maemo Mapper tries to connect to my gps. I have the bluetooth option selected and MMapper found it when doing a scan but will not connect.

I went back to 2.05 on my 770 and it works fine with my GPS.

2.2 works great on my n800 with 2008 beta installed using the same GPS unit.
 
Posts: 2 | Thanked: 0 times | Joined on Dec 2007
#48
Hi,

I just installed 2007HE and Maemo Mapper on my 770. It used to work fine with 2006 and my Nokia LD-3W (thanks for a great app, btw).

I've read a few posts about people having problems with bluetooth gps receivers on 770 with 2007HE using Mapper. I experience the same behavior: pairing goes fine, when connecting the bluetooth icon pops up but after three tries it show an error.

So I tried using rfcomm:

Nokia-770:~# rfcomm bind /dev/rfcomm0 00:02:76:FD:67:25
Nokia-770:~# rfcomm
rfcomm0: 00:02:76:FD:67:25 channel 1 clean
Nokia-770:~# head /dev/rfcomm0
$GPGGA,172128.258,,,,,0,00,,,M,0.0,M,,0000*56

$GPGSA,A,1,,,,,,,,,,,,,,,*1E

$GPGSV,3,1,10,11,53,276,,20,13,228,,19,49,174,,14, 42,091,*7B

$GPGSV,3,2,10,01,34,132,,22,31,060,,28,24,301,,03, 18,164,*7C

$GPGSV,3,3,10,09,09,023,,17,03,319,*77

So far so good :-)

Now let's try gpsd:

Nokia-770:~# /usr/sbin/gpsd -N -n -F /tmp/gps.sock /dev/rfcomm0
Illegal instruction

Hmm, not good. Any hints?

Best regards,

Peter
 
Posts: 2 | Thanked: 4 times | Joined on Jul 2007
#49
On my N770, I got the "illegal instruction" error when running gpsd and had to update it, resolving the issue for me.

Here's the process I followed:
*Reference: http://sucs.org/Knowledge/Articles/Nokia%20770
*Install new libgps16
**Get http://packages.debian.org/sid/libgps16/armel/download
**mkdir tmp1
**dpkg --extract libgps16* tmp1
*Install new gpsd
**Get http://packages.debian.org/sid/gpsd/armel/download
**mkdir tmp2
**dpkg --extract gpsd_2.33-5_armel.deb tmp2
*Copy new files into place
**cp tmp2/usr/sbin/gpsd /usr/sbin
**cp tmp1/usr/lib/* /usr/lib
*Tweak libs
**cd /usr/lib
**ln -s libdbus-1.so.2.0.0 libdbus-1.so.3

Last edited by j800; 2007-12-03 at 18:42.
 

The Following 4 Users Say Thank You to j800 For This Useful Post:
Posts: 2 | Thanked: 0 times | Joined on Dec 2007
#50
I tried the fix copying in new libgps and gpsd binary. It now works when gpsd is started from the command line (rfcomm first, then gpsd). Maemo mapper works when connecting to local gpsd.

But maemo mapper crashes/quits if I try the bluetooth option :-/

So: how do I automate the above, or is there a way to fix maemo mapper so that it works?
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 16:30.