question

Jonathan avatar image
0 Likes"
Jonathan asked Kavika F commented

A* Navigation and Travel Task Sequences

My operator needs to go to a queue to refill their machine. I'm using Process flow to control the task sequence. I need them to follow a specified path so I put in an A* path. This apparently conflicts with the Travel Task Sequence (see screenshot). How do I fix this? (Software 21.0.6)

1651761491718.png

FlexSim 21.0.10
a star navigationtravel task
1651761491718.png (438.0 KiB)
· 1
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Kavika F avatar image Kavika F ♦ commented ·

Hi @Jonathan, was Regan Blackett's answer helpful? If so, please click the "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.

If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always unaccept and comment back to reopen your question.

0 Likes 0 ·

1 Answer

Regan Blackett avatar image
1 Like"
Regan Blackett answered Jonathan commented

Based on your screenshot of the error, it appears the travel destination isn't being properly assigned to the traveler. Where it says "involved1" it should reference a destination object, but since it says "NULL" that would mean the traveler was assigned a bad reference for a travel task's destination. Recheck how that destination is being assigned to make sure that the object is valid. If you post your model we can help track it down.

· 2
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Jonathan avatar image Jonathan commented ·

Figured it out. I had an incorrect destination in the "Travel: Install New Spool" task. The destination was listed as "Item" instead of a proper object.

1 Like 1 ·
Jonathan avatar image Jonathan commented ·
I've e-mailed you my model. Thank you.

Once we figure it out a description of the fix can be posted here.

0 Likes 0 ·