AOI - BNI00KM

• The BNI00KM hub does not have any configuration setting in the RSLogix5000 I/O Configuration Tree.  All data must be passed through an IO-Link master that communicates with the PLC using EtherNet/IP.  To understand how to configure an IO-Link master, please refer to the AOI_BNI006A_50_31_040 User Guide (for use with the Balluff BNI EIP-508-105-Z015).
• When the IO-Link master has established a connection with the PLC using EtherNet/IP, the IO-Link port connected to the BNI00KM Hub must be configured for IO-Link mode as described in the AOI_BNI006A_50_31_040 User Guide.
• The BNI00KM hub is a configurable IO-Link device; therefore, certain parameters can be changed from the default setting.  This can be done by using an explicit message instruction or the Balluff User Interface to the IO-Link Master that will write to the parameters as defined in the BNI00KM hub user manual.
• For more information about setting up explicit message instructions or using the webserver function, please reference IO-Link master user manual.

• For the BNI00KM to function, it must be tied to the corresponding AOI port data from the Balluff IO-Link master, which can be accomplished as shown below by using a “Drag and Drop” procedure to copy the BNI_EIP_508_Port_1_Data tag from the master AOI to the IO_Link_Port_Data tag in the slave AOI.  In the above example, the tag name that is copied this way is “PORT_1” data which is of the data type IO_Link_Port_Data. The tag chosen for this “Drag and Drop” is dependent on which port of the IO-Link master device that the slave is connected to.

The User-Defined Data Type for the Add-On Instruction defines the interface for the AOI and the user’s project.  One additional UDT is defined, IO_Link_Port_Data, for integrating data through configured IO-Link ports. 

4.1.1.1 Port_X01 (BMC_UDT_PROC_BNI00KM_Analog_Ch_3625US)

• Value (DINT) – Measurement Value
• Switch_Point_1 (BOOL) – Pre-Defined Limit value
• Switch_Point_2 (BOOL) – Pre-Defined Limit Value
• Underflow (BOOL) – Analog Signal Below Threshold
• Overflow (BOOL) – Analog Signal Above Threshold

4.1.1.2 Port_X02 (BMC_UDT_PROC_BNI00KM_Analog_Ch_3625US)

• Value (DINT) – Measurement Value
• Switch_Point_1 (BOOL) – Pre-Defined Limit value
• Switch_Point_2 (BOOL) – Pre-Defined Limit Value
• Underflow (BOOL) – Analog Signal Below Threshold
• Overflow (BOOL) – Analog Signal Above Threshold

4.1.1.3 Port_X03 (BMC_UDT_PROC_BNI00KM_Analog_Ch_3625US)

• Value (DINT) – Measurement Value
• Switch_Point_1 (BOOL) – Pre-Defined Limit value
• Switch_Point_2 (BOOL) – Pre-Defined Limit Value
• Underflow (BOOL) – Analog Signal Below Threshold
• Overflow (BOOL) – Analog Signal Above Threshold

4.1.1.4 Port_X04 (BMC_UDT_PROC_BNI00KM_Analog_Ch_3625US)

• Value (DINT) – Measurement Value
• Switch_Point_1 (BOOL) – Pre-Defined Limit value
• Switch_Point_2 (BOOL) – Pre-Defined Limit Value
• Underflow (BOOL) – Analog Signal Below Threshold
• Overflow (BOOL) – Analog Signal Above Threshold

4.1.1.5 Port_X05 (BMC_UDT_PROC_BNI00KM_Analog_Ch_3625US)

• Value (DINT) – Measurement Value
• Switch_Point_1 (BOOL) – Pre-Defined Limit value
• Switch_Point_2 (BOOL) – Pre-Defined Limit Value
• Underflow (BOOL) – Analog Signal Below Threshold
• Overflow (BOOL) – Analog Signal Above Threshold

4.1.1.6 Port_X06 (BMC_UDT_PROC_BNI00KM_Analog_Ch_3625US)

• Value (DINT) – Measurement Value
• Switch_Point_1 (BOOL) – Pre-Defined Limit value
• Switch_Point_2 (BOOL) – Pre-Defined Limit Value
• Underflow (BOOL) – Analog Signal Below Threshold
• Overflow (BOOL) – Analog Signal Above Threshold

4.1.1.7 Port_X07 (BMC_UDT_PROC_BNI00KM_Analog_Ch_3625US)

• Value (DINT) – Measurement Value
• Switch_Point_1 (BOOL) – Pre-Defined Limit value
• Switch_Point_2 (BOOL) – Pre-Defined Limit Value
• Underflow (BOOL) – Analog Signal Below Threshold
• Overflow (BOOL) – Analog Signal Above Threshold

4.1.1.8 Port_X08 (BMC_UDT_PROC_BNI00KM_Analog_Ch_3625US)

• Value (DINT) – Measurement Value
• Switch_Point_1 (BOOL) – Pre-Defined Limit value
• Switch_Point_2 (BOOL) – Pre-Defined Limit Value
• Underflow (BOOL) – Analog Signal Below Threshold
• Overflow (BOOL) – Analog Signal Above Threshold

• Port_X01 (BOOL)
• Port_X02 (BOOL)
• Port_X03 (BOOL)
• Port_X04 (BOOL)
• Port_X05 (BOOL)
• Port_X06 (BOOL)
• Port_X07 (BOOL)
• Port_X08 (BOOL)

The following events can generate errors on the port.

• Short circuit at Pin 1
• Wire break at Pin 1
• Wire break at Pin 2 / Pin 4

• LowUS1 (BOOL) – Sensor Supply Undervoltage (<=17V)
• HighUS1 (BOOL) – Sensor Supply Overvoltage (>=31V)

The device offers 4 digital logic blocks that can be configured as AND/NOR/OR/ONE-SHOT. Each of these logic blocks has 4 input signals. These input signals are evaluated cyclically according to the cycle time.  These can be configured via the Web User Interface or with explicit messages using the MSG instruction.  Once configured, a single discrete output will be energized once the configured block conditions are true.

• Block_1_Result (BOOL)
• Block_2_Result (BOOL)
• Block_3_Result (BOOL)
• Block_4_Result (BOOL)

• Vibration_Alarm (BOOL) – Threshold value for the detection of excessive vibrations
• Inclination_Alarm (BOOL) – Deviation from the reference inclination
  • 
• Temperature_Alarm (BOOL) – Upper or Lower threshold value for temperature

Consists of tags needed to pass input process data to PLC.  IO-Link diagnostic data is only available from Balluff EtherNet/IP IO-Link masters. For more details, please reference IO-Link master user manual under “IO-Link Input Data”.  A description of this UDT and its function is included here:

• • • DeviceOK – Port in IO-Link mode, device is connected, vendor and device ID match.
    • MismatchFault – Port in IO-Link mode, device is connected, vendor or device ID does not match.
    • CommFault – Port in IO-Link mode, device not connected
    • ValidationFailed – Validation failed
    • ProcessDataInvalid – Process data invalid
    • DSValidationFailure – Data storage validation failure
    • IOLShortCircuit – IO-Link short-circuit
    • Event – IO-Link slave device event codes – 9 bytes – 3 event buffer - FIFO
    • VendorID – 2-byte vendor ID
    • DeviceID – 3-byte device ID

The IO_Link_Port_Data UDT consists of the 48 input bytes (SINTs) and 48 output bytes (SINTs) that the IO-Link master allocates to each port.  Under normal operating conditions, the user will not be aware of any data being passed through this UDT.  The AOI automates the parsing of the data for each port and allows the user to access the data directly without mapping each of the four port’s data into the master’s single data buffer.  This UDT is used for both the IO-Link master AOI as well as each IO-Link slave AOI.  The master and slave must share the same tag name for the corresponding port.

• Inputs – this 48-byte SINT array contains all raw input data values being passed from the IO-Link slave device input array to the master device input array.
• Outputs – this 48-byte SINT array contain all raw output data values being passed from the IO-Link slave device output array to the master device output array.

• BMC_AOI_PROC_BNI00KM_3625US- Declaring an instance of the AOI.
• IO_Link_Port_Data – Pointer to IO-Link master port data. Contains both input and output process data from an IO-Link device connected to that specific port.
• Mapped_BNI00KM_Data – UDT Mapped data specific to the BNI00KM process data.

The following terms are used in this guide with these definitions:

• Controller Organizer – the area of RSLogix5000 where all project components can be accessed.  If this toolbar is not visible, it can be opened by pressing Alt+0.

• AOI – Add-On Instruction – reusable software module created with RSLogix5000.  Balluff’s AOI modules are composed of UDTs and associated logic to implement control algorithms.  This module is hardware specific.  All AOI modules contained in a project will be in the Controller Organizer as shown below:

• Controller scoped tag – a tag of any valid data type that is available to all programs within a project and must be used uniformly throughout the entire project.
• AOI Parameter – a tag of any valid data type that is created during the definition of the AOI module and is isolated to that AOI.  Its scope is limited to each discrete use of the AOI function.
• UDT – User-Defined Data Type – reusable software module created with RSLogix5000.  Balluff’s UDTs define the input and output tag names to be used when implementing our AOI modules.  A UDT can be composed of any combination of standard Data Types defined by RSLogix5000 or other UDTs.  All UDTs contained in a project will be in the Controller Organizer as shown below:

• I/O Configuration Tree – the area of RSLogix5000 where all physical, or “real world”, Inputs and Outputs associated with the controller are defined.  One example of an I/O Configuration Tree is shown below:

• EDS – Electronic Data Sheet – software configuration file that defines how a hardware product will communicate with the network master using EtherNet/IP.  The format and content of an EDS is defined by ODVA, the controlling organization for EtherNet/IP specifications.

The following Balluff documents support the release of this User Guide and its related software module.  Each of these documents can be obtained by contacting Balluff Technical Support at [email protected].

• AOI_BNI006A_05_31_040 User Guide
• BNI EIP-508-105-Z015 User’s Guide
• BNI LH5-72-S51-Z012 Configuration Guide
• BNI LH5-72-S51-Z012 Manual

Bit Mapping BNI00KM Excel Workbook