question

Mischa Spelt avatar image
0 Likes"
Mischa Spelt asked Mischa Spelt commented

AGV Deallocation does not take custom centroid into account

Suppose the Deallocation strategy for a control point is set to Trailing Edge.

When the AGV has a custom centroid (centroid value 2, with subnodes indicating the relative position of the center), it seems that the trailing edge is incorrectly calculated when the x-value is not equal to 0.5.

See the attached model, for instance, where the three AGVs have centroid [0, 0.5, 0.5], [0.5, 0.5, 0.5] and [1, 0.5, 0.5], respectively. They all leave a control point with deallocation strategy "trailing edge + 1m". As you can see, they deallocate the control point when their trailing edge passes 0, 1 and 2 m respectively.

deallocation.png

It seems like the deallocation always occurs after 1 m of travel.

Deallocation_Centroid.fsm


Edit: as a workaround, I suspect that when centroid.x > 0.5, I can add (centroid.x - 0.5) * agvSize to the deallocation distance as a workaround... so I guess my two questions are

(1) is this a bug and

(2) is the formula for the workaround correct?

FlexSim 23.0.4
agvagv deallocation typesrotational centroid
· 1
5 |100000

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

Mischa Spelt avatar image Mischa Spelt commented ·
@anthony.johnson I realize the combination of centroid = 2 and deallocate after distance is probably quite obscure, but could you confirm whether this is a bug or not? Thanks :-)
0 Likes 0 ·

1 Answer

anthony.johnson avatar image
0 Likes"
anthony.johnson answered Mischa Spelt commented

The AGV module was designed assuming that the AGVs use a standard centroid. Non-standard centroids aren't supported.

· 1
5 |100000

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

Mischa Spelt avatar image Mischa Spelt commented ·
Yes, it doesn't work. No, it's not a bug. Got it! :-)
0 Likes 0 ·