Up to now I have used the R10 I purchased in December as a base, and have sent corrections over both the cell modem and the radio. No problem.
Now I want to use it as a rover on a VRS. I am running access on a Yuma 2 tablet. I can get it to work connecting over the modem in the Yuma 2. I can also get the R10 to connect directly to the VRS over its internal GSM modem. What I cannot seem to find is how to tell access to just use the corrections that are coming in on the R10. Well, I know the corrections are applied in the receiver, not the data collector. But the various styles all seem to want a connection.
This is probably a simple configuration, I just can't seem to find the right page. I did just download the help files for access (which I have never used before now, I have always used survey controller), so I will read through them and see if it explains it.
The reason I want this option is because the R10 is AT&T, and the tablet is verizon. So that will give me more connection options. In WV, for example, AT&T has much better coverage than verizon in a lot of places.
I haven't been able to figure out how to do it, but there are some people I can ask who should know for sure.
What I'm hearing is that the internal modem is designed primarily for use as a hotspot, base, or NTRP caster. No one has been able to tell me how it can be used for rover corrections.
I have gotten this to work a few months ago, and have some direction for you. Go to internet setup in trimble access. Under 'mobile internet connection' select new/edit. Go through the steps to set up the SIM card installed in the R10. We use AT&T and I remember using 'w/acceleration' or something similar setting to get it to work. After its set up and connected, start your RTN survey style and it should be all good.
If you have a SIM card activated on your TSC3 this may cause conflicts. You may need to turn it off before attempting to connect with the R10.
Seems kind of dumb not to have that as an easy to use option. I will give that a try.
R10 Ntrip-UPDATE
It occurred to me that since all of the RTK action goes on in the receiver, not the data collector, this should work. At least with trimble, the RTK engine is in the receiver. The data collector is just used to control it and maybe receive the corrections and forward them to the receiver. So in this case I just wanted the receiver to directly receive the corrections over the cell connection on the internal sim card.
I didn't actually try to do this again until last night after dinner. I setup one of the Ntrip client on the R10 options to our VRS login, and enabled it. Connected right up. Looking at the position screen, it was showing RTK fixed. So, I connected the yuma 2, and it worked right away, showed RTK fixed, and was able to do the regular survey styles.
I didn't really do anything different, so it turned out to be pretty easy.
Here is a plot of the horizontal. You can see the time I turned on the Ntrip client where the difference went way down to almost zero (from the reference position). When the NTRIP RTK connection was not on, WAAS was on, that is why it is about 1 meter off and varying.
R10 Ntrip-UPDATE
:good:
