I set up on a point forming almost a perfect triangle with two other known points.
After any number of D&R observations, clicking "Calculate" produces nothing but "Type: No Solution".
What am I missing? Ideas?
Maybe exit the software and reboot the collector?
> Maybe exit the software and reboot the collector?
I'll try that. If the standard errors are set to tight, might that cause that message? That is, it can't find a solution within those tolerances?
> I set up on a point forming almost a perfect triangle with two other known points.
> After any number of D&R observations, clicking "Calculate" produces nothing but "Type: No Solution".
> What am I missing? Ideas?
So, did you measure distances to the other two known points as well as the directions to them?
I have the same question as Kent...
> So, did you measure distances to the other two known points as well as the directions to them?
Yes, I did. I did the math "long hand", and it almost closes:
1 to 500 = S36-25-44W 273.15'
500 to 102 = N10-38-16E 297.45'
102 to 1 = S55-55-34E 129.53
Both points 1 and 102 are in the file. Resection should work in the software, but just doesn't. I feel like dumping SurvCE and trying something else, but I know that would be misplacing the fault. I'm beginning to feel though, like I was better off with my field book and HP calculator.
> > So, did you measure distances to the other two known points as well as the directions to them?
>
> Yes, I did. I did the math "long hand", and it almost closes:
>
> 1 to 500 = S36-25-44W 273.15'
> 500 to 102 = N10-38-16E 297.45'
> 102 to 1 = S55-55-34E 129.53
>
> Both points 1 and 102 are in the file. Resection should work in the software, but just doesn't.
So, just to be clear, you set up on an unknown control point that you called No.500 (and which point number was not already in use in the database) and you took directions face left and face right to control points 1 and 102? Did you rezero the instrument when you changed face or do anything else that would cause the angle measurement to go haywire?
Presumably, you have the data collector configured to expect resection measurements to be done in a certain way. My guess would be that you departed from the configuration settings, but this is just a guess.
> So, just to be clear, you set up on an unknown control point that you called No.500 (and which point number was not already in use in the database) and you took directions face left and face right to control points 1 and 102?
It probably was. I continued the job file I used yesterday. I can't remember though, whether I went to "Survey, Store Points" first, and TOLD it I was on 500, or right to "Resection", wherein it doesn't ask where you are at all...it just requests the points you're going to sight to. After resection though, it's supposed to ask if you want to save the point. If I happened to put a point in that was already there, I presume it would ask me if I wanted to "save raw data", or use another point.
>Did you rezero the instrument when you changed face or do anything else that would cause the angle measurement to go haywire?
First time I tried it, it asked me at the beginning if I wanted to re-zero. I said yes. Never did it between D/R though. Second time, I chose not to.
>
> Presumably, you have the data collector configured to expect resection measurements to be done in a certain way. My guess would be that you departed from the configuration settings, but this is just a guess.
The choices in configuration are to do angles only (which I didn't), and ignore Z (which I didn't). Not sure what to think. It just didn't go the way the manual has it going.
The resection program is telling you that something is amiss. I have used the routine and it does work though it can be a little hard to figure out. I would try to just use 1 measurement to each and see if that works, if it does, then its a procedural thing.
In my experience that message occurs when the wrong stored coordinate is selected or the values are entered/computed wrong.
Double/triple check your #s.
> In my experience that message occurs when the wrong stored coordinate is selected or the values are entered/computed wrong.
>
> Double/triple check your #s.
That sounds like it might be it. I was weeding out my points and I found several which were supposed to be the "same" points, but which had different coordinates. I'll take another close look. Thanks!
What version of SurvCE are you using?
The last version of 2.5xxx was so filled with bugs that you were essentially forced to upgrade to 3.0...and it was bug filled...so forced to 4.0
I really like Carlson, but that was a tough road...
Anyway, resection does not work properly in some builds of SurvCE, in my experience. The Customer Service people always acted like it was my bad, but I have used that routine a lot, and it was just not working correctly in some instances.
What version are you using?
What version of SurvCE are you using?
> The last version of 2.5xxx was so filled with bugs that you were essentially forced to upgrade to 3.0...and it was bug filled...so forced to 4.0
>
> I really like Carlson, but that was a tough road...
>
> Anyway, resection does not work properly in some builds of SurvCE, in my experience. The Customer Service people always acted like it was my bad, but I have used that routine a lot, and it was just not working correctly in some instances.
>
>
> What version are you using?
Version 2.07. Based on your comments, I'd guess 2.0x would be even worse than 2.5xx, lol. I'd be thrilled to learn though, that in this small, limited case it IS the crappy software, and not the incompetent user.:-D
Perhaps this weekend to prove it (or not), I'll do the exact same resection using my demo version of Topcon Magnet Field and see what I get.
What version of SurvCE are you using?
My first experience was with 2.5xxx.
2.5 represents a major upgrade.
I actually like SurvCE. The knowledge base (on line) is very useful.