about Basic conveyor pick windows

Hi, in this post
http://www.flexsim.com/community/for...read.php?t=841

Phil BoBo gave a model using Basic conveyor to define pick windows. The model is here:

http://www.flexsim.com/community/for...do=file&id=201

I test the model in flexsim 6.0.2, and find that if we "save" the model in flexsim 6 and reset and run it, the second decision point (HoldItem decision point) on the Basic conveyor never triggered. You can add pt("second") in the second decision point's trigger to test. Why?

Thanks in advance.

Thanks for bringing this model to our attention. In order to minimize the number of events occurring, the basic conveyor had some features added which destroys events if an item had been released. So in the case of this model when the item crosses over the ReleaseItem Decision Point it gets released from the conveyor and then its future events (of crossing the other Decision Points) get destroyed.

I have recreated the logic in the model as well as updated it to version 6.0.2 and you can find that attached.

Thank you Cameron . I replace the receiving conveyor with a processor and run the model, the system console will output error message. why?

The test of item's state is made 20 seconds after the releaseitem. But if the item has been processed then it goes to the sink before the test and an error occurs.

Hi,

If at some some point the conveyor stops y resumes after a moment, the release item corresponding to the end of the conveyor will occur before the item reaches this point.
Is it possible to prevent the basic conveyor from erasing the following decision points events?

Thanks a lot for your help!

Hi,

I finally got my model work.
The thing is that, adjusting the model as Cameron suggested works fine if there are no stops on the line. (3rd line)
In this case, the conveyor stops for various reasons, and it should stop the whole line. Because the exit from one seccion to another is manged with messages, when the conveyo is stop I "resend" messages every time the box should have reached the end of the seccion in order to check if it is stopped, or if it did reach the exit point. (4th line)

Is there anyway to adjust the original logic (Cameron's one), without needing to send as much mesages as I am sending. Since this model is a simplifie part of the complete one, I would have a lot more mesages in the future model.

Any suggestion is welcomed!
Thanks!