I can't seem to get the GPS to work. I've checked it on Open CPN, GPS Satellites, and GPS Panel. I'm using the Qstarz BT-Q1000XT with a USB cable. It works perfectly with Windows based OpenCPN. I had to install a windows driver for it. Is there a driver required for Navigatrix?

Thanks,

Tim

With Navigatrix and the gps daemon (gpsd) you should not need to install any drivers. It normally just works.

However when it does't we need to figure out what link in the data chain is broken.

The easiest way to tell if the gpsd is recognising the gps is to fire up xgps or Menu> Navigation> GPS Satellites

If the gpsd is not picking up the gps it will look like this...the noticeable "proto" in the line:

If the gpsd recognises the gps it will look like this:

Which do you see?

If you see the gpsd pick up the gps like /dev/ttyUSB0 we need to do something else...but, I'm making the wild assumption that you're seeing the first screenshot. If that is the case...open a terminal.

In the terminal execute:

sudo dpkg-reconfigure gpsd


Make what you see in your terminal look like what you see in the following images. The <tab> key moves you around and cycles through your options if you get too excited and overshoot. <Enter> commits the screen and moves you to the next screen.



This is the only tricky part. You need to add -N to the line with -n -b -G. Order is not important.Spa cing is. Tab to <Ok> when your done and <Enter> to go to the last exciting screen.



The easiest thing is to reboot. ..and give it a whirl.

Your assumption was correct... proto in the command line is clearly visible and no satellites. I went through the procedure above. When I re-booted and ran xgps it said gpsd not running.

I reverted back to yes on the " start gpsd automatically and tried again. I still have the proto and no satellites showing.

How do I start gpsd manually? Any other suggestions?

Thanks again,

Tim

I ran a number of trials to replicate...try and replicate what is going on.

I came up with two scenarios that it would happen....then I realised some idiot posted the wrong screenshot. You want the gpsd to start automatically.

It should be:

...at least I hope that it was just a lapse on my part.

Give that a go. If it fails to pick up. Execute lsusb in the terminal and post the return so we can start looking at the hardware involved.

Sorry for the inconvenience....

OK I ran lsusb with the GPS plugged in and running. These are the results...

x@nx:~$ lsusb
Bus 002 Device 004: ID 04f2:b1d8 Chicony Electronics Co., Ltd
Bus 002 Device 003: ID 154b:0059 PNY
Bus 002 Device 002: ID 8087:0020
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 007: ID 0e8d:3329 MediaTek Inc.
Bus 001 Device 005: ID 0cf3:3005 Atheros Communications, Inc.
Bus 001 Device 002: ID 8087:0020
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
nx@nx:~$

I also ran it with the GPS unplugged.

nx@nx:~$ lsusb
Bus 002 Device 004: ID 04f2:b1d8 Chicony Electronics Co., Ltd
Bus 002 Device 003: ID 154b:0059 PNY
Bus 002 Device 002: ID 8087:0020
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 0cf3:3005 Atheros Communications, Inc.
Bus 001 Device 002: ID 8087:0020
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
nx@nx:~$

This is the only thing missing after unplugging the GPS...

Bus 001 Device 007: ID 0e8d:3329 MediaTek Inc.

Thanks again,

Tim

...and therein lies the problem.

The computer doesn't know your gps is a gps. It is technically listed as a "gadget" and probably being loaded as an "asynchronous communication mechanism" (/dev/ttyACMx).

The good news is 'gadgets' have had kernel support for the last 4 years. We'll take a look for the module (driver) in Navigatrix and figure out how to tell the gpsd "No, this isn't a gadget...it's a gps."

The bad news is I'm scheduled to hang some more pictures and shelving on the walls for the next few days...if I don't I'm dead meat.

Unless someone else chimes in it'll be a few days.

...actually, a cheap easy fix is to tell the gpsd where the gps is located.

sudo dpkg-reconfigure

GPSD Automatic: yes
GPSs Automatic: yes

...but in the third step Device the GPS receiver is attached to:

Enter:

/dev/ttyACM0

In the next window remove the -N that was added.

...and then Ok your way out.

The downside of doing it this way is the gpsd will only recognise this gps, or gpses of this type (ACM)...or be confused if you plugin a non-gps ACM before you stick in your gps.

OK... This has me up and running. If you happen to come up with a better solution, please let me know. In the mean time I have GPS. Your assistance has been fantastic.

Thanks again,

Tim

Ok, Tim...ready for some more fun?

Since it worked, this might be a simple solution that doesn't limit your possibilities....then again it might not work at all. I had no way to test this.

Open a terminal and enter:

This opens a text file of rules for the device manager. Every gizmo you plug in has a manufacturer's id and a product id. In the case of your gps it's 0e8d:3329; vendor: product.

If you add the following rule to this text file the device manager will look up the rules and assign this vendor's product, your gps, to gpsd The first line is a comment to make it easier for programmers to remember what the next line is for because programmers apparently have poor memories. The second line is the rule. Computers are really good at following rules. It's a match made in heaven.

This snippet is added at the end of the list of other rules for gizmos that the device manager assigns to the gpsd. it's position in the list is insignificant....but to be tidy and keep the machine from getting an attitude place it before the line

ACTION=="remove", RUN+="/lib/udev/gpsd.hotplug.wrapper"

...which is the rule for when a device is removed from the system.

Save the change.

Reconfigure the gpsd with sudo dpkg-reconfigure gpsd and blank the line where you pointed the gpsd to /dev/ttyACM0.

Plug in that bad boy and give it a whirl. If it works....yea!

If it doesn't...undo the changes and we'll go back to the drawing board.

Success!!!

Thanks again Moe! I'm grinning from ear to ear.

Tim

Cool.

I am also having trouble getting my GPS to work. I have a Lowrance Endura GPS and have tried these solutions without success. Here are my results from Isusb:

With GPS running
nx@nx:~$ lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 04f2:b015 Chicony Electronics Co., Ltd VGA 24fps UVC Webcam
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 008: ID 045e:ffff Microsoft Corp.
Bus 001 Device 003: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 2.0 Stick (4GB) / PNY Attache 4GB Stick
Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Without GPS running
nx@nx:~$ lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 04f2:b015 Chicony Electronics Co., Ltd VGA 24fps UVC Webcam
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 2.0 Stick (4GB) / PNY Attache 4GB Stick
Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Oh this might be a toughie... I did a quick look and the USB device (045e:ffff Microsoft Corp.) that appears to be your GPS is showing up in ebook readers and SD card readers.

I'll dig a little deeper.... (I'm assuming that when you said "tried these solutions" you swapped out the vendor and product IDs.)

In the meantime, try booting with nothing attached to the machine. After it's done grinding; attach your gps...wait about 10 seconds..and then unplug it.

Run dmesg | tail > ~/Desktop/dmesgtail.txt

This should give both the unplugging and plugging events in one go.

...and for addition fun execute another lsusb > ~/Desktop/lsusb.txt

Stick in you wireless adapter if you need and either cut'n'paste the contents of those two files that have magically popped onto your Desktop or attach them to a post and we'll take a look.

Help me out a little...since all the references I've found so far refer to the chip set as a 'storage device' in some form or the other. No one on the entire intertube was having problems with live data. I was beginning to think there is no live NMEA output. Sure it can download and upload maps, gpx files etc; and there are plenty of people who are having trouble with that....but can it stream realtime data?

There are 3 Lowrance Endura models, Sierra, Safari, and Out & Back. All three report to have NMEA output....but apparently must be configured on the handheld. I'd rather not wade through the all the manuals if I can just wade through one.

So...basically...what's the model and is it set up to port out the data?

I tried the two commands you suggested and nothing appeared on the terminal emulator just went back to a cursor? The GPS is an Endura Out & Back and the NMEA0183 output is enabled under settings-gps.

OK, I see the files on the desktop. I was looking for the information on the screen....guess I should read more carefully the first time. Here are the results:

[ 65.206855] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 66.041703] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[ 66.041717] ata3.00: waking up from sleep
[ 66.041733] ata3: hard resetting link
[ 66.364098] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 66.369200] ata3.00: configured for UDMA/100
[ 66.369269] ata3: EH complete
[ 75.312057] wlan0: no IPv6 routers present
[ 339.086671] usb 1-4: USB disconnect, device number 5
[ 339.111502] scsi: killing requests for dead queue

Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 04f2:b015 Chicony Electronics Co., Ltd VGA 24fps UVC Webcam
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 2.0 Stick (4GB) / PNY Attache 4GB Stick
Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Our wires got crossed somewhere.

The dmesg|tail command shows the last 10 line of your log file (default is 10 lines "tail -n X" for X number lines). The little chunk on th end (> ~/Desktop/some_name) writes the output from the terminal to a file at the home of the current user...in a directory (e.g.,Desktop) with some_name.

The system recognises your hard drive (~60 second range) and the gps being unpluggged at 339.08667 seconds into the operation.

What I was looking for is that bit (at 339 sec.) and what the machine says when the gps is plugged back in after waiting 10 seconds (so the machine doesn't port jump); and then seeing how it is relating to the "new" device.

As the lsusb indicates the gps is not attached.

However,the disconnect message appears that it is seeing it as an external storage device.

I don't have a Lowrance Endure Out&Back so this is a SD card as an example.

The machine logs as much data as the device provides and tells me where it's attached (/dev/sdb1).

So humour me and see how much data we can extract from the log when the gps is plugged in. Maybe we can find out how it's attached to the system...and maybe we can figure out how to have the gpsd pick it up through the udev rules; or have those rules not pick it up as a storage device before the gpsd can see it.

I've just been through the Out&Back's manuals and specifications. I do not see any indication that it works as anything other than a storage device when it is connected to a computer. The gps reads and writes to a storage device and the computer transfers to/from that storage.

I do see that it will output NMEA data, but nothing that indicates it will output that data in realtime. That is data is written to memory...and then that memory is transfer after it has been collected.

I do not see any of the typical indicators that there is the possibility of streaming realtime data....but I'm a few years behind on the swanky new gps units. On this subject the intertube is tall grass and bushes and I can't find the information I think I need. I am, however, currently in a large metropolitan city and I'll swing by a few shops to chat with people who deal with these units and perhaps lay my hands on one to investigate....currently I'm not optimistic. The good news is that I'm not the last word.

My new best friend at The House o' GPS indicates the statement on page 16 of your manual is true...and it will not pump live data to a computer.

...of course he did want to sell me another gps that was priced at more than the GPD of a small nation. These folks are mad.

I have a DeLorme LT-40 and a backup LT-20. Neither is working in Navigatrix despite being properly identified in lsusb as 1163:0200. Since these seemed a bit slow to get a fix I was thinking about replacing them with GlobalSat BU-353, either S3 or S4. Can anyone verify that these devices work as they should with Navigatrix?