question

Junyuan S avatar image
0 Likes"
Junyuan S asked tannerp commented

Item stuck on the first conveyor exit (conveyor 106)

Hi Folks

I noticed a problem in the model that items will alaways stuck on the first converyor exit. I checked all connectoins with the station in the middle since they worked in same way, but I didn't find any difference. However, the station in the middle just functioned well but the first station didn't. Could someone help with that?

Best

model.fsm

FlexSim 19.1.1
conveyor
model.fsm (11.0 MiB)
· 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.

gilbert jerald avatar image gilbert jerald commented ·

@Junyuan S

1) On Exit Triggers, have a condition based on the queue2 content. The problem is Queue2 does not exist in the model.

2) For referring an Object, the parameter should be a string value and it should be inside double quote Model.find("Combiner1").

Fix this two bug in you model and check the model behavior

Thanks

0 Likes 0 ·
Junyuan S avatar image Junyuan S gilbert jerald commented ·

Hi Gilbert

I just deleted the trigger but the item still will stuck on the first conveyor exit

0 Likes 0 ·

1 Answer

tannerp avatar image
1 Like"
tannerp answered tannerp commented

Hi @Junyuan S,

There seems to be something causing a traffic jam in your model. Let me explain what I think is happening and you can correct me...

ExitTransfer1 is sending a smallbox flowitem to Combiner2, where the smallbox item is being placed inside of a BigBox item. Combiner2 then sends the flowitems to Combiner 105, where the BigBox receives a Product flowitem from KittedMachine1. Lastly, Combiner 105 sends the flowitems back onto the conveyor system. Is this correct?

Assuming the process described above is correct, the gridlock is happening because KittedMachine1 is being asked to use an Object connected to a center port for transportation.

This connection doesn't exist, however, so Combiner105 is not receiving a Product flowitem from KittedMachine1.

From there, it causes a chain reaction and the items at your first conveyor exit are getting stuck.

I was able to run the model through to completion. Here's the model I changed:

junyuan-answers.fsm

All I did was uncheck the "Use Transport" box, but you will have to determine whether that's the right thing or if you need to add a center port connection.

Additionally, the model seems to have other errors, as @gilbert jerald mentioned, that will probably need to be addressed before you use the model for gathering data. (Note: I did not fix these in the attached model.)

Hopefully this helps! Let us know if you have any further questions.


kittedmachine.png (20.9 KiB)
no-central-ports.png (38.1 KiB)
junyuan-answers.fsm (11.0 MiB)
· 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.

Junyuan S avatar image Junyuan S commented ·

Thanks for all your response. Now I think it might be just a bug for 2019 update 2. I did uncheck the "Use Transporter" and delete the "OnExit" trigger in the model (not the one attached ) but the item will still stuck on the conveyor. However, update 1 version doesn't have that problem.

0 Likes 0 ·
tannerp avatar image tannerp Junyuan S commented ·

Another possible problem could be the size of the exit transfer. For whatever reason, if the exit transfer is not as wide as the items, it sometimes causes a bug where the items can't leave. Try resizing the exit transfer like shown in the gif below.

0 Likes 0 ·
resize-exit-transfer.gif (95.5 KiB)