




|
GNSS module |
U-blox ZED-F9P |
|
|
Compass |
QMC5883 |
|
|
Weight |
20g |
|
|
Application |
Rover (Aircraft) or Base |
|
|
Receiver type |
â– GPS L1C/A L2C â– Galileo E1 E5b â– GLONASS G2 G1 â– BDS B1l B2l |
|
|
Sensitivity |
Tracking |
-163dBm |
|
Reacquisition |
-147dBm |
|
|
Time-To-First-Fix¹ |
Cold Start |
≤35 s |
|
Warm Start |
20s |
|
|
Hot Start |
1 s |
|
|
Position accuracy² |
Autonomous |
2.0 m CEP |
|
DGNSS |
0.5m CEP |
|
|
RTK |
1cm+1ppm (Horizontal)3 |
|
|
Accuracy of time pulse signal |
RMS |
30ns |
|
Velocity accuracy |
GNSS |
0.1 m/s |
|
D-GNSS |
0.05 m/s |
|
|
Operational limits4 |
Dynamics |
≤ 4 g |
|
Altitude |
18000 m |
|
|
Velocity |
515 m/s |
|
|
Baud Rate |
38400-230400 bps(Default 38400 bps) |
|
|
Max navigation update rate |
10Hz |
|
|
1. All satellites at ≥-130dBm 2. CEP, 50%, 24 hours static, ≥-130dBm, > 8SVs 3. Based on 30km, the accuracy error increases by 1cm every 10km from the base station 4. Assuming Airborne < 4 g platform |
||
| Pin | Label | Description |
| 1 | GND | Ground |
| 2 | TX2 | UART 2 Data Output, TTL |
| 3 | RX2 | UART 2 Data Input, TTL |
| 4 | SDA | Compass I2C SDA Pin |
| 5 | SCL | Compass I2C SCL Pin |
| 6 | TX1 | UART 1 Data Output, TTL |
| 7 | RX1 | UART 1 Data Input, TTL |
| 8 | VCC | Module Power Supply, 3.6-6.0 VDC, 5.0V recommended. 5V Power from Serial Port (GPS or telemetry) of FC is ideal. |
- Connect module to serial port of flight controller
|
GenX RTK F9P Air |
Flight Controller Serial Port |
|
VCC |
VCC |
|
GND |
GND |
|
TX1 |
RX |
|
RX1 |
TX |
|
SDA |
SDA |
|
SCL |
SCL |
- If using with Pixhawk Cube use GPS 2 Port, If no other GPS is connected on GPS 1 port set parameter SERIAL3_PROTOCOL to -1 or anything else than 5. You can also use Telemetry 1 or Telemetry 2 Port but make sure no other ports protocol is set to 5(GPS) except the one on which GPS is connected.
- Without RTK Base correction data module can be used as normal GPS (GNSS) module.
- When RTK Base is available the correction data can be sent to flight controller through ground station software (Mission planner / QGroundControl) and telemetry link.
- Normal GNSS modules do not provide good accuracy in vertical direction making it unusable for altitude control and that’s why most flight controllers use barometers which measures atmospheric pressure to control altitude of aircraft.
- Change in temperature and pressure may cause large drifts in altitude in few minutes. Sometimes this may lead to inaccurate data or crash in challenging terrains.
- When RTK is available GPS can be used for GPS altitude as first option, this helps achieve control over altitude in centimeter level precision.
- However it should be set to barometer when no RTK correction data is present.
- For more details see : https://ardupilot.org/copter/docs/common-gps-for-alt.html
- For high power drones or ground vehicles where magnetic interference from motors, ESCs or external things like power line can harm stability of drones or ground vehicles, GPS yaw can be used to estimate heading.
- In this case 2 GPS modules are used on the drone and RTK base is optional. All processing is done onboard making it a more reliable system.
- Out of 2 modules used on board, one acts and moving base and second acts as rover.
- This is advance feature and should be used with caution. More documentation here : https://ardupilot.org/copter/docs/common-gps-for-yaw.html
Reviews
There are no reviews yet.