You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 23, 2023. It is now read-only.
If you need any debug channel, let me know.
I am using latest version of CP.
Course is created with 5 headlands, started working from up/down, then headlands.
The white part of the field is unplowed, worker simply skips it.
The text was updated successfully, but these errors were encountered:
I dont think so, because i am using small plow and only 1 worker and it happens only on headland which is cutting up/down rows in half (take a look at Start position and next 4-5 rows)
If you see on the picture the limed part of the field is skipped by worker, only because headland is cutting those up/down rows.
I think worker should continue over the headland and finish the up/down row, but instead of that, once he reach headland that is cutting up/down row, he turns around and continue doing next row, so the other half of up/down rows stay unplowed.
Fixed connecting track between two blocks, making sure we do not
overshoot the starting waypoint of the up/down row when changing
from one block to the other.
Relevant only for complex fieldwork courses where the field has
to be split into multiple blocks.
If you need any debug channel, let me know.
I am using latest version of CP.
Course is created with 5 headlands, started working from up/down, then headlands.
The white part of the field is unplowed, worker simply skips it.
The text was updated successfully, but these errors were encountered: