AGV does unwanted rotation after offset travel

patrick_zweekhorst
Advocate Advocate
1 View
4 Replies
Message 1 of 5

AGV does unwanted rotation after offset travel

patrick_zweekhorst
Advocate
Advocate

[ FlexSim 22.0.8 ]

Hi,

In the attached model you see two situations where an AGV does some offset travel after the last control point. After some second the AGV needs to return to the control point driving backwards. However, the AGV just flips around and starts driving forward. How can we prevent this?

Thank you for any advice.

Patrick

OffsetTest.fsm

0 Likes
Accepted solutions (1)
2 Views
4 Replies
Replies (4)
Message 2 of 5

kavika_faleumuE6HT5
Autodesk
Autodesk
Accepted solution

Hey @Patrick Zweekhorst, from what I can tell, once the AGV passes the end of the current Path to perform the Offset travel, it will think it's not connected to the Path anymore and will try to turn around to get back on. If your Path Offset travel is lower (or you have an AGV Body Offset to counteract the Path Offset) and the AGV stays on the path, then it will remain forward facing.

agv-stop-on-path.gif

0 Likes
Message 3 of 5

patrick_zweekhorst
Advocate
Advocate
Hi @Kavika F ,

Thank you for looking into this. You are correct, if the AGV stays at the path it looks to be working fine. However, in the actual model we do have separate paths (like to top example) where the straight path continues, but it is made out of multiple paths. In fact, the second path has a condition that states that the path is closed at that specific time, and that the AGV can only travel there with offset travel (creating 1 big path won't work). So, it would have been nice if the top example would have worked.

Do you think this behaves like it is intended to do and that we are modelling something that the AGV network is not able to do, or would you see this as a bug?

0 Likes
Message 4 of 5

kavika_faleumuE6HT5
Autodesk
Autodesk
Hey @Patrick Zweekhorst, I just spoke with some developers and showed them this behavior. They verified that this is a bug. We're adding it to our list. Thank you for pointing out this behavior to us!
0 Likes
Message 5 of 5

matthew_gillespie
Not applicable

@Patrick Zweekhorst This issue is fixed in 23.0.6 released today.

0 Likes