From 248001b4044f9d3010e00191716ef8b93283e092 Mon Sep 17 00:00:00 2001
From: Peter Barker <pbarker@barker.dropbear.id.au>
Date: Tue, 3 Dec 2019 13:11:21 +1100
Subject: [PATCH] AP_NMEA_Output: NavEKF constructors no longer take
 rangefinder

---
 .../AP_NMEA_Output/examples/NMEA_Output/nmea_output.cpp      | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/libraries/AP_NMEA_Output/examples/NMEA_Output/nmea_output.cpp b/libraries/AP_NMEA_Output/examples/NMEA_Output/nmea_output.cpp
index 2884a36813..4e508054c0 100644
--- a/libraries/AP_NMEA_Output/examples/NMEA_Output/nmea_output.cpp
+++ b/libraries/AP_NMEA_Output/examples/NMEA_Output/nmea_output.cpp
@@ -49,9 +49,8 @@ static AP_Logger logger{logger_bitmask};
 
 class DummyVehicle {
 public:
-    RangeFinder sonar;
-    NavEKF2 EKF2{&ahrs, sonar};
-    NavEKF3 EKF3{&ahrs, sonar};
+    NavEKF2 EKF2{&ahrs};
+    NavEKF3 EKF3{&ahrs};
     AP_AHRS_NavEKF ahrs{EKF2, EKF3, AP_AHRS_NavEKF::FLAG_ALWAYS_USE_EKF};
 };