I updated my trimble r10, and copied over my old template that was always set right. Everything on my normal startup screen was normal but when i got back to the office I didn't have a .to2 file. I went and checked and in the setting the base was set to rtk and not rtk + logging. Is there any way to rescue these points and have them be correct?
You did some points PPK?
Not sure to be honest. Usually my here survey gets corrected by several feet. Wouldn’t I assume the current data is the same several feet off since no correction has taken place?
I would say no. If it was set to RTK only, then no base data file was created. I always start the R10 as a base using my phone or laptop connected by wifi. No data collector needed at the base.?ÿ
Not sure how updating the R10 would change the setting in the data collector...the survey style should always be the same, unless you mean you updated the data collector? I believe that even if you have the R10 set to automatically log data, if you use a DC to start the base and have the survey style set to RTK only it will override the setting in the R10 and shut down the base data collection.?ÿ
I wish Trimble would default to always log data at the base, I know a lot of people never do that, not sure why you would NOT want to do that even if you don't always use it. At least you could send the base file to OPUS or RTX as a check on the base position and HI?ÿ
To answer your question, connect to the receiver over wifi and you can see and download any files stored on the base
If you don't have the static data from the base, you're not going to be able to correct its position without returning to the site. If there are no T02/T04 files with data for that date in the base, there are no data.
Go back to to the control point your base was set up on, run a static session, post process (OPUS/TBC/whatever you desire), and then enter the corrected values as a control class coordinate for your RTK base in your TBC project. Recompute and your RTK data will be updated.
Did i read that last part right where there is a way to salvage my rover shots (8 hours worth) if I go and do another here survey, only? or do I have to redo all my rover shots too during that time period I thought the base was logging.
No, just occupy the base point, don't hit here, don't run a rtk survey, just collect static data, you don't even need a data collector. If you do use a data collector just do a fast static observation
Then process that data or send to OPUS or RTX and use the coordinate as the base coordinate.?ÿ
I should add this will work if you have the RTK vectors, I know some people don't even use the job file, they just download a csv file with coordinates. Strange but true
Yes, I agree with John and Rover.
PPK points are points collected at the rover that need the .To2 file from the base and rover to process, if you had collected some with the rover, then there would be no way to process them to the base since there is no static file at the base. If you are setting on a here point at the base without having the base collect data you could possible fix it if the rover was collecting some data.?ÿ
I would make sure the rover isn't logging data, if it is, there is an outside possiblility that you can put good coordinates on some rover points and back in the base position. I doubt it, but you should check to be sure the rover doesn't have processable files in it.?ÿ
Otherwise, do as suggested and collect static data at the base.?ÿ
You want the base point to have good coordinates, on the other hand you need to be sure that it's important for this job. I hate having a here control point, but if it's for a one off lot survey, it may not be all that important to spend the time "fixing" it.?ÿ
Also, check to see where the static files are intended to be collected. You have a choice of collecting in the receiver (preferred for the base) or in the collector (preferred for the rover). Do this in the survey style menu.
When you pick up the base at the end of the work session, if you want to have static files collected be sure to shut down the survey (not the receiver), then go to receiver files menu and transfer the day's base file to the collector. This takes only a few minutes and it is much easier to download into TBC than plugging in the R-10 or bluetoothing it to the computer. You will know immediately that there is or isn't a file available at the base before leaving a job. If it wasn't collecting you can sit for 10-15 minutes and get enough data to process to a nearby CORS. I know this cause I've lived the same mistakes, changing equipment and having similar issues crop up.?ÿ
?ÿ
With the processor speed and amount of storage in today's receivers and collectors, there's no reason to not run all RTK survey styles as "RTK + Logging" or store vectors rather than positions.
Then again, I have seen several outfits around here, run by alleged professionals, that do nothing but CSV exports from the controller, in all circumstances...
If all your rover shots are RTK then you can definitely recompute them.
If some of your rover shots are PPK then those have to be redone.
I suggest your return to the site, setup your base, connect to it as a base with your controller, run a faststatic base survey for as many minutes or hours as necessary to get enough data to get a good position from OPUS or CORS or other control.?ÿ If you need to re-shoot PPK points then you will need to start the base as RTK base+logging and do your PPK shots.
@moosesamuel
I'm trying to remember the sequence of events that cascaded down through the Trimble receivers. As I recall one of them automatically collected data as it was turned on. That was an issue for some because it filled up the memory faster than they wanted. I liked it, I used them as static control receivers back then on many projects so it was just a matter of setting them up and letting them process. Trimble listened to complaints and did some receivers that would collect on their own if you pressed a button on the front of the machine,
These days I control everything with the DC and survey styles, you have to be careful and walk through the survey style set-up and make sure it's how you want it to be.
I have probably a dozen survey styles in my DC depending on the task and the receivers.