Processor does not correctly change its state when resumed

Question

question

Alfonso V2 asked Jan 22, '19 Alfonso V2 edited Jan 23, '19

Processor does not correctly change its state when resumed

I have a model that uses 2 different systems to stop processors.

1) A time table makes the processor stop for maintenace based on the model time.

2) A process flow uses a global table to make the processor stop (breakdown) based on the number of units processed.

On some occasions, a certain sequence of these stops make a processor to keep its "maintenance" state when it resumes. This creates a completely irrelevant state bar.

I believe that the problem is related to the fact that the processor is stopped by two different times, and that it was already resumed once when it has to be resumed the second time. It may be basic but I can't figure out how to fix this issue.

Here attached is a simplified model that illustrate this problem.

Thank you for your help.

cusersavillega2desktoptime-tableglobal-table.fsm

Software Version:

FlexSim 18.2.2

process flow global table time table stop and resume state change

cusersavillega2desktoptime-tableglobal-table.fsm (503.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 · 2019-01-22T16:15:33Z

Joerg Vogel answered Jan 22, '19 Alfonso V2 commented Jan 23, '19

If you combine several different stop object commands, you should set for each combination of stop and resume an unique ID.

time table stop
mttb/mttr stop
request stop for setup
request stop for process
request stop while processing through preempting only

different-stop-object.fsm

different-stop-object.fsm (34.5 KiB)

· 1

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.

Alfonso V2 commented · Jan 23, 2019 at 09:03 AM

It looks like it worked. It makes sense, thank you!

0 ·

question