Internal Port Queues
Overview
- AutoStore creates "Internal Port Queues" when using Task Interface
- These port queues are not visible (normally, see Viewing the Internal Queue below)
- If a port is closed then taskgroups in its queue can be reflowed into another port's queue
- The queue constantly changes based on the system's current state
- Example: The system may reorder taskgroups in order to maximize throughput, accomodate task groups with a low request time to be selected quicker, etc.
Viewing the Internal Queue
- Use the configureport method along with the getnexttaskgroups method
- You can use the configureport within the Console as well
- getnexttaskgroups method returns a list of planned taskgroups for a specific port
- A PTG segment will be sent to the Log Publisher including the list of planned taskgroups
- Important: The queue will be locked for the length of bins configured. getnexttaskgroups method simply returns the list of planned taskgroups. This method does not "lock" the queue, the queue is locked as soon as the port is configured using configureport. This setting can be cleared by setting the config value to 0.
- See Get Next Task Groups page for more details
Content Code Bin Selection
- When requesting bins via content codes, AutoStore never selects bins already in any port queue (internal or WMS-set)
- This applies to both internal queues and queues set by the warehouse management system (WMS)
Updated 2 months ago