We have had an issue arise with our Magnet software that you guys might be able to figure out. Today the software starting reporting that all points checked were 0.06' to high....Backsight or checks on stake out points. When we review the raw data the backsight checks fall almost flat. We ran the vertical collimation routine and checked the EDM mode (running in Fine mode)...and the problem persists. We are running a Topcon PS-105.
Any idea what is going on? Yesterday it was running fine and today it isn't.
Usually when there are problems with elevations in total station work a measure up is to blame. And do we really know that you are 0.06' high today, or were you 0.06' low the first time?
I remember someone else having a raw vs. stake-out data discrepancy with Magnet a while back. Maybe they'll see this and chime in cause it sounds like a cat that's already been skint.
And here he is.....
LOL...I thought it was covered here also, but that a GPS issue.
Mark- I thought the same thing....The crew to test this possibility staked a hub, stored the data, and wrote their cut on the stake. Then staked out the stored data and it told them to cut 0.06' to the point. Yet when we ran the RAW file everything looked fine with no indication of the 0.06'.
Mark is correct. This sounds more like human error, not software. So you are saying the software calculated the proper height one day, then several days later it is calculating it differently. Hmmmmm, not sure how that could happen. Show us the raw data for each.
What do you mean by " review the raw data the backsight checks fall" Have you tried to hand calc this to verify?
What version of software are you using?
Were you using the Topcon ATP1 or ATP2 prism with the and Topcon graduated prism with the correction spacer?
Did you verify this spacer was used for each measurement?
Was the same prism pole and prism used?
Lee,
When I have a few moments I will try to upload the RAW data. What I meant is the data collector showed the backsight vertical difference was 0.06' when compared to the coordinate data supplied in the backsight check routine. Yet when the observation is reviewed in raw format the vertical error was only 0.002'.
The exact same setup was used for all observations....including checking it on our office baseline (that showed the exact same results). We are using the ATP1 prism manually measured.....I do not think this is the cause as I noted above, we can store point data and then check the store data through the stake out routine and the 0.06' shows up with no changes to any setup data. I also don't think it is human as it showed up in the field and here at the office...with the identical error. I did have the PC reduce the raw data by hand and the calc's showed the vertical difference at the 0.002' as the raw data showed and not the 0.06' the backsight check showed.
We are using the latest version of magnet...4.1.2, Same prism and and prism pole for all observations. I did have the guys completely shut down the data collector and restart it to see if there was some oddity in the software, but the problem persisted after exercise. I also checked to see if the data collector was doing some weird grid reduction, but our settings are sent to ground so that shouldn't cause a problem.
I don't use Magnet, I use Survey Pro. But in Survey Pro there is a "Stakeout Offset by Distance" routine. You can stakeout a point offset by a distance relative to a defined line in the go/come, left/right, or up/down. If there is a similar routine in Magnet I'd check to see if there is a vertical offset of 0.06 set.
Terminus-NC, post: 404329, member: 11581 wrote: Lee,
When I have a few moments I will try to upload the RAW data. What I meant is the data collector showed the backsight vertical difference was 0.06' when compared to the coordinate data supplied in the backsight check routine. Yet when the observation is reviewed in raw format the vertical error was only 0.002'.
The exact same setup was used for all observations....including checking it on our office baseline (that showed the exact same results). We are using the ATP1 prism manually measured.....I do not think this is the cause as I noted above, we can store point data and then check the store data through the stake out routine and the 0.06' shows up with no changes to any setup data. I also don't think it is human as it showed up in the field and here at the office...with the identical error. I did have the PC reduce the raw data by hand and the calc's showed the vertical difference at the 0.002' as the raw data showed and not the 0.06' the backsight check showed.
We are using the latest version of magnet...4.1.2, Same prism and and prism pole for all observations. I did have the guys completely shut down the data collector and restart it to see if there was some oddity in the software, but the problem persisted after exercise. I also checked to see if the data collector was doing some weird grid reduction, but our settings are sent to ground so that shouldn't cause a problem.
https://surveyorconnect.com/community/members/terminus-nc.11581/&apos ;">Terminus-NC,
I see now. You are looking at the Basksight CHECK routine where the software calcs the HD error and VD error. This was a software bug back a few versions, was fixed, now appears broken again. I just ran a few test's with 4.2.1 in manual mode in offset, (-18å¡F outside w/ 2ft of snow) and I too see in consistent results in this computation by Topcon.
Best you can do is log a support ticket with your Topcon dealer, and also contact [USER=8922]@pmoran[/USER] Pat Moran works for Topcon/Sokkia and frequents this board.
Lee,
It is weird...all I could think is that it was something in the software. I have contacted my dealer who is sending a request to Topcon Tech support to figure our what is happening.
By any chance do you remember David Edwards...He works with me now, but grew up and surveyed in your neck of the woods?
Terminus-NC, post: 404352, member: 11581 wrote: Lee,
It is weird...all I could think is that it was something in the software. I have contacted my dealer who is sending a request to Topcon Tech support to figure our what is happening.
By any chance do you remember David Edwards...He works with me now, but grew up and surveyed in your neck of the woods?
Don't expect a fix on this from Topcon. Try to find a work around if you can.
Yes, I never met Dave Edwards. Spoke with him on the phone. Roscup and Edwards did work in my area 20 years agoor so.
That is him....worked with Jack. Small world.
Terminus-NC, post: 404356, member: 11581 wrote: That is him....worked with Jack. Small world.
I see Jack Roscup around, I think he works with local water authority.
Dave made a good choice heading south. Really difficult doing any survey work around here with this weather.
When he first saw your town...He said that it had to suck up there today.
Yes, it sure sucks if you're trying to work outside.
Lucky for me I'm in the office, editing machine control surface models for Universal Studios new water park (Volcano Bay) in Orlando, FL, along with some gas pipeline work in Jackson, MS.
Now I may need to do a site visit real soon ...........