SBAS Code Diff Position

This setting under General Group/Operating Mode/Advanced/GNSS, what does it do if checked on/off. Recommendations for its use or non use.?
 

Darren Clemons

Well-Known Member
The release version of the GNSS update that came through Wednesday morning did this I think. One of my crews called me and were getting nowhere.......we (Matthew Sibole and I were both pecking away through RAMS at the same time - that's SO awesome!) He first switched them the the pre release of the GNSS update and were able to get them back going and using Glonass through the constellations selections within the engine screen.
The T1M base on this system doesn't have Galileo or Beidou available though so I've now switched them back to the release version of the GNSS and after switching off the SBAS code/differential position, it seems they're back cooking....
 

Phillip Lancaster

Active Member
This setting under General Group/Operating Mode/Advanced/GNSS, what does it do if checked on/off. Recommendations for its use or non use.?
Just checked now and completely agree Steve Hankins. SBAS correction has an negative impact on position. I can quickly change back and forth and the better fix is with it unchecked.
 

Joe Paulin

Active Member
I noticed this a while ago, forget exactly when, but it was before last week.
1555333599779.png


Check out the Sats row: 9+0. It's like that for all my points in this project, the second number is always zero, which I assume is the Glonass count used for solution. It looks like this could be related?? I checked some of my older projects and they have both numbers greater than zero. I just checked, I have a job on March 24 where I first saw this situation where the second number is always zero.
 

Shawn Billings

Shawn Billings
5PLS
The SBAS issue would cause what you are seeing, but I don't think the issue goes back to March 24, but I could be wrong.
 

Aaron S

Active Member
I wonder if this is why I was having trouble yesterday... I had a very difficult time getting a fix in fairly open skies. When I looks at the satellites screen, the signal strength for the Glonass satellites was zero - as if the LS was seeing them, but not using them.

Might this explain why I had trouble getting a fix?
 

Joe Paulin

Active Member
I just updated and it fixed my issue that I mentioned above, now I see numbers of GPS and Glonass displayed correctly. Thanks!
 

Sdrake14

Active Member
This may be totally unrelated to this thread but I could use some feedback. I just updated the firmware on my Triumph 2 (yesterday) and since the update the receiver will not compute a position. I even tried downgrading and it did not return to computing. Then reloaded new firmware. No position. Soft or hard reset, no position. Examined all the settings in Netview and can not make sense of the problem.......Anyone have any ideas? Thanks.
 
Top