TinyRTK Drone Edition - Fully integrated RTK module with u-blox NEO-M8P


u-blox NEO-M8P is the smallest high precision RTK GNSS (Real Time Kinematics) module available on the market and TINY RTK is the first global solution for u-blox NEO-M8P. The RTK algorithms are pre-integrated into the module. As a result, size and weight are significantly reduced, and power consumption is five times lower than existing solutions, thus cutting costs and improving usability dramatically.

Following a high demand for an integrated solution for UAV users, we jointly achieved with u-blox and PX4 a version specially designed for this purpose : TinyRTK Drone Edition. The boards include patch antennas and a battery-powered base. Base can stream differential data to ground control station through a BLE module.


  • Centimeter‑level GNSS positioning for mass market, based on U-Blox M8P

  • Integrated Real Time Kinematics (RTK) for fast time‑to‑market

  • Smallest, lightest, and best energy‑efficient RTK module

  • Receiver type: 72-channel GPS L1 , GLONASS L1, BeiDou B1, GALILEO E1

  • Nav. update rate: up to 8 Hz

  • Position accuracy: 2.5 cm

  • MAVLink protocol encapsulation through u-blox NINA-B1 Bluetooth Low Energy module

  • Connectors: USB, JST-GH

  • Compass : HMC5983

  • Power : LiPo 1S compatible / USB with integrated charger

  • Size: 50 x 50 mm

  • Weight : 24g


Why this architecture?

  • it is small and consumes little energy

  • base can be standalone, wireless, rechargeable and located on a good sky view spot regardless of ground control station's position

  • base is compatible with 1S LiPos, rechargeable by USB with integrated charger

  • rover module is supported by Pixhawk

  • base module : encapsulation within MAVLink protocol is under development (some developers have already got our boards, we will keep sending them to all)

  • rover includes a compass (HMC5983)

  • patch antenna included to avoid additional integration costs


Support us in our Indiegogo campaign and do not hesitate to ask any question !


Drotek Team


Views: 2854

Comment by Marc Dornan on September 20, 2016 at 4:44pm
Drear Drotek--please fix your wiki! I emailed through your web contact form days ago. Smart Nav wiki has no images. I need this fixed soon as I am deploying one that has sat on my shelf for too long. Sorry to post OT messages but I hope this is seen...
Comment by DROTEK on September 21, 2016 at 12:06am

@Marc: we have migrated the wiki to our site and you can see all docs here https://drotek.com/en/documentation/

Comment by DROTEK on September 21, 2016 at 12:56am

@Thorsten ;

In progress!

@RPM : 

In accordance with u-blox documentation refresh rate is firmware-limited to 5Hz for multi-GNSS RTK. Exactly you got the point, it will provide more accurate readings at a slower rate. I guess the good way to deal with the delay between timestamps would be to interpolate position thanks to hot-shoe precise timestamp (CAM message).

Comment by Chopin-Yan on February 22, 2017 at 2:30am

i use gps inject function on mission planner, it can receiver RTCM from base(M8P) as image below, also i have setup px4 gps_inject parameter (send to all), it's seem nothing have been send by gps_inject function

NEO-M8P-2 (base)               NEO-M8P-0 (rover)


You need to be a member of DIY Drones to add comments!

Join DIY Drones

© 2017   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service