Dear friends, I would like to introduce you the RTKite GNSS RTK L1+L2 module receiver.


Designed specifically for Pro and Semi-pro UAV, Robotics and Industrial applications, it connects directly to the Pixhawk and other autopilots and is specific for millimetric Photogrammetry, LIDAR Scans, Themography, etc.

The RTKite is a full Receiver (not a basic GNSS board) with an internal OS that can connect directly to standard CORS stations with its embedded GSM/GPRS cellular modem, can be configured and operated by Bluetooth, COM or TTL communications and can be set with our freeware for Android, Windows PC or WindCE or Linux, or even with text string commands.

It also can receive and transmit RTCM or CRM correction signals by UHF radio or our unique AutoCaster system that allows direct link connection by the integrated mobile modem with an stable transmission range of 75Km on Fixed position.

In is in fact a miniaturization of our professional surveying RTK receiver SmaRTK, (first generation released on 2012), and is compatible with our unique AutoCaster system for direct Base to Rover cellular data link.

Below, an Autocaster test on a modified DJI drone with Pixhawk and the RTKite GNSS with the lightweight helical antenna.3689681774?profile=original



E-mail me when people leave their comments –

You need to be a member of diydrones to add comments!

Join diydrones


  • Dear Evan

    Thank you for your question. At the moment we are adding new fuctions to the Heading RTKite Receiver.

    Currently the outputs for heading include:

    NMEA: $GPHDT that outputs the Heading from True North (Yaw)

    CUSTOM: $GPNAV, outputs in ASCii all that is normally needed on a single string: Position, Yaw, Pitch, roll, etc.

    Novatel ASCii and Binary: HEADINGA and HEADINGB

    And in we are in the process of adding new output formats.

    You can drop us a question directly as a support ticket on this Link:

    And also you will find many details on the integrator ordering site:

    If you need anything else, just send us an email! emea - at -


    Help Desk
  • Just a quick inquiry, as I didn't find information on the datasheet - 

    For the new Heading RTKite GNSS RTK Receiver, is the heading data part of a standardized NMEA stream? Or is it only included in your binary format?

    I am curious about potentially using this board in ArduPilot-based systems, for which a driver would need to be developed in the binary format case.

  • Hello! We are introducing the new Heading RTKite GNSS RTK Receiver module, with all the great features of the original RTKite but adding double antenna to increase the position accuracy for the applications where directional positioning is critical, without increasing the investment!


    The receiver whith these and many more options can be ordered directly from our Integrator Outlet:

    if you need any customization or want to as us a question, just drop us a line:


  • Hello all, kindly note that we have ready a Photo integration kit to connect directly the RTKite to any Hotshoe equipped camera for delay-free geotagging of pictures:

    Also we are already accepting Debit and Credit cards on the website.


  • Hello Mr. Volkmann, our receivers do not need interpolation as the RTK engine can be triggered on the fly so it does not matter how many Hz are used for navigation, the geotagging is recorded delay free. Cheers!

  • Dear Mr. Kopelman, I understand that you are already ordering the RTKite module. I will forward your question to our technical department to see what they comment. Best!

  • Looking to buy or build a module for converting the negative (and noisy) flash pulse that comes from the hot shoe to a sharp pulse for rtkite image triggering.
    Any link to where to buy or detailed instructions on how to build wiuld be appreciated.
  • Thank you a lot for your comments. I really hope that you like its performance and we can help you with many more.

    Here a couple of nice videos from our users that you might like:


  • Thanks for the clarifications. That clears my doubt.

    I am in process of buying two RTKite systems and maybe more after that if we feel happy with its performance. I have to say the effort and support from your team(Luis and Juan) is really commendable. And, your insights in this blog post have really helped me to arrive at the decision of buying this RTK solution for our application. Thanks again!

    Will share my feedback on the product once we test it with our UAV systems.


  • Dear Mr. Banshiwala, thank you for your comments.

    Regarding your questions, please note:

    - The datasheet mentions sampling rate upto 10Hz and 150Hz event log. Could you explain more about what do you exactly mean by event log here and what is it's utility?

    The real time output, i.e. for navigation is selectable as 1Hz, 5Hz or 10Hz (the Pixhawk uses 5Hz).

    There is also the logging for postprocessing DGPS (i.e.RINEX files) and then the logs can be 1,5,10 or 20Hz binary (saved on internal memory).

    - When you mention that, 
    "the position is log at the exact moment that the shutter operates, without any delay ",

    These sampling rates are fine for navigation but too slow for photogrammetry as in a moving vehicle even a little offset could create a big error. So we use a trigger mode where the position is called on demand (i.e. the camera trigger) and in this case then the navigational sampling rate does not matter and the RTK gives out an instantaneous response. For this purpose, the datasheet mentions 150Hz, but it is actually unlimited.

    as the GPS clock time(1,5,10Hz) is much lesser, is this faster logging a repetition of the last recorded GPS data? Or some kind of extrapolation or other methodology is used to estimate the position at the time of logging?

    It is not an extrapollation or a repetition, but indeed a real-time solution computation from the internal algorithm.

    Simply put, the data output is ASCII, that is very slow, so after 20Hz, it makes more sense to use binary data, so it can go way faster. And to avoid saturation, the trigger data is only output on demand, but it is the actual real time position, without any relation with the navigational ASCII output.

    O hope I have made myself clear, cheers! 

This reply was deleted.