I don't have the unit in front of me, but we've got rented out in the field a Trimble R8 model 3 with a TSC3 connected to a myfi device.
The problem is when we start the survey, it doesn't want to store vectors, only the positions.
We've asked the place we rented it from and they don't know how to fix it.
Has anyone got an answer?
What kind of network are you on? If it's a Trimble VRS network then you have to go to the Settings menu > Survey Styles; pick the survey style that you use for VRS. Go to Rover Options and change Store Points As from Positions to Vectors.
Lee D, post: 325230, member: 7971 wrote: What kind of network are you on? If it's a Trimble VRS network then you have to go to the Settings menu > Survey Styles; pick the survey style that you use for VRS. Go to Rover Options and change Store Points As from Positions to Vectors.
I'm just curious, but what are the advantages to storing the vectors in a VRS survey?
guyinstreetwithcamera, post: 325241, member: 10149 wrote: I'm just curious, but what are the advantages to storing the vectors in a VRS survey?
Storing vectors in a VRS survey lets you incorporate the measurement data in an adjustment. So instead of just a coordinate list, you have a usable vector to incorporate into your network. It stores a vector to the nearest base with whichever QC data combo you have selected.
guyinstreetwithcamera, post: 325241, member: 10149 wrote: I'm just curious, but what are the advantages to storing the vectors in a VRS survey?
I don't trust GPS any farther than I can throw it. I've gotten enough bad data over the years to never trust anything without the vectors.
Tommy Young, post: 325257, member: 703 wrote: I don't trust GPS any farther than I can throw it. I've gotten enough bad data over the years to never trust anything without the vectors.
My understanding is that in a VRS survey, a virtual base is created at your initial position, then corrections are sent out from this "virtual" base to your rover. Then wouldn't the vectors be to a base point that only exists virtually? I don't see how that does any good, since your next VRS login will have a different virtual base with no correlation.
guyinstreetwithcamera, post: 325327, member: 10149 wrote: My understanding is that in a VRS survey, a virtual base is created at your initial position, then corrections are sent out from this "virtual" base to your rover. Then wouldn't the vectors be to a base point that only exists virtually? I don't see how that does any good, since your next VRS login will have a different virtual base with no correlation.
Depending on which broadcast format is used, the vectors are stored either as from the "virtual base" or from a physical CORS. CMR+ I believe always stores it from a physical CORS, although it may give it a made-up name like PRSxxx... But, RTCM3.0 stores it from the virtual base, at least in Trimble Survey Controller and Access. The problem with that is if you are moving around, it may duplicate the name. For example, it may use RTCM0103 on different days fir different virtual points.
I have learned to use CMR+ whenever possible to avoid the above problem.
That's quite interesting. I would have guessed the broadcast base location would be the same regardless of the language. I'm guessing someone at Trimble realized the validity of vectors to known CORS over the near uselessness of vectors to virtual bases.
guyinstreetwithcamera, post: 325340, member: 10149 wrote: That's quite interesting. I would have guessed the broadcast base location would be the same regardless of the language. I'm guessing someone at Trimble realized the validity of vectors to known CORS over the near uselessness of vectors to virtual bases.
I believe it still uses the virtual base (advantage=short line, network solution using surrounding stations) for the solution, but stores it as a vector from a CORS. I always adjust the data, often combined with static baselines, or conventional data, so being able to do that is a plus.
The VRS does use the virtual base, that's the whole point. When I first tested it, however many years ago the Louisiana Gulfnet came online, the virtual base position was displayed if you were using CMR. But Trimble fairly quickly changed it so that it referenced a CORS station. My understanding was that the reason they did so was that vector components to a physical CORS are repeatable and verifiable. But those vector components are calculated and stored after the rover's position has been determined from the VRS.
I've never used RTCM with VRS; there's simply no reason to when running Trimble rovers on a Trimble network.
