Resource release problem in OpenTCS v5.16

[csliao0524]

As shown in the attached image, when I try to dispatch different vehicles from different position to Point-0023, e.g.,

Vehicle-0001 (from Point-0007 to Point-0023)
Vehicle-0002 (from Point-0006 to Point-0023)

Both cases hold the resources from Point-0007 to Point-0023 (occupying too many resources), which does not happen with other routes
(e.g., dispatching Vehicle-0001 from Point-0023 to Point-0029 as shown in the image).

Has anyone encountered a similar situation? Is this behavior normal or is it a bug? Are there any solutions?

Thank you for your help!

[swltr]

@csliao0524 There was an issue related to resource management in 5.16 that has been fixed in 5.17. Can you still reproduce that situation with 5.17?

[csliao0524]

Hi @swltr
Below are the test results using the 5.17, it seems like the vehicles still hold the unnecessary resources at the specific route.
In addition, I've tried to assign the vehicle by ways of "Sent to location" and "transportOrder web api", both have same problem.
I'm not sure how to tackle with this issue, any advice?
Thanks for your reply!

[martingr]

@csliao0524 How long are the paths between Point-0007 and Point-0023? The rulers would suggest that each path has a length of 10.000 mm. Is this what's acutally configured in the "length" attribute of the paths?

[csliao0524]

Hi @martingr
It seems the issue was related to the path length. I neglected to check and recalculate the path length when adjusting the layout, resulting in many paths being shorter than 10,000 mm.

After recalculating the path length, all paths returned to their normal length of 10000 mm. And the test result shows that the resources now can be released correctly for both versions 5.16 and 5.17(as shown in the attached image).

Additionally, could you please let me know where the suggestion of 10,000 mm from the ruler is documented in the official files? I don't seem to recall seeing it.

Thank you for your assistance!

[martingr]

I'm glad I could help and that this fixed your issue.

As for your questing regarding the ruler: There is no specific documentation on this. I simply looked at the ruler in one of your screenshots (see the green rectangle):

[csliao0524]

Ok! thanks for your reply, Although the issue is fixed, I still can not figure out why the incorrect length configuration would result in this resource problem? Any idea?

[martingr]

Since version 5.9, openTCS makes use of the vehicle's length for resources management. When releasing resources after a vehicle has completed a movement command, the vehicle's length is considered to decide which resources are actually not required any more.

In your example

the paths from Point-0008 to Point-0023 had a combined length of 3 mm, which was not enough to cover the vehicle's length of 1000 mm. In such cases, openTCS will keep paths behind the vehicle allocated until the length of the vehicle is fully coverered according the the length of the paths.