How to dynamically load recipe into FlowMixer using FloWorks?

Question

question

Benjamin W2 asked Jun 24, '19 Benjamin W2 commented Jun 25, '19

How to dynamically load recipe into FlowMixer using FloWorks?

I am trying to load a recipe into a FlowMixer on the "On Empty" trigger. The recipes are all stored in the recipes table. Each time the mixer empties, the "recipeCounter" global variable increments and tells the mixer to load the next recipe on the "Schedule" table.

I am trying to load the recipe using the following code in the "On Empty" trigger. I know that the code is running, but it will not load the recipe into the Flow Mixer.

RecipeCounter++;
int recipeCounter = RecipeCounter;

string nextRecipe = Table("Schedule")[RecipeCounter][1];

if (nextRecipe == "Flat")
{
	current.as(FlowMixer).loadRecipe("Flat Prelatex");
	current.as(FlowMixer).startRecipe();
}

else if (nextRecipe == "Semi")
{
	current.as(FlowMixer).loadRecipe("Semi-gloss Prelatex");
	current.as(FlowMixer).startRecipe();
}

else if (nextRecipe == "High")
{
	current.as(FlowMixer).loadRecipe("High-gloss Prelatex");
	current.as(FlowMixer).startRecipe();
}

Here is a picture of the recipe that I am trying to load:

Is there something that I am missing? I also made sure to uncheck the "Continuously repeat recipe" box.

sample-paint-factory-6.fsm

Software Version:

FlexSim 18.2.3

FloWorks mixer recipe

schedule-table.png (3.3 KiB)

product-table.png (41.2 KiB)

sample-paint-factory-6.fsm (77.8 KiB)

Answer 1 · 2019-06-25T09:17:46Z

Mischa Spelt answered Jun 25, '19 Benjamin W2 commented Jun 25, '19

Hi Benjamin,

TL;DR: We'll fix the bug, you can temporarily work around by adding the following code at the top of the On Empty trigger:

int currentStep = getvarnum(current, "curstep");
if(currentStep > 0) {
  // Mixer is not idle yet, On Empty will fire again in just one or two events from now.
  return 0;
}

What is going on?

Thanks for bringing this to our attention. There is an issue in the Flow Mixer, and by the looks of it has been for a while. At first I thought that it was just a timing problem where the mixer hadn't registered its Idle state yet, and therefore did not load the recipe, but it's worse: in your model the On Empty trigger actually fires twice! So it seems like recipes aren't loaded at all, but what happens is that the first time the mixer is not internally set to idle yet and the recipe change is rejected. Then the second time you increment the recipe counter again and the recipe is loaded... but that happens to be the same product that was already on it! In fact, the odd rows of your schedule table will give you Flat, Flat, Flat, Semi, Flat.

I will fix this in an upcoming version. We are finalizing a bug fix version for 19.0 which will be out shortly. For now, you can use the workaround at the top of this answer. It checks whether the mixer is internally idle by looking at the curstep variable. When you step through you will see that the first time the trigger fires, this value is still set to 3 (the last step of the Flat recipe), then the On Mixer Empty event fires and the curstep is reset to 0 -- this is the moment that loadRecipe() will actually accept a change.

In addition, there seems to be a bug in the return value of loadRecipe that I need to resolve with FlexSim, but the idea is you can check that as well: it's supposed to return 1 when the recipe change is successful and 0 when it is not because the product is invalid or the mixer is not idle, for example.

Some general tips

As a side note, I noticed you have a FlexSim Fluid Ticker in your model which is generating a lot of events. If you are only using FloWorks objects, you may want to remove the ticker to speed up your model a bit.

Also, since you are already using Process Flow in the model: there is a Process Flow template to make a mixer run through a production schedule. If you haven't checked it out already, have a look -- you can add it with the Process Flow button on the toolbar, "Add a FloWorks Process Flow" -- "Mixers with recipe table".

· 1

Benjamin W2 commented · Jun 25, 2019 at 01:55 PM

Thank you! I appreciate the feedback.

0 ·

question