893234 distributed modular i/o quick start guide for 4 port io-link master
DESCRIPTION
A step-by-step guide to setting up and configuring the IO-Link master for EtherNet/IP BNI EIP-502-105-Z015. This guide will help with:--- downloading and installing EDS files- I/O port configuration- IO-Link port configuration- reading process data- troubleshootingTRANSCRIPT
Distributed Modular I/O Quick Start Guide for 4 port IO-Link Master
Co
mm
unic
atio
n
Dis
cret
e I/
O
Dis
cret
e I/
O
Ana
log
I/O
Out
put
s
Sp
ecia
lty
Po
wer
Power
DiscreteI/O
AnalogI/O
Valve ManifoldControl
RFID or Specialty Devices
DiscreteI/O
Quick Start Guide
BNI004ABNI EIP-502-105-Z015
2
Connect the Distributed Modular I/O Master Block
11. 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.
Port 0
Port 1
Port 2
Port 3
Port 4
Port 5
Port 6
Port 7
IO-Link 1
IO-Link 2
IO-Link 3
IO-Link 4
Pin Function Description
1 TX + Transmit Data +
2 RX + Receive Data +
3 TX - Transmit Data -
4 RX - Receive Data -
M12 Network Port
Pin Function Description
1 + 24 V Actuator Supply
2 + 24 V Sensor/Bus Communication Supply
3 0 V Sensor/Bus Communication Supply
4 0 V Actuator Supply
7/8" Auxiliary Power Port
Pin Configurable Port IO-Link Port
1 + 24 V + 24 V
2 Input 2 or Output 2 Input/Output 2
3 0 V 0 V
4 Input 1 or Output 1 IO-Link or Input/Output 1
5 FE FE
M12 I/O Port
Network
Aux Power
Pushbutton DisplayIP address subnet mask gateway
00 01
04
1514
1312
1110
09
06 07
08
05
0302
3
Tell the Controller About the Device
21. 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 Data Length (Bytes)
Input 100 200
Output 101 134
Configuration 102 98
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.
Troubleshooting Tips:n For assistance with programming these values into a specific controller or
engineering software, please contact the controller manufacturer.n Some controllers have a maximum data size below the 200 bytes required,
review the parameters of the controller before selecting.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.
Using Electronic Data Sheet (EDS) Files
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
4
Confirm Communication is Established
3It 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 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.
Solid GreenSolid green at 100Mbps, off if using 10Mbps
Intermittent flashing orange
Functional Communication Is Established:
Depending on which port has the cable plugged into it, these could be on or off
5
Configure IO-Link Ports for Distributed Modular I/O
4Once 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.
Description Byte Bit
7 6 5 4 3 2 1 0
For Standard I/O: 0x00For IO-Link: 0x01
0 IO-Link 2 IO-Link 1 0 0 0 0
1 IO-Link 4 IO-Link 3 0 0 0 0
2...97 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.
Configuration Data BreakdownReference Image for the IO-Link Port numbering
IO-Link 1 IO-Link 3
IO-Link 2 IO-Link 4
6
Reading the Process Data – Inputs
5aIt 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.
Description Byte Bit (block pin #)
7 6 5 4 3 2 1 0
Input Data(Pin Number of Input)
0 07 06 05 04 03 02 01 00
1 15 14 13 12 11 10 09 08
Short Circuit (Pin1 to Pin3)(Port Number of Status)
2 Port 3 Port 2 Port 1 Port 0
3 Port 7 Port 6 Port 5 Port 4
Overload Status(Pin Number of Output)
4 07 06 05 04 03 02 01 00
5 15 14 13 12 11 10 09 08
Aux Power Status OK 6 0 0 0 0 0 0 US UA
Reserved Data 7 0 0 0 0 0 0 0 0
Description IO-Link 1 IO-Link 2 IO-Link 3 IO-Link 4 Bit
7 6 5 4 3 2 1 0
IO-Link Slave Device Specific Data 8...39 56.. 87 104...135 152...183 IO-Link Slave Device - 32 bytes of Input(For bitmap details, see slave device manual)
DC: Device ConnectedIOL: IO-Link Mode OK
40 88 136 184 0 0 0 0 0 0 DC IOL
VF: not typically used, see the manual. 41 89 137 185 0 0 0 0 0 0 0 VF
This tells you the slave device’s vendor info 42, 43 90, 91 138, 139 186, 187 IO-Link Slave Device – Vendor ID Data
This tells you the part number of the device 44...46 92...94 140...142 188...190 IO-Link Slave Device – Device ID Data
Newest Error Reported 47...49 95..97 143...145 191...193 IO-Link Slave Device – Error Code Event #1
(For code details, see slave device manual) 50...52 98...100 146...148 194...196 IO-Link Slave Device – Error Code Event #2
Oldest Error Reported 53...55 101...103 149...151 197...199 IO-Link Slave Device – Error Code Event #3
IO-Link Ports – Input Data
Standard 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 – Outputs
5bIt 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.
Description Byte Bit (block pin #)
7 6 5 4 3 2 1 0
Output Data(Pin Number of Output)
0 07 06 05 04 03 02 01 00
1 15 14 13 12 11 10 09 08
Restart Output (after overload)(Pin Number of Output)
2 07 06 05 04 03 02 01 00
3 15 14 13 12 11 10 09 08
Reserved Data 4 0 0 0 0 0 0 0 0
DL: Display Lock / PLC LockGN: Display Green LEDs ONRD: Display Red LEDs ON
5 0 0 0 0 0 DL GN RD
Standard Output Data
IO-Link Ports – Output Data
Description IO-Link 1 IO-Link 2 IO-Link 3 IO-Link 4 Bit
7 6 5 4 3 2 1 0
IO-Link Slave Device Specific Data 6...37 38...69 70...101 102...133 IO-Link 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
6
networks.balluff.com
USA Balluff Inc. 8125 Holton DriveFlorence, KY 41042Phone: (859) 727-2200 Toll-free: 1-800-543-8390Fax: (859) 727-4823 E-Mail: [email protected]: www.balluff.us
MexicoBalluff de Mexico S.A. de C.V 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: [email protected]: www.balluff.mx
CanadaBalluff Canada, Inc. 2840 Argentia Road, Unit #2Mississauga, Ontario L5N 8G4Phone: (905) 816-1494Toll-free: 1-800-927-9654Fax: (905) 816-1411E-mail: [email protected]: www.balluff.ca
Networking & Connectivity Catalog for selecting specific part numbers & accessories
Whitepaper for detailed information about the benefits of Distributed Modular I/O with IO-Link
Add-on-Instructions (AOI) for use with Allen Bradley PLCs
Distributed Modular I/O Overview Brochure
Manuals 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.
Doc. N
o. 893234/Mat. N
o. 228088 • Ed
ition 1209 • Prod
uct specifications,
availability, and
pricing are sub
ject to change without notice.