We are having problems adjusting a closed traverse on Trimble Access.
We do not have Trimble Business Center, and have no problems with the adjustment on SurveyPro.
Here's what we have tried:
- Setup 102, BS 101.
- Measure rounds 101-103.
- Setup 103, BS 102.
- Measure rounds 102-104.
- Setup 104, BS 103.
- Measure rounds 103-101.
- Setup 101, BS 104.
- Measure rounds 104-102.
- The closing angle should be 104-101-102.
- Traverse, start station 102.
- Traverse path 102-103-104,101-102.
- Start station backsight 101.
- End station foresight 103.
- Adjust.
I don't think that is correct because the closing angle isn't what it should be. But if I use the end station as 101, then the traverse length is short one leg.
Using the traverse path 101-102-103-104-101 gives the correct traverse length but similar results.
We did an experiment around the office last weekend and ran it conventionally with surveyPro and robotic with Trimble Access. The surveyPro closure was 1:60000 and Access was 1:30000, despite having virtually identical angles and distances.
We are missing something but I can't figure out what it is.
Any help would be greatly appreciated.
That is a simple traverse, when you run it longhand what's the closure?
There isn't enough info to tell you what is going on, if I had to guess I might guess that there is a setting adjusting the angles after the imput but before the calculation of closure for one program and for the other program it's not turned on.?ÿ
Just a guess,,,,,,,,,,, probably the 1 in 60 is the one that doesn't adjust the angles first, only uses raw numbers to get the closure.?ÿ
1 in 30 over 1000' is .03' in 100,000' we are looking at some real numbers. Scale means something when discussing traverses.?ÿ
could you upload an RW5 file so it can be adjusted in StarNet?
If you don't have the stylesheet for Access, download it here:
http://trl.trimble.com/dscgi/ds.py/Get/File-394365/TDS%20RW5%20file.zip
It goes into the Trimble DataSystem Files folder on the Trimble Controller.?ÿ That allows you to Custom Export to a TDS RW5 file which can be easily converted to the StarNet DAT format.
By hand, I get 1:55587.
I'm looking for the correct way to do it in Trimble Access.
I can look at the raw data in the office, but it appears that I can't upload it here.
Either way, we are looking for a field solution. Thanks to these replies, I have been able to work out that I am not getting the result I am looking for from the Trimble Access software. I must be doing something wrong on the collector.
What comes to mind is maybe the instrument is/isn't applying a check and adjust in either software. If I remember correctly the Leica 1200 series stored the C&A on the pcmcia card, for the last adjustment. ?ÿ
So I know you can't do this with a Trimble instrument, cause there is no screen, but if you were to (probably too late now) compare the screen angle readout to the dc readout, and maybe look over the directs and reverses in the raw file to see if the mean agrees.
I'm just guessing here.
Without knowing any real details of what you did, I just went into my emulator and recreated your process using simple 90 degree angles and 100' distances on each leg. The first thing is, when you key in point 102 it has to have Control Point checked. If you imported it, you can pull it up in Key In Points and check Control as well. Then when you go to Traverse in COGO, you put in 102 as the start station. When you hit Add it should ask you if the next point is 101 or 103; after you select 103 keep hitting Add until it comes back to 102 (your closing point is 102, not 103). Then hit Adjust.
Thank you! I will try it again with 102 as a control point.
I should also clarify - 102 is your End Station; 103 is your Foresight and 101 is your Backsight.
An RW5 is a text file, you can just copy the text & paste it directly into the thread.
