Sie sind auf Seite 1von 8

Distributed Modular I/O Quick Start Guide for 4 port IO-Link Master

Communication

Discrete I/O

Discrete I/O

Analog I/O

Specialty

Outputs

Power

BNI004A BNI EIP-502-105-Z015

Power

Discrete I/O

Quick Start Guide

Discrete I/O

Analog I/O

Valve Manifold Control

RFID or Specialty Devices

Connect the Distributed Modular I/O Master Block

1. Using an M12 D-coded EtherNet/IP cable, connect the block to the Ethernet network. 2. Power up the block using 24VDC 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 manual. M12 Network Port Pin Network Pushbutton Display
IP address subnet mask gateway

Function TX + RX + TX RX -

Description Transmit Data + Receive Data + Transmit Data Receive Data -

1 2 3 4

Aux Power

7/8" Auxiliary Power Port Pin 1 2 Function + 24 V + 24 V 0V 0V Description Actuator Supply Sensor/Bus Communication Supply Sensor/Bus Communication Supply Actuator Supply

Port 0
00 01 08 09

Port 4

3 4

Port 1
02 03 10 11

Port 5

M12 I/O Port Pin 1 2 3 4 5 Configurable Port + 24 V Input 2 or Output 2 0V Input 1 or Output 1 FE IO-Link Port + 24 V Input/Output 2 0V IO-Link or Input/Output 1 FE 2

Port 2 IO-Link 1 Port 3 IO-Link 2

04

05

12

13

Port 6 IO-Link 3 Port 7 IO-Link 4

06

07

14

15

Tell the Controller About the Device

1. 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 ID: where the data is located in the device, sometimes called the assembly instance number. Data 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 spreadsheet.

Using Electronic Data Sheet (EDS) Files

Instance ID Input Output Configuration 100 101 102

Data Length (Bytes) 200 134 98

The EDS file in RSLogix5000 Ver 20 To make life easier for some engineering platforms the eds files are available for download from networks.balluff.com

Troubleshooting Tips:

n For assistance with programming these values into a specific controller or


engineering software, please contact the controller manufacturer. review the parameters of the controller before selecting.

n Some controllers have a maximum data size below the 200 bytes required, n Some controllers are using a third party device (such as an Anybus gateway)
to communicate over EtherNet/IP. These devices typically require additional software to configure and establish communication properly.

Confirm Communication is Established

It 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.

Functional Communication Is Established:

Solid Green

Solid green at 100Mbps, off if using 10Mbps Intermittent flashing orange

Depending on which port has the cable plugged into it, these could be on or off

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 devices. n Ensure that the devices are connected on the same LAN or hardwired network. 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. 4

Configure IO-Link Ports for Distributed Modular I/O

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 setup.

Reference Image for the IO-Link Port numbering

Configuration Data Breakdown Description For Standard I/O: 0x00 For IO-Link: 0x01 Byte 0 1 2...97 Bit 7 6 5 4 3 2 0 0 1 0 0 0 0 0 IO-Link 2 IO-Link 1 0 IO-Link 4 IO-Link 3 0

IO-Link 1

IO-Link 3

Most customers do not use this functionality. It is used for validation of slave device details like: Vendor ID, Device ID or Serial Number. Please consult the manual for details.

IO-Link 2

IO-Link 4

Reading the Process Data Inputs

5a

It 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 there.

Standard Input Data Description Input Data (Pin Number of Input) Short Circuit (Pin1 to Pin3) (Port Number of Status) Overload Status (Pin Number of Output) Aux Power Status OK Reserved Data

(bytes of data in the input buffer of the master block) Byte 7 0 1 2 3 4 5 6 7 07 15 6 06 14 5 05 13 Bit (block pin #) 4 04 12 3 03 11 2 02 10 1 01 09 0 00 08

Port 3 Port 7 07 15 0 0 06 14 0 0

Port 2 Port 6 05 13 0 0 04 12 0 0

Port 1 Port 5 03 11 0 0 02 10 0 0

Port 0 Port 4 01 09 US 0 00 08 UA 0

IO-Link Ports Input Data Description

(organized by bytes of data in the input buffer of the master block) IO-Link 1 8...39 40 41 42, 43 44...46 47...49 50...52 53...55 IO-Link 2 56.. 87 88 89 90, 91 92...94 95..97 98...100 101...103 IO-Link 3 104...135 136 137 138, 139 140...142 143...145 146...148 149...151 IO-Link 4 7 6 5 4 152...183 184 185 186, 187 188...190 191...193 194...196 197...199 Bit 3 2 1 0 IO-Link Slave Device - 32 bytes of Input (For bitmap details, see slave device manual) 0 0 0 0 0 0 0 0 0 0 0 0 DC 0 IOL VF

IO-Link Slave Device Specific Data DC: Device Connected IOL: IO-Link Mode OK VF: not typically used, see the manual. This tells you the slave devices vendor info This tells you the part number of the device Newest Error Reported (For code details, see slave device manual) Oldest Error Reported

IO-Link Slave Device Vendor ID Data IO-Link Slave Device Device ID Data IO-Link Slave Device Error Code Event #1 IO-Link Slave Device Error Code Event #2 IO-Link Slave Device Error Code Event #3 6

Reading the Process Data Outputs

5b

It 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, it will be an output there. There are diagnostic inputs available that will indicate an overload on an output from the master block.

Standard Output Data Description Output Data (Pin Number of Output)

(organized by bytes of data in the input buffer of the master block) Byte 7 0 1 2 3 4 5 07 15 07 15 0 0 6 06 14 06 14 0 0 5 05 13 05 13 0 0 Bit (block pin #) 4 04 12 04 12 0 0 3 03 11 03 11 0 0 2 02 10 02 10 0 DL 1 01 09 01 09 0 GN 0 00 08 00 08 0 RD

Restart Output (after overload) (Pin Number of Output) Reserved Data DL: Display Lock / PLC Lock GN: Display Green LEDs ON RD: Display Red LEDs ON

IO-Link Ports Output Data Description IO-Link Slave Device Specific Data

(organized by bytes of data in the input buffer of the master block) IO-Link 1 6...37 IO-Link 2 38...69 IO-Link 3 70...101 IO-Link 4 7 102...133 6 5 4 Bit 3 2 1 0 IO-Link Slave Device - 32 bytes of Output (For bitmap details, see slave device manual)

Additional Resources - available on the web

Add-on-Instructions (AOI) for use with Allen Bradley PLCs

Manuals for detailed technical information about IO-Link master and slave devices

Networking & Connectivity Catalog for selecting specific part numbers & accessories

Whitepaper for detailed information about the benefits of Distributed Modular I/O with IO-Link

Distributed Modular I/O Overview Brochure

Visit our website to see more information on IO-Link, including full product technical specs, applications, brochures, and more.

USA Balluff Inc. 8125 Holton Drive Florence, KY 41042 Phone: (859) 727-2200 Toll-free: 1-800-543-8390 Fax: (859) 727-4823 E-Mail: balluff@balluff.com Web: www.balluff.us

Canada Balluff Canada, Inc. 2840 Argentia Road, Unit #2 Mississauga, Ontario L5N 8G4 Phone: (905) 816-1494 Toll-free: 1-800-927-9654 Fax: (905) 816-1411 E-mail: balluff.canada@balluff.ca Web: www.balluff.ca

Mexico Balluff de Mexico S.A. de C.V Anillo Vial II Fray Junpero Serra No. Colonia La Vista Residencial Quertaro, QRO 76232 Phone: (++52 442) 212-4882 Fax: (++52 442) 214-0536 E-Mail: balluff.mexico@balluff.com Web: www.balluff.mx

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

networks.balluff.com