I have a U-blox7 USB GPS. I have successfully used it on StellarMate on an Rpi3 using GPSD. It just worked out of the box. Now I am trying to use it on Astroberry Server 2.0 on a Pi4. Ekos says the device is connected, but NO FIX. The light on the dongle is blinking green, indicating that is has determined its position.
I tried playing with the GPSD configuration file in /etc/default/ to change the DEVICE = to “/dev/ttyUSB0” as suggested in another thread, but I get a permissions error when trying to save the changes to the file.
So I am stuck.
Hope someone here has had success they can pass along. Thanks.
That's right. GPSD autodetects USB connected GPS automatically and adjusts to its parameters, without any configuration. However, I had a problem with a Prolific PL2303 USB-to -serial adapter - it always stopped working with GPSB after some 8-15 seconds of successful communication. Still don't know if it is a specific problem of the combination of GPSd and PL drivers or whether my PL adapter is just defect, but it seems to work well under other circumstances, e.g. when just dumping the serial messages to the console.
I am having the same issue with a Uputronics Raspberry Pi GPS/RTC Expansion Board and a RPi 4B running latest Astroberry (updated today). GPSD works perfectly on the RPi (as shown on gpsmon) with current time and position, but on Ekos, GPSD, while connecting, shows the message "gps fix in progress" but never gives the fix. The serial connection is ttyS0. I've spent the last 3 days reading everything I can on this issue, and this is the closest that I've come to what may be the problem, but, whenever I try to modify the config file at /etc/default/gpsd, I'm denied permission, including when I use "sudo." Any help will be greatly appreciated. Thanks, and Happy Holidays.
Here's the log from GPSD on Ekos:
2020-12-25T01:13:16: [INFO] Device configuration applied.
2020-12-25T01:13:16: [INFO] GPS Update Timer enabled.
2020-12-25T01:13:16: [INFO] Loading device configuration...
2020-12-25T01:13:14: [INFO] GPS fix is in progress...
I was creating a new Arch Linux based build for my own personal RPi. Found that GPSD would get a fix but Ekos wouldn't. For me I was lucky to have a spare microSD card to go back to my Astroberry build an the GPSD and Ekos worked within seconds. Turns out that there was a breaking change in GPSD v3.22 that would mean the libindi-gpsd would never see the fix happen.
I'm not sure if this was your issue but check what version of GPSD is installed on your machine and if its is v3.22 then I would suggest to downgrade to 3.21 or earlier, otherwise try a nightly build of indi as my fix has been accepted into the main repo.
RPI 4 B (4Gb) running Manjaro ARM
SkyWatcher Esprit 80ED
ZWO ASI1600MM Pro
PrimaLuceLab Sesto Senso 2
I am having the same issue with the Pi4. Everything worked fine on the Pi3. But now I am having issues when I added my ZWO ais120 guide cam the gps stops working. I tried the edit of the /etc/default/gpsd change it to the GPS device name I have tried both gps0 and ttyACM0.
Hi by USB3 do you mean USB 3.0 the blue plugs in the Pi4?
Doing both cgps and gpsmon when the gps dongle is only connected works fine it all stops working once I add the ZWO camera which is a USB 3.0 blue connection(tired both pulgs as well still crashed the gps). I will try connecting everything on the a USB2.0 with a hub and see if that helps
It works. So running gps u-blox 7 on Pi4 it will conflict with the USB3.0. So connecting everything on the USB2.0 was the fix now all the devices are working thanks for you suggestion.