You sent the project to support. Can you share a link to the project archive so one of the 5PLS team members can try and open it and see if we can help?
I'm a little confused about the full sequencing in DPOS
- Thread starter Nate The Surveyor
- Start date
Mark Wheeler
Active Member
Nate, M-Local crashes my LS every time also. I figured I was my first try (multiple).
Mark
Hi Nate,
We are looking into the issue. Unfortunately I did not find the job. Please could you send exported project through this forum.
Hi Nate, Something goes wrong with the project you send. Try to send to support again.
Reed222-191029 15_36_22.zip
Nate The Surveyor
Well-Known Member
Thank you Shawn. Base17 is the last one, that just won't move.
When using the DPOS review screen (DPOS>then the little button in the upper right corner) (same thing is available from the POINTS screen).
EXPECTED behavior and appearance of the BASE points, should be DIFFERENT than the Sideshots review.
SIDESHOTS should allow RTK, or PPK, and the 0-Local column should simply say what the BASE source is. Base source could be M-Mocal, or Autonomous, or Cors Fixed. And could show the BASE SOURCE, in text, such as "Base source is M-Local" or "Base source is DPOS CORS", but beyond that, it should NOT be active, when viewing sideshots.
Nate
When using the DPOS review screen (DPOS>then the little button in the upper right corner) (same thing is available from the POINTS screen).
EXPECTED behavior and appearance of the BASE points, should be DIFFERENT than the Sideshots review.
SIDESHOTS should allow RTK, or PPK, and the 0-Local column should simply say what the BASE source is. Base source could be M-Mocal, or Autonomous, or Cors Fixed. And could show the BASE SOURCE, in text, such as "Base source is M-Local" or "Base source is DPOS CORS", but beyond that, it should NOT be active, when viewing sideshots.
Nate
Last edited:
Nate The Surveyor
Well-Known Member
Hello? Was my file ever fixed?
Yes, the issue has been resolved in development/testing version. It was related to long time processing. I hope to include the fix into upcoming release.
Nate The Surveyor
Well-Known Member
Long time processing?
As in long DPOS session?
Or, ?
Thanks.
Nate
As in long DPOS session?
Or, ?
Thanks.
Nate
Maybe processing time is slow for some internal reason...
It is updating a lot of coordinates in trajectories and so on. It takes time. We will try optimize that later.
Nate The Surveyor
Well-Known Member
It was not locked up. It was just taking more time than I thought it needed?
Yes, new version will work, but very slowly due to huge trajectories. For now you can separate trajectories by projects and process them independently as best as you can.