gpsd-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: COEX GPS (model UBX-M8030 IC) on Raspberry Pi 4 Model B 2018 connect


From: Kerry Hoath
Subject: Re: COEX GPS (model UBX-M8030 IC) on Raspberry Pi 4 Model B 2018 connection issues
Date: Tue, 20 Jul 2021 16:20:00 +0800
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0


Okay let me see if I can sort out a little of this mess.



Garry does not like systemd and is of the opinion that it makes gpsd difficult to manage.

For this reason it is best to take gpsd out of the control of systemd and have scripts that start and stop it yourself.


The reason that you should upgrade to the latest gpsd is that there are many fixes and improvements for newer protocols and gps units in the latest version and distributions often bundle old buggy code.


The newest version should talk to more GPS units and is considered to be the best to run in production.


All the names Garry gives to systemD like SystemDreamon are just because he has had bad experiences with it and dislikes it so much it amuses him to come up with a different insult for it which I agree could confuse a new user not used to this.


I have not tried GPSD on the raspberry Pi myself but plenty have and I believe the docs on the GPSD website and the latest code are highly recommended.


Basically it boils down to installing a recent GPSD, (perhaps compiling it yourself from source)

figuring out which serial device on the Pi has your GPS on it, and pointing GPSD at that device to see if it can communicate with a hardware device on that port.


Hope this helps a little.


Regards, Kerry.


On 20/07/2021 2:24 pm, Aranza Shaccid Leon wrote:
Hello and good afternoon sir,

Thank you very much for the advice. I’m afraid I’m a bit confused by the instructions though and if I may, I have a few questions:

1) Updating the GPSD version, what new changes would there be and what version should I be changing too?

2) I was reading the update file that was sent where it states : “import gps;print(gps._version_)” I’m assuming if I want gpsd version 3.22, I type  “import gps;print(gps.3version22)”?

3)May I ask what the differences are for system d(root), system d(ilbert), system d(rippy), or system d(dnk)? I’ve attempted to search for this, but I’ve only found information on system d and nothing this specific.

4)Is the older model of gpsd, in any way imposing on its ability to receive GPS data from the connection between the flight controller to the GPS and flight controller to the RPi? If not, is there a way to configure the GPSD to recognize the other devices in ttyACM0 (usb connection of flight controller and RPi). 

5) I will be removing system d by using systemctl as recommending, but may I ask what gpsd docs for the nonsystemd-parts I should use? Is it similar to the bottom portion of this link I found or should the instruction be present in gpsd.io?  

https://maker.pro/raspberry-pi/tutorial/how-to-use-a-gps-receiver-with-raspberry-pi-4

I apologize for still not having the gpsdebuginfo,
I’m not sure how to get to root on the RPi as I only ever enter as a normal user. I understand that in some cases sudo should not used, but some instructions I found say that using sudo gpsdebuginfo could work as a root command?


Thank you for your time and consideration,

Sincerely,
Leon 


Sent from my iPhone

On Jul 13, 2021, at 9:13 PM, Gary E. Miller <gem@rellim.com> wrote:

Yo Charles!

On Tue, 13 Jul 2021 20:05:26 -0600
Charles Curley <charlescurley@charlescurley.com> wrote:

As I said, I despise systemd(ilbert).  I have no idea how to
configure it.

Maybe someone else can help with that.  

There is some information on using systemd with gpsd in the gpsd docs.

You do not want to disable systemd, despite Gary's disdain for it.

Sorry I was not clear.  You are stuck with sysmted(rippy).  What
I intended to say was disable gpsd running under systemd(dnk).

Doing so will leave you with a massive mess and may render your
system unbootable.

Yes.  A bit worse than the mess you get when you do run systemd(reamon).

What you want to do is either 1) remove gpsd from
systemd's control or 2) get the systemd configuration working to suit
your application.

I vote for 1).

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
   gem@rellim.com  Tel:+1 541 382 8588

       Veritas liberabit vos. -- Quid est veritas?
   "If you can't measure it, you can't improve it." - Lord Kelvin
CAUTION: This email originated from outside of the PNW environment. Do not click links or open attachments unless you recognize the sender and know the content is safe.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]