task executer probleme in process flow

[djami_zinedine]

[ FlexSim 24.1.0 ]

hello every one, hope you are doing well,

i have encoutred a new problem in my flexsim model and i would like some help

the probleme faced is in the last part of the work, it envolves a task executer loading a product from a pallet and unload it into a sink, this task must be done twice as there is twe products in each pallet

the main probleme is that the task executer does not load the second product from the pallet, but it load the same product that was unload in the sink (the first product), and so, a task error is shown an invalid task of unload because i am reffering that it unloads the second product whilt the transporter is loading the first, i dont understand why its doing like this, although a made an assign for each product in the process flow(the first and for the second).

simple_example_probleme_TRANSPORT.fsm

thank you for your help in advance

[joerg_vogel_HsH]

This is logic. If you transport your first item from a pallet, a staying item becomes a first item then. If you want to use 1st and 2nd as a reference, you should transport second item, before you transport first item.

[djami_zinedine]

thank you for your response, i think i miss defined the problem, tha logic that i made makes the staying item (the second) the first one, but for some reason the transporter takes the first item, puts it into the sink and then reloads the same item from the sink, which seems a lot illogical but this is what it happens

my goal is, like you said "If you transport your first item from a pallet, a staying item becomes a first item then" but it doesnt work

[jason_lightfootVL7B4 · Accepted solution]

It looks like you should synchronise on token.palette not token.splitID.

You're setting a label called 'labelName' in the final section rather than itempris which is the label to which you refer for the item to unload.

Also you can refer to itempris with just token.itempris if you remove the space from assignLabels - not then you don't need token.labels["itempris "].value, and you won't end up with what (confusingly) looks like two itempris labels on the token.

simple-example-probleme-transport_jl.fsm

If you create task sequences you don't need to use Acquire and Release of Resources.

If you were using ports to control the flow and using the standard 'use transport' option, instead of opening and closing ports you would be better holding the item on the send to port and releasing the palette through a given port. If you didn't do this then multiple pallets could be allowed to exit before they are emptied or have the correct item returned. As it is in your model, you've put the transport in the process flow so the port control is bypassed.

[moehlmann_fe]

You haven't adjusted the label name in one of the Assign Labels activities. Hence the "itempris" label still points to the first item afterwards and the same item is loaded again.

You also have two "itempris" labels, one with a space at the end and one without. I don't know if this is on purpose, but this might also cause issues, since both labels looking the same on first glance and might be used in the wrong place as a result.

[djami_zinedine]

just like you refered, the problem was in the "labelname" i didnt change it to itempris, thank you very much

also, thank you for noticing that there was two itempris, it was a mistake that i made and i couldn't correct, could you please refer to me where i can modify the labels that i created, thank you

[jason_lightfootVL7B4]

Click to the right of the labelname field in your Assign labels - you'll see the cursor is to the right of itempris so press backspace to delete the extra space.

[djami_zinedine]

thank you very much for your detailed description, it works perfectly

[djami_zinedine]

thank you again for your help