This User Guide describes the installation, use and maintenance of the Add On Instruction (AOI) software module for the BNI EIP-502-105-Z015. This software module is designed for use with RSLogix5000.

This guide was developed for use with the software module AOI_BNI004A_40_27_041.L5X. This software module is available for download at the website www.balluff.com

This software module was developed for use with the Balluff EtherNet/IP Connectivity block BNI EIP508-105-Z015 (hardware version 5.0, firmware version 3.1).

For the development of this software module and hardware configuration, the following system components were used and validated:

• RSLogix5000, version 18.01 (or later)
• Rockwell 1756-L63 controller

This section describes the process for installing and using the AOI module. This is a three step process that must be followed sequentially: hardware configuration; import AOI module along with all associated UDTs; and create new ladder logic with AOI modules.

Balluff EtherNet/IP IO-Link Master Features

Configuring the BNI EIP-508-105-Z015 in RSLogix5000

1. Establish 1756-ENxx communication module in I/O Configuration
   
    
2. Right click 1756-ENxx and choose New Module:
   
    
3. Choose ETHERNET MODULE – Generic Ethernet Module:
   
4. Establish properties of BNI EIP-508-105-Z015:
   

   communication format: Data - SINT
   Input Size: 392 Bytes	Assembly Instance: 100
   Output Size: 262 Bytes	Assembly Instance: 101
   Configuration Size: 194 Bytes	Assembly Instance 102

    
   
5. Depending on the application and network design, verify whether a Unicast connection is required:
   
   
6.  

Import Balluff IO-Link AOI

1. Right-click on the Add-On Instructions element of the Controller Organizer to view a menu that includes “Import Add-On Instruction…” as shown below:
   
2. Locate your folder containing the downloaded Balluff AOI modules, highlight AOI_BNI006A_50_31_040.L5X and click Import… 
   
3.  If the operation is successful, all UDTs associated with the AOI module will be imported into the project along with the AOI. This can be verified by checking the User-Defined element under Data Types in the Controller Organizer. 
   

Create logic using RSLogix5000

1. Once an AOI has been imported, it can be used in the same manner as other ladder instructions. A new Element Group tab will be displayed in RSLogix5000’s Language Element toolbar. This is shown here with the hover window information displayed:
   
2. The AOI module can now be added to a rung of ladder:
   
3. All parameters must be defined with tags of valid data type as defined by the AOI module. The user should create each Tag Name relevant to the user’s project.
   

   Parameter Name	Description	Data Type	Tag Name (User specific)
   AOI_BNI006A_50_31_040	Unique Control Tag for AOI Module	AOI_BNI006A_50_31_040	Master_Control_Tag
   BNI_EIP_508_Raw_Input Data	392 byte array of raw data from Hardware Module Defined Tags	SINT[392]	Module_Name.I.Data
   BNI_EIP_508_Raw_Output Data	262 byte array of raw data from Hardware Module Defined Tags	SINT[262]	Module_Name.I.Data
   BNI_EIP_508_Raw_Config_Data	194 byte array of raw data from Hardware Module Defined Tags	SINT[194]	Module_Name.I.Data
   BNI_EIP_508_Port_1_Data	All I/O Data Associated with IO-Link Port 1	IO_Link_Port_Data	Port1_Data
   BNI_EIP_508_Port_2_Data	All I/O Data Associated with IO-Link Port 2	IO_Link_Port_Data	Port2_Data
   BNI_EIP_508_Port_3_Data	All I/O Data Associated with IO-Link Port 3	IO_Link_Port_Data	Port3_Data
   BNI_EIP_508_Port_4_Data	All I/O Data Associated with IO-Link Port 4	IO_Link_Port_Data	Port4_Data
   BNI_EIP_508_Port_5_Data	All I/O Data Associated with IO-Link Port 5	IO_Link_Port_Data	Port5_Data
   BNI_EIP_508_Port_6_Data	All I/O Data Associated with IO-Link Port 6	IO_Link_Port_Data	Port6_Data
   BNI_EIP_508_Port_7_Data	All I/O Data Associated with IO-Link Port 7	IO_Link_Port_Data	Port7_Data
   BNI_EIP_508_Port_8_Data	All I/O Data Associated with IO-Link Port 8	IO_Link_Port_Data	Port8_Data
   Mapped_BNI_EIP_508_Data	All Unique data associated with BNI EIP-508 module	UDT_BNI006A_50_31_040	Mapped_Master_Data

    Note that in this example, Module_Name has been defined in the I/O Configuration Tree as Balluff_IO_Link_Master.

The User-Defined Data Type for the Add On Instruction defines the interface for the AOI and the user’s project. For AOI_BNI006A_50_31_040, the highest level UDT. UDT_BNI006A_50_31_040, is comprised of three sub-UDT components: Input (I), Output (O) and Configuration (C). One additional UDT is defined, IO_Link_Port_Data, for integrating data through configured IO-Link ports.

The highest level UDT (UDT_BNI006A_50_31_040) consists of the three sub-UDT components described in Sections 4.1 through 4.3 below.

The Input UDT (UDT_BNI006A_Inputs_50_31_040) consists of all inputs associated with the BNI004A block. A description of this UDT and its function is included here:

The Output UDT (UDT_BNI004A_Outputs_40_27_041) consists of all outputs associated with the BNI004A block. A description of this UDT and its function is included here:

The Configuration UDT (UDT_BNI004A_Configuration_40_27_041) consists of all IO-Link data associated with each port for the BNI004A block. A description of this UDT and its function is included here:

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.

If the preceding instructions (5.0 Instructions) have been successfully completed, the software module will be integrated into the RSLogix5000 project and it will be ready to use. The user will be able to verify the proper operation of the AOI by monitoring the transition of a controller-scoped tag and its corresponding real-world device. This section describes a sampling technique that will verify the proper operation of one input bit, one output bit, and a configuration parameter.

This example describes how to validate the transition of a controller-scoped input tag

This example uses Port 6, Pin 4 (Input buffer byte 0, bit 6) although any input bit will suffice. Note that all I/O points are freely configurable as either inputs or outputs and will respond to logic accordingly. The key point of this example is to ensure that the AOI bit corresponding to the selected input bit follows it. Place a device (discrete sensor or jumper wire) between pins 1 and 4 on Port 6 to cause this Input bit to transition to ON or “high”. This bit can be viewed in the Controller scope tags as shown below:

Note that when the AOI module was used in the logic, the parameter Mapped_BNI_EIP_502_Data was assigned to a tag named “Mapped_Master_Data”.

While this bit (Mapped_Master_Data.I.Data.12) is ON or “high”, the corresponding LED on the I/O block should be lit. If this is not the case, please refer to Section 7.0 Troubleshooting.

This example describes how to validate the transition of a controller-scoped output tag

This example uses Port 4, Pin 4 (Input buffer byte 0, bit 4) although any output bit will suffice. Note that all I/O points are freely configurable as either inputs or outputs and will respond to logic accordingly. The key point of this example is to ensure that the AOI bit corresponding follows the selected output bit. Place a device (pilot light, voltage meter or other discrete output device) between pins 1 and 4 on Port 4, then transition the output bit to ON or “high”. This bit can be viewed in the Controller scope tags as shown below:

Note that when the AOI module was used in the logic, the parameter Mapped_BNI_EIP_502_Data was assigned to a tag named “Mapped_Master_Data”.

While this bit is ON or “high”, the discrete output device should transition to its ON state, indicating that power is being passed to the device.

While this bit is ON or “high”, the corresponding LED on the I/O block should be lit. If this is not the case, please refer to Section 7.0 Troubleshooting.

After confirming the operation of this output bit, return the bit to “low” or OFF to ensure that the operation of logic is not affected.

This example describes how to validate the transition of a controller-scoped configuration tag

This example uses Port 1 Vendor ID although any configuration tag will suffice. The key point of this example is to ensure that the AOI value corresponding to the selected configuration value displays properly. this example will include a two-step process:

1. Configure Port 1 to IO-Link mode
   To configure Port 1 to IO-Link mode, set the value of the Port_1_Function tag equal to 1. After this tag has changed value, cycle the power to the BNI004A device in order for the port function change to take effect. After power is restored to the BNI004A, the Port 1 IO-Link LED will be lit steady green while an IO-Link device is connected (this LED will blink green if it is in IO-Link mode without an operational device connected). Your controller scope tags should look similar to this:  
   
2. Observe Balluff’s Vendor ID
   While any Balluff device is connected to Port 1 while this port is in IO-Link mode, the displayed Vendor ID should be 0378h or in decimal of 3(120). These values bit can be viewed in the Controller scope tags as shown below (the two screen shots are identical except for the “Style” column): 
   
   Note that this screen shot and the following screen shot display the same information except that two tags have been changed to Hex format. 
   
   Note that when the AOI module was used in the logic, the parameter Mapped_BNI_EIP_502_Data was assigned to a tag named “Mapped_Master_Data”. 

While any Balluff IO-Link device is connected to Port 1 in IO-Link mode, these values will be displayed. When the IO-Link slave is disconnected from Port 1, these values will return to 0. If this is not the case, please refer to Section 6.0 Troubleshooting.

All released Balluff AOI modules have been validated according to Balluff QF 4.4.12. A copy of this validation report can be obtained by contacting Balluff Technical Support at http://www.balluff.com/go/contact

• If the user does not obtain the results described in Section 5.0 above, please ensure that the following match those described in this User Guide: 
  
  • Hardware System layout – the system must consist of the following:
    • Rockwell Automation Logix processor 
    • Rockwell Logix EtherNet/IP network bridge
    • ODVA-compliant EtherNet/IP physical media
  • Software configurations – RSLogix5000 version 18.01 or higher must be used with this Add-On Instruction
  •  Revision levels
• After confirming the revision levels of all system components, the next step should be to observe the raw data from the EtherNet/IP master in RSLogix5000. This can be accomplished by observing each step through the process of an input bit through the raw data into the AOI data buffers.
  • The initial step is to confirm that the IO_Link_Port_Data tag for the input is received. For the controller-scoped input tag described in Section 5.2 (Port 6, Pin 4), you must observe Input buffer byte 0, bit 6 while the input has transitioned to “high” or ON as shown here:
     
  • To confirm the raw data for this same input bit, you must observe the Input buffer of the IO-Link master. Since this BNI0039 hub is connected to Port 1 of the master, the subject bit should be byte 8, bit 6 as shown here:
     
    Note that byte 8 corresponds only to Port 1 on the BNI004A master. This input bit will be indicated in byte 56 (Port 2), byte 104 (Port 3), or byte 152 (Port 4). 
• If all system components are consistent with those described in Section 6.1 above and the raw data is being received properly in RSLogix5000 but the user does not view AOI data as described in Section 5.1 above, additional steps can be taken to verify the proper operation of both the software configuration and the hardware system and components.
  • To validate the software configuration:
    • Ensure that the Balluff hardware is communicating properly with the Logix processor. A communication error is easily identified when RSLogix5000 is online with the processor as the network hardware will be identified with a yellow warning triangle when the communication fails.
    • Start a new RSLogix5000 project using only the Balluff hardware and AOI module. This should eliminate any potential software conflicts.
  • To validate the hardware system and components:
    • Remove all other hardware nodes from the Ethernet network so that only the Balluff module and the Logix processor are connected.
    • Verify that any switches used in the network layout are operating properly and have solid connections.
    • Identify and remove any potential sources of electrical noise or interference that might impede network communication.
• f the system still does not respond properly, please contact the Balluff Technical Support Group at http://www.balluff.com/go/contact

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 located 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 the each discrete use of 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 located 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 at the website www.balluff.com or by contacting Balluff Technical Support at http://www.balluff.com/go/contact

• IO-Link Master AOI User Guide
• Balluff device-specific hardware User Guides
• Using Explicit Messages to Configure IO-Link Devices Tech Note

Other documents – Each Balluff IO-Link device that may be connected to this IO-Link Master device will have its own User Guides, both for hardware and for the AOI module software.