Since 3.0.10.402:
- RTPK 3.0 (additional checks of a fixed solution validity, improved performance)
- RTPK 3.0 (additional checks of a fixed solution validity, improved performance)
PreRelease 3.0.10.409
- Thread starter Michael Stazhkov
- Start date
Nate The Surveyor
Well-Known Member
Does this apply to T-2 LS folks too, or does it only apply to T-3 LS+ Folks?
(Many T2 folks still out here!)
Thanks
N
(Many T2 folks still out here!)
Thanks
N
RTPK works with both the LS and LS+ and uses whatever signals the base is transmitting, the more signals, the better.
The RTPK 3.0 engines does the following to validate the solution. The raw data is divided into 2 minute sections and processed in sections. The coordinates from each section are compared to check if they agree. If there are 2 sections that agree then the solutions are averaged and a result is returned, otherwise processing is marked as failed and a result is not provided. If there is less than 2 minutes of data then the data is divided in half.
Note that I have found a bug in this version: The issue is if initially a point is processed with a short duration of data and yields a fixed result but then it is reprocessed with more data and fails, the previous fixed result is not deleted.
Note that I have found a bug in this version: The issue is if initially a point is processed with a short duration of data and yields a fixed result but then it is reprocessed with more data and fails, the previous fixed result is not deleted.
Sean Joyce
Well-Known Member
Nate The Surveyor
Well-Known Member
Yes, please tell us... I upgraded before the memo from Matt Johnson.
I may go backwards, to user version...
N
I may go backwards, to user version...
N
No, when it is fixed there will be a different version with a new version number.
Nate The Surveyor
Well-Known Member
Ok, I've gone one step back. To the latest user version. (Rodeo avoidance maneuver).
Thank you for the heads up / warning, @Matt Johnson
Nate
Thank you for the heads up / warning, @Matt Johnson
Nate
Darren Clemons
Well-Known Member
Has .413 pre release update fixed this bug?
In this version a message is displayed if a solution can't be produced and in the case when a previous solution was obtained and reprocessing with more details results in no solution, the previous solution is deleted as should be the case.
Sean Joyce
Well-Known Member
running .413 and getting this message all day never seen before, , (no solution for this vector) RTPK results even in open area not good,
only seemed to have 5 engines in good conditions all day. anyone else have this issue?
only seemed to have 5 engines in good conditions all day. anyone else have this issue?
Could you send the project to support (Projects screen -> "Send Project to Support" button).
Sean Joyce
Well-Known Member
Done but my internet is slow so will be awhile project is JS2101 AMEY
Trouble started using base 212 on the 27th.
Trouble started using base 212 on the 27th.
Last edited:
I wonder if clearing NVRAM on the base would help. With only 5 engines fixed, it sounds like you might not have all of the signals in your corrections.
Sean Joyce
Well-Known Member
That occurred to me too, I had done it the day before but after the update I should have done it again.
Nate The Surveyor
Well-Known Member
Any further information yet?
Thx,
N
Thx,
N
Sean Joyce
Well-Known Member
How are 2D Delta and Delta H on your base setup?
Sean Joyce
Well-Known Member
2D 0.31
DH 0.12
Your question brought up another issue. This is the 3rd base setup on this point. Up until recently I had it set to capture the screenshot when the base was started.
for some reason it does not do that anymore so I happened to capture this base setup manually.
somewhere a setting has been changed and can't find how to change it back.
Looked in Action profile and it is set to capture screen shots.