Cancel
Showing results for 
Search instead for 
Did you mean: 

Waituntil before sending to successor

Creator
Creator

Hello,

 

I am currently stuck with a problem regarding the waituntil control. 

 

In my attached photo you can see four variables. QT_Total is the sum of QT_Turning1 and QT_Turning2 (which are the Queue time of Buffer_Turning1 and Buffer_Turnning2).

The variable Stop_Flow is set to False when QT_Total < 4800 and True otherwise. 

 

I want to write a method (Method_StopFlow2) that make the MUs wait at BufferMilling if Stop_Flow = True and wait until the variable is set to False again.

 

Could anyone please help me? My method does not work. It sets the variable back to False when the QT_Total < 4800, but it won't start sending the MU's again. 

 

Right now the method for setting the variable Stop_Flow to true or false is located in the Drain's Entrance Control. The Mwthod_StopFlow2 is located in BufferMilling's Exit Control.

 

Thanks,

Mal

2 REPLIES 2

Re: Waituntil before sending to successor

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom

So, basically you want a kind of CONWIP system.

 

I think the easiest way is to lock/unlock the exit of your milling buffer. In that case you do not need to Method_StopFlow2 anymore. In Method_StopFlow21 you need to replace Stop_Flow with BufferMilling.ExitLocked.

 

BTW, there is a standad Exit-strategy to pick the shortest queue (Min.Contents), so no need for SimTalk.

 


Gert Nomden
Digital Factory Consultant
cardsplmsolutions.com
Highlighted

Re: Waituntil before sending to successor

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor
in your method method_stopflow2 --> else branch: delete return, insert @.move; if you use a exit control front, you need to move the MU (e.g. @.move)
Steffen Bangsow
freelance simulation specialist  
web: www.bangsow.eu
mail: steffen@bangsow.net