question

Yes, this logic is defined in the AGV process flow. The logic uses the cpconnection() command, and all of the logic just assumes the first location connection (cpconnection(obj, "Location", 1)).

The locations where this logic is defined are:

1. The Loaded Items list contains a field named destCP, that gets the first location connection.
2. The Loaded Items list contains a field named distance, that gets distance based on the location connection.
3. The Assign CP activity in the Item Pickup section assigns the cp label to the first location connection.

To adjust the Loaded Items list to take multiple location connections into account, you could probably change the distance field to go through each location connection (1 to cpnumconnections()) and return the minimum distance found. You could then, instead of using the cpDest field, add a hasCPDest field that searches the location connections and compares it against getlabel(puller, "cp") (the current cp that the AGV is looking for work on).

Changing the Loaded Items list will fix issues with dropping off items to destinations with multiple location connections. Changing the Item Pickup mechanism to handle multiple location connections is quite a bit more tricky. The problem is that if you have multiple location connections, and each has PickupPoints connections, the task of figuring out which pickup point to assign an item to is much harder because your possibilities are spread across multiple list partitions, so you can't just do a single pull from list. You'd have to pull from each of the lists, and then resolve which one of the results you want. I would suggest just using the first location connection for pickup points. If you feel that would be too difficult to teach a user, then my suggestion would be to separate the Location connection into two different connections, something like PickupLocation and DropoffLocation. PickupLocation should only have one connection, but DropoffLocation can have multiple. The other option is to leave the Location connection, but add a PickupLocation connection, and say that when you have an object that may have multiple Location connections, the user must add a PickupLocation connection that defines which one to use. Then in the AGV process flow logic, you see if there is a PickupLocation connection, and if so, use that one, otherwise use the first Location connection.