Skip to content
English
  • There are no suggestions because the search field is empty.

vOS 1.19.3 - January 26th, 2026

Resolution for blue lookahead dot jumps

Quick search

Resolved Issues

Known Issues

Please view the vOS 1.19.0 release notes for information about other features and bug fixes included in the vOS 1.19 update series. Click here.

Resolved Issues 

  • Lookahead dot jump: This issue, which previously caused the vehicle to pause due to a path error when the dot jumped between passes, has been addressed. It was most commonly observed in missions with multiple overlapping turns in the headland. The vehicle now navigates between passes smoothly without unintended pauses.

 

Known Issues

Discovered in vOS 1.19.3:

  • Lookahead dot visual discrepancy: When the mission is completed, the dot may visually jump behind the vehicle. This does not affect performance when running a new mission, or running the next mission in the queue.  

Discovered in prior releases:

  • CV False Positives: We have observed a few scenarios where the CV system may claim an obstacle is present, when it is not. - Please contact Sabanto support if you encounter issues. 

  • CV Pauses for Obstacles too far away: We have observed pauses from the CV system when an obstacle is actually present, but is across the field due to improperly calibrated CV cameras. - Please contact Sabanto support if you encounter issues. 

  • The Sabanto Autonomy System needs to reconfigure the infrared obstacle detection system: This bug can occur randomly at the start of the day after a device has booted. When you click resume navigation, the system may pause with the above error message about re-configuring the obstacle detection system. This issue will not resolve without intervention. 

    Workarounds:

    • Perform a device restart from vMC on the devices page.

    • Cycle the ignition on vMC or physically on the vehicle. 
  • PTO fails to engage: After saving any changes to the implement on the implement page of vMC, the vehicle may fail to allow the PTO to engage

    Workarounds:

    • Perform a device restart from vMC on the devices page.