topic Re: Operator Vs Transporter in FlexSim Forum

Operator Vs Transporter

MohammadMajd — Fri, 09 Feb 2024 18:47:10 GMT

[ FlexSim 23.0.7 ]

operator vs transporter.fsmI have combiners and a transporter and an operator. Is there a way to specify only transporter does the transporting to and from combiners and the operator only does the setup and processing? I know I could use process flow but this is a part of a bigger model and i have to make a lot of changes to the original model to add process flows.

Re: Operator Vs Transporter

joerg_vogel_HsH — Sat, 10 Feb 2024 00:30:50 GMT

Wherever you can select a taskexecuter doing something, you must set a reference to this taskexecuter. Typically it is a first centerport object or current.centerObjects[1] . One is a rank number of existing connections to objects. You can have more centerport connections to different taskexecuters. First is connected to a transport. Second is connected to an operator. It is up to you how you reference taskexecuters doing their jobs.

Hint: If you get an error message, like there is an array out of bounds, then you set a number of a rank that is not connected to an object.

Re: Operator Vs Transporter

jason_lightfoot_adsk — Sat, 10 Feb 2024 00:37:27 GMT

Sure, you can do it by specifying current.centerObjects[2] for the combiner transports, but in larger models where you might need many references to other object the port connection rank can be a pain due to the ranks changing when you disconnect and reconnect objects on the centerport.

For this reason I prefer to set up two pointer labels on the combiners one for the operator and one for the transport and refer to each using:

current.operator

and

current.transport

Not only is this more stable by avoiding ranks, it's also easier to read and check:

So I think it's a good habit to try and adopt.