TINY RTK : The world smallest precision GPS ... and the cheapest

 

Ultra precise positioning at low cost and reduced form factor.

We just release TINY RTK, the world smallest RTK GPS based on u-blox NEO-M8P.

Size: 23.5 x 24.5 mm

Key features

  • 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
  • Connectors: SMA, USB, JST-GH
  • Data link: whatever can be connected to a UART : Bluetooth, 433-868-915 MHz radio link, XBee, WiFi...

We've decided to launch an INDIEGOGO campaign to lower chip prices by ordering mass. 

If you're interested by precision GNSS and want a Plug&Play solution at an incredible price ... TINY RTK is designed for you

Go To TINY RTK campaign

We'll post regular informations about TINY RTK during the campaign. We're also available for answering your questions, do not hesitate.

 

Views: 10280

Comment by Brian on September 12, 2016 at 1:36pm

@KUJayhawk:  I believe the M8P supports all the standard protocols that other ublox modules support, so it should work with DJI.  The only difference is that the position estimate is/can be more accurate.

Comment by Brian on September 12, 2016 at 1:40pm

@RPM: NavSpark actually had a similar module much earlier, and it's significantly less expensive, but I don't know how it compares to the ublox module.

http://navspark.mybigcommerce.com/ns-hp-rtk-capable-gps-gnss-receiver/

Comment by RPM on September 12, 2016 at 1:44pm

Thanks @Brian but I am talking specifically about the uBlox NEO-M8P-2-10.

Comment by AJ152 on September 12, 2016 at 5:22pm

@DROTEK It looks awesome, is it compatible and ready to use with Pixhawk? 

Comment by Brian on September 12, 2016 at 6:47pm

Developer
Comment by davidbuzz on September 12, 2016 at 7:46pm

what's it weigh *with* an antenna of equivalent capability to one/s we usually use. :-)    It won't work without an antenna.  :-)

Comment by DROTEK on September 13, 2016 at 7:10am

@ Taras Rafa : 

1) The maximum distance for L1 RTK goes up to 10-15 km. Above this distance, ionosphere starts to have a bigger impact on solutions because the error is not cancelled by double differences. If you need longer baselines you would then need an additional base or a L1/L2 system.

2) u-blox chips contain built-in anti-spoofing algorithms, for more details have a look at this.

@Rob_Lefevre :

It can be achieved with the Inject GPS function in Mission Planner and it is work in progress with QGroundControl.

@Brian :

Even though the design looks simple we have been thinking a lot about it. There are several reasons for not adding the antenna directly : 

- active antennas are expensive so users might not want to buy an additional antenna if they already have one (we have selected Tallysman antennas as an option in the Indiegogo campaign)

- antennas can be waterproof but in general electronic boards are not, so with this board you can place your antenna at the top of your drone keeping the electronics protected in a case

- the design is modular with your own design

- we also have another alternative with integrated compass, antenna and a BLE chip to send differential data to ground station wirelessly so if it is what you are looking for go for the other design instead

Why isn't there any compass on the board? 

- HMC5983 is becoming obsolete

- new generation autopilots with include newer and more performant electronics components that might remove the need for an additional external compass

- again, there is another design with an integrated compass

The board has been thought to make it easy for the user. Connectors stick to Dronecode standard and make it possible to encapsulate differential data through telemetry link or to use a separate datalink only for the corrections.

@Paul Meier :

Everything is embedded in the internal processor

@KUJayhawk :

The M8P works with u-blox protocol so there is no reason it does not work with DJI. It might need configuration though.

@RPM : 

Well, the advantages of RTKlib are that you can change the code to your convenience, modify the algorithms, add your own integrity functions, set up TCP servers in order to stream differential data, whatever you want... SMARTNAV has been developed to keep RTK user-friendly/plug-and-play while still having access to everything. The advantage of the M8P is that it may be even easier to manipulate for unexperienced users. Basically you only need to configure your base to send RTCM corrections and set up a position (that can be averaged automatically by the way...).

 

Comment by DROTEK on September 13, 2016 at 7:21am

@Brian : 

We ignore the performance/capabilities of such boards. However our tests on M8P show good results, it looks like u-blox has spent a significant amount of time/money on R&D for this project. Their market entry is maybe posterior but the solution is truly strong.

@davidbuzz : 

We recommend Tallysman TW4721 for the rover, its weight is 34g + cable of 0.31 g/cm. 

Comment by kiki boy on September 13, 2016 at 7:49am

Smartnav RTK is not so user friendly and you should have linux basics.

5g for an M8P vs 12g for M8T (Emlid Reach) and same antenna. Reach have ardupilot camera feedback integration and better support (see their forum)...

Good luck for buyers with support. Smartnav is an abandonned product at this time : just watch wiki => they delete pictures

Comment by DROTEK on September 13, 2016 at 7:55am

@kiki boy : 

Support is not public and no customer has been left unattended for any request. SMARTNAV is not abandoned at all, we have completely changed our website and wiki is now on the website and will be removed from Github.

Comment

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

Join DIY Drones

Groups

Season Two of the Trust Time Trial (T3) Contest 
A list of all T3 contests is here. The current round, the Vertical Horizontal one, is here

© 2019   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service