Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A. D. does not use the setting "Restrict pathfinder to field" #1116

Open
KroshkaRoo opened this issue Apr 10, 2024 · 4 comments
Open

A. D. does not use the setting "Restrict pathfinder to field" #1116

KroshkaRoo opened this issue Apr 10, 2024 · 4 comments

Comments

@KroshkaRoo
Copy link

KroshkaRoo commented Apr 10, 2024

If the task "unloading of the combine" and A.D. starts not within the borders of the field, then the setting "Restrict pathfinder to field" is ignored. As a result, in the fields of complex shape, A.D. tries to get to the combine on the shortest path, including through the relief.
Is it possible that at the beginning of his work he check the presence of the border of the field into a certain radius, and if there is a field, then he built a route inside the field?
For example, at first he crossed the border of the field, and then began to build a route to the combine, using the setting "Restrict pathfinder to field"?

@Iwan1803
Copy link
Collaborator

"Search for the path only within the boundaries of the field"? 🤔

If there is a catch line for AD around the field, then set the field exit strategy to "nearest".

@KroshkaRoo KroshkaRoo changed the title A. D. does not use the setting "Search for the path only within the boundaries of the field" A. D. does not use the setting "Restrict pathfinder to field" Apr 15, 2024
@KroshkaRoo
Copy link
Author

KroshkaRoo commented Apr 15, 2024

"Restrict pathfinder to field" - this option

Edited first post.

If there is a catch line for AD around the field, then set the field exit strategy to "nearest".

I use this. It's no problem.

@KroshkaRoo
Copy link
Author

KroshkaRoo commented Apr 15, 2024

Situation: The combine unloader took the fruit to the destination point, and returned to the field. The route point, marked as field number, is located next to the field, because otherwise the unloader will interfere with the combine. And when the combine calls the unloader, the "Restrict Pathfinder to Field" option is ignored. If the unloader is restarted inside the borders of the field, then this option is used. But, until the next departure of the unloader from the field for unloading.
I hope so clearer.
Example of fields of complex form - Yagodnoe map

@rohne83
Copy link

rohne83 commented Apr 24, 2024

But this makes sense. If the unloader is outside field boundaries when it is started, how shall it be able to stay within the field boundaries? AD pathfinder is by far less complex than CP pathfinder, and I don't think it applies some kind of cost to the waypoints. So if it cannot find a path totally inside the field as it already is outside, I guess it will just ignore this setting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants