Trimble Business Center

I have been using TBC for years for GNSS processing, but my company recently acquired a Trimble C3 Total station, ahead of a project.

I have successfully acquired data with the equipment and taken the data into TBC for traverse processing, however the adjusted results from TBC are outrageously off. I know this because the same points have been surveyed with a Leica total station and computed using LISCAD. Also, the traverse has been computed using a third software.

The unadjusted coordinates on TBC are closer to the true values, but as soon as the traverse is adjusted on TBC, the values go haywire.

I do all initial setups (Project Settings) before bringing in the data.The Total Station Editor also shows the angles were logged crrectly.

One thing I notice in the TBC result is that it adjusts the coordinates of the first control point (which is the first Instrument Station). This  point is not supposed to be adjusted as I have input its coordinates and that of the first reference point (which are the two controls for the job), and tagged the coordinates as controls

If you want me to look at the problem you will have to provide me with the Data File from the Controller and the Project that you are working with (the VCE File or the Archive of the Project that will contain all of the Folders and associated files is better (Close the Project, then Go To File, Archive Project and it will create a ZIP of the project).

You can then either post the file here on the Forum or send it to me directly (alan_sharp@trimble.com) and I will either look at it myself or have one of my Geospatial Colleagues look at it for you as the C3 Total Station and the Software that you run it with (Likely Trimble Access) are not CEC Products (they come from Geospatial Division I believe) and they may need to look at the problem for you as they will be more familiar with how to set up Access etc to get the best results. If you are using SCS900 with the C3 and you did purchase it from a SITECH Dealer then let me know and I can for sure get you an answer as I know those products well.

I cannot hope to answer this type of problem without having the data to work with - apologies - I will await your data

Alan

The equipment was purchased from Geoverdict (Lordsfield)in Lagos , Nigeria.

I have attached the files.

Thanks for the data - that helped a lot to be able to answer your question

The problem was caused by the Software on  the C3 Total Station (I think it is Survey Pro On Board) that you are using, puts an extra Azimuth Record in each Station Setup and that is throwing the calculations off. I disabled those Azimuth observations and then created the Traverse and it processed all ok - however depending on what you have set for your Traverse Calculation Tolerances, you may Pass or Fail Tolerance now, but at least the Traverse Computes correctly using the approach shown in the video below

Hope this helps

Alan

Thanks for the reply Alan, I have successfully adjusted the traverse.

However, am still trying to find a way of observing without this unwanted Azimuth Record showing up. I would try changing a few settings in the instrument to see if this eliminates the unwanted Azimuth Record, but I wouldn't mind having some help with that from you, if possible.

Thanks a lot

I have put in a request to the Survey Pro Team for direction here - the

Geospatial Team thinks that there may be a newer version of the C# Total

Station Software that may address this issue if you install it - if you

could tell me what version you are running I can check that for you here.

The Survey Pro team will hopefully get back to me with some advice at some

point - I will post an update here when I hear something.

Sorry that I cannot answer this directly, these are not my products so I

dont know what is possible without a lot of work on my side - so I have to

rely on those that know the answers quickly - I will do what I can to help

and to get you an answer

Glad that we could get you moving at least

Alan

On Thu, Mar 7, 2019 at 3:12 AM adebisir@yahoo.com <trimble@jiveon.com>

Thanks for your assistance so far.

I would look out for any new information from you

Software: Pre-install version: 4.0.1.2

This is copied from the RAW data download, I believe it refers to the installed software version

"Yes, the field software version is 4..1.2 while the operating system version is 4.0.11"

This is a message from my distributor about the software version

i have seen these azimuth records using survey pro software as well. they occur when you observe an 'azimuth' for your backsight. there is a drop down to observe a 'point' or 'new point' or 'azimuth' when setting up your backsight. the azimuth record is created when measuring to a 'new point' or an 'azimuth' but not when you measure to a point. these days we mostly setup on two rtk hubs so have two points and then no 'azimuth' records show up in tbc. but every once in a while we setup on random points and the record is created and tbc will hold this record over any control points, unless there is a setting i have missed in tbc(that is how i stumble on this thread). so if there is a setting that we could change in the tbc template that would be helpful, thanks. 

but for adebisi, setting up on points will help you.