GPS on the Neo 1973 - Revision history

Glenn: -cat

2009-07-19T07:14:04Z

-cat

Kempelen: Category: Application Developer

2008-09-15T22:58:21Z

Category: Application Developer

Brian H Wilson: Manually using GPS moved to GPS on the Neo 1973: THe page name did not make any sense and info is only for the Neo 1973

2008-08-15T20:34:33Z

Manually using GPS moved to GPS on the Neo 1973: THe page name did not make any sense and info is only for the Neo 1973

Spin: /* Using UDP */

2008-03-26T22:45:12Z

‎Using UDP

Spin: dont use print to avoid extra newlines

2008-03-26T22:42:04Z

dont use print to avoid extra newlines

Spin at 22:37, 26 March 2008

2008-03-26T22:37:58Z

AudriusA: Project rename

2008-02-05T12:10:02Z

Project rename

AudriusA: Added about GPS preview

2008-01-20T17:39:36Z

Added about GPS preview

AudriusA: Moved the piece of obsolete information into separate article, consider deleting.

2008-01-12T20:41:07Z

Moved the piece of obsolete information into separate article, consider deleting.

AudriusA: /* Quick test (driver output to console) on Neo1973 Phase 1 */

2008-01-12T11:27:05Z

‎Quick test (driver output to console) on Neo1973 Phase 1

← Older revision		Revision as of 07:14, 19 July 2009
Line 89:		Line 89:

	Some information about it is available at [http://gpsinformation.org/dale/nmea.htm gpsinformation.org] and on [http://en.wikipedia.org/wiki/NMEA Wikipedia].		Some information about it is available at [http://gpsinformation.org/dale/nmea.htm gpsinformation.org] and on [http://en.wikipedia.org/wiki/NMEA Wikipedia].
−

	[[Category:GPS]]		[[Category:GPS]]
−	~~[[Category:Application Developer]]~~

← Older revision		Revision as of 22:58, 15 September 2008
Line 92:		Line 92:

	[[Category:GPS]]		[[Category:GPS]]
		+	[[Category:Application Developer]]

@@ Line 79: / Line 79: @@
       line = s.recv(1024)
       sys.stdout.write(line)
 the program just prints those to stdout but other methods are possible (i feed them into a NMEA parser).

@@ Line 71: / Line 71: @@
 the help says that -nmea is the default, fact is that gllin logs nmea sentences into ./log/<date> wich will fill up mem or rootfs for long running tests. the following python script reads the nmea sentences (you need to have python-io installed to get the socket module):
   import socket
   s = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
@@ Line 76: / Line 78: @@
   while True:
       line = s.recv(1024)
-      print line
+      sys.stdout.write(line)
 the program just prints those to stdout but other methods are possible (i feed them into a NMEA parser).

@@ Line 69: / Line 69: @@
   -nmea
-the help says that -nmea is the default, fact is that gllin logs nmea sentences into ./log/<date> wich will fill up mem or rootfs for long running tests. the following python script reads the nmea sentences:
+the help says that -nmea is the default, fact is that gllin logs nmea sentences into ./log/<date> wich will fill up mem or rootfs for long running tests. the following python script reads the nmea sentences (you need to have python-io installed to get the socket module):
   import socket

@@ Line 18: / Line 18: @@
 This way it is possible to see the first results very easily.
-== The "GPS preview" program with graphic interface ==
+== The "GPS Sight" program with graphic interface ==
-''Main article: [[GPS preview]]''
+''Main article: [[GPS Sight]]''
-There is also a working open source GPS preview program to get the gllin output to the graphical environment. It can immediately show the location, altitude, speed and curved distance from selected point. This program, however, does not draw any maps.
+There is also a working open source GPS preview program to get the gllin output to the graphical environment. It can immediately show the location, altitude, speed and curved distance from selected point. This program can also draw the covered path (no background map).
 == The old program in /home/root/DM2/gps ==

← Older revision		Revision as of 17:39, 20 January 2008
Line 17:		Line 17:

	This way it is possible to see the first results very easily.		This way it is possible to see the first results very easily.
		+
		+	== The "GPS preview" program with graphic interface ==
		+	''Main article: [[GPS preview]]''
		+
		+	There is also a working open source GPS preview program to get the gllin output to the graphical environment. It can immediately show the location, altitude, speed and curved distance from selected point. This program, however, does not draw any maps.

	== The old program in /home/root/DM2/gps ==		== The old program in /home/root/DM2/gps ==

@@ Line 5: / Line 5: @@
 All purchased phones do not include the GPS binary driver.  [http://lists.openmoko.org/pipermail/community/2007-July/008466.html]
 But finally, as described in [[November_29%2C_2007_Community_Update]], the binary driver is available to the community now.
 There is an ongoing effort to write a Free Software
@@ Line 21: / Line 18: @@
 This way it is possible to see the first results very easily.
-== Binary Daemon GLLIN ==
+== The old program in /home/root/DM2/gps ==
-For those few with the binary driver in the meantime, Pavel Machek
+In the very early shipment to 50 Phase 1 developers, a binary-only program for talking to the the GPS was accidentally included
-[http://pavelmachek.livejournal.com/39229.html provides] the
+in /home/root/DM2/gps, (and presumably, the same binary would function on a P0 device). It was compiled to OABI format which now is obsolete as OM2007.2 builds are in EABI format, but developers suggested tricks to run it with ''chroot''. These approaches seem now obsolete and the old binary seems even no longer easily available.
-following script for recording an NMEA stream from the binary program.
-−
- #!/bin/sh
- echo 1 > /sys/class/leds/gta01\:vibrator/brightness
- killall gllin cat
- sleep 1
- echo 0 > /sys/class/leds/gta01\:vibrator/brightness
- mknod /tmp/nmeaNP p
- cat /tmp/nmeaNP >> /tmp/gps.nmea &
- /home/root/DM2/gps/gllin -low 5
- /home/root/DM2/gps/gllin -periodic 3
-−
-The binary program was compiled to OABI format which now is obsolete as OM2007.2 builds are in EABI format. You can still run the binary with ''chroot''. [[user:Zdanek|Bartek Zdanowski]] wrote an [http://www.openmoko.org.pl/node/55 aticle] how to run GPS receiver. Alternativly ld-linux can be used to do the trick:
-−
-==The ld-linux trick==
-−
-you need the following files:
-−
- bin/gllin
- bin/gllin.sh
- lib/ld-linux.so.2
- lib/libc.so.6
- lib/libgcc_s.so.1
- lib/libm.so.6
- lib/libnss_dns.so.2
- lib/libnss_files.so.2
- lib/libpthread.so.0
- lib/libresolv.so.2
- lib/librt.so.1
- lib/libstdc++.so.6
- lib/libutil.so.1
-−
-the file bin/gllin.sh contains:
-−
- #!/bin/sh
- `pwd`/lib/ld-linux.so.2 --library-path `pwd`/lib `pwd`/bin/gllin -low 5
- test -p /tmp/nmeaNP || ( rm -f /tmp/nmeaNP && mknod /tmp/nmeaNP p )
- `pwd`/lib/ld-linux.so.2 --library-path `pwd`/lib `pwd`/bin/gllin -periodic 3
-−
-be shure to start at least a `cat /tmp/nmeaNP` somewhere.
-−
-another aproach (chroot) is described in [[Gllin]] - here is also a link to a archive with all needed shared libraries in the right format.
-−
-==Strange effects==
-−
-the message
-−
- Stack size 8864 bytes (9 KB)
-−
-means, nobody is reading on the pipe /tmp/nmeaNP, you probably forgot to start the `cat ...`.
-−
-the message
-−
- gllin: early exit(3) in halInit()/681
-−
-is issued by the low-level hardware test but gllin works fine afterwords.
-−
-do not use the option
-−
- +daemon
-−
-because gllin writes all files to /tmp then which is a bad idea. because /tmp is ram it is lost. because ram is limited the logfile will eat up your memmory.
 == Bluetooth GPS ==