Skip to content
English
Submit Issue Sign in
vMC Sign in
  • There are no suggestions because the search field is empty.

vOS 1.19.2 - January 8th, 2025

Smarter obstacle detection, Increased System Reliability, and Improve Hitch Calibration

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 

  • Radar false positives on ROPS platforms: We resolved an issue where the radar system would detect parts of the vehicle (I.E Muffler) causing false positives. With this change, obstacles inside the vehicles shape will be ignored. Please ensure your vehicle measurements are up to date. 

 

Known Issues

  • Lookahead dot jump: This bug has been observed in rare cases. When the dot jumps from one pass to another, the vehicle will typically pause from a path error unless it is able to navigate to the other pass. This issue happens most commonly when a mission is generated with multiple overlapping turns in the headland.

    Workarounds:

    • Generate a new coverage plan and mission with more headlands than the last mission to prevent mission plans from generating with double circle turns on end of row turns. 

  • 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.