<p>I am running ardurover (title bar says &quot;Mission Planner 1.3.77 build 1.3.8110.38294 ArduRover V4.4.0-dev (650e8652) on a Beaglebone Blue with Linux 5.10.140-bone-rt-r68. I have a GPS connected to the GPS connector, and I can see NMEA sentences when I stop ardurover and use minicom on /dev/ttyS2 at 9600 baud.</p>
<pre><code>$GPGGA,165720.000,...,1,04,2.17,61.0,M,-17.1,M,,*6C
$GPGSA,A,3,23,15,18,10,,,,,,,,,2.38,2.17,0.98*03
$GPRMC,165720.000,A,...,0.19,149.90,021022,,,A*7D
$GPVTG,149.90,T,,M,0.19,N,0.36,K,A*35
</code></pre>
<p>However, Mission Planner always says no GPS. I've set the rates up for all ports except SERIAL0 to be SERIALX_BAUD: 9 and SERIALX_PROTOCOL: 5 (also tried 20), and SERIALX_OPTIONS: 0. I've restarted Ardurover and the entire board.</p>
<p>This is how it is being launched using systemctl:</p>
<pre><code>SERIAL0=&quot;-A udp:192.168.0.27:14550&quot;
SERIAL1=&quot;-C /dev/ttyS1&quot;
SERIAL3=&quot;-B /dev/ttyS2&quot;

/usr/bin/ardupilot/ardurover <span class="math-container">$SERIAL0 $</span>SERIAL1 $SERIAL3
</code></pre>
<p>What am I missing?</p>

CC BY-SA 4.0
2022-10-03T15:06:56.487Z
You could try setting "SERIALX_PROTOCOL: 5" only on one port at a time. There is a note on https://ardupilot.org/rover/docs/common-flight-controller-wiring.html which states: "It is important that a GPS be connected to the first SERIALx port that has its SERIALx_PROTOCOL parameter set to “5” (GPS) since it will stop searching for GPS during bootup if not found on the first port configured for GPS protocol." So, if your GPS is not on the first port perhaps it is also not looking past the first port?
Kralc
CC BY-SA 4.0
2022-10-03T20:15:42.260Z
I will attempt that and let you know.
Steve
<ardupilot><gps>
Ardurover: Cannot get NMEA from GPS to ardurover: Raw serial is fine
Steve
# Ardurover: Cannot get NMEA from GPS to ardurover: Raw serial is fine

(Asked by: username_0 on 2022-10-02)

I am running ardurover (title bar says "Mission Planner 1.3.77 build 1.3.8110.38294 ArduRover V4.4.0-dev (650e8652) on a Beaglebone Blue with Linux 5.10.140-bone-rt-r68. I have a GPS connected to the GPS connector, and I can see NMEA sentences when I stop ardurover and use minicom on /dev/ttyS2 at 9600 baud.

```
$GPGGA,165720.000,...,1,04,2.17,61.0,M,-17.1,M,,*6C
$GPGSA,A,3,23,15,18,10,,,,,,,,,2.38,2.17,0.98*03
$GPRMC,165720.000,A,...,0.19,149.90,021022,,,A*7D
$GPVTG,149.90,T,,M,0.19,N,0.36,K,A*35

```

However, Mission Planner always says no GPS. I've set the rates up for all ports except SERIAL0 to be SERIALX\_BAUD: 9 and SERIALX\_PROTOCOL: 5 (also tried 20), and SERIALX\_OPTIONS: 0. I've restarted Ardurover and the entire board.

This is how it is being launched using systemctl:

```
SERIAL0="-A udp:192.168.0.27:14550"
SERIAL1="-C /dev/ttyS1"
SERIAL3="-B /dev/ttyS2"

/usr/bin/ardupilot/ardurover $SERIAL0 $SERIAL1 $SERIAL3

```

What am I missing?

**Tags:** ardupilot, gps

> **Comments:**
> **username_1**: You could try setting "SERIALX_PROTOCOL: 5" only on one port at a time. There is a note on https://ardupilot.org/rover/docs/common-flight-controller-wiring.html which states: "It is important that a GPS be connected to the first SERIALx port that has its SERIALx_PROTOCOL parameter set to “5” (GPS) since it will stop searching for GPS during bootup if not found on the first port configured for GPS protocol." So, if your GPS is not on the first port perhaps it is also not looking past the first port?  
> **username_0**: I will attempt that and let you know.  

---

## 0 answers

