Delay operator after load

[alejandro_ulises_tp]

proyect-rev01.fsmHow can i delay an operator after he makes a load in the processor?

I want to simulate that after the load he makes another operation in the same processor, once he finishes the delay he can proceed to the next operation.

Please, anyone could help me?

[alejandro_ulises_tp]

@Logan Gold @Joshua S @Matthew Gillespie @Isaac Litster, could you help me, please?

[alejandro_ulises_tp]

@zachary.h, could you guide me?

[joshua_s · Accepted solution]

You can set the load time of the operator to the delay amount you want. If you want the delay to happen right after he picks up the item, you can have a small process flow activity block that fire when he loads an item, then have a custom code activity that stops him, then a delay, then a resume activity.

[alejandro_ulises_tp]

proyect-rev03.fsmI did this but it doesn't work fine:

They don't respect the delays as i want it.

I want the operator delay to work just after the processor setup time is finished.

[joshua_s]

So the item will not be processed until the operators delay is finished as well? I'm confused on what is supposed to happen when. Your processflow is firing too much, so it fires for both operators when an item finishes setup at a processor.

[alejandro_ulises_tp]

The exact thing I'm looking for is that when the operator finishes the setup time the operator stops for about 25 seconds, then resumes. That stop is in order to simulate that the operator is filling a checklist.

Did you understand? I'm having a hard time with this 😕

[joshua_s]

I put the operators in a group, so now anytime they finish the task of setting up, the operator is stopped for 25 seconds, and so they can't do anything else until the delay finishes and they are resumed. All of this is found in the activity block I added.24682-proyect-rev01-1.fsm

[alejandro_ulises_tp]

@Joshua S Thank you so much! that is exactly what i needed but i don't understand why do you put 2 delays but just one have time?

Could you explain me?

[joshua_s]

I use that as a breath activity, meaning at a specific time multiple events fire, so that allows the activity to fire above, the item is then processed, and the operator is stopped. Without it the operator is stopped before the processor changes from setup to processing, so the item will wait the 25 seconds before it is released to be processed. Sometmies lots of events will happen all at once, and this gives a buffer to the order of events that fire.

[alejandro_ulises_tp]

joshua-s-error-delay.fsmI tried to change the basic delay for a task sequence delay in order to make a statistic out of it, but it throws me an error "Task executer activity "delay" in "process flow"

Do you know why is that?

[joshua_s]

You don't have to change the delays to task sequence delays, in the first custom code change the state to processing. Also it wasn't working because the event triggered source added a label called operator pointing to the operator that it was called on, so the labels needed to match on your activities to token.operator.

[preetdesai]

@Joshua S This solution helped me. So thank you. I have a question. What is the task type 5 "match value" in the event trigger?

[joshua_s]

This means that when the event "On Finish Task" for any of the operators occurs, I check to see if the Task Type of the event is equal to 5, and if it is, create a token.

[jason_lightfoot_adsk]

You can replace the literal 5 with the macro for the task for better readability - in this case TASKTYPE_UTILIZE