The UHF folks, via T3, and LS+

Nate The Surveyor

Well-Known Member
OK, I did the maiden voyage today. It worked.... Pretty good. I had it set to 2 seconds rate on the radio. Internally, the T3 stores at 1 second rate, for post process RTPK.
Now, the LS was jumping back and forth... 29+1 to 9+7
So, I ask, I am going to need a solution to make this thing optimized, for UHF.
I also plan to try again to move over to Cellular corrections. But, that is not going to work all the time, out here in the sticks.
Also....
RTPK, runs awful good at the 10" cycle, even in the deep woods. Until it has been there for while, and then it does not have time to finish a RTPK cycle.
What we need is the ability to run at odd cycle times, like 15", 20", 25" etc.
Maybe just the ability to just key in a value. Maybe we can look at the number of sats, (29+3) and the density of the foliage overhead, and pick a number.... Hmmmm 18" for this area.... etc.
Anyway, it is MUCH improved. Even with the JUMPING around.
Thanks
Nate
 

Nate The Surveyor

Well-Known Member
20250927-13.08.55_00435_RTPK_Usage.png
20250927-13.09.01_00435_RTPK_Environment_Category.png


Thank you Phillip. I cannot seem to find anything more than 10 Seconds, 30 Seconds, 1 minute, 90 Seconds, and 2 minutes.
Would you mind showing where to set it to those intermediate times?
Also, it would be good if I had a way to set the Satellites to the best settings for UHF, 2 second intervals, and maybe upsampling, etc. So that I can maximize the functionality
for UHF corrections.
 

Matt Johnson

Well-Known Member
5PLS
JAVAD GNSS
I cannot seem to find anything more than 10 Seconds, 30 Seconds, 1 minute, 90 Seconds, and 2 minutes
If you click on the interval you can change it to any of these values but I would not recommend setting it to less than 1 minute when you are under tree canopy.

CASE-EDITOR_20250927-15.27.58.png


Now, the LS was jumping back and forth... 29+1 to 9+7
So, I ask, I am going to need a solution to make this thing optimized, for UHF.
The RTK engine configuration should remain the same rather you have corrections from UHF or cellular. The communication channel is not the problem. The satellite count is jumping back and forth because the receive is switching between a RTK and code float solution when you have the RTK rate set to 5 Hz and there are more than 20 satellites being used in the RTK solution. The processor is not able to keep up with the RTK rate and it causes this behavior. If you want, change the RTK rate to 2 Hz and it will not do this.
 

Michael

Active Member
John or Matt. Satellites are not jumping as much with the latest Pre-release installed. My RTK rate in the RTK/DGPS Settings screen is 0.02 sec. Is this the 2 Hz rate that you talk about? And also should the Data Upsampling be unchecked. Thank you guys for the hard work. Mike
 

Matt Johnson

Well-Known Member
5PLS
JAVAD GNSS
So basically I should have the 2 Hz setup for better performance?
You won't have better performance with 2 Hz, it will just prevent the satellite count from jumping up and down on the action screen. I'm hoping a 4 Hz rate can be added in the future which should be more compatible with the new RTK engine configuration.
 

John Rosco

Administrator
JAVAD GNSS
John or Matt. Satellites are not jumping as much with the latest Pre-release installed. My RTK rate in the RTK/DGPS Settings screen is 0.02 sec. Is this the 2 Hz rate that you talk about? And also should the Data Upsampling be unchecked. Thank you guys for the hard work. Mike
0.5 sec interval is 2Hz 'Upsampling' of the 'base' RTK RTCM correction rate . . .
To use the 2Hz Rate, 'Data Upsampling' needs to be 'checked' . . .

1760896415716.png
 
Last edited:

Matt Johnson

Well-Known Member
5PLS
JAVAD GNSS
A faster RTK should allow the receiver to fix faster but I don't think you will notice much difference in performance with the new profiles between a 2 and 5 Hz RTK rate. The issue that causes the satellite count to jump does any cause any harm to the RTK performance from what I have seen.
 

John Rosco

Administrator
JAVAD GNSS
A faster RTK should allow the receiver to fix faster but I don't think you will notice much difference in performance with the new profiles between a 2 and 5 Hz RTK rate. The issue that causes the satellite count to jump does any cause any harm to the RTK performance from what I have seen.
If you are 'surveying a static location' (and are not measuring a moving kinematic solution), then the solution using a 2Hz 'resampling' for RTPK 'confirmation' over RTK should be repeatable, especially if using redundant and repeated 'check observations . . .
1759185168785.png

For reliability, 'a repeated observation' at the same location can be exercised with the 'Distance-to-Last' information, so as to confirm the user has a reliable solution . . .

1759185279463.png

1759185603110.png
 
Last edited:

Nate The Surveyor

Well-Known Member
Another Question:
From the Collect Screen, then the compass button, (Top middle of screen), then RTPK Usage,
Here, we get BASE DATA UPSAMPLING.
Here, we have 3 Options.
NONE
INTERPOLATE
EXTRAPOLATE.
Which one would you recommend, Especially with the "New way of doing things" Apparently a Matt Johnson invention, (Probably the product of testing, and more testing).
Thank you,
Nate
 

Nate The Surveyor

Well-Known Member
20251001-07.46.02_00435_General_Settings.png
20251001-07.45.36_00435_RTK_DGPS_Settings.png

OK, so from Main Menu A, we hit the SETUP button (This is the one with a small and large gear)
Then we hit the GENERAL button, (Again, has small and large gear)
Then RTK/DGPS button, which is the first image I posted above.
Then, this takes us to the second image I posted above.
Here, we have a checkbox, DATA UPSAMPLING.
Do we want this one Unchecked, or Checked?
Thank you,
Nate
 

Nate The Surveyor

Well-Known Member
OK, Thanks Matt....... For your patience...
the LAST pics I posted, were pertaining to RTK, and the Previous ones were pertaining to RTPK......
I think I'm getting the pic. (It's obvious now!)
Nate
 

JAVAD Support

Member
Staff member
5PLS
JAVAD GNSS
UHF Radio 'Modulation Type' and 'Link Rate' for RTCM corrections from 'base':

When providing GPS + GLO + GAL + BDS RTCM 3.2 MSM Short corrections from a JAVAD 'base', do ensure that you use the D8PSK modulation type encoding for the 'Transmit Format' . . .

RTCM Data Transmit Protocol.jpg T-LS Rover ready to start T-3 Base.jpg

Radio Modulation vs Link Data Rate.jpg

Footnote: For North America, the Channel Bandwidth should be 12.5kHz (not 25kHz)
 
Last edited:
Top