Quick Start Guide - Balluff

1 Distributed Modular I/O Quick Start Guide for 4 port IO-Link Master CommunicationDiscrete I/ODiscrete I/OAnalog I/OOutputsSpecialtyPowerPowerDiscreteI/O AnalogI/OValve ManifoldControlRFID or Specialty DevicesDiscreteI/OQuick Start GuideBNI004 ABNI EIP-502-105-Z0152 Connect the Distributed Modular I/O Master Block11. Using an M12 D-coded EtherNet/IP cable, connect the block to the Ethernet network. 2. Power up the block using 24 VDC and a 7/8" 4pole connector wired according to the below diagram. 3. Set the IP address of the block using the pushbutton display. For instructions on operating the display, see the 0 Port 1 Port 2 Port 3 Port 4 Port 5 Port 6 Port 7IO-Link 1IO-Link 2IO-Link 3IO-Link 4 PinFunctionDescription1TX +Transmit Data +2RX +Receive Data +3TX -Transmit Data -4RX -Receive Data -M12 Network PortPinFunctionDescription1+ 24 VActuator Supply2+ 24 VSensor/Bus Communication Supply30 V Sensor/Bus Communication Supply40 VActuator Supply7/8" Auxiliary Power PortPinConfigurable PortIO-Link Port1+ 24 V+ 24 V2 Input 2 or Output 2 Input/Output 230 V0 V4 Input 1 or Output 1IO-Link or Input/Output 15 FEFEM12 I/O PortNetworkAux PowerPushbutton DisplayIP address subnet mask gateway 000104151413121110090607080503023 Tell the Controller About the Device21.

2 Every controller will need to know three things about the device being connected over EtherNet/IP: n The IP address of the block n Where to look for the data (Instance ID) in the block n How much data is at the location (Data length) 2. Setup the block in the engineering software with the Instance ID and the Data Length for the input data, the output data and the configuration data. Instance IDData Length (Bytes)Input100200 Output101134 Configuration10298 Instance ID: where the data is located in the device, sometimes called the assembly instance length: how much data to expect at this location, these are 8bit, 1byte short integers. For controllers that read in 2byte words or in individual bit counts, please see the Balluff website for the data assistance Tips:n For assistance with programming these values into a specific controller or engineering software, please contact the controller Some controllers have a maximum data size below the 200 bytes required, review the parameters of the controller before Some controllers are using a third party device (such as an Anybus gateway) to communicate over EtherNet/IP.

3 These devices typically require additional software to configure and establish communication properly. Using Electronic Data Sheet (EDS) FilesThe EDS file in RSLogix5000 Ver 20 To make life easier for some engineering platforms the eds files are available for download from Communication is Established3It is important to confirm the device is talking to the controller; this can be done by verifying status lights on the block just below the aux power ports and just above the first M12 I/O ports. Troubleshooting Tips:n Some controllers require a power cycle of the device or the controller or both before the communication is established. n Make sure there are no IP Address conflicts between Ensure that the devices are connected on the same LAN or hardwired network.

4 N EtherNet/IP DLR (Device Level Ring) capable devices ship with the default setting, DLR enabled. Some controllers may require that the device has this functionality disabled before communication can be established. Solid GreenSolid green at 100 Mbps, off if using 10 MbpsIntermittent flashing orangeFunctional Communication Is Established:Depending on which port has the cable plugged into it, these could be on or off5 Configure IO-Link Ports for Distributed Modular I/O4 Once communication is established you now need to tell the device how it will be used for Distributed Modular I/O. Every port can be used for standard I/O and is defaulted to this configuration. To tell the master block to look for an IO-Link device, there are some configuration bytes that must be Standard I/O: 0x00 For IO-Link: 0x010IO-Link 2IO-Link 100001IO-Link 4IO-Link customers do not use this functionality.

5 It is used for validation of slave device details like: Vendor ID, Device ID or Serial Number. Please consult the manual for Data BreakdownReference Image for the IO-Link Port numberingIO-Link 1IO-Link 3IO-Link 2IO-Link 46 Reading the Process Data Inputs5aIt is important to note that every standard I/O on the block is setup as a freely configurable port. If the controller is programmed to look for an input and there is an input wired there, it will be an input. If the controller is programmed to fire an output, the block will drive an output (block pin #)76543210 Input Data(Pin Number of Input)0070605040302010011514131211100908 Short Circuit (Pin1 to Pin3)(Port Number of Status)2 Port 3 Port 2 Port 1 Port 03 Port 7 Port 6 Port 5 Port 4 Overload Status(Pin Number of Output)407060504030201005151413121110090 8 Aux Power Status OK6000000 USUAR eserved Data700000000 DescriptionIO-Link 1IO-Link 2IO-Link 3IO-Link 4 Bit76543210IO-Link Slave Device Specific Slave Device - 32 bytes of Input(For bitmap details, see slave device manual)DC: Device ConnectedIOL: IO-Link Mode OK4088136184000000 DCIOLVF.

6 Not typically used, see the tells you the slave device s vendor info42, 4390, 91138, 139186, 187IO-Link Slave Device Vendor ID DataThis tells you the part number of the Slave Device Device ID DataNewest Error Slave Device Error Code Event #1(For code details, see slave device manual) Slave Device Error Code Event #2 Oldest Error Slave Device Error Code Event #3IO-Link Ports Input DataStandard Input Data(organized by bytes of data in the input buffer of the master block)(bytes of data in the input buffer of the master block)7 Reading the Process Data Outputs5bIt is important to note that every standard I/O on the block is setup as a freely configurable port. If the controller is programmed to look for an input and there is an input wired there, it will be an input.

7 If the controller is programmed to fire an output, it will be an output there. There are diagnostic inputs available that will indicate an overload on an output from the master (block pin #)76543210 Output Data(Pin Number of Output)007060504030201001151413121110090 8 Restart Output (after overload)(Pin Number of Output)207060504030201003151413121110090 8 Reserved Data400000000DL: Display Lock / PLC LockGN: Display Green LEDs ONRD: Display Red LEDs ON500000 DLGNRDS tandard Output DataIO-Link Ports Output DataDescriptionIO-Link 1IO-Link 2IO-Link 3IO-Link 4 Bit76543210IO-Link Slave Device Specific Slave Device - 32 bytes of Output(For bitmap details, see slave device manual)(organized by bytes of data in the input buffer of the master block)(organized by bytes of data in the input buffer of the master block)Additional Resources - available on the web USA Balluff Inc.

8 8125 Holton DriveFlorence, KY 41042 Phone: (859) 727-2200 Toll-free: 1-800-543-8390 Fax: (859) 727-4823 E-Mail: de Mexico de Anillo Vial II Fray Jun pero Serra No. Colonia La Vista Residencial Quer taro, QRO 76232 Phone: (++52 442) 212-4882 Fax: (++52 442) 214-0536 E-Mail: Canada, Inc. 2840 Argentia Road, Unit #2 Mississauga, Ontario L5N 8G4 Phone: (905) 816-1494 Toll-free: 1-800-927-9654 Fax: (905) 816-1411E-mail: & Connectivity Catalog for selecting specific part numbers & accessoriesWhitepaper for detailed information about the benefits of Distributed Modular I/O with IO-LinkAdd-on-Instructions (AOI) for use with Allen Bradley PLCsDistributed Modular I/O Overview BrochureManuals for detailed technical information about IO-Link master and slave devices Visit our website to see more information on IO-Link, including full product technical specs, applications, brochures, and more.

9 Doc. No. 893234/Mat. No. 228088 Edition 1209 Product specifications, availability, and pricing are subject to change without notice.