question

Adil M avatar image
0 Likes"
Adil M asked Adil M commented

Exception Caught in FixedResource Error

Hi I'm running into an error with my model I wanted to increase the number of diverts per zone and added a decision point and a queue. The model was working perfectly when I only had 5 queue (Buffer zones) on the main belt. I went ahead and added 'P66' and the model was still running well. But when I added P67 I've been getting an error. Not sure what's causing it since it was built in the same way.Trial for 20 diverts.fsm

FlexSim 21.2.4
exception caught in fixedresource
trial-for-20-diverts.fsm (97.4 KiB)
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.

1 Answer

Jacob W2 avatar image
0 Likes"
Jacob W2 answered Adil M commented

Hi @Adil M,

It looks like this is a bug. We are passing it along to our dev team. There is a work around that we found however. If you extend the length of the exit transfer that connects to p67 the error goes away.

Another option would be to have the decision points directly send the items to the queues instead of the having the queues pull the items. The could be done by using the send by case trigger on the decision points.

The attached model shows the extended exit transfer.

Trial for Diverts Fix_JW.fsm


trial-for-diverts-fix-jw.fsm (98.6 KiB)
· 3
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.

Adil M avatar image Adil M commented ·

Hi, thank you for your response I extended the exit transfers but now I'm getting another Exception caught error. Model 2 w. 30 exit transfers.fsmException caught eror.PNG

0 Likes 0 ·
exception-caught-eror.png (401.1 KiB)
model-2-w-30-exit-transfers.fsm (98.3 KiB)
Jacob W2 avatar image Jacob W2 ♦ Adil M commented ·
@Adil M,

What changes have you made to the model? It seems like something else has been changed that is causing this new error. On the model that I was working on it will run until the stop time without errors. Could you provide details on what you have added or done to the model since?

0 Likes 0 ·
Adil M avatar image Adil M commented ·
Hey- I was just breaking down the queues(one queue was sending to 12 locations earlier) to more queues (so that each queue can send a package to 3 locations instead)
0 Likes 0 ·