-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No QGC location with external GPS #10271
Comments
I found this gem in the Qt documentation:
Additional documentation on the setUserEquivalentRangeError Qt function: https://doc.qt.io/qt-6/qnmeapositioninfosource.html#setUserEquivalentRangeError I added this little change to the current master code and the position update starts working again: diff --git a/src/PositionManager/PositionManager.cpp b/src/PositionManager/PositionManager.cpp
index 10d26c3bb..53392b615 100644
--- a/src/PositionManager/PositionManager.cpp
+++ b/src/PositionManager/PositionManager.cpp
@@ -101,6 +101,7 @@ void QGCPositionManager::setNmeaSourceDevice(QIODevice* device)
}
_nmeaSource = new QNmeaPositionInfoSource(QNmeaPositionInfoSource::RealTimeMode, this);
_nmeaSource->setDevice(device);
+ _nmeaSource->setUserEquivalentRangeError(5.1);
setPositionSource(QGCPositionManager::NmeaGPS);
}
|
"QNmeaPositionInfoSource supports reporting the accuracy of the horizontal and vertical position. To enable position accuracy reporting an estimate of the User Equivalent Range Error associated with the NMEA source must be set with setUserEquivalentRangeError." Source: https://doc.qt.io/qt-6/qnmeapositioninfosource.html#details Commit 2a9ecab introduced new behaviour that broke use of external GPS. This change fixes the problem reported in mavlink#10271.
"QNmeaPositionInfoSource supports reporting the accuracy of the horizontal and vertical position. To enable position accuracy reporting an estimate of the User Equivalent Range Error associated with the NMEA source must be set with setUserEquivalentRangeError." Source: https://doc.qt.io/qt-6/qnmeapositioninfosource.html#details Commit 2a9ecab introduced new behaviour that broke use of external GPS. This change fixes the problem reported in #10271.
Fixed in master. |
"QNmeaPositionInfoSource supports reporting the accuracy of the horizontal and vertical position. To enable position accuracy reporting an estimate of the User Equivalent Range Error associated with the NMEA source must be set with setUserEquivalentRangeError." Source: https://doc.qt.io/qt-6/qnmeapositioninfosource.html#details Commit 2a9ecab introduced new behaviour that broke use of external GPS. This change fixes the problem reported in mavlink#10271.
I see, no wonder the accuracy estimate weren't there. Thanks for the fix! |
"QNmeaPositionInfoSource supports reporting the accuracy of the horizontal and vertical position. To enable position accuracy reporting an estimate of the User Equivalent Range Error associated with the NMEA source must be set with setUserEquivalentRangeError." Source: https://doc.qt.io/qt-6/qnmeapositioninfosource.html#details Commit 2a9ecab introduced new behaviour that broke use of external GPS. This change fixes the problem reported in mavlink#10271.
"QNmeaPositionInfoSource supports reporting the accuracy of the horizontal and vertical position. To enable position accuracy reporting an estimate of the User Equivalent Range Error associated with the NMEA source must be set with setUserEquivalentRangeError." Source: https://doc.qt.io/qt-6/qnmeapositioninfosource.html#details Commit 2a9ecab introduced new behaviour that broke use of external GPS. This change fixes the problem reported in mavlink#10271.
"QNmeaPositionInfoSource supports reporting the accuracy of the horizontal and vertical position. To enable position accuracy reporting an estimate of the User Equivalent Range Error associated with the NMEA source must be set with setUserEquivalentRangeError." Source: https://doc.qt.io/qt-6/qnmeapositioninfosource.html#details Commit 2a9ecab introduced new behaviour that broke use of external GPS. This change fixes the problem reported in #10271.
Thank you for solution. |
Expected Behavior
Using external GPS device should provide GCS position and is shown on map
Current Behavior
GCS position is not available even though the device is being read
Steps to Reproduce:
System Information
When posting bug reports, include the following information
Detailed Description
The issue is currently only experienced with v4.2.0 with v4.1.x still providing GCS location. File changes suggested that this is due to incorrect handling of stricter requirements in #9483 which enforces QGeoPositionInfo::HorizontalAccuracy or HDOP availability. Reverting these commits solves the issue.
Also note that this requirements are also set only in follow me mode which is aimed at mobile device which has internal gps; maybe they need different handlings?
Log Files and Screenshots
The text was updated successfully, but these errors were encountered: