RTPK Real Time Processed Kinematic

Mark Wheeler

Active Member
I am running standard LS on Recommended software. I was going to update to pre-release this weekend and try this out. When I select update, J-Field 3.08.411, GNSS 3.7.9.200803 and Linux 4.4190.11 are available. Should we be updating all 3 and based on the previous comments should I be waiting until J-Field 3.08.411 is fixed (allowing option to turn PRTK off?
 

Nate The Surveyor

Well-Known Member
Just a thought. Since adding the white box, "RTPK", the RTPK processes simultaneously with rtk. So, in essence, we have 2 processors going at the same time.
Would it be productive for it to sound a chime, when RTPK, and rtk agree by some 0.05'? And, some sort of popup, before storing the shot, that tells the difference between the shots?
This means, shoot a point 3 x, gives you 6 shots!
Just thinking here. There's probably a better way than this, but it certainly seems that surveying will NEVER BE THE SAME!
Thanks,
Nate
 
When I go to updates I get "your unit is already updated" However, JField is 3.0.6.249, GNSS is 3.7.7.200408, & Linux is 4.4.190.4, should I be looking somewhere else for these updates? I want to try this complimentary RTPK.
Thanks for any input
 

Mark Wheeler

Active Member
I downloaded the pre-release and tried this with the State RTN. A message popped up occasionaly "One error has occured: can't create an arc". Not sure what that is about. With the Standard Ls: 4 Constellation, 2 and 6 engines, the progression was similar to Adam's video, except at the very end after processing the point an error message "Exception: Can't process vector" instead of an asteric and solution. I also noticed Bedoi was greyed out and could not be selected. Prior to the pre-release update I was getting Bedoi on the state network. Also, No matter what I select it seems to pick the best for both engines (now high numbers versus low number quality indicators).
I then tried it with the traditional GPS & Glonass V6 and it produced the RTPK points. Any setting that might help the 4 constellation "no vector" issue?
 

Shawn Billings

Shawn Billings
5PLS
When I go to updates I get "your unit is already updated" However, JField is 3.0.6.249, GNSS is 3.7.7.200408, & Linux is 4.4.190.4, should I be looking somewhere else for these updates? I want to try this complimentary RTPK.
Thanks for any input
You have to use pre-release
 

Michael Stazhkov

Developer
JAVAD GNSS
I downloaded the pre-release and tried this with the State RTN. A message popped up occasionaly "One error has occured: can't create an arc". Not sure what that is about. With the Standard Ls: 4 Constellation, 2 and 6 engines, the progression was similar to Adam's video, except at the very end after processing the point an error message "Exception: Can't process vector" instead of an asteric and solution. I also noticed Bedoi was greyed out and could not be selected. Prior to the pre-release update I was getting Bedoi on the state network. Also, No matter what I select it seems to pick the best for both engines (now high numbers versus low number quality indicators).
I then tried it with the traditional GPS & Glonass V6 and it produced the RTPK points. Any setting that might help the 4 constellation "no vector" issue?
Could you send the project to support?
 

Mark Wheeler

Active Member
Michael, I sent project "Testmsm4" to support. Easier than trimming it down and emailing to the wrong location. Ls 479, no note.
Mark Wheeler
 

Mark Wheeler

Active Member
Michael, A few other important issues since updating to latest pre-release 0.416 software.

1. The USB dongle drive is not recognized. This is my communication method used to transfer point files, etc. Help.
2. Tested a few scenarios yesterday:
a. LS V6 with T2 Base (GPS & Glonas) both with MAX RTCM3. (GPS & GLonas) and with i-MAX RTCM 3.x(MSM4) . Both worked fine and produced RTPK solutions for GPS/Glonas
b. LS with i-MAX RTCM 3.x(MSM4) using 4 constellation signal setup:
1. 4 Const 6 Engine: generated points, but did not utilize BDS (greyed out-unselectable). With Release version BDS was incorporated using the State RTN. Was unable to generate RTPK ("no vector message).
2. 4 Const 2 Engine: generated points but: did not utilize BDS (greyed out-unselectable). Engine 1 and Engine 2 selected/used the same exact sateyllytes no matter what selection choices I made or strategy checked (no redundancy). Was unable to generate RTPK ("no vector message). On the release version all 4 constellations were used and each engine had different groupings. It also appeared that when Auto Engine Setup was clicked, that it re-set up the sats used based on current conditions (that was what it appeared to do). A plus is that multi-constellation setups in the Pre-release did not get as bogged down as in the Release version.

In pre-release 0.416 multi-constellation, BDS was sometimes the "best" available, but unselectable.

Imediate concern is restoring communication with the USB drive.

Mark
 

Adam

Well-Known Member
5PLS
Mark, can you try a different USB drive? It is functioning properly on my LS which is on .416.
 

Mark Wheeler

Active Member
Adam, I just turned the LS on. A message popped up "out of space on USB Dongle. Please manage data to get more free space". The message was not true. I clicked mange data button, doing nothing else and the USB was recognized. Don't know how to explain it. Rebooted to check it and it functions correctly. Check that off my help list. The rest of the items are still not functioning.
Mark
 

Joe Paulin

Well-Known Member
So I tried RTPK yesterday for the first time. My setup is a standard LS with a T2 and UHF radio. My T2 is only GPS and GLONASS. It was really neat to see the RTPK work, however, for most of my canopy shots, my boundary profile of 180 seconds wasn't enough time for RTPK to provide a reliable solution. The solutions would come back as fixed but they weren't correct. So clearly more time is needed when just using 2 constellations. There were instances that the rtk solution would go through 180 seconds and pass verification and then it would process the static and come back with an incorrect solution. In this case, I didn't see how to resume the session, I would have to shoot another point. My DPOS timer is set for 5 minutes and that wasn't enough time either in some of my cases. I will need to set it for longer and experiment more. Normally if I am in a difficult area I would collect two 15 minute static shots for post processing later. I guess I still need that longer time frame using only GPS and GLONASS??

Still, what an incredible tool we have here!
 
Top