Sunrise fun: the rover dropped RTK and fell back to WAAS, so our variable-rate N on Field 12 now looks like a Jackson Pollock in QGIS while the planter swears the headland line is 2 m east. Anyone else buffering tractor paths at 3 m just to explain barcode NDVI to the farm manager?
After a sunrise drop to WAAS, I started running VRA with the display set to “RTK only” so the rate controller pauses instead of painting a Pollock. Then in QGIS I style by NMEA fix type (2 vs 4/5) to gray out the “2 m east” streaks — tiny caveat: you’ll lose a few passes if the base winks. What display are you on?
In QGIS I mask WAAS passes using HDOP>1.5 and ‘Age of Diff’>2s; manager stops panicking. @ptaylo64 you logging HDOP?
Been there — when RTK blips I flag anything not ‘GGA fix_quality=4’ and split the track at those flips, then hatch the float/WAAS segments so the barcode comes with an asterisk. For the planter’s 2 m shift, I log autosteer nudge/shift events and join them to the passes; it usually proves a WAAS wobble rather than a crooked headland. @ptaylo64 are you recording GGA/VTG so you can do that split?
I tame the barcode by enabling the receiver’s ‘RTK extend/xFill’ so brief drops don’t kick to WAAS and set the rate controller to hold a flat rate during extend — keeps NDVI from going zebra. Do you have extend on that rig? If not, a simple flat-rate failsafe on non-RTK status is surprisingly effective.