Page 1 of 1

What's going on here? GPSD and XGPS LMDE 17

Posted: Wed Oct 22, 2014 4:58 pm
by SHEEPMAN!
As I understand it ...when you launch GPSD you must use sudo (or similar). The program cycles a couple times then changes ownership from supervisor to Nobody or something. It's designed that way for security.

Where I run them the GPS can see enough sky to acquire a lock in under 10 seconds. This is multiple CF-30 units with LMDE 17 OS.

The problem:

1. GPSD is fired up.
2. xgps is run with no sudo (or su) acquires a lock and then quits looking. Often acquiring a lock however due to visibility.

I have a CF-53 in a bad place here, using a Gobi2000 and it just keeps checking the sats.

So did Linux, Mint or Debian leave something out?

Re: What's going on here? GPSD and XGPS LMDE 17

Posted: Wed Oct 22, 2014 7:05 pm
by UNCNDL1
Couple of thoughts. Everything as above worked okay in LM16, right?
And you've of course added yourself to the dialout group?
Is gpsd configured for your gps device?
Did you run this code first? sudo killall gpsd
Try reading through all of these hints to jog your memory,
From the OpenCPN Manual: http://opencpn.org/ocpn/setting_up_gps
Linux
To proceed, the "user" you use on your computer must belong to a group that is allowed to open serial connections. This group is normally "dialout" on Debian based Linuxes, including Ubuntu, and "uucp" on Red Hat based distributions. Read more in Data Connections.
Check your status by writing "groups" on a command line. The response will be all groups that the user belongs to. Make sure that "dialout" or "uucp" is included. If not, you have to add your user to this group. There are many ways to do this, one is to issue this command:
"sudo usermod -a -G dialout $USER"
This applies to many Debian based distibutions, for other distros just drop the sudo and do the command as root, using "su".
All major Linux distribution includes a graphical user settings dialog, where adding a user to a group, could be fixed.
Two methods are available, direct connection or through gpsd.
We start with gpsd.
Install the gpsd and gpsd-clients packages
$ sudo apt-get install gpsd gpsd-clients
"xgps" is client that comes with the gpsd-clients package, and is useful for testing that the gps and gpsd is working properly. If xgps isn't working, it's a gps or gpsd problem, not an OpenCPN problem
To do this in Linux for BU 353 as well as many other gps:es, make sure that gpsd is running and that the package "gpsd-clients" is installed. On Ubuntu 12.04 gpsd needs to be temporarily installed. Make sure to kill any instances of gpsd with the command "sudo killall gpsd"
The command $gpsctl -n will put the GPS into NMEA mode.
If that doesn't work, try $ gpsctl -f -n /dev/ttyUSB0 .This will force a low-level access, bypassing gpsd. For more information: $man gpsctl
More information is as always available through "man gpsctl" Close down OpenCPN before running gpsctl.
None of this is normally noticed when using gpsd, as this program reads both NMEA and SIRF binary sentences.
More Linux hints
If you can't connect to a physical port, such as /dev/ttyUSBO, indicated by a line in the opencpn.log file. Check that you, as a user, belongs to the group "dialout". To see which groups you belong to, run the command "groups". Not all Linux distributions add the user to this group by default. To add your self to the dialout group -> "sudo usermod -a -G dialout $USER"
Check if gpsd is working:
$ ps aux | grep gpsd
nobody 12338 0.3 0.1 4124 1448 ? S<s 18:31 0:00 gpsd -F /var/run/gpsd.sock
you 12356 0.0 0.0 3036 800 pts/3 S+ 18:32 0:00 grep --color=tty -d skip gpsd
This or similar responses indicate that gpsd is running. If you only have something like the second line, ....it is not running.
Run the command "$ls -lrtd /dev/*|tail -10", and see the 10 latest created device files. Run this just after plugin in your gps to see which device was created.

Determine which device your GPS is on your linux system by checking the startup. Look for a line that says something about GPS and /dev/ttyUSB# in the command "dmesg"
Or even better, after connecting a gps mouse, BU-353, we look for a dmesg by running this command.

$ dmesg | grep tty
and get this response back.
[13616.095305] usb 2-3: pl2303 converter now attached to ttyUSB0

Add a script to start gpsd, if this is not done by your distribution. I saved mine as startgps and set the executable attribute. Edit line 3 to match your device, ie /dev/ttyUSB0

#!/bin/sh
sudo killall gpsd
sudo gpsd -n -D 2 /dev/ttyUSB0


Run the script:

$ ./startgps
end of copy and paste

From your other post, are these the steps you are using?
1. sudo echo "\$GPS_START" > /dev/ttyUSB1 #start command for Gobi
2. sudo gpsd -D5 -N -n /dev/ttyUSB1 # starts gpsd. Gpsd prefers to see satellites at this point so a partial clear sky (no roof) is a good thing.
3. Start FoxtrotGPS and wait. I click the auto-center button.
As a last resort, try installing Navigatrix and configuring gpsd for your gobi/gps, and see if it works. I only have a gobi card in the MK3 CF-30, and just might have to pop in the Linux hard drive and see what I can see, so to speak.
It's just me bouncing ideas off of my mentor, sometimes it's something easy. I was also thinking maybe something is conflicting i.e. BT, etc... :doh:

Re: What's going on here? GPSD and XGPS LMDE 17

Posted: Wed Oct 22, 2014 9:28 pm
by SHEEPMAN!
I did this once before and don't think that I missed any of the above.Being bull-headed though I want it to work with no conflicts. These things have been around too long to have to deal w/any stinkin conflicts. Personally I think something was left out.

Several flavors deal with it with no conflicts.

Until proven otherwise I blame LMDE though it may be my fault. I loaded LMDE MATE and upgraded to Cinnamon.

What say you all?

Re: What's going on here? GPSD and XGPS LMDE 17

Posted: Sun Oct 26, 2014 4:20 pm
by SHEEPMAN!
Check if gpsd is working:
$ ps aux | grep gpsd
nobody 12338 0.3 0.1 4124 1448 ? S<s 18:31 0:00 gpsd -F /var/run/gpsd.sock
you 12356 0.0 0.0 3036 800 pts/3 S+ 18:32 0:00 grep --color=tty -d skip gpsd
This or similar responses indicate that gpsd is running. If you only have something like the second line, ....it is not running.
This I need to check.

Thanks,

Cleve, Your MK2 is ready, plus I just finished a MK-1CCS85BM....installed W7 on a Intel 180 SSD. WWAN working (5725 Sierra), Gps working. Repaired touchscreen. Also put a new panel in a another CF-30 (same model).

Small load of hay coming.

J'd the multi-tasker.

Re: What's going on here? GPSD and XGPS LMDE 17

Posted: Mon Oct 27, 2014 2:30 pm
by kode-niner
I should screw around with the GPS on this CF-30. I haven't really given it much thought.

Re: What's going on here? GPSD and XGPS LMDE 17

Posted: Mon Oct 27, 2014 3:54 pm
by UNCNDL1
Loads of fun, you might try this program, OpenCPN: http://opencpn.org/ocpn/setting_up_gps
It's for sailing/navigating but is an interesting program, once you configure your gps. Another one is Navigatrix: viewtopic.php?f=39&t=1319
but their website is not always up and running...

Re: What's going on here? GPSD and XGPS LMDE 17

Posted: Fri Oct 31, 2014 4:29 pm
by SHEEPMAN!
Now THAT'S interesting.

CF-30 MK 2FCS85AM
New install Navigatrix
Fiddled around for a couple hours and finally XGPS was showing the right words but no satellites....waited hours.

HERE IT COMES >>>>> Closed the lid, went in the house, came back out opened the lid and XGPS started working and locked on my location in three seconds. Repeated on re-boot BTW.

Question: What is lid closure doing? Is it buggy?

I see a butt kick script in the future.

I can't wait 'til February 7. (teaser)

Re: What's going on here? GPSD and XGPS LMDE 17

Posted: Fri Oct 31, 2014 4:51 pm
by UNCNDL1
Who else can make it out Left? :salute:
Who ever heard of a left handed salute??

Re: What's going on here? GPSD and XGPS LMDE 17

Posted: Fri Oct 31, 2014 5:14 pm
by SHEEPMAN!
Feb 7 is a separate post...just throwing teasers out now.

I asked several times if there was a right handed salute guy but no action from HQ.:D