\uD83D\uDCDA Relevant data
This decision matrix is derived from this document : Better RTK GPUS support for Ardupilot
\uD83D\uDCD8 Background
L1, L2 and L5
Our end-goal is to be able to locate our drone while the module maintains safe, consistent fixes.
Most RTK solutions support L1/L2. The L1 signal uses the frequency 1575.42 MHz, while L2 signal uses the frequency of 1227.60 MHz. Lower frequencies allow the signal to travel through obstacles such as cloud cover, trees, and buildings better. However, since L1 is the oldest signal out in the field of GPS, one can say that even the cheapest GPS is capable of supporting it. L5 is lot newer than L1 and L2. It is the most advanced signal but not every GPS supports it.
It is important to keep in mind that when choosing GPSs for base station and rover (drone), we need to ensure both support the same frequency bands. If, for example, drone supports L1, L5 and base supports only L1; we are effectively handicapping the drone to just L1. RTK requires common frequency bands for performing the computation. If using L1, L2 on drone and L1 ,L2 on base; both the bands are tracked by the drone and RTK will be able to perform at dual frequency and better performance.
Existing support
Currently our drone is supported by NEO M8 GPS manufactured by Team Blacksheep. We are currently attempting to source another GPS from VectorNav for a VN-200 rugged dev kit through sponsorship.
M8P vs F9P
M8P | F9P | |
---|---|---|
Description | single-banded (L1), M8P module uses M8 positioning engine and is able to support Time Kinematic (RTK) technology. | Dual banded (L1, L2), F9P module uses F9 positioning engine. which is newer than M8, and is able to support Time Kinematic (RTK) technology. |
Pros and cons | Cheaper Easier to find alternatives Incorrect position compared to F9P | Resolves RTK FIXED within seconds Better position hold performance Expensive |
ZED vs NEO
M8P | F9P | |
---|---|---|
Description | ||
Pros and cons | advantage disadvantage | advantage disadvantage |
🚨 M8P Options & D9S
Buy link / datasheet | NEO M8P | NEO D9S |
---|---|---|
Product Page | ||
Reliability | L1 only | All L-bands However, Rover Only & Less community experience. |
Cost (CAD) | $129-199 | $48.85 |
Size and Weight | 12.2 x 16.0 x 2.4 mm, 1.6 g | 12.2 x 16.0 x 2.4 mm, 1.6 g |
Position Accuracy | 0.025 m + 1 ppm CEP | Undocumented |
Convergence time | < 60 s Cold start 26s - 29s | Undocumented |
VSupply | 2.7 V to 3.6 V | 2.7 V to 3.6 V |
Interfaces | Already have driver | Driver needed. |
Weatherproof? | −40 °C to +85 °C | −40 °C to +85 °C Model B −40 °C to +105 °C Model A |
👾 F9P Options
NEO F9P | ZED F9P | ZED F9R | |
---|---|---|---|
Product page | https://www.u-blox.com/en/product/neo-f9p-module?legacy=Current#Product-Selection | ||
Cost (CAD) | $350 | $129 | $150-220 |
Reliability | L1, L5 | L1, L5 | L1, L2 Rover only |
Size and Weight | 12 x 16 x 3.6 mm, 1.25g | 17 x 22 x 2.4 mm, 2g | 17 x 22 x 2.4 mm, 2g |
Position Accuracy | 0.01 m + 1 ppm CEP | 0.01 m + 1 ppm CEP | < 0.01 m + 1 ppm CEP |
Convergence time | < 10 s Cold start 27s - 37s | < 10 s Cold start 25s - 30s | < 10 s Cold start 24 s - 28s |
VSupply | 2.7 V to 3.6 V | 2.7 V to 3.6 V | 2.7 V to 3.6 V |
Interface | Driver needed. | Driver needed. | Driver needed. |
Weatherproof? | −40 °C to +85 °C | −40 °C to +85 °C | −40 °C to +85 °C |
\uD83C\uDF1F Recommendations
✅ Outcome
For M8P | For F9P |
---|---|
🗒️ Changelog
Version | Date | Comment |
---|---|---|
Current Version (v. 4) | 2023-11-16 00:18 | Yashashwin Karthikeyan |
v. 6 | 2023-11-23 02:14 | Yashashwin Karthikeyan |
v. 5 | 2023-11-23 01:25 | Ayoung Eun |
v. 4 | 2023-11-16 00:18 | Yashashwin Karthikeyan |
v. 3 | 2023-11-15 23:51 | Ayoung Eun |
v. 2 | 2023-11-15 09:55 | Ayoung Eun |
v. 1 | 2023-11-09 01:13 | Ayoung Eun |
Add Comment