question

Rahul R avatar image
0 Likes"
Rahul R asked Rahul R commented

A star traveler not de-allocating node

I am modeling AMR movement using A star network and have few questions-

1. I noticed some travelers are not de-allocating nodes after passing them. They finally release this node on reaching destination. Other travelers are left to be in blocked state because of this. I have tried changing de-allocation time offset in A star navigator properties to 0,0.1, 1 sec but the issue still exist. Any idea why this is happening?

At 375 sec, AMR363 does not de-allocate the node and subsequently, AMR403 gets blocked.Test_Model_AStar.fsm





FlexSim 23.1.3
agva star navigationamr
ground-hub-sc.gif (12.0 MiB)
test-model-astar.fsm (110.2 KiB)
· 2
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

Julie Weller avatar image Julie Weller commented ·

Hi @Rahul R,

For your first question, it's hard to know how to help without looking at your model. To receive a more accurate solution, please post your model or a sample model that demonstrates your question.

If your model contains sensitive information, you could first toggle your post as private using the "make private" option under your question's "gear" menu. Private questions are visible only to site moderators. You can also contact your local FlexSim distributor for phone or email help.

For the second question, you could add a preferred path to help reduce congestion if you know where you want them to go?

0 Likes 0 ·
Rahul R avatar image Rahul R Julie Weller commented ·
@Julie Weller - I edited the original question and added a test model
0 Likes 0 ·

1 Answer

Jason Lightfoot avatar image
0 Likes"
Jason Lightfoot answered Rahul R commented

I was able to avoid this issue by turning off the option to ignore inactive travellers. This meant that the AMRs have to be assigned by distance to the pickup queue which is best evaluated once when the AMRs are pushed to the list, otherwise the constant evaluation kills the run speed.

Model attached.

test-model-astar_jl.fsm


However I still think there are issues with the model so will create a report for the developers. Just know that if a fix is forthcoming, it will be in the latest supported versions, not 23.1.


test-model-astar-jl.fsm (110.1 KiB)
· 1
5 |100000
Toggle Comment visibility. Current Visibility: Viewable by all users

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

Rahul R avatar image Rahul R commented ·

Thanks Jason for the solution and adding bug to the dev list. Curious to know what is causing this weird behavior? I look forward to solve in subsequent releases.

0 Likes 0 ·