Looks like a bug

Nate The Surveyor

Well-Known Member
#1
20190304-15.05.12_00435_Processed_Point_Info.png
20190304-15.05.42_00435_Processed_Point_Info.png
20190304-15.06.15_00435_Processed_Point_Info.png

Now, here is the problem. I set up on Base 29. Autonomous. Then, I shot on POINT 4467, which is PREV base 5.
After using mlocal, everything is fine. AFTER dpos, it updates the position for the base, and moves it 0.08'. (See 3rd screen shot) IF I use 1local, (2nd photo) then, it moves it 12,000 in eastings and 2800 in northings. It should show the 0.088 Northing change, and 0.017 as shown on the 3rd screen shot. But, the 3rd one won't allow it to do that.
Ideas? It does have a localize in it.
Thanks
Nate
 

Ryan

New Member
#4
Yeah, I'm pretty sure this is a known issue. I think its processing and shifting your points because you setup on an autonomous base. That showed up as an issue for me because sometimes I am provided a coordinate from a client that I need to hold, if you process base and rover it will shift to the processed coordinates no matter what as far as I can tell. I dont have my receiver on now but there is an option in dpos settings to not process the base. If you do that it wont shift after dpos.
 

Nate The Surveyor

Well-Known Member
#7
Well, m-Local and 1Local are messed up. They won't work at all now. I don't have time to mess with it any more. I am going to hold the DPOS version, 0.09' from the proper M-Local position. I can either translate this in acad, or go jump in the lake. Where is me hat?
 

Vladimir Prasolov

Well-Known Member
5PLS
#8
Well, m-Local and 1Local are messed up. They won't work at all now. I don't have time to mess with it any more. I am going to hold the DPOS version, 0.09' from the proper M-Local position. I can either translate this in acad, or go jump in the lake. Where is me hat?
Hi Nate, I'm so sorry I cannot investigate the issue right now. I'm creating JIRA issue and I will look in it as soon as possible.
 
#11
Is this a problem everyone is having, or is this just me-specifically?
I have used this sequence before, no problem.
Set up autonomous.
Use m-local to adjust a few feet.
Perform work.
Go home. DPOS. This allows ppk base-rover processing.
Then, I can choose the DPOS, or m-local, for the source coord, for that day's work.
Thank you,
N
 
#12
Is this a problem everyone is having, or is this just me-specifically?
Either I'm doing something wrong or I'm seeing a similar problem.
I started the base with autonomous coordinate then applied Real-time Position Shift to move point 1001 (surveyed) to point 1 (design). I'm sure I checked that points 1 and 1001 had the same coordinates before proceeding. After DPOS, they no longer have the same coordinates.
Map on collect screen shows two different locations.
20190313-19.22.52_00229_3_COLLECT.png


Clicking on the orange Shift Details button shows that the shift is applied.
20190313-19.14.02_00229_Position_Shift.png


Inversing shows non-zero distance between them.
20190313-19.13.48_00229_Inverse.png


The base point page shows only AUTO and CORS. Shouldn't there also be a 1-Local?
20190313-19.14.46_00229_Processed_Point_Info.png


I sent project "Foundation" to support. LS Serial No. 229.