TE stopped at wrong ControlPoint instead the one specified in tasksequence

Hi!

The problem I encountered in the attached model is that the TE stopped in advance at the wrong control point instead of the one specified in its travel task. And it began to unload the item to "Buffer2".

Through the AGV class method (.currentCP), The OHT1's current cp is CP102 instead of CP101 where it truly currently stopped. Let's take a look at the CP102's tree structure. Nothing exists inside its allocation node.

This is odd. Can anyone give a clue?

test.fsm

@anthony.johnson @Jason Lightfoot @Felix Möhlmann

Software Version:

FlexSim 22.0.16

001.png (112.3 KiB)

003.png (78.9 KiB)

test.fsm (3.1 MiB)

test.fsm (2.4 MiB)

· 4

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Felix Möhlmann commented · Sep 13 at 07:29 AM

This doesn't happen for me in the model you uploaded. Are you sure you uploaded the correct versionP The CP on the right is not named ControlPoint102 in the uploaded version, for example.

Also, what exact FlexSim version are you using. I tested this in 22.0.5 and 22.0.16.

0 ·

K_yun Felix Möhlmann commented · Sep 13 at 08:21 AM

Thanks for your reply. I updated the model in which CP101 corresponds to buffer1 and CP102 corresponds to buffer2. And the version is 22.0.1

You mean nothing like the picture above shows up as you run the model?

0 ·

Felix Möhlmann K_yun commented · Sep 13 at 08:30 AM

No, for me OHT1 moves to the correct location before unloading.

Then I get error messages at around 104s that ultimately bring the model to a halt. (The node that is supposed to be assigned as unload station in "变更标签" is not found. As a result the label does not have a valid value in the next activity.)

Maybe try updating to the latest bugfix release (22.0.16). It might be a bug that was fixed in 22.0.3.