Check itemtype of downstream items

Question

question

Jeff Kaczmarczyk asked Oct 18, '16 Adrian Haws edited Oct 18, '16

Check itemtype of downstream items

I'm working on a basic simulation where boxes travel on a conveyor and get processed at either processor in the simulation. The baseline logic is to process every other box at each processor (top flow in model). Itemtype1 boxes get processed at "processor1" with a mean cycle time of 8 sec. Boxes that bypass to the 2nd processor have a cycle time of 1 sec. I think the baseline model is working properly.

For the 2nd model (bottom flow in model), I'm trying to implement better logic in order to achieve a higher output by looking downstream. The physical layout can not be changed.

My first thought was to do the following-set the item to itemtype2 On Exit of the source, then set it to itemtype1 before the item enters Processor 1b if there are 2 or more items with itemtype2 downstream (in queue3, queue4 or processor2b)

First, I'd like to know how to implement this logic. Second, is there a better way to do this?

Thanks, Jeff

Software Version:

FlexSim (other)

Software Version:

FlexSim (other - please specify)

itemtype tracked variable downstream tracked

jeff-process-flow-rev-2fsm.fsm (19.2 KiB)

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Answer 1 · 2016-10-18T18:39:58Z

Adrian Haws answered Oct 18, '16 Adrian Haws edited Oct 18, '16

Jeff,

You can implement this logic by using a tracked variable. When an item enters Queue3b, the tracked variable is incremented by one. It is then decremented in the On Exit of Processor2b. Then in the On Entry trigger of Processor1b I wrote a couple lines of code to check whether the tracked variable is set to 2 or greater, then to change the item type and color if that condition is true.

I've attached the updated model.

jeff-process-flow-rev-2-updated.fsm (22.0 KiB)

· 2

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Jeff Kaczmarczyk commented · Oct 18, 2016 at 06:54 PM

Im having problems opening the file, what version did you save the file?

I'm on version 7.3

0 ·

Adrian Haws Jeff Kaczmarczyk commented · Oct 18, 2016 at 07:28 PM

@Jeff Kaczmarczyk I updated it in version 16.2.1. I could save it to a different version, but the implementation that I mentioned is as I've described. It just involves creating a tracked variable and using pick list options to modify it in the triggers. The only exception is the bit of code used in the On Entry of the processor or the On Exit of Queue2b, which I'll include here ("ChangeItemType" is the name of the Tracked Variable):

int condition = gettrackedvariable("ChangeItemtype");
if (condition >= 2) {
	setitemtype(item, 1);
	colorred(item);
}

0 ·

question