Skip to content
This repository has been archived by the owner on May 23, 2023. It is now read-only.

worker skips half the field #6652

Closed
Commissar0617 opened this issue Jan 10, 2021 · 11 comments
Closed

worker skips half the field #6652

Commissar0617 opened this issue Jan 10, 2021 · 11 comments
Assignees

Comments

@Commissar0617
Copy link

20210109185711_1
20210109185717_1

so, im using a 2 implement course..... one of the workers decided it doesn't want to be behind, and skips like half the field. using up/down w/ 3 headlands.

https://mega.nz/file/fK4zEIZA#Y0QbucmpfOJmo6iyyrnff_-4sQvObK8VNXbgrN14948
log too big for github

@Commissar0617
Copy link
Author

20210109231347_1
20210109231408_1
20210109231418_1
log.txt

more logging for ya.

@Commissar0617
Copy link
Author

yeah, this seems to be happening with all seeders and fieldwork implements. have not noticed it with a combine

@pvaiko
Copy link
Contributor

pvaiko commented Jan 12, 2021

Sorry, it is probably obvious to you but I have no idea what exactly is happening when it "skips half the field".

@Commissar0617
Copy link
Author

Sorry man, so basically what happens is that in seeding or fieldwork, after doing one set of lanes, the worker then skips a number of lanes and continues to work.

It just drives down the field and starts there, and runs to the end.

@pvaiko
Copy link
Contributor

pvaiko commented Jan 12, 2021

Show me your course generator screen for this course.

@pvaiko
Copy link
Contributor

pvaiko commented Jan 12, 2021

And a screenshot of the course, with the lanes being skipped marked.

@Commissar0617
Copy link
Author

Commissar0617 commented Jan 13, 2021

20210111223146_1

this was a screenshot from yesterday that should give you some idea. this one was made using lands, and others up/down. the cp worker says it is done at this point.

ill get you the other screens you wanted still. it's happened on multiple fields with multiple tractors and implements.

@Commissar0617
Copy link
Author

for some reason, it didn't do it tonight. before, it did it on fields 90, 68, 27, and 11 on landdownunda

@pvaiko
Copy link
Contributor

pvaiko commented Jan 13, 2021

It is because of that insanely long rig you have there. This happens after it finishes a turn and then is looking for the next waypoint in front of it to continue on the up/down row. I'd really need to see the course in that area, for example in your second log, it was the turn starting at waypoint 1287.

@Commissar0617
Copy link
Author

Commissar0617 commented Jan 13, 2021

I mean, yeah, the planter is pretty insanely long. I had to drop the spreader off the end of the aircart for one field because i couldn't get enough headland in, but that's just an inherent problem, i wouldn't expect any sorta fix for.

The disks i don't think are that extraordinary. My db120 is about as long unfolded. I did 2 headlands, with two implements. I believe it was the 2nd turn on the up/down in the 1st screenshot. It generates the temp waypoints for the turn, but doesn't follow them. If that helps.

Ill see if i cant reproduce it after harvest. With video this time.

@Commissar0617
Copy link
Author

i got eet
log.txt

https://youtu.be/OFqf1ZAYkSw?t=1747

i do have the generator up at the end.

pvaiko added a commit that referenced this issue Feb 7, 2021
Also fixing #6781, do not reset tool offset when starting, only on attach.
@pvaiko pvaiko closed this as completed in b899a62 Feb 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants