Quick Start Guide. Distributed Modular I/O Quick Start Guide for 4 port IO-Link Master. Communication. Analog I/O Outputs

Transcription

1 Distributed Modular I/O Quick Start Guide for 4 port IO-Link Master Power Communication Discrete I/O Discrete I/O Analog I/O Outputs Specialty BNI004A BNI EIP Z015 Power Discrete I/O Quick Start Guide Discrete I/O Analog I/O Valve Manifold Control RFID or Specialty Devices

2 Connect the Distributed Modular I/O Master Block 1 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 Function Description Network 1 TX + Transmit Data + Pushbutton Display IP address subnet mask gateway 2 RX + Receive Data + 3 TX - Transmit Data - 4 RX - Receive Data - Aux Power 7/8" Auxiliary Power Port Pin Function Description V Actuator Supply V Sensor/Bus Communication Supply Port 0 Port V Sensor/Bus Communication Supply V Actuator Supply Port 1 Port 2 IO-Link Port 5 Port 6 IO-Link 3 M12 I/O Port Pin Configurable Port IO-Link Port V + 24 V 2 Input 2 or Output 2 Input/Output 2 Port 3 IO-Link Port 7 IO-Link V 0 V 4 Input 1 or Output 1 IO-Link or Input/Output 1 5 FE FE 2

3 2 Tell the Controller About the Device 1. Every controller will need to know three things about the device being connected over EtherNet/IP: The IP address of the block Where to look for the data (Instance ID) in the block 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. Using Electronic Data Sheet (EDS) Files 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. Instance ID Data Length (Bytes) Input Output Configuration 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: For assistance with programming these values into a specific controller or engineering software, please contact the controller manufacturer. Some controllers have a maximum data size below the 200 bytes required, review the parameters of the controller before selecting. 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. 3

4 Confirm Communication is Established 3 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: Some controllers require a power cycle of the device or the controller or both before the communication is established. Make sure there are no IP Address conflicts between devices. Ensure that the devices are connected on the same LAN or hardwired network. 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

5 Configure IO-Link Ports for Distributed Modular I/O 4 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 IO-Link 1 IO-Link 3 Configuration Data Breakdown Description Byte Bit For Standard I/O: 0x00 0 IO-Link 2 IO-Link For IO-Link: 0x01 1 IO-Link 4 IO-Link 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 5

6 5a Reading the Process Data Inputs 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 (bytes of data in the input buffer of the master block) Description Byte Bit (block pin #) Input Data (Pin Number of Input) Short Circuit (Pin1 to Pin3) 2 Port 3 Port 2 Port 1 Port 0 (Port Number of Status) 3 Port 7 Port 6 Port 5 Port 4 Overload Status (Pin Number of Output) Aux Power Status OK US UA Reserved Data IO-Link Ports Input Data Description IO-Link 1 IO-Link 2 IO-Link 3 IO-Link 4 Bit IO-Link Slave Device Specific Data IO-Link Slave Device - 32 bytes of Input (For bitmap details, see slave device manual) DC: Device Connected IOL: IO-Link Mode OK (organized by bytes of data in the input buffer of the master block) DC IOL VF: not typically used, see the manual VF This tells you the slave device s vendor info 42, 43 90, , , 187 IO-Link Slave Device Vendor ID Data This tells you the part number of the device IO-Link Slave Device Device ID Data Newest Error Reported IO-Link Slave Device Error Code Event #1 (For code details, see slave device manual) IO-Link Slave Device Error Code Event #2 Oldest Error Reported IO-Link Slave Device Error Code Event #3 6

7 5b Reading the Process Data Outputs 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 (organized by bytes of data in the input buffer of the master block) Description Byte Bit (block pin #) Output Data (Pin Number of Output) 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 DL GN RD IO-Link Ports Output Data (organized by bytes of data in the input buffer of the master block) Description IO-Link 1 IO-Link 2 IO-Link 3 IO-Link 4 Bit IO-Link Slave Device Specific Data IO-Link Slave Device - 32 bytes of Output (For bitmap details, see slave device manual) 7

8 Doc. No /Mat. No Edition 1209 Product specifications, availability, and pricing are subject to change without notice. Additional Resources - available on the web 6 Add-on-Instructions (AOI) for use with Allen Bradley PLCs USA Balluff Inc Holton Drive Florence, KY Phone: (859) Toll-free: Fax: (859) balluff@balluff.com Web: Manuals for detailed technical information about IO-Link master and slave devices Networking & Connectivity Catalog for selecting specific part numbers & accessories Canada Balluff Canada, Inc Argentia Road, Unit #2 Mississauga, Ontario L5N 8G4 Phone: (905) Toll-free: Fax: (905) balluff.canada@balluff.ca Web: Whitepaper for detailed information about the benefits of Distributed Modular I/O with IO-Link Visit our website to see more information on IO-Link, including full product technical specs, applications, brochures, and more. networks.balluff.com Mexico Balluff de Mexico S.A. de C.V Anillo Vial II Fray Junípero Serra No. Colonia La Vista Residencial Querétaro, QRO Phone: ( ) Fax: ( ) balluff.mexico@balluff.com Web: Distributed Modular I/O Overview Brochure