OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: bazmi on January 13, 2005, 03:43:39 am
-
on a SL6000, i had an ambicom GPS-CF working with the standard sharp rom. after loading OZ 3.5.2 i cant get the gps to work. the software is qpeGPS. in the gpsd setting page i have tried to enter different arguments but still can connect to the gps. when the gps card is inserted, the system seems to recognize it as a serial or modem card and dmesg shows the port assigned is ttyS03. the blue light on the gps card also blinks as it normally should but gpsd cant seem to connect to it. has anyone got it running? if so, how? thanks in advance.
cheers,
/bazmi.
-
I have an SL5500, but it should be a similar problem. OZ sets the serial port to look for a console connection. You will need to disable this in order for serial devices to work. Using your favorite editor, open /etc/inittab. Look for the line that references /dev/ttyS3 (on the 5500 it's ttyS0), and add a hash # to the beginning of that line. Reboot your Z and you should be ready to go.
-
Maybe one of you can help me. I am having trouble getting my gps unit (from serialio.com) to work with my 5600 with opie. I tried commenting out the line you suggest bazmi but I still cannot get it to work. I know it can work because I had it working with qpeGpS on the sharp rom. Any other ideas would be greatly appreciated. Thanks
P.S. I'm trying to get the gps unit to work with qpeGPS and all my programs are on a 256MB SD card in case that helps.
-
Which serial port is QpeGPS (or gpsd) looking at? Is it the correct one?
OZ sets the serial port to look for a console connection.
This is new then, as it didn't used to do this before the 3.5.x ROMs. This does happen with the Sharp ROMs though.
In any case, isn't ttyS0 the serial port on the 5600 too?
Si
-
by default, gpsd looks for ttyS0 but you can change it in the configuration page.
-
Using your favorite editor, open /etc/inittab. Look for the line that references /dev/ttyS3 (on the 5500 it's ttyS0), and add a hash # to the beginning of that line. Reboot your Z and you should be ready to go.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=62397\"][{POST_SNAPBACK}][/a][/div]
here is what my inittab looks like:
l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6
# Normally not reached, but fallthrough in case of emergency.
z6:6:respawn:/sbin/sulogin
S:2345:respawn:/sbin/getty 115200 ttyS0
# /sbin/getty invocations for the runlevels.
#
# The "id" field MUST be the same as the last
# characters of the device (after "tty").
#
# Format:
# <id>:<runlevels>:<action>:<process>
#
1:2345:respawn:/sbin/getty 38400 tty1
# 2:23:respawn:/sbin/getty 38400 tty2
# 3:23:respawn:/sbin/getty 38400 tty3
# 4:23:respawn:/sbin/getty 38400 tty4
i even if i comment out the line which refers to ttyS0 and reboot it doesnt help. and there is no line referncing ttyS3 or ttyS03.
since you have it working, there must be some other step i am missing or could it be something diff about 6000L hardware?
cheers,
/bazmi.
-
Which device have you all been setting gpds to look at? (in the settings screen in QpeGPS)?
Also, are these CF GPS cards or serial ones?
Serial ones should use /dev/ttyS0, the CF ones vary by machine (I think), but I'd start with ttyS1 and work upwards until one works.
Si
-
it is a CF card.
i have tried /dev/ttyS0 thru /dev/ttyS3 and nothing works. when i flash back to the standard sharp rom, it is ok.
dmesg tells me that /dev/ttyS03 is a serial port.
-
Might be worth eliminating the possibility that qpegps isn't communicating correctly with gpsd, but that gpsd is working correctly. I should be possible to telnet to the port on which gpsd is outputing data to see whether it's working.
I'd try starting gpsd from the command line without using qpegps.
Apologies if you've already done this.
Si
-
Hello,
here are my observations with 3.5.2 and my Pretec-CF-GPS-Card. Maybe this helps.
I couldn't get it to run either, but at leas i had a little bit of success.
First of all, use dmesg to see which tty the CF-Card uses. In my case its ttyS3.
Second use cat /dev/ttyS3 to see the raw output. If its a NMEA-Receiver it will print the position information in clear ascii. So you can see whether the hardware runs or not.
Use stty to set the baud rate to 4800.
Then i installed the gpsd from the 3.5.2 feed. qpegps sees the gpsd but dosn't accept its output. qpegps seems to use a special version of gpsd. zroadmap includes a programm
called RoadmapGPS which simply shows the sattelites and the position. This works with the feed version of gpsd.
I took the gpsd from an non-gcc3-Version of qpegps from sourceforge and startet it (it uses no libs so no comapt is needed). With this qpegps works, but due to the floating point changes gives nonsense positions.
You can, and for testing schould, start the gpsd in the console with
gpsd -p /dev/ttySx
you can add -D 3 to see the nmea-Sequences. You will see the sequences only when a program connects.
I tried to compile the newest version of gpsd with openembedded, but the packae is broken (the ipk contains no binary) and after copying the gpsd onto the Z by hand it segfaultet after two sequences.
This is all on a Z-5500 with OS 3.5.2. I hope thia helps in finding a solution for the gps-problems.
-
I would recommend pestering the qpegps folks as for what changes they did to the standard gpsd and if they did send their changes upstream. gpsd 2.6 in OE should now be packaging correctly, btw.
-
AFAIK the changes were submitted to the developers. The current version in the feed is very old. Unfortunately i still couldn't get OE to run until now so i can't test the current 2.6.
-
I am using a serial gps unit on a 5600 and am still having no success. Here is my inittab:
# /etc/inittab: init(8) configuration.
# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $
# The default runlevel.
id:2:initdefault:
# Boot-time system configuration/initialization script.
# This is run first except when booting in emergency (-b) mode.
si::sysinit:/etc/init.d/rcS
# What to do in single-user mode.
~~:S:wait:/sbin/sulogin
# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.
l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6
# Normally not reached, but fallthrough in case of emergency.
z6:6:respawn:/sbin/sulogin
#S:2345:respawn:/sbin/getty 115200 ttyS0
# /sbin/getty invocations for the runlevels.
#
# The "id" field MUST be the same as the last
# characters of the device (after "tty").
#
# Format:
# :::
#
1:2345:respawn:/sbin/getty 38400 tty1
# 2:23:respawn:/sbin/getty 38400 tty2
# 3:23:respawn:/sbin/getty 38400 tty3
# 4:23:respawn:/sbin/getty 38400 tty4
As you can see, I have tried commenting out the suggested line but I still can't get it to work. If I try cat /dev/ttyS0 as suggested it doesn't display anything and I have to ctrl+c. I also tried to cat /dev/ttyS3 and got "cat: Read error: Input/output error". Does anyone have any suggestions on how I can get the raw data without gpsd? I figure I might as well start with baby steps... BTW the light on the gps unit does flash on and off like it did when it was working before.
Thanks
-
Try
stty -F /dev/ttyS0 4800
stty -F /dev/ttyS0 should then display that the serial port was set to 4800 baud.
Then cat /dev /ttyS0 should display something
-
Try
stty -F /dev/ttyS0 4800
stty -F /dev/ttyS0 should then display that the serial port was set to 4800 baud.
Then cat /dev /ttyS0 should display something
[div align=\"right\"][a href=\"index.php?act=findpost&pid=64310\"][{POST_SNAPBACK}][/a][/div]
That worked like a charm. I appreciate the help now on to zRoadmap and qpegps. Thanks again.
-
Hello
I couldn't get the feed versions (including those in the upgrade section) of qpegps and gpsd to work together. I pulled the gpsd sources from the qpegps sf page and compiled those. That seems to work (openSIMpad 0.9-rc1, Garmin Legend on serial cable).
Regards,
Reiner
-
Try
stty -F /dev/ttyS0 4800
stty -F /dev/ttyS0 should then display that the serial port was set to 4800 baud.
Then cat /dev /ttyS0 should display something
[div align=\"right\"][a href=\"index.php?act=findpost&pid=64310\"][{POST_SNAPBACK}][/a][/div]
That worked like a charm. I appreciate the help now on to zRoadmap and qpegps. Thanks again.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=64436\"][{POST_SNAPBACK}][/a][/div]
Did you have any luck with qpegps when I run gpsd I can cat /dev/ttyS0 and I can see NMEA data once I start qpegps but qpegps can't see the data it just shows that it is connected to gpsd but it can not get GMT.
Donald.
-
[ You are not allowed to view attachments ]
Try
stty -F /dev/ttyS0 4800
stty -F /dev/ttyS0 should then display that the serial port was set to 4800 baud.
Then cat /dev /ttyS0 should display something
[div align=\"right\"][a href=\"index.php?act=findpost&pid=64310\"][{POST_SNAPBACK}][/a][/div]
That worked like a charm. I appreciate the help now on to zRoadmap and qpegps. Thanks again.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=64436\"][{POST_SNAPBACK}][/a][/div]
Did you have any luck with qpegps when I run gpsd I can cat /dev/ttyS0 and I can see NMEA data once I start qpegps but qpegps can't see the data it just shows that it is connected to gpsd but it can not get GMT.
Donald.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=73879\"][{POST_SNAPBACK}][/a][/div]
Apperently qpegps only works with the ancient version of gpsd on the qpegps site. I was able to compile it on my 5600 and it seems to work. Just use the attached executable. It also works for zRoadmap. Let me know if this works.
I will try to see if I can figure out how to fix qpegps to work with the new 2.0 gpsd builds when I get a chance, but that might be a while.
Cheers,
Henry von Tresckow
-
I did just try it and it does run and qpegps can get data from it but the lon and lat cordinates returned are incorrect.
-
I did just try it and it does run and qpegps can get data from it but the lon and lat cordinates returned are incorrect.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=79511\"][{POST_SNAPBACK}][/a][/div]
I tried this out with my unit yesterday and all three versions fo gpsd that I have (my binary, the 1.1 packagae from the feed and the 2.6 package from the feed) gave me the same answer. Looking at my local map in zRoadmap had me in the correct location. What kind of GPS are you using? Mine is a serial NMEA interface. I know that the new releases of gpsd have a lot of new features (esp. SIRF support) that weren't in the ancient (~2000) version that qpegps was based on.
-
Hi i have a serial NMEA device as below.
GlobalSat BR-304
http://www.selective.co.nz/gpsbr304.html (http://www.selective.co.nz/gpsbr304.html)
It can use either SIRF II binary or NMEA if I cat /dev/ttyS0 whilst qpegps is running I can see the NMEA data stream. I have also tried this device on a Laptop running gpsdrive and it works fine.
I guess I should install the gpsd from the OZ feed and telnet into GPSD and see what data that returns.
Donald.
-
OK you can ignore my last post about it not returning the correct cordinates, I have just tried it again and i works fine. Thank you hvontres for your efforts I am very grateful.
Donald.
-
OK you can ignore my last post about it not returning the correct cordinates, I have just tried it again and i works fine. Thank you hvontres for your efforts I am very grateful.
Donald.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=79687\"][{POST_SNAPBACK}][/a][/div]
You're welcome.
-
Hello, hvontres. Big thanks for your gpsd, but I am having a small problem. I copied it over, and ran it, then started qpegps...and everything worked! I even got maps for my area, and I was ecstatic! But then, I thought that the gpsd ipk was just taking up room, so i removed it (after dutifully renaming the binaries back so that ipkg removes the correct, non-working one)...and it stops working. I tried removing and reinstalling everything several times, but no good. qpeGPS doesn't seem to want to get gps data from your gpsd binary. I have a 5600, running OZ 3.5.3, and I am plugging a Haicom 303CF into the CF slot. Again, i had this setup working briefly. If you could provide *any* insight, I would be extremely grateful. Thanks!
-
Anyone?
-
Have you tried re-installing gpsd 2.20 from the OZ feed and then replacing the gpsd binary in /usr/sbin with the one from hvontres?
This worked very well for me. If you leave the name as gpsd then it should work. you may need to modify the /etc/init.d/gpsd script to point at the correct serial port. If you are using a device that connects to the Sharp IO port then you will need to set it to /dev/ttyS0 if you are using a CF card then typically you would use /dev/ttyS0. I am using the Sharp IO port and I found that I had to use the following command to set the serial port speed: stty -F /dev/ttyS0 4800 I also created a sym link file in the dev folder like this ln -s /dev/ttyS0 /dev/gps.
I hope this helps.
Donald.
-
Have you tried re-installing gpsd 2.20 from the OZ feed and then replacing the gpsd binary in /usr/sbin with the one from hvontres?
This worked very well for me. If you leave the name as gpsd then it should work. you may need to modify the /etc/init.d/gpsd script to point at the correct serial port. If you are using a device that connects to the Sharp IO port then you will need to set it to /dev/ttyS0 if you are using a CF card then typically you would use /dev/ttyS0. I am using the Sharp IO port and I found that I had to use the following command to set the serial port speed: stty -F /dev/ttyS0 4800 I also created a sym link file in the dev folder like this ln -s /dev/ttyS0 /dev/gps.
I hope this helps.
Donald.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=80778\"][{POST_SNAPBACK}][/a][/div]
Hmm, I just tried this with my SL5500 running OZ3.5.3 and get weird results. I assume because the gpsd from hvontres is compiled for the SL5600. Basically, the gpsd telltale in qpegps flickers between green OK and red ERR. RoadmapGPS shows gobbledygook, control characters etc. Using the gpsd 2.20-r1 from the 3.5.3 feed I get proper nema data in RoadmapGPS, but nothing in qpegps, only a green OK.
Anyone got a gpsd compiled for the 5500 they could send me?
-
Have you tried re-installing gpsd 2.20 from the OZ feed and then replacing the gpsd binary in /usr/sbin with the one from hvontres?
This worked very well for me. If you leave the name as gpsd then it should work.
I hope this helps.
Donald.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=80778\"][{POST_SNAPBACK}][/a][/div]
Basically, the gpsd telltale in qpegps flickers between green OK and red ERR. RoadmapGPS shows gobbledygook, control characters etc. Using the gpsd 2.20-r1 from the 3.5.3 feed I get proper nema data in RoadmapGPS, but nothing in qpegps, only a green OK.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=96908\"][{POST_SNAPBACK}][/a][/div]
Replacing the gpsd binary gave me great results on my collie 5500 under OZ 3.5.4. Both qpegps and roadmap run perfectly (and at the same time), track logs are great, but signals are sometimes hard to get (Abicom CF GPS with external antenna). I had screwed around with alot of commands before hand, but it turned out that all I needed to do was have everything installed (gpsd, qpegps, roadmap), then simply replace the /usr/sbin/gpsd with the version provided previously in this threadz (https://www.oesf.org/forums/index.php?act=Attach&type=post&id=528). I had experienced proper function in roadmap and none in qpegps using the latest version of gpsd, it just seems a downgrade is required to have qpegps working, but this doesn't effect function in roadmap.
I did, however, experience the flashing gpsd status message at times, I believe it was related to having two copies of gpsd running, or resuming from suspend and having problems with that.
SUGGESTION: If you are using a CF GPS card and you wish to suspend, simply suspend and then remove the card. When you want to resume, resume the zaurus and then plug the CF card in. It will then work properly, I've done this and aquired GPS signals within seconds of resume.
Good luck, it's worth all the effing around!
-
Hello,
Any software for GPS and gpe/oz on 3100?
Anyone used gpsdrive?
Thnx
Tasos