Survey Pro Resection Problem

I'm not sure what to do other than reload the software.

David Livingstone, post: 436885, member: 431 wrote: I'm not sure what to do other than reload the software.

Tried that. No love.

Mark Mayer, post: 436887, member: 424 wrote: Tried that. No love.

Only a guess. Perhaps a portion of the circuit board or the processor that is used for least squares solutions has gone bad. Are there other functions on the data collector that would require least squares to be solved? If so, do those functions still work or do they fail also?

https://surveyorconnect.com/community/threads/explanation-of-closure-value-in-a-resection.331041/#post-433476

I have seen issues where a file goes bad and have no explanation as to why. Try starting a new job file and import the csv from the old file. A lot of times it will do the trick.

What version of survey Pro are you running? I believe the latest version is 6.1.0 .23

Sent from my XT1650 using Tapatalk

Assume tie translate rotate

sirveyr, post: 437019, member: 6680 wrote: What version of survey Pro are you running?

6.0.1.13

Try 6.1.1.19 I think that is the newest version. As a side note we ran t41s and now getac t800 and I have only seen 1 resection problem that was fixed when I shot the third point

Mark Mayer, post: 436883, member: 424 wrote: I routinely do resections using Survey Pro on a TSC3. But on Monday, without warning, the thing refused to solve the least square solution. We tried it wit ha differnt mix of control points. No luck. I tried it on a second site where I had resected several times before with the same result. I then tried it with another identical data collector (same gun, same control file) and the resection solved, no problem.

The recalcitrant dc seems to work fine other than this one problem. When the thing refused to solve the resection we completed our work by occupying control and turning out from there. Everything checked fine.

I figure maybe there is a corrupted seed file in the "bad" dc. But I don't know which one. Have any of you encountered this? Do you have a solution?

Were any of the points you are using computed from COGO in Survey Pro, such as by distance-distance intersection? If they were, and you staked them out, and then tried to do a resection from them, it might not solve. Here is why.... For some unknown reason when my version of Survey Pro on the TSC2 computes the coords of the result of a COGO dist-dist computation, it does not set the elevation value to 0.0000. It sets it to a very huge negative number like 1 E-27 or maybe a huge number 1 E 27. When export that as an ascii file you will see it clearly. When I import it into Carlson, Carlson won't even plot it when I draw points. If the vertical is a not zero, or if it is is in outer space, it might be messing up your resection calculations because the vertical distance is enough to be too far away. Seems like for all we pay for this equipment that the software writers could get this right.