I'm new to this version of survey pro, but I've managed to get my GPS base and rover setup on it and connected. The problem comes when I try to start survey and set the point number. It appears to convert the state plane coords to Lat long coords, but the it pops up a message about autonomous base and tries to resave my existing point as POINT#_GNSS. I believe it is trying to set an autonomous base instead of using the known coords. Any ideas?
Let it. Ours does the same thing. I believe it has to resolve its geo location with a "dummy" point. Why? I don't know...the older versions didn't.
If we have a control point and localize using that point number it comes out like this in the point file:
1,10000.000,10000.000,1000.00,cp
GNSS_1,10000.000,10000.000,1000.00,cp
I did that, but the point it stores has the wrong northing and easting and when I go to check a control point it's 10 feet off. I double checked my projection as well.
KJac, post: 353831, member: 8328 wrote: I did that, but the point it stores has the wrong northing and easting and when I go to check a control point it's 10 feet off. I double checked my projection as well.
I just asked one of my guys (you see how smart I am...) and I will tell you what he told me (although I don't understand it):
He said that will happen if you try and occupy a known control point (?!). He said he always sets a 'new' control point and then localizes to the other existing cps (you have to have three). Otherwise it does what you're describing.
That doesn't make sense to me, but that is apparently what we do here.
Kinda like Radar O'Reilly on M.A.S.H.....when the C.O. asks him "what am I signing?".... and Radar's reply was "you don't want to know, sir."
I don't want to know how they make it work...it sounds messed up...:pinch:
paden cash, post: 353838, member: 20 wrote: I don't want to know how they make it work...it sounds messed up...:pinch:
Haven't we always "made it work"?
I remember; when I was in the field; we always made it work. There was no way I was coming back in saying: I couldn't make it work.
Maybe this should go in Nate's thread about remembering....hahaha
I don't know if we're using the same version of SurveyPro (my last update was 2014); but I've had the same issue. Did you set your projection or just check it? Even though it is correct; I still have to set the projection before I start on a known point.
Like Paden said. Let it. The software is going to pare up your SP coordinate value for your control point with an autonomous lat/long creating a 'PNT#_GNSS' point. It's going to do that using the autonomous position it derives on the spot, giving you a warning if the SP value you're providing is outside of tolerances. It should hold that SP coordinate value you provided (as long as it's within tolerances). If this is a new point, then it will give you an SP based on the autonomous lat/long. The elevation of the point you provide for the control point has to be pretty close or it will blow up on you, not literally, but it won't allow you to get started. SOP, go hit a couple of your other control points to make sure nothing goofy is going on.
If your trying to get on to some existing control doing a quasi-resection off that existing control using the autonomous position, hit a few known points and inverse your autonomous derived positions to the known and then use the point and direction function to push a new point out from your autonomous position using the mean inverses and create a new point that matches with the existing. Kill the base and restart using the new point you just pushed out, creating a new '_GNSS' pare up. Whatever you do, do not translate that original autonomous base point or you'll be pulling your hair out trying to figure out how things suddenly just got so gobbed up.
Survey pro is a lot more user friendly than Access.
Have fun!
Williwaw, post: 353868, member: 7066 wrote: Like Paden said. Let it. The software is going to pare up your SP coordinate value for your control point with an autonomous lat/long creating a 'PNT#_GNSS' point. It's going to do that using the autonomous position it derives on the spot, giving you a warning if the SP value you're providing is outside of tolerances. It should hold that SP coordinate value you provided (as long as it's within tolerances). If this is a new point, then it will give you an SP based on the autonomous lat/long. The elevation of the point you provide for the control point has to be pretty close or it will blow up on you, not literally, but it won't allow you to get started. SOP, go hit a couple of your other control points to make sure nothing goofy is going on.
If your trying to get on to some existing control doing a quasi-resection off that existing control using the autonomous position, hit a few known points and inverse your autonomous derived positions to the known and then use the point and direction function to push a new point out from your autonomous position using the mean inverses and create a new point that matches with the existing. Kill the base and restart using the new point you just pushed out, creating a new '_GNSS' pare up. Whatever you do, do not translate that original autonomous base point or you'll be pulling your hair out trying to figure out how things suddenly just got so gobbed up.
Survey pro is a lot more user friendly than Access.
Have fun!
LOL nothing in that post sounds "user friendly" to me!! In Access I key in or import my control point, occupy it, and voila!! Done!!
Yeah it seems much more complicated now. In survey pro 4.7 all I did was pick a control point to occupy, connect my base and rover and that's it. I'm going to have to do a lot of tinkering with this new version it seems.
