You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to achieve higher position and orientation accuracy through sensor fusion, absolute time and date without a ground station providing it, as well as to enable fully autonomous flight modes, use of GNSS receivers is required.
For now, use of Ublox M8N GNSS receivers is the first option, due to its low price, ubiquity and knowledge base around them, however this choice can be reevaluated.
There are 2 approaches which can be taken in order to obtain the data from the receivers:
Use the NMEA-0183 protocol and Zephyr's GNSS Interface
This has the downside of the inacurracy of the ASCII-based NMEA-0183 protocol and its extreme runtime performance requirements due to string parsing, however is a very easy starting point and there is a possibility to implement support for manufacturers binary protocols under the hood down the line.
Write our own parser for the GNSS manufacturer of choice's binary protocol
This is much more work-intensive and doesn't use a standardized interface, but should be more accurate and much faster.
The text was updated successfully, but these errors were encountered:
First approach seems like a good starting point to me, only issue would be that there would be no way to configure Ublox M8N using NMEA messages.
Luckily, the M8N has SQI flash and BBR which could be used to retain device configuration, but we would need to configure the device first (i.e. via PC application).
This would also a big reason to implement manufacturer's binary protocol in the future.
In order to achieve higher position and orientation accuracy through sensor fusion, absolute time and date without a ground station providing it, as well as to enable fully autonomous flight modes, use of GNSS receivers is required.
For now, use of Ublox M8N GNSS receivers is the first option, due to its low price, ubiquity and knowledge base around them, however this choice can be reevaluated.
There are 2 approaches which can be taken in order to obtain the data from the receivers:
This has the downside of the inacurracy of the ASCII-based NMEA-0183 protocol and its extreme runtime performance requirements due to string parsing, however is a very easy starting point and there is a possibility to implement support for manufacturers binary protocols under the hood down the line.
This is much more work-intensive and doesn't use a standardized interface, but should be more accurate and much faster.
The text was updated successfully, but these errors were encountered: