question

Farah_najihah A avatar image
0 Likes"
Farah_najihah A asked Farah_najihah A commented

what is wrong with my agv

FT HBW.fsmtime: 17.492851 exception: Exception Caught in dispatchtasksequence(treenode tasksequence, treenode dispatcher DEFAULTNULL)

time: 17.492851 exception: Exception caught in start() of activity Process/Travel to Next Work Point in process flow "AGV". Continuing throw...

time: 17.492851 exception: Exception caught in TreeNode::callMemberFunction() main function. Throwing...

time: 17.492851 exception: Exception caught in evaluation of MAIN:/project/exec/usercommandlist/Process Flow/releasetoken/node

these are the error I got, not sure why, is it related to the process flow? my agv got stuck at the second decision point. this error appears when I added more processor and decision point in the agv path. how do I fix this? Thank you in advance! I attached my model below,


FT HBW.fsm

FlexSim 22.1.1
agvprocessflowagvpathprocessors
ft-hbw.fsm (14.2 MiB)
· 4
5 |100000

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

Jason Lightfoot avatar image Jason Lightfoot ♦ commented ·
You'll need to post your model in order for us to advise you.
0 Likes 0 ·
Farah_najihah A avatar image Farah_najihah A Jason Lightfoot ♦ commented ·

Hi @Jason Lightfoot thanks for highlighting that, I didnt notice I forgot to attach the model! I have updated my question. the error earlier was fixed which I dont know how :( but I have another error coming up! If you could pleaseFT HBW.fsm advise, thanks in advance! 1652366335652.png

0 Likes 0 ·
1652366335652.png (494.5 KiB)
ft-hbw.fsm (14.2 MiB)
Jason Lightfoot avatar image Jason Lightfoot ♦ Farah_najihah A commented ·
You're missing a destination label on the item your AGV is carrying. You need to add then when you push it to the AGVwork list (and it's usually an option in the picklist pulldown/template).
0 Likes 0 ·
Show more comments

1 Answer

·
Jason Lightfoot avatar image
0 Likes"
Jason Lightfoot answered Farah_najihah A commented

Some of the processors do not have "First Available" as the SendToPort destination and are instead pushing to a list. You should change this since the Transport Dispatcher is set to push to AGVWork instead, and that will correctly set the destination for you.

Correct:

1652378716983.png


Incorrect:

1652378752017.png




1652378716983.png (6.8 KiB)
1652378752017.png (7.6 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.

Farah_najihah A avatar image Farah_najihah A commented ·
Thank you for the clarification! that works :)
0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

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