Hybrid RTK

See video at the bottom of this page.



With six RTK engines, auto verify, Confidence and Consistency counters, and validation features of our RTK you are already confident that you have reliable and accurate RTK results. You may have base/rover communication outages in some points and you may want to make sure your base location was correct. You may want to use Autonomous solutions for your base and then find the accurate position. DPOS complements your filed work.

With DPOS we check the accuracy of you Base in two ways. One is to post process the Base raw GNSS data with CORS stations and second is to use the known points during your survey and inverse to base. We record the history in three buckets of the “Base” screen. 1) Original base, 2) CORS processed, and 3) m-Local reverse calculations.

In m-Local reverse calculation of the Base, you can pair as many known points with the points that you have surveyed.

We also check the accuracy of the RTK solutions in two ways: 1) we post process your base and rover data and 2) we process your rover data directly with CORS stations, provided that there is enough data for long baseline processing.

We record all histories in the following ways:

In Base screens there are three buckets for the Original Base, CORS processed Base, and m-Local processed Based. We don’t show the coordinates of the CORS stations. They can be viewed in reports.


…while we fill the other 5 buckets.


For the Original Base there are two buckets in “Auto/Known” screen: one for the RTK solutions in the field and second for the PPK (Post-Processed Kinematic) based on the Original base.

For the CORS processed base, there are two buckets in “Absolute” screen: One for the corrected RTK solutions and one for the PPK based on the corrected base with CORS.

For the rover data processed directly with CORS, there is one bucket in the “Absolute” screen.

Rover solutions that are corrected with “m-Local” are also shown in the m-Local

bucket of the “Absolute” screen.

So, the six rover solutions are shown in two screens: two in the “Auto/Known” screen and four in the “Absolute” screen. You can view them by clicking the boxes in the upper left of the “Point Detail” screen.

We will show one solution as default, but you can change to what you want by clicking the radio button of that point bucket. Buckets in the Base screen are only for information.

In the Base screen, the selected coordinate for the base is recorded as the effective position of that base for future use.


And this is how it works.

Version 2.0.0.208 and later.

Here we explain the process and details of the six solution buckets (in Auto/ Known and Absolute screens) and three buckets of base in Base screen.

When survey is done, in Base/Rover Setup screen, download the base data in rover and enter a name for Base.

Click “Points” to see the list of points that you have surveyed. The first in the list is your base, followed with all the points that you surveyed relative to that base.
Click to see details of base and rover points details.

The original Base coordinate is saved in “Auto/Known” bucket of the “Base” screen.

The RTK solution of each point is saved in the “RTK” bucket of that point in the “Auto” screen.
You can long click on the Point name box and select which of point code and description also to be shown in that box.

If you want to verify and improve your original solutions click “DPOS” to send your data to DPOS server and do the following tasks automatically and fill the other 5 buckets.

Base and rover data is sent to DPOS.

First DPOS will post process the rover data at each point with the Base data and verify that RTK results were correct. The new results are saved in PPK (Post Processed RTK) bucket of each rover point in the “Auto” screen. This will cover any failure at RTK due to communication loss or else.

The status and progress of DPOS process is shown in the DPOS screen.

Then DPOS will process the base data with CORS stations and record accurately calculated coordinate of the base in the CORS bucket of the “Base” screen. You could have installed the Base in any location, use Autonomous solution for base and later find its accurate position in DPOS.

The accurate position of the base calculated with CORS stations is used to adjust the rover RTK solutions and record them in the PPK bucket of each point in the “ABS” (Absolute) screen. As said, you don’t need to know the accurate position of your base. You can toggle the top left button.

DPOS also processes all rover data directly with CORS stations (if sufficient data) without need for your own Base station. This is another way to check the accuracy of your RTK.

The CORS processed rover points are saved in the CORS bucket of the points in the “ABS” screen.

If you know the accurate location of some of the points that you have surveyed, you can use the “m-Local” process to pair them, “reverse calculate” the position of the base. You can do this in the field in real time too.

The inversed location of the base is saved in the “m-Local” bucket of the base screen.

The adjusted points according the “inverse calculate” base are saved in the m-Local buckets of the points in the ABS screen. With this process you don’t need to know the accurate location of your base or use this to verify your works.

You can continue the “m-Local” process with more than one pair and enhance your base and results.

The result of newly reverse calculated base is recorded in the m-Local bucket of the Base screen.

The impact on points are recorded in m-Local bucket in the ABS screen of each point.

The summary of the six buckets and the one that is selected is shown in the points list screen. You can change the selection in the detail point screen. Shift and GNSS raw data symbols, number of solutions, solution type, Process type, and Base type are shown in columns.


Advantages of your own base station
and short baselines

1. Shorter baselines provide significantly better reliability because the ambiguities are much easier to resolve and the correct ambiguity solution has an obvious contrast.

 

2. Shorter baseline has better accuracy because most of errors (like atmospheric and tropospheric effects) are common and cancel.

 

3. Shorter baseline ambiguities are resolved much faster. In longer baselines, incorrect ambiguities may pose as being correct in the statistical evaluations and it takes longer to isolate incorrect ambiguities.

 

4. Shorter baselines make it feasible to work in difficult areas (under tree canopy and in urban environments) because ambiguities have better contrast and are easier to resolve.

 

5. Beast Mode RTK is available only via our TRIUMPH-2 and TRIUMPH-1M base station. It makes ambiguity resolution up to 5 times faster because base station transmits base data 5 times per second. 5-Hz Beast Mode RTK is totally different from the up to 100-Hz RTK that is done by extrapolating the same 1-Hz data 100 times per second AFTER the ambiguities are fixed. This extrapolation technique does not improve the ambiguity resolution speed and is mainly used in applications like machine control after the ambiguities are fixed.

 

6. In addition to savings due to speed and reliability, it saves you RTN and communication charges. A complete system, Base + Rover + Radio + Controller & Controller Software, starts at $19,990. 0% financing available ($1,537.69 per month for 13 months) to active license US Professional Land Surveyors (PLS). Extended finance terms also available




July 13, 2022. Firmware Version 4.2.01 Release Notes November 21, 2021. Tracking S Signal of Navic system November 20, 2021. QZSS L1 C/B Signal is Being Tracked August 10, 2021. RTPK – White Paper October 13, 2020. We created our own Virtual 3D Booth August 3, 2020. TRIUMPH-LS PLUS August 1, 2020. The Next-Generation Program July 1, 2020. The Legacy of a GPS Pioneer July 2, 2020. All Available Signals Tracked July 3, 2020. RTPK July 4, 2020. TRIUMPH-3 July 5, 2020. J-Mate February 21, 2020. TRIUMPH-LS New Options October 29, 2019. J-Mate as the 7th RTK Engine August 19, 2019. Survey Product Training at INTERGEO 2019 November 16, 2018. Where Have You Been With Your TRIUMPH-LS Lately September 6, 2018. BeiDou AltBoc Signal is Being Tracked July 26, 2018. Spoofer Revealed June 18, 2018. J-Mate April 3, 2018. Special Event on Aerospace & Technology November 2, 2017. New Localization Videos October 3, 2017. TRIUMPH-F1 at INTERGEO 2017 September 6, 2017. Who Moved My Base? August 01, 2017. GNSS Review June 23, 2017. TRIUMPH-LS vs. R-10 June 8, 2017. TRIUMPH-LS Customer Reports April 11, 2017. Localization in J-Field February 21, 2017. TRIUMPH-LS and J-Field Hands Free Operation January 24, 2017. Don't take your gloves off! December 21, 2016. The Tallest GNSS Antenna Installation December 16, 2016. J-Pack & J-Tip in Use December 2, 2016. The Ultimate Land Survey Machine October 31, 2016. J-Pod October 27, 2016. J-Tip Users Manual September 26, 2016. The first Magnetic Object Finding Olympiad (MOFO) July 17, 2016. J-Tip May 11, 2016. Hybrid RTK with Javad J-Field May 4, 2016. Hybrid RTK March 1, 2016. Your thick trees and Our six RTK engines making friends! December 29, 2015. They all break your necks, TRIUMPH-LS does not! December 7, 2015. Remembering History November 14, 2015. Make more money and have fun too November 13, 2015. Advantages of short baselines October 23, 2015. MULTIPATH BUSTERS October 22, 2015. TRE-3 Successfully Tracks First Live TMBOC Signal October 19, 2015. Monitor and record the health of your shots October 03, 2015. Localizations September 16, 2015. Complete the Job with One Complete Tool August 31, 2015. Form Factor August 21, 2015. Clean UHF Channel August 14, 2015. BEAST RTK August 12, 2015. Collecting Points August 11, 2015. Auto Verify… Auto Validate… RTK August 10, 2015. Cluster Averaging August 9, 2015. Verification Video July 27, 2015. Good Support July 21, 2015. 180-pound Gorilla Test June 25, 2015. User Report on Multipath/Interference Test May 21, 2015. Introducing RAMS May 19, 2015. RTK V6+ April 30, 2015. Double Bubble April 29, 2015. TRIUMPH-2 Antenna Calibration April 28, 2015. Even in Heavy Canopy April 27, 2015. Field reports April 01, 2015. John Nailed It! March 30, 2015. IRNSS RTK positioning March 27, 2015. Beware of Scams March 15, 2015. Triumph-LS Precision and Localization March 03, 2015. How GPS and GLONASS got together February 27, 2015. Visual Stake Out February 20, 2015. VB-RTK December 09, 2014. Camera Features October 29, 2014. IRNSS positioning October 01, 2014. We track IRNSS September 04, 2014. JAVAD Users Forum August 19, 2014. JAVAD DPOS August 18, 2014. TRIUMPH-F1 August 15, 2014. TRIUMPH-LS & TRIUMPH-2 are now shipping August 14, 2014. RTK Confidence... Unlimited May 28, 2014. GPS/GLONASS Dispute May 08, 2014. Delta TRE-3 QZSS LEX released April 21, 2014. TRIUMPH-LS drop test February 12, 2014. JAVAD GNSS Webinar January 28, 2014. TRIUMPH-2 Scalable GPS January 15, 2014. 5 Talented PLS... September 20, 2013. We decode LEX data September 19, 2013. TRIUMPH 2 Chip May 13, 2013. Galileo Positioning January 25, 2013. BeiDou Positioning December 29, 2012. We track B3 signal from all Compass satellites December 28, 2012. We track LEX signal from QZSS satellite December 27, 2012. We track Galileo E6 B/C October 01, 2012. How to report Interferences? September 28, 2012. We track GAGAN L1 and L5 September 10, 2012. Javad's FCC filing September 09, 2012. J-Shield, Spectrum, Cycle-Slips August 16, 2012. J-Shield at ION Jule 03, 2012. Have you seen our software... lately? May 22, 2012. Using Visual Stakeout May 18, 2012. Where Were You in 1982? March 15, 2012. GPS C/N0 variations February 28, 2012. Javad's Comment to FCC January 30, 2012. Blindfolds off! January 24, 2012. GPS/LSQ Confusion December 28, 2011. My GNSS History December 14, 2011. Javad's Letter to FCC December 12, 2011. Galileo PRN 11 has been tracked! November 18, 2011. JAVAD presented at PNT October 28, 2011. JAVAD presents at PNT October 20, 2011. LightSquared is a Gem! October 03, 2011. Spread Spectrum Radio September 21, 2011. LightSquared Inside May 23, 2011. LightSquared Attacks May 15, 2011. Introducing GyrAnt+GPS receiver system April 21, 2011. Comparison of Multipath Errors on Different Receivers April 08, 2011. First from Javad and from Russia: GLONASS-K L3 CDMA March 25, 2011. TRIUMPH-VS tracks Galileo E5 altBOC signal March 03, 2011. Signal updates on Galileo GIOVE-B and Compass satellites February 04, 2011. JAVAD GNSS receivers can track Chinese Compass (Beidou-2) February 03, 2011. Introducing "Lift & Tilt" Survey October 29, 2010. All JAVAD GNSS receivers track QZSS Satellite and its New L1C signal October 20, 2010. TRIUMPH-VS shows interferences in all GNSS bands August 14, 2010. U.S. Geological Survey Awarded JAVAD GNSS up to $3.9M Contract. August 19, 2009. GPS SVN 49 and JAVAD GNSS Triumph Technologies August 18, 2009. JAVAD GNSS receivers tracked all current and future Galileo satillite signals August 11, 2009. Highest Score in Japanese CORS "GEONET" Selection Process July 24, 2009. JAVAD ArcPad Extension April 24, 2009. Our Customers Now Track GPS L5 Signal October 24, 2008. We tracked MBOC of Galileo GIOVE-B October 23, 2008. Stimulus Package for Surveyor`s Recovery July 29, 2008. 1st Annual JAVAD GNSS User Conference a Resounding Success April 10, 2008. Carlson Software Supports JAVAD GNSS March 14, 2008. Accepting Orders Starting on March 20, 2008 March 10, 2008. Fair Competition in the Global Village February 26, 2008. Javad: Staying connected with www.javad.com February 01, 2008. Javad: I Have Been Waiting for This... January 06, 2008. Javad: Supporting our old products... December 24, 2007. Javad: As we transition to the next generation of products... August 23, 2007. Javad Acquired ArWest Communications Corporation
Archived Products →