I have a UBLOX-7 USB stick and everything used to be fine. Maybe when playing around with the baud rate settings in another context, it stopped working.

I attached some screenshots:
-GPSD file
- Output when running minicom for ttyACM0 (I am getting timestamp, but no GPS coordinates)
- gpsmon
- systemctl status

- cgps shows: (to me this looks like there is something wrong):

ospf 89 OSPFIGP # Open Shortest Path{"class":"WATCH","enable":tr
ue,"json":true,"nmea":false,"raw":0,"scaled":false,"timing":false,"split24":fals

56Z","flags":1,"native":0,"bps":9600,"parity":"N","stopbits":1,"cycle":1.00}]}
{"class":"WATCH","enable":true,"json":true,"nmea":false,"raw":0,"scaled":false,"
timing":false,"split24":false,"pps":false}


I am not sure if this could be an indicator of the problem, but when for instance entering in the terminal "stty -F /dev/ttyACM0" I am getting as response that resource is busy. Maybe this is correct because the port has already been accessed by the GPSD-daemon when boot?

Isn't it the case that GPS is in binary mode? You can use gpsctl -n to set it back to NMEA mode.
Add "-D 4" to gpsd options to verbose logging and debug.

Hi Radek,

Thanks a lot. Tried gpsctl -n, and removed -b from the options. Unfortunately, not there yet. I also set -D4 for logging, but where do I find the log files?

Best, Helge

Hi Helge, the documentation says this

to be honest, I do not really understand what it means

I have been trying to find the logs, and checked a couple of websites to get my head around, including looking into syslog files, but got lost.

If I run "cgps", this is what I am getting - any other ideas on what I could try?

Kill gpsd and run it in a terminal with -N option (plus all options from config file) i.e.

this is what I am getting...

first I entered the line as suggested, and received a couple of error messages

then checked systemctl status gpsd

another screenshot, with more messages

gpsd is not killed and is blocking the port. You can use other port to overcome this with option -S

Dear Radek,

in a way, things seem improving, at least I can see the time...but still no position data...(i.e. no fix)

Attached, please find the output when entering the command as suggested, in addition what I see on gpsmon.

One thing I still wonder about: the gpsd file stored under /etc/default : what should be included? I commented out (with #) those lines that initiate to start the GPSD daemon upon boot as well as the sentence on USB hotplugging. Is that right? Maybe this has been causing the blocking of the port?

I think you just don't get a fix. Try this out outside. Leave it there for long time to test.
Your gpsd configuration posted previously looks ok. I wouldn't change it

Helge,
I had a similar issue on a laptop with my GPS dongle, the page below sorted it for me,

raspberrypi.stackexchange.com/questions/28483/cgps-gps-timeout

Amend the /etc/default/gpsd file to read

DEVICES="/dev/ttyUSB0"

All working fine now

Regards

Alan