Problem when calling Resource in common Sub Flow

Question

question

Andy asked Aug 21, '18 Ben Wilson edited Sep 25, '18

Problem when calling Resource in common Sub Flow

Good morning!

I'm having trouble adquiring a specific Resource from a group when I call it from a common subflow.

Right now I have 3 stations, 2 operators and 1 crane.

- Station 1 and 2 --> Operator1 (after he finishes all his Tasks in Station1 he starts working on station2)

- Station 3 --> Operator2 (he stays there all the time)

I have a token for each operator and tokens for each Item Type (there's a different type in each station)

I have a sub flow (with coordinated Tasks) that helps the respective Operator work together with the crane during some Tasks in the station (because Items represent heavy assemblies).

That's why both operators use the same Sub Flow (for the ONLY available crane). Right now I managed to change dyamically the ItemsType, Origins and Destinations for each sub flow with labels that refer to the position rank in each group (Group: "Operators" for the 2 of them, Group: "Destinations" with 2 available, Group: "Origins" with the 3 stations), but I can't call the right resource.

I tried creating labels for the child tokens in my sub flow, for example : LabelName: Operators, value: Group("Operators")[token.OperatorsNumber]. But an error apears

Operator" Sub Flow Name

Software Version:

FlexSim 18.2.0

subflow resources coordinated task sequence sub flow common sub

xzktx.png (2.4 KiB)

· 2

Joerg Vogel commented · Aug 21, 2018 at 02:27 PM

@Andy , please add the model. Thanks.

0 ·

Ben Wilson ♦♦ commented · Sep 20, 2018 at 03:45 PM

Hi @Andy,

Were you able to solve your problem? If so, is the Answer something you'd be willing to post below in response to your own question?

If you're still having this issue, as @Jörg Vogel mentioned, your model file would be most helpful in providing support for your problem. Is that something you can provide?

If you're concerned with sharing your model file publicly, you could instead start a new, private question. Private questions are visible only to our main office staff, so they're a good way to get help with issues in confidential models.

0 ·

Answer 1 · 2018-09-24T14:12:41Z

Andy answered Sep 24, '18 Ben Wilson edited Sep 25, '18

Hi @Ben Wilson

I solved it by leaving the acquire resource before (outside) my subflows.

Thank you,

question