Hey guys, I need some help ASAP. I have been encountering odd problems with the traverse routine on my TS15, by the way we are running version 5.05 and 5.00. We are starting our traverse on random coordinates, we are just entering a point ID with coordinates 5000,1000,100 Meters. We set up on our first station, go to the traverse app, set our orientation, then Fore Sight our next point, turning 6 sets. Once we set up on our FS, we are encountering BS checks up to 140mm. We are using Leica's Traverse Kit, like we have many times before and have never encountered any error over just our physical errors such as measured wrong, wrong prism whatever.
Of course we have tried this a dozen times checking all measurements, prisms offsets, coordinate systems, scale factors, everything we can think of. We have tried with/without the SD card on the gun and on the controller (CS15), we have tried using the ATR and sighting manually and every time we get an absurd error on our back sight.
This is where it gets funny. If we were to set our gun off to the side of these two points and just survey them in arbitrarily, and also survey in another point to check to, then we set the gun up on one of the points we surveyed in, go to "setup by known back sight" then try to check it checks fine. The problem we are running into occurs every time we try to occupy our first foresighted point. We have even tried updating the firmware.
Does anyone have any suggestions?
My suggestion.
Until you get this issue resolved, ditch the robotic/software routines and get back to basics.
1.) Measure your prism offset of all your prisms and verify the settings are correct in the DC. Three points....AB, BC, AC -> Offset = AC-(AB+BC)
2.) Verify where your PPM gets applied and that it is correctly set.
3.) Visit a calibrated baseline.
4.) Physically turn the angles and record your traverse measurements in a field book. Look at your angular closure (N-1*180). Check your linear closure.
Once you have figured out where your error lies, return to automated routines.
EDIT: I would use the simple measurement display (recording HA, VA, SD) rather than any of the software routines. I would verify if you need to apply the PPM to these measurements or if it has already been done.
Measure the distance to the backsight and calc a point in direction at the desired Azimuth with measured HD and Elev. Use the resultant coordinate as a BS with the known bs option.
Sorry if this is too obvious and you have already thought of it.
I have not traversed with Leica using anything other than Known BS or Helmert resection.
We've tried to start with known backsight as well, and when we originally setup in traverse routine we started off with a good backsight check. The problem keeps occurring once we occupy our first FS point. We have tried just going to regular setup and setting up with known backsight then just shooting another point, then moving there and using setup with known BS and it checks out. Like I said only in traverse app do we run into the problem... We are lost on what the issue is.
In Smartworks you can do you setup in one program/application and then continue to use that same setup in another. I would assume they did not change that feature in the Viva re-write. Give that a shot and see if it works.
> In Smartworks you can do you setup in one program/application and then continue to use that same setup in another. I would assume they did not change that feature in the Viva re-write. Give that a shot and see if it works.
Right, this we have tried as well and it still bust once we get to the foresight. We have called it quits on trying to get it to work as it is obviously malfunctioning. We ran the entire traverse with the vertical error and we are now in process of running a digital level through it to correct the vertical issue.
Thanks for all the help, I will try to post up what the issue is once it is figured out.
The error is in the vertical, I missed that. Are you sure you do not have an offset applied as continuous?
I totally missed that as well.
Maybe it was the metric units that threw me off.
