Help me on Pallete Distribution

Hi,


Explanation of the Model
I have two sources as configured in attachement. they produce 90% red pallets and 10% green ones.

I want the red ones to go to Queue_Wagon1 and Rack_Sortie_1 (Queue_Wagon1 (60 pal.) should be filled first and the rest which cannot go there, be stocked in Rack_Sortie_1).why? there is a condition that Queue_Wagon1 will be emptied to sink_wagon at 13 p.m. everyday.(model time in hours. model starts at 6 p.m. monday).


the green ones go to Rack_Sortie_2 and then go to Queue_Camion1 and then sink_camion.

The timetables have been set about Queue_Wagon1 and Queue_Camion1.

Wanted
to be clear, I am using one transporter (Transporter_EquipeLogistique) to move the red pallets from Rack_Sortie_1 to Queue_Wagon1 (these red pallets couldn't be delivered to wagon (it was filled at the time). this transporter is shared with green pallets.(which go to Queue_Camion1).

I want the three transporters to collaborate to fill the Queue_Wagon1 after it is emptied at 13 p.m.

My Approach
I have used the triggers of Queue_Wagon1 to manage the distribution. the codes look if the Queue_Wagon1 is full, the red pallets (label "Dest"==1) are send to the Rack_Sortie_1. with a messaging system, the 24 hour cycle of emptying the the Queue_Wagon1 is done.


Problem
my model works alright the first day, but there is something that doesn't allow the three available transporters to work together at the second day and ....

I mean the Transporter_PC and Transporter_GC are stopped when the Transporter_EquipeLogistique is transporting red pallets from Rack_Sortie_1 to Queue_Wagon1.

I don't understand why????

IF U DON'T GET MY QUESTION, pls ask me to reformulate.

I haven't taken the time to try and fully understand your model sorry. Also, I didn't see the first day working like you describe. However I think you should use a dispatcher on centerport1 of Rack_Sortie_1 and connect all three transporters to the dispatcher. Then set a priority for the Job on Rack_Sortie_1 if you want it to have priority over other jobs.

Another quick point - if you're going to add msg() dialogs to the run, it's a good idea to put a stop() command after them so that the model doesn't continue/catch up when you hit ok/cancel. Otherwise you can end up not being able to interrupt it easily.

@Jason regarding the msg()
I normally use the following code if I like to have a screen message. The message gives me some information (you can add more information in the concat statement) and depending on OK or CANCEL the model stops or runs further. I find this very handy. The repaintall() I included, to be sure, that a screen refresh is done.

stop(); repaintall(); if(msg(getname(current),concat("Time: ",numtostring(time(),0,4) )) == 1) {go();} else {stop();}

For the code specialist: Yes, I know that the else statement is not necessary, but I find the code is more understandable if it is there.