Something I have seen from time-to-time, and it drives me nuts, is that once in a while TBC won't perform an adjustment because "There are unconnected sub-nets in the network".
The only problem is, there aren't?! Everything starts from a known control point...
It's odd, I can have a couple of runs that start this way and everything processes fine, three is OK, four is OK, but once there's a fifth or so I start getting this message?
Sometimes it does it with only two...?
Hi Bill.
I have this same problem too. It's almost like TBC does not recognize the backsite as a shot and therefore doesn't think the networks are connected. Have you found a solution?
Trevor Leja, post: 454537, member: 13182 wrote: Hi Bill.
I have this same problem too. It's almost like TBC does not recognize the backsite as a shot and therefore doesn't think the networks are connected. Have you found a solution?
The only solution I've found is to back up and include additional data that links the sets. Either the original CORS or RTK job files.
FWIW, in my experience Star*Net doesn't have a problem with unconnected subnets. As long as each subnet comprises sufficient data to stand on its own, they'll all be adjusted without complaint.
Here is the problem as I remember it (I don't do adjustments in TBC other than a free adjustment to get better coordinates for processing)...the GPS adjustment in Trimble software (Trimnet, TGO, TBC, etc) has four auxiliary parameters turned on by default...scale, azimuth, and two rotations (deflections of the vertical). So, each network must have at least 2 H constraints and 3 V constraints. I keep these turned off. But, if you don't turn them off, then each sub net needs its own control. I have seen several instances of adjustments done by others that were linear projects and had pathological results due to the known elevations being in a line...that totally screws up the elevations of points located off of the line.
I remember a similar problem from way back when, some software does not like to backwords solve a network. check and see if there is a setting that can enable that option.
Paul in PA
Network Adjustment Error?ÿ
Error - There are unconnected sub-nets in the network.
This message should appear when there is a group of baselines connected and another group of baselines connected but no connection from group 1 to group 2.?ÿ?ÿTBC requires all the baselines to be connected.?ÿWhen this occurs on large data sets with multiple static sessions, in order?ÿto find where the disconnected data is?ÿTrimble Support recommends?ÿto start again and import each day??s data then process before adding the next. It may be more difficult to work with a merged data set that has multiple disconnected sub-nets then to work in smaller batches before merging. Also, with a large data set,?ÿthere may have been some baselines disabled so this may cause an isolated network to be hidden among the rest. Currently, there is no tool in TBC to locate the sub networks although there are requests from TBC community members to get this. Trimble Support is aware of this need.
i have the same problem with i cant adjust the network because of the same reaseon can any one help with that ,
raw data file more than 37 mb?ÿ can i uploaded here ?!
