question

There are some subtleties when using the crane. First it's important to understand that the Crane does not travel like other objects like the Operator or Forklift. The crane uses offset travel to move. You'll notice that your cranes never spend anytime in their Travel tasks because these have no affect on the crane. Instead you need to use the Travel to Loc activity.

I'm not entirely sure why setting the state of the crane doesn't work, however, it often is the case that manually setting states of objects does not work due to them managing their own states. Because of this, I changed the setstate activities to use a Custom Task activity that is set to the Wait for Task type. This gives you the option to set the state on the object and it will ensure that no new task sequences can be started. The crane will wait in that state until a new task is added to the end of its active task sequence. Because I have to be adding tasks to the actual task sequence, I also had to add a Create TS activity to the beginning of the 2nd crane's set of tasks.

At the very end I have one final task activity that is a delay with 0 time that then sets the state of the crane back to idle.

See the attached model. 6130-crane-flow.fsm