Loss of performance, on a Job with screenshots

[Nate The Surveyor]

These First 3 are from last week.
Getting 32 sats, and 2 extra

These next 3 are from an old file, that I just loaded, and added to it. Both sets of screen shots were taken last week.
As you can see, the second 3 screen shots are using 12, and tracking 3, or 10+10

So, What settings need to be set different?
I just don't remember.
Thanks
Nate

 

[Shawn Billings]

Nate, Is it possible the base isn't sending corrections for Galileo and Beidou (RTCM3 instead of RTCM3.2 MSM)? Also could be that the broadcast period and link rate aren't correct for RTCM3 MSM.

Having said that, sometimes, I have noticed my LS Plus doesn't correctly auto setup the engines no matter how many times I hit auto setup. Eventually it kicks in and sometimes a reboot helps, but not always. It seems sometimes the issue simply has to resolve on its own.

But from the screen shots, I would start with determining if some of the constellations aren't being used by looking at the engine screen and if so, why.

 

[Matt Johnson]

Screenshots of the most import setting, the RTK engine configuration screen showing what signals are being used are missing. It looks like the RTK engines are all configured similarly with 4 engines being fixed and the signal variety only reaching a 0.68. If the engines are optimally configured as I prefer with 2 signals from each constellation then 4 engines being fixed will yield a signal variety of 2.1.

 

[Nate The Surveyor]

OK, I spoke with Steve Hankins. He recommended some changes. This is a screenshot of how I found my T-3 configured.
How I got here is:
Main Screen
Remote Base
Triumph 3, (directly beneath the START BASE button)
System Signals and Tracking>
But, I am turning ON:
Glonass L3 - Galileo E5aBoc - and BeiDou B2aBoc
Is that ok/Good?

Also, on the LS side, I found a bunch of QZ SS, and SPAS were on.
I turned all those off (ie, greyed out the button) as shown below:

The one on QZSS L6 would not grey out.
How I got there is:
Main screen
Setup
General
GNSS>
System and Signals Tracking>

 

[Nate The Surveyor]

Next, I went:
Setup
General
RTK/DGPS>
Advanced RTK Settings>
(Now engines 1-4 are listed)
Engine 1 is Set: AFCL Extra Low (90%) -Elev 12.0- and Max Signals 28
Engine 2 is Set: AFCL Extra Low (90%) -Elev 12.0- and Max Signals 30
Engine 3 is Set: AFCL Extra Low (90%) -Elev 12.0- and Max Signals 30
Engine 4 is Set: AFCL Extra Low (90%) -Elev 12.0- and Max Signals 30

Any comments would be appreciated.

Thanks

Nate

 

[Matt Johnson]

None of those changes will improve how the RTK engines are configured or help maximize signal variety and the speed at which the engines fix. See the attached document I wrote on this subject.

 

[Nate The Surveyor]

OK, So, Mr. Matt Johnson, what settings were used for that above test?
I have read all that several times.
Please make that information available on a LOWER shelf. (For people like me)
Thanks
Nate

 

[Nate The Surveyor]

I used it today, and signals variety NEVER got above 1.00. Many had 3 mins with a variety of 0.62.
Last week, it often finished with 2.12 Variety.
What setting do I need?
Thanks
Nate

 

[Adam]

I've seen the engines misfire as well.

RTPK is awesome!

 

[Shawn Billings]

I used it today, and signals variety NEVER got above 1.00. Many had 3 mins with a variety of 0.62.
Last week, it often finished with 2.12 Variety.
What setting do I need?
Thanks
Nate

I've been seeing similar issues, Nate. I also cannot manually change the engine signal settings.

Are you seeing each constellation represented in the four engines? I'm getting signals from all constellations in the engines, but the automatic configuration just isn't very robust on mine.

 

[Matt Johnson]

I also cannot manually change the engine signal settings.

I saw this issue on someone's LS and thought it was due to a hardware issue. The signals being broadcast by the base were not being shown on the engine configuration screen. If this is the same problem you are having, it seems there may be a bug causing this. I believe that Auto Setup Engines cannot work if base signals aren't properly known by J-Field.

 

[Matt Johnson]

OK, So, Mr. Matt Johnson, what settings were used for that above test?
I have read all that several times.
Please make that information available on a LOWER shelf. (For people like me)
Thanks
Nate

I configure the RTK engine as shown in the document and in this screenshot.

 

[Adam]

I've been seeing similar issues, Nate. I also cannot manually change the engine signal settings.

I saw this yesterday. I call it engine misfire.

I've also seen them with one constellation only in all engines. Usually Bdu

 

[Nate The Surveyor]

I started a completely NEW job today. NO PROBLEMS. Performance was back.
Possibly some odd setting in the database, started long ago.
Nate

 

[giulio]

but this value should not always be equal to zero (being the distance from the first mover). On my instrument it shows a measurement referring to a point where I had established a base about a year ago. I also always have these problems when I use the cadastral networks, as soon as I download the data I'll show you some screenshots.I was only sure of the measurements when I used a t3 I had on loan

 

[giulio]

I attach today's screenshots which highlight my problems with the RTN networks to which I connect my LS+ rover. I am in an urban area with a good view of the sky to the South and East. In fact I don't have positions I can trust and I go back to surveying with my old Navcom Sf3040, which only has GPS and Glonass and 66 channels. As you can see, they only resolve engines with AFCL 90% and where Glonass is excluded (this happens frequently regardless of whether you activate the glonass biases option or not) the first survey and from a GPS and Glonass only network at 20 km point 1 and 5 are the same and are respectively 140 cm (p1) and 25 cm (p.5) distant from the right position, Rtpk does not coincide with RTK nor with the right position. the second survey, again of the same points, was from a station (leica) with GPS Glonass Galileo and Beiudou at 40km, here we have RTK at 330 cm and RTPK at 50cm from the correct position. the third from another station (Stonex) about 40 km away here rtk diverges from RTPK by about 16 cm and the correct position is about the midpoint. (the last two screenshots are of the multi-constellation stations)

 

[nusouthsc]

Nate, Is it possible the base isn't sending corrections for Galileo and Beidou (RTCM3 instead of RTCM3.2 MSM)? Also could be that the broadcast period and link rate aren't correct for RTCM3 MSM.

Having said that, sometimes, I have noticed my LS Plus doesn't correctly auto setup the engines no matter how many times I hit auto setup. Eventually it kicks in and sometimes a reboot helps, but not always. It seems sometimes the issue simply has to resolve on its own.

But from the screen shots, I would start with determining if some of the constellations aren't being used by looking at the engine screen and if so, why.

Shawn,
This past week we encountered that very issue. The T3 randomly switched to RTCM3. I noticed I had 4 engines fixed with no variety. Went back to the base, switched to RTCM3MSM, and immediately had 2.3 variety. Not sure how/why it changed.

 

[Matt Johnson]

Not sure how/why it changed.

If you clear the NVRAM on the base all the radio parameters will get reset to default values and the radio will need to be configured again. Did you clear the NVRAM?

 

[Mark Wheeler]

Matt, When you configure the Engines as shown above, does that limit the solutions to using only those selected for each engine when half of them may be excluded from the solution due to current sky conditions? And is AFCL 90% always the recommendation? I found with 90% too much garbage is let in, creating many buckets that were clearly no good, clogging up the final solution.

 

[Matt Johnson]

Matt, When you configure the Engines as shown above, does that limit the solutions to using only those selected for each engine when half of them may be excluded from the solution due to current sky conditions?

The way I have it configure each engine has access to 2 signals from each satellite. This strategy makes it possible to have the most satellites available for use from each engine. If you use Auto Setup Engines many satellites will be excluded because there aren't any signals selected for every constellation. You are correct that only the selected signals will be used.

And is AFCL 90% always the recommendation? I found with 90% too much garbage is let in, creating many buckets that were clearly no good, clogging up the final solution.

I tend to agree 90% lets a lot of garbage in. There was never any testing done to prove that 90% yields better results.