Reach RS+ Altitude Jumping Around

[kylelanman]

@TB_RTK

And both recievers runned latest firmware? I ask because recent version have improved RTK engine, specially latest DEV version.

The rovers are both running 2.22.4. I need to check the base. If I remember correctly I was struggling to get it to update so it is on an older version.

@TB_RTK

Sure, reduced some functions made this result. A combination of old ephemeris data and fix&hold. Using continous would avoid this but then lose feature of Fix&hold.

I’m moving at 4 inches a second for days at a time. I have about 4 inches of forgiveness side to side before bad things happen. In this scenario am I better to use continuous or fix and hold? I read your thread Fix & Hold vs Continuous. Ignorance is not bliss on the topic and it isn’t clear to me which is better in my application.

@TB_RTK

From the record it looks like GPS renew its ephemeris every 2 hour and by processing after 2000 hours you would avoid bringing old data into the loop with Fix&hold thus not having such jump late in the ephemeris session.

Forgive me, I didn’t understand that. Can you dumb it down? Is there anything actionable to take away from it?