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
What is the problem this feature/enhancement solves?
Currently when mowing with a front and rear mower, CP lowers both at the same time. This results in leaving bits behind.
Describe the solution you'd like
Once the tractor is aligned, lower the front mower and move forward. Once the rear mower is at the start of the lane, lower it to begin cutting. Reverse the process at the end of the lane by raising the front mower first and as soon as the rear mower clears the crop raise it as well.
Describe alternatives you've considered
I'm not sure there is a CP alternative, but I manually mow a 2nd headland then set CP up for a single headland.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Came here to request a very similar feature, I don't find there to be an issue when mowing, but it would be great to have independent lifting of front/rear attachments when using a front cultivator and rear seeder/planter as the current process can make very messy headlands.
What is the problem this feature/enhancement solves?
Currently when mowing with a front and rear mower, CP lowers both at the same time. This results in leaving bits behind.
Describe the solution you'd like
Once the tractor is aligned, lower the front mower and move forward. Once the rear mower is at the start of the lane, lower it to begin cutting. Reverse the process at the end of the lane by raising the front mower first and as soon as the rear mower clears the crop raise it as well.
Describe alternatives you've considered
I'm not sure there is a CP alternative, but I manually mow a 2nd headland then set CP up for a single headland.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: