Adapters Request Portal

In order to handle capacity alarms between BLIM and AutoCU (through nI), a new standard event is required: HopperCapacityUpdated. This event is triggered by the IDS codes 1028, 1038, 1029 and 1039 (here). Below you can find the details of this event and how it behaves based on the code generated:

• • Hopper Capacity: Represented as a boolean value under $.data.hopper.isFull
    --> value would be "true" for message codes 1028 and 1038
    --> value would be "false" for message codes 1029 and 1039

  • Priority Hopper: A boolean value under $.data.hopper.priority, indicating whether the hopper is a priority hopper. This follows the same structure as the workplace priority for PX13.

  • Message Code Storage: A $.data.code object is included to store the original message code. I believe this will be helpful to retain the data sent by BLIM for reference.

  • You’ll find 4 examples of these events attached for your review:

    • Main Hopper full

    • Main Hopper not full

    • Priority Hopper full

    • Priority Hopper not full

Based on that, the codes mentioned previously will not be sent together with the already generated DeviceStatusChange event, but with the new HopperCapacityUpdated event.