Device (command) and interface events

The communication between Objective and ASRS mainly happens via NodeRed. The events can be queried in the device (command) and interface events.

• The content of the messages from Objective to ASRS can be queried at the Device Command Events.
  • STORE_TRANSPORT_COMMAND: generated if an ingoing transport order is created from stage-in into the ASRS.
  • RETRIEVE_TRANSPORT_COMMAND: generated if an outgoing transport order is created from the ASRS to stage-out.
• Returning messages from ASRS to Objective via NodeRed can be queried in the Device Events.
  • STORE_CONFIRMATION: generated when the stock has reached the right location in the ASRS. It will trigger the closing of the store transport order.
  • PICK_CONFIRMATION: generated when the picked stock has reached the stage-out location. It will trigger the closing of the retrieve transport order.
  • MOVE_NOTIFICATION: generated when an LPN is moved from stage-in to the ASRS, to another area/location within the ASRS or from the ASRS to stage-out.
  • STORE_TRANSPORT_TRIGGER: generated if a message from ASRS to Objective is generated via NodeRed, to create a transport order. Errors are displayed if the event is not accepted.
  • STORE_TRANSPORT_REJECT_TRIGGER: generated if an LPN is rejected at entering the ASRS. The transport order will be aborted, and the underlying relocate task is deleted with the configured terminate reason.
  • TRANSPORT_REQUEST_ALLOCATION: generated when an LPN to be picked from the ASRS is swapped. The locations from the initial and the new LPN need to be in the same work zone and LPN swap needs to be enabled. When the swap is possible, the transport order will be updated with the new LPN.
• Download and upload events to and from objective are reflected in the Interface Events.
  • LPN_MOVE: generated when an LPN is moved from stage-in to the ASRS, to another area/location within the ASRS or from the ASRS to stage-out.