Where did you find this paragraph - It's not in the quick start link you posted.
Sorry, I mistakenly linked the User's Guide instead of the Quick Start Guide at http://www.javad.com/downloads/java.../Triumph-LS-Quick-Start-Guide-Spread-View.pdf
Where did you find this paragraph - It's not in the quick start link you posted.
Adam, can you describe how this is done, and how it can be overridden when the base is set up on a known point? Right now I use my LS to establish a point via RTN, then swap in the T2 and send the position from the LS to the T2. When I return on another day I use the base position previously established rather than getting a fresh RTN position for it.
Adam, can you describe how this is done, and how it can be overridden when the base is set up on a known point? Right now I use my LS to establish a point via RTN, then swap in the T2 and send the position from the LS to the T2. When I return on another day I use the base position previously established rather than getting a fresh RTN position for it.
I too am interested in this - are you using the Javad Mobile Tools app to collect the the RTN point and then set up the base and radio using the app?
Does the base have to be configured and started by the LS for DPOS to work? Of course at the end of the day one would stop the base and download the base file with the LS.
Yes, unless you use "Recover DPOS session" to manually create the DPOS session. This would make the process more complicated than it needs to be.
The downside to this is that the position will only be determined by a single epoch rather than an average of many epochs.
My shifts after DPOS are around .04 to .1 horizontally, vertical is usually less than .15 ft using this method. Plenty good for most of the rural boundary work I do.That's a significant downside. I think I'll stick with my current method, it's not onerous and I get to assess the quality of the base point prior to starting the base.
Data will still continue to be logged. You can view how many epochs have been collected with the GNSS Data Recording white box. You need to Accept the point for data to be saved.
OPUS does not offer processing of base-rover data like DPOS does. Longer baselines such as those with CORS to local base require longer observation times to get good solutions. Also OPUS is GPS only where DPOS is using GLONASS too.