Satellites jumping up and down

Michael

Active Member
In the satellites used box in collect screen, the satellites are jumping between say 28 to 8 in a very quick way. It was doing at 7.5 miles from base and within 100 feet of base. Using new profiles Using TCP as communication. just haven't seen this that erratic before. Any thoughts? Mike
 

John Thompson

Well-Known Member
I noticed that too. Yesterday the LS seemed to really be struggling out in wide-open places. Often only 1 or 2 engines fixed.
 

Matt Johnson

Well-Known Member
5PLS
JAVAD GNSS
In the satellites used box in collect screen, the satellites are jumping between say 28 to 8 in a very quick way. It was doing at 7.5 miles from base and within 100 feet of base. Using new profiles Using TCP as communication. just haven't seen this that erratic before. Any thoughts? Mike

I suspect this a latency issue. What latency do you see in the RTCM screen? Do you have the correction rate set to 1 second? Also in the satellite screen do you the satellite statuses (SS) jumping. If the SS values are not jumping around and RTK is working I would not worry about the number of satellites displayed in the collect screen.
 

Matt Johnson

Well-Known Member
5PLS
JAVAD GNSS
I noticed that too. Yesterday the LS seemed to really be struggling out in wide-open places. Often only 1 or 2 engines fixed.
The RTK performance is fixed the PreRelease version with GNSS firmware 4.2.0.4. All 4 RTK should fix instantly when in the open. If you are still using the old firmware GLO P2 must be turned off or you will have this issue.
 

Matt Johnson

Well-Known Member
5PLS
JAVAD GNSS
I was using the PreRelease version. J-Field 4.0.1.671 and GNSS 4.2.0.4. I'll try it again this afternoon.
Is the firmware on your base up to date? The base firmware needs to be at least 4.3 for the GLO P1 issue to be fixed on the base.
 
Last edited:

Nate The Surveyor

Well-Known Member
Thanks Matt,
OK, USB on one end, what on the other? is this a JAVAD only product?
And, where does it plug in?
I found a cable, that has USB on one end, and the other into Port 3 from the left to right, on the back of the T-3.

Thanks!
Nate
 
Last edited:

Nate The Surveyor

Well-Known Member
OK, I got it hooked up. And, it shows up in NetView and Modem.
It shows up as COM 6 And it shows up as Firmware 4.2.01-220630
build 22 etc.
What nxt. ?
Anyway, would you mind posting a detailed step by step for us? I am sure others will benefit.
Thanks
Nate
 

John Rosco

Administrator
JAVAD GNSS

nusouthsc

Active Member
Is the firmware on your base up to date? The base firmware needs to be at least 4.3 for the GLO P1 issue to be fixed on the base.
Matt,
Thank you and John for all the help on this. I had a conversation with John this week but I don't think I was clear on my issue.

Since the update, I have noticed that the unit only runs at 1-3 Hz. Is this intended? My unit is set on 0.2 sec sample rate. In my investigation I have noticed that there is a new setting for "2 signals per engine" which is now checked by default. This setting appears to also force the maximum number of signals per engine to 60.

In my investigation, I unchecked the "2 signals per engine" and set the maximum number of signals to 30. That seemed to allow the engines to operate back at 5Hz and collect the normal 5 epochs/sec. But I also noticed the variety was not a high using this setup.

This is quickly getting over my head but I would like to better understand why its operating at a slower rate and in turn getting less epochs.

I would appreciate any input or clarification.

Josh Ellis
Nu-South Surveying
 

Matt Johnson

Well-Known Member
5PLS
JAVAD GNSS
Matt,
Thank you and John for all the help on this. I had a conversation with John this week but I don't think I was clear on my issue.

Since the update, I have noticed that the unit only runs at 1-3 Hz. Is this intended? My unit is set on 0.2 sec sample rate. In my investigation I have noticed that there is a new setting for "2 signals per engine" which is now checked by default. This setting appears to also force the maximum number of signals per engine to 60.

In my investigation, I unchecked the "2 signals per engine" and set the maximum number of signals to 30. That seemed to allow the engines to operate back at 5Hz and collect the normal 5 epochs/sec. But I also noticed the variety was not a high using this setup.

This is quickly getting over my head but I would like to better understand why its operating at a slower rate and in turn getting less epochs.

I would appreciate any input or clarification.

Josh Ellis
Nu-South Surveying

To allow all satellites to be used by each the engine the Max Signals setting has to be increased to 60. When there are many satellites visible this puts a lot more demand on the processor and the RTK rate will decrease to rate at which the processor is able to keep up so this is why you see the RTK rate decrease. It is much more beneficial to be using signals from all available satellites in each RTK engine than it is to have a 5 Hz RTK rate.
 
Top