"Far from STDL" on all engines...

[APADDEN07]

Getting this error this morning, tough time getting a fix, mostly float and cdf about 175' from the base. Just updated yesterday when I got back from vacation, is there something in the latest pre-release that's made this go wonky? Tried uploading a photo from my phone, but it's too big I guess.

 

[Matt Johnson]

It sounds like you are getting an error message that the base position being broadcast is too far from the base’s actual position and it’s standalone position. You need to restart the base with an Autonomous position.

 

[APADDEN07]

Doesn't seem to be the issue. I started from autonomous originally, 2d delta and h delta are both still green. Restarting to see if that helps.

It's wet with a low ceiling and some fog this morning, but I didn't think that would bother things.

After restart, still getting far from STDL and now also "no base time tag"

 

[Adam]

Try tapping the settings icon, then rtk, advanced rtk settings, then tap on each engine and set the top left setting to either 0 or raise the value up to 50.

 

[APADDEN07]

They're all currently set to 20. I did a full restart of everything and it's working better, but still getting intermittent episodes of the far from STDL. What does that setting change?

 

[Alexander Khvalkov]

RTK first computes the rover's position as a code differential one and compares it with the standalone. If the difference is bigger than the threshold, RTK resets itself. If the threshold is set to zero, it doesn't compare at all.

 

[Michael Stazhkov]

RTK first computes the rover's position as a code differential one and compares it with the standalone. If the difference is bigger than the threshold, RTK resets itself. If the threshold is set to zero, it doesn't compare at all.

"RTK Advanced Settings" -> Engine 1

 

[Adam]

RTK first computes the rover's position as a code differential one and compares it with the standalone. If the difference is bigger than the threshold, RTK resets itself. If the threshold is set to zero, it doesn't compare at all.

I've helped quite a few folks with the same problem. I think we should up the default some. Alexander, it seems maybe this setting isn't as helpful as I thought when we talked about it in the meeting. What do you think?

 

[APADDEN07]

What are the consequences of setting it to zero and no longer comparing the two? I'm already down to one engine fixes, I'm not big on further degrading any kind of quality control that's been built in.

Just noticed that the elevation is busted badly as well... Off about a hundred feet, which seems like a geoid issue, but I haven't changed any settings and it's been working like a dream until this latest update. Sent the project to support LS 00998 project name is WE-20-161 WAY TO PHURIPHAN

 

[Alexander Khvalkov]

The idea of differential positioning is that that the base-to-rover vector is computed with high accuracy, then the vector is being added to the base's position, and finally the rover's position is provided. Big difference between RTK rover's position and a standalone rover's position might be caused by two reasons:
- harsh environment at the rover location, and the solution cannot be considered as a reliable,
- incorrectly set base's coordinates, what is also a subject to pay attention to.