Miniature Metal Flat Pack Inductive Sensors with IO-Link ... · troubleshooting 871FM miniature...

Miniature Metal Flat Pack Inductive Sensors with IO-LinkCatalog Numbers 871FM-M7BA20-x, 871FM-MV7BA20-FD02X, 871FM-M10BA30-x, 871FM-MV10BA30-x

User ManualOriginal Instructions

Important User Information

Read this document and the documents listed in the additional resources section about installation, configuration, and operation of this equipment before you install, configure, operate, or maintain this product. Users are required to familiarize themselves with installation and wiring instructions in addition to requirements of all applicable codes, laws, and standards.

Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are required to be carried out by suitably trained personnel in accordance with applicable code of practice.

If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be impaired.

In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment.

The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams.

No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this manual.

Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited

Throughout this manual, when necessary, we use notes to make you aware of safety considerations.

Labels may also be on or inside the equipment to provide specific precautions.

WARNING: Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to personal injury or death, property damage, or economic loss.

ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence.

IMPORTANT Identifies information that is critical for successful application and understanding of the product.

SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may be present.

BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach dangerous temperatures.

ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to potential Arc Flash. Arc Flash will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL Regulatory requirements for safe work practices and for Personal Protective Equipment (PPE).

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Who Should Use This Manual? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Overview and Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 1Product Overview Product Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2Installation Status Indication User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 3871FM Miniature Metal Flat Pack with IO-Link Overview

What Is IO-Link? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Why IO-Link? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Seamless Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Real-time Diagnostics and Trending . . . . . . . . . . . . . . . . . . . . . . . . 16Sensor Health Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Device Profiles and Automatic Device Configuration. . . . . . . . . 16Descriptive Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

How Does IO-Link Work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Transmission Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Transmission Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Response Time of the IO-Link System . . . . . . . . . . . . . . . . . . . . . . 17

IO-Link Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Process Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Value Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Device Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Access IO-Link Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Cyclic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Acyclic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Start-up the I/O System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Assign Device Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Premier Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20871FM Sensor IO-Link Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Correlation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Automatic Device Configuration (ADC) . . . . . . . . . . . . . . . . . . . . . . . 22

Rockwell Automation Publication 871FM-UM002A-EN-P - April 2017 3

Table of Contents

Chapter 4Configure the 871FM Sensor for IO-Link Mode

Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Example: Setup the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Chapter 5Create a Project Begin a New Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 6Configure the IO-Link Master Configuration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

AOP Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 7Connect the 871FM Sensor to the IO-Link Master

Connection Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 8Register the 871FM IODD Registration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 9Review the 1734-4IOL IO-Link AOP Overview — Device Parameter Behavior . . . . . . . . . . . . . . . . . . . . . . . . 47

Common Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Identification Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Observation Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Parameter Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Operation Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Sensor Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Counter/Timer Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Data Mapping Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Diagnosis Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Device Access Locks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Service Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Operation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Communication Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Manage Parameter Differences between IO-Link Devices and Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Chapter 10Install the 871FM Sample Code Add-On Instruction

Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59AOP Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Change Operation State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Chapter 11Troubleshooting Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

4 Rockwell Automation Publication 871FM-UM002A-EN-P - April 2017

Table of Contents

Appendix AInstall the Add-on Profile Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Perform the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Appendix BDevice Parameters Identification Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Observation Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Parameter Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Diagnosis Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Process Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Appendix CError Codes and Events Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Appendix DExplicit Messaging Examples Service Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Write Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Read Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Write Subindex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Read Subindex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Byte Swapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85


Table of Contents

Notes:


Preface

This manual is a reference guide for Bulletin 871FM inductive sensors with IO-Link. It describes the procedures that you use to install, configure, troubleshoot, and use these sensors.

Who Should Use This Manual?

Use this manual if you are responsible for installation, configuration, or troubleshooting 871FM miniature metal flat pack inductive sensors with IO-Link.

Overview and Benefits Rockwell Automation is the only supplier who provides every piece of the Connected Enterprise solution from top to bottom. Plus, exclusive features, and Premier Integration between Allen-Bradley components and an Integrated Architecture® system allow for a seamless connection and commission of control components. Empowers the ability to reap the benefits of an IO-Link solution with access to more detailed and customized plant-floor information than other solutions can offer.

Terminology The following abbreviations are used in this publication.

Table 1 - Abbreviations

Additional Resources These documents contain additional information concerning related products from Rockwell Automation.

You can view or download publications athttp://www.rockwellautomation.com/global/literature-library/overview.page. To order paper copies of technical documentation, contact your local Allen-Bradley distributor or Rockwell Automation sales representative.

Abbreviation DefinitionADC Automatic Device ConfigurationAOI Add-On InstructionAOP Add-on ProfileASN Application Specific NameIEC International Electrotechnical CommissionIODD I/O Device DescriptionNEC National Electric CodeQD Quick DisconnectSIO Standard I/O

Resource Description871FM Inductive Sensors with IO/Link Interface User Manual, Publication 871FM-UM001

Provides information to mount and install 871FM extended range sensors.

Industrial Automation Wiring and Grounding Guidelines, publication 1770-4.1

Provides general guidelines for installing a Rockwell Automation® industrial system.

Product Certifications website, http://www.rockwellautomation.com/global/certification/overview.page

Provides declarations of conformity, certificates, and other certification details.


http://literature.rockwellautomation.com/idc/groups/literature/documents/um/871fm-um001_-en-p.pdf

http://literature.rockwellautomation.com/idc/groups/literature/documents/in/1770-in041_-en-p.pdf

http://www.rockwellautomation.com/global/certification/overview.page?

http://www.rockwellautomation.com/global/certification/overview.page?

http://www.rockwellautomation.com/literature/

http://www.rockwellautomation.com/global/literature-library/overview.page

Preface

Notes:


Chapter 1

Product Overview

Product Description The Bulletin 871FM miniature metal flat pack inductive sensors are the result of a unique collection of enhancements—electrical and mechanical—that make these sensors the optimal solution for harsh duty applications. The machined stainless steel housing combines an unusually thick sensing face with one-piece construction. The result is a sensor that is exceptionally resistant to abrasion and impervious to fluid ingress, a feature especially crucial in applications that involve cutting fluids and chemical washdowns. The 871FM sensors stainless steel housing with metal face provides a more rugged solution in harsh environments.

The IO-Link interface enables consistent communication for diagnosing and parameterizing through to the sensor level and makes the intelligence that is already integrated in every 871FM inductive sensor fully available. These features provide particular advantages in the service area (fault elimination, maintenance, and device replacement), during commissioning (identification and configuration), and during operation (continuous parameter monitoring and online diagnosis). The 871FM sensor operates as a standard discrete sensor on pin four (black) or communicates via IO-Link on the same pin when connected to an IO-Link master.

Operating Modes The sensor can operate in two modes:• Standard I/O (SIO) Mode: The sensor default operation mode. The

sensor and its output act as a standard inductive sensor without IO-Link functionality. This mode of operation is active when the sensor is connected to a digital input device such as a PLC input module, a distribution box, or an input terminal connection.

• IO-Link Mode: This mode is automatically activated when the sensor is connected to an IO-Link enabled master device. Upon entering this mode, the yellow status indicator on the sensor stays solid to indicate that IO-Link communication has successfully been established with the master. The sensor transmits parameter and diagnostic information that can be accessed via PLC process data. No user intervention is required to enable this functionality within the sensor.


Chapter 1 Product Overview

Features • 10…30V DC operating voltage• Stainless steel housing• Equal sensing for both steel and aluminum • IP67/IP69K rated• 3- or 4-wire operation • IO-Link communication protocol helps minimize downtime and

increase productivity• IO-Link sensors are forward/backward compatible with standard

sensors: the same sensors and same cables that are used in IO-Link and non-IO-Link applications

• IO-Link provides– Remote detection of the health of the sensor– Margin status (low alarm)– Timer function

SpecificationsAttribute General-purpose Weld Field Immune

Load Current ≤ 100 mA; Auto detect (PNP/NPN) at power-up

Leakage Current ≤ 10 µA

Operator Voltage 10…30V

Voltage Drop ≤1.8V

Switching Frequency ≤200 Hz ≤50 Hz

Power-On Delay (Time delay before availability)

<80 ms

No-Load Supply Current ≤10 mA

Repeatability ≤5%

Hysteresis 5% typical

Protection Type False pulse on power, transient noise, reverse polarity, short circuit, and overload

Certifications c-UL-us Listed and CE Marked for all applicable directives

Enclosure Type Rating IP69K IP67

Housing Material Stainless Steel 303 with Stainless Steel face

Factor-1 equal sensing Yes

Connections 203.2 mm (8 in.) pigtail with 4-pin Micro QD

Operating Temperature -25…+70 °C (-13…+158 °F)

Storage Temperature -40…+70 °C (-40…+158 °F)

Operating Humidity 5…95% relative (noncondensing)

Shock 30 g (1.06 oz) with 11 ms pulse duration

Vibration 55 Hz, 1 mm amplitude

IO-Link

Protocol IO-Link V1.1

Interface Type IO-Link

Mode COM 2 (38.4 kBd)

Cycle Time 10.4 ms, minimum

SIO (standard I/O) Supported (pin 4 for either IO-Link or SIO)


Product Overview Chapter 1

Mounting Dimensions are shown in mm (in.).

20 (W) x 32 (L) x 8 (H) mm[0.94 (W) x 1.25 (L) x 0.31 (H) in.]

A B C D E

7 mm Sensing 24 (0.94) 35 (1.38) 20 (0.79) 20 (0.79) 48 (1.89)

30 (W) x 52 (L) x 14 (H) mm[1.18 (W) x 2.04 (L) x 0.55 (H) in.]

10 mm Sensing 45 (1.77) 45 (0.79) 30 (1.18) 30 (1.18) 90 (3.54)


Chapter 1 Product Overview

Notes:


Chapter 2

Installation

Status Indication User Interface

Table 2 - Standard I/O Operation

Table 3 - IO-Link Operation

Mounting Securely mount the sensor on a firm, stable surface or support for more reliable operation. Mounting that is subject to excessive vibration or shifting could cause intermittent operation. Once securely mounted, the sensor can be wired per the wiring instructions in the next section.

The location of the target in relation to the sensor face can require you to adjust the sensor mounting. The 871FM sensor offers margin indication through the orange status indicator. The status indicator blinks when the target is 80% of the maximum sensing distance or farther from the sensor face. We recommend adjusting the sensor to be closer to the target.

Green Indicator (Power) Orange Indicator (Output) Condition

Off Off Power Off

Off Flash at 2 Hz Passed on point (margin zone)

On Off Powered On/No Target

Flash at 2.0 Hz Off Short Circuit, Fault

Green Indicator (Power) Orange Indicator (Output) Condition

On Off No target or target far away

Off On Target present

Flash at 2.0 Hz Flash at 2.0 Hz; reverse from green status indicator

Location indication mode

IMPORTANT When the sensor is connected to IO-Link, the status indicators do not indicate margin status. The margin status is shown as a process bit in the Studio 5000® controller tag.


Chapter 2 Installation

Dimensions Dimensions are shown in mm (in.).

Wiring

20 (0.79) R2.514 (0.55)

32(1.26)

21.75(0.86)

3(0.12)

2x n3.3

13 (0.51)

50(1.97)

M12x1 Thread

StatusIndicator

3(0.12)

L

8 (0.31)

3(0.12)

M12x1 Thread

50(1.97)

L 20 (0.79)

2x n4.5

StatusIndicator

36.75(1.45)

52(2.05)

R2.530 (1.18)

5(0.2)

1: BRN +

2: WH NC (DO)4: BLK NO (C/Q)

3: BLU -PNP (Sourcing)

NPN (Sinking) 12

43

L +

L -


Chapter 3

871FM Miniature Metal Flat Pack with IO-Link Overview

What Is IO-Link? IO-Link technology is an open point-to-point communication standard and was launched as (IS) IEC 61131-9. IO-Link is now the first globally standardized technology for sensor and actuator communication with a field bus system. This technology provides benefits to both OEMs and end users.

IO-Link provides communications-capable sensors to the control level by a cost-effective point-to-point connection. IO-Link provides a point-to-point link between the I/O module and sensor that is used for transferring detailed diagnostics, device identity information, process data, and parameterization.

IO-Link communication is based on a master-slave structure in which the master controls the interface access to the sensor. The option of using the intelligence that is integrated into the sensor provides you with new methods to commission the device. Benefits of IO-Link technology range from reduced installation time during startup to increased diagnostics over the lifetime of the machine. Other benefits of IO-Link technology include:

• Reduced inventory and operating costs • Increased uptime/productivity • Simplified design, installation, configuration, and maintenance • Enhanced flexibility and scalability• Detailed diagnostic information for preventive maintenance

Why IO-Link? IO-Link offers a full range of advanced features and functions.

Seamless Integration• Forward and backward compatible, sensor catalog numbers remain the

same• No special cables required• Connectivity options remain the same• Access IO-Link functionality by simply connecting an IO-Link enabled

device to an IO-Link master


Chapter 3 871FM Miniature Metal Flat Pack with IO-Link Overview

Real-time Diagnostics and Trending• Real-time monitoring of the entire machine down to the sensor level• Optimized preventive maintenance—identify and correct issues before

failures can occur• Detect sensor malfunctions/failure

Sensor Health Status• Real-time monitoring verifies that sensors are operating correctly

Device Profiles and Automatic Device Configuration• “Golden” device configurations are stored in the IO-Link master

module• Within minutes instead of hours, modify sensor parameters to produce

different finished goods

Descriptive Tags• Faster programming during initial setup • More efficient troubleshooting-process data tags are named based on the

information they provide • Easily monitor sensor data though intuitive tag names

How Does IO-Link Work? IO-Link delivers additional operational data and diagnostics using the same standard field cabling that is used today. By connecting an IO-Link sensor to an IO-Link master, the field-device data and diagnostics are accessible. This connection allows you to go beyond detecting products on the machine. You can now monitor the health of the machine as it runs.

Pin Signal Remark

1 L+ 24V

2 Out Depends on sensor

3 L- Ground

4 C/Q Communication/switching signal

IMPORTANT The response time of an IO-Link system could be fast enough for high-speed applications. In this case, it is possible to monitor/configure the sensor through IO-Link on pin 4 while pin 2 is connected to a standard input card.


871FM Miniature Metal Flat Pack with IO-Link Overview Chapter 3

Transmission Rates

Three baud rates are specified for the IO-Link device:• COM 1 = 4.8 kBd• COM 2 = 38.4 kBd• COM 3 = 230.4 kBd

An IO-Link device typically supports only one of the specified transmissions rates, while the IO-Link V1.1 specifications requires an IO-Link master to support all three baud rates. (See Product Specifications for product baud rate.)

Transmission Quality

The IO-Link communication system operates at a 24V level. If a transmission fails, the frame is repeated two more times. If the transmission fails on the second try, the IO-Link master recognizes a communication failure and signals it to the controller.

Response Time of the IO-Link System

The device description file (IODD) of the device contains a value for the minimum cycle time of the device. This value indicates the time intervals at which the master can address the device. The value has a large influence on the response time. In addition, the master has an internal processing time that is included in the calculation of the system response time.

Devices with different minimum cycle times can be configured on one master. The response time differs for these devices. When configuring the master, you can specify a fixed cycle time and the device-specific minimum cycle time that is stored in the IODD. The master then addresses the device that is based on this specification. The typical response time for a device therefore results from the effective cycle time of the device and the typical internal processing time of the master. (See Specifications on page 10 for minimum product cycle time.)



IO-Link Data Types There are four data types available through IO-Link:

Process Data

The process data of the devices are transmitted cyclically in a data frame in which the device specifies the size of the process data. Depending on the device, 0…32 bytes of process data are possible (for each input and output). The consistency width of the transmission is not fixed and is thus dependent on the master.

Some devices can support multiple process data modes, which allow you to select different cyclic process data themes.

Value Status

The value status indicates whether the process data is valid or invalid. The value status can be transmitted cyclically with the process data.

Device Data

Device data supports device-specific configurable parameters, identification data, and diagnostic information. They are exchanged acyclically and at the request of the IO-Link master. Device data can be written to the device (Write) and also read from the device (Read).

Events

When an event occurs, the device signals the presence of the event to the master. The master then reads out the event. Events can be error messages and warnings/maintenance data. Error messages are transmitted from the device to the controller via the IO-Link master. The transmission of device parameters or events occurs independently from the cyclic transmission of process data (see Error Codes and Events on page 77 for device-specific events and associated codes).

Process data → Cyclic data

Value status → Cyclic data

Device data → Acyclic data

Events → Acyclic data



Access IO-Link Data Cyclic Data

To exchange the cyclic process data between an IO-Link device and a controller, the IO-Link data from the IO-Link master is placed on the address ranges assigned beforehand. The user program on the controller accesses the process values using these addresses and processes them. The cyclic data exchange from the controller to the IO-Link device (that is, IO-Link sensor) is performed in reverse.

Acyclic Data

Acyclic data, such as device parameters or events, are exchanged using a specified index and subindex range. The controller accesses these using Explicit Messaging. The use of the index and subindex ranges allows targeted access to the device data (that is, for reassigning the device or master parameters during operation).

Start-up the I/O System If the port of the master is set to IO-Link mode, the IO-Link master attempts to communicate with the connected IO-Link device. To do so, the IO-Link master sends a defined signal (wake up pulse) and waits for the IO-Link device to reply.

The IO-Link master initially attempts to communicate at the highest defined data transmission rate. If unsuccessful, the IO-Link master then attempts to communicate at the next lower data transmission rate.

If the master receives a reply, the communication begins. Next, it exchanges the communication parameters. If necessary, parameters that are saved in the system are transmitted to the device. Then, the cyclic exchange of the process data and value status begins.

Assign Device Parameters Configuration of a device for a specific application requires changes to parameter settings. The device parameters and setting values are contained in the IODD of the device.

I/O Device Description (IODD) files contain information about the device identity, parameters, process data, diagnostic data, and communication properties. These files are required to establish communication with the sensors via IO-Link.

The IODD consists of multiple data files; the main file and several optional language files are in XML-format and graphic files are in PNG format (portable network graphics). These files adhere to the IO-Link open standard, which means that they can be used with any IO-Link masters.

IODD files are assigned using Studio 5000® and the 1734-4IOL Add-on Profile (when using the 1734-4IOL IO-Link master module).



Premier Integration The Studio 5000 Logix Designer® environment combines design and engineering elements in one interface, enables you to access I/O and configuration data across the Integrated Architecture® system. Use of a Rockwell Automation solution, provides a smooth, consistent integration of Allen-Bradley® IO-Link enabled devices into the system.

To simplify the integration of the Allen-Bradley IO-Link devices to the Rockwell Automation architecture, there is an IO-Link Add-on Profile (AOP) available for the 1734-4IOL master module. The use of an AOP simplifies the setup of devices by providing the necessary fields. This setup allows you to build and configure their systems in a quick and efficient manner.



871FM Sensor IO-Link Features

The following features are available in the 871FM sensor:• Triggered: The process data bit that indicates the change in state of the

871FM sensor upon the detection of a target. The status of the triggered bit can be viewed in a Studio 5000 controller tag.

• Polarity: Changes the operation of the triggered parameter. It performs the same function as normally open or normally closed in standard I/O (SIO) mode.

• Margin Status: The process data bit that indicates the target is within or beyond 80% of the maximum sensing range of the sensor. The margin status bit can be viewed in Studio 5000 controller tag.

• Timer: Measures the amount of time the output is present and absent up to a maximum of 4 seconds.

Correlation

The AOP reads all configuration read/write (R.W.) parameters directly from the connected IO-Link devices and compares the values to ones stored in the controller. This action determines if there are differences (note that the correlation does not work for read-only (R.O.) in the parameters or for competitive sensors.). This feature is for Allen-Bradley enabled IO-Link devices only and is an online only function that runs when opening up the AOP.

• No differences: You go directly into the AOP.• Differences: If there are differences, you are provided with a differences

dialog window that identifies the IO-Link parameters that, do not match for each channel. You can then choose, on a channel by channel basis (where differences exist) to upload the parameters that are currently in the device and store them in the controller. Alternatively, you can choose to download the parameters that are stored in the controller to the connected IO-Link device.



Automatic Device Configuration (ADC)

Replacing damaged sensors is easy. Simply remove the original Allen-Bradley sensor and connect the new sensor (with the same catalog number) — the controller automatically downloads the configuration to the new sensor.

Upon failure, a sensor can be replaced with the same catalog number that is defined in the IO-Link channel sensor. Upon connecting the new sensor, the configuration is automatically downloaded.

No personal computer is required to configure the sensor, unless the setting requires changing. The IO-Link channel configuration is stored within the Logix controller.

Tag Naming for I/O Data: Rockwell Automation system solutions provide tag names that are based on the Allen-Bradley sensor connected. I/O data is converted, formatted, and named based on the Allen-Bradley sensor applied. Reduces commissioning time by the OEM and reduces troubleshooting time by the end user when searching for sensor data. Consistent naming techniques are used.

The Triggered and Margin Status that is previously shown are examples of consistent tag names that are used across all Allen-Bradley sensors. These tags give insightful and descriptive meaning to the operation of the sensor output. The tags can change depending on the type of sensor being used and the functionality within the sensor.


Chapter 4

Configure the 871FM Sensor for IO-Link Mode

This chapter shows the physical hardware and software that is required to configure the 871FM sensor through IO-Link and provides a simple guide for setup of the hardware.

The products that are required include the following hardware and software.

Hardware • 871FM-x• CompactLogix™ or ControlLogix® PLC Platform• POINT I/O™ Communications Interface: 1734-AENTR• POINT I/O IO-Link Master Module: 1734-4IOL• POINT I/O Terminal Base: 1734-TB• RJ45 network cable for EtherNet/IP connectivity:

1585J-M8TBJM-1M9*• 889D cordsets (optional): 889D-F3AC-2xx (IO-Link maximum

acceptable cable length is 20 m [65.6 ft])

Software • Studio 5000® environment, version 20 and higher• Sensor-specific IODD• 1734-4IOL IO-Link Add-on Profile (AOP)


Chapter 4 Configure the 871FM Sensor for IO-Link Mode

Example: Setup the Hardware

In this example, an Allen-Bradley® POINT I/O™ chassis is shown with a 1734-AENTR adapter and a 1734-4IOL IO-Link master module in the first slot. The 1734-AENTR adapter is communicating with a CompactLogix™ controller via an EtherNet/IP network.

When adding a 871FM sensor to the 1734-4IOL master module, complete the following steps:

1. Provide power to the 1734-AENTR adapter.

2. Set the node address on 1734-AENTR adapter.

3. Connect the 1734-AENTR adapter to the controller with the recommended RJ45 Ethernet cable.

4. Wire the sensor cable to the desired location on the IO-Link master (in this example, we are showing the sensor that is wired to the channel 0).

5. Connect the 871FM sensor to the other end of the sensor cable.

6. After connecting the sensor, you must create/open a project in Studio 5000 to establish communication with the controller that is being used. You must also add the 1734-AENTR adapter and 1734-4IOL IO-Link master module to Controller Organizer Tree (see Chapter 6 and Chapter 7 for detailed instructions).


Chapter 5

Create a Project

Begin a New Project To begin a new Studio 5000® project, use the following procedure.

1. Double-click the Studio 5000 icon.

2. Click New Project.

3. In the New Project dialog box, select the controller for your project, name the project, and click Next.

In this example, the project is named 1769 L24ER CompactLogix 5370 controller.

IMPORTANT If there is an existing project within Studio 5000 with CompactLogix™ or ControlLogix® hardware that is installed and communicating online, go directly to Chapter 6.


Chapter 5 Create a Project

4. After selecting the controller, name the project and click Next.

In this example, the project name is “Project871FM.”

5. To verify communication, set the IP address by clicking the browsing icon.

Project871FM opens.


Create a Project Chapter 5

6. Select the controller that is being used for the project and click Go Online to start communication.

In this example, we are using a 1769-L24ER-QB1B CompactLogix.

The next step is to Configure the IO-Link Master on page 29.


Chapter 5 Create a Project

Notes:


Chapter 6

Configure the IO-Link Master

Configuration Procedure 1. Make sure that the controller is offline to configure the IO-Link Master.

2. In the controller organizer tree, find Ethernet under I/O Configuration and right-click to add New Module.

The module window pops up and shows the available modules.


Chapter 6 Configure the IO-Link Master

3. Select the “1734-AENTR, 1734 Ethernet adapter, 2-port, twisted-pair media” and click Create.

4. Name the Ethernet adapter (in this example our adapter name is “adapter”), set the chassis size, check the module revision, and configure the adapter Ethernet address. Click OK and then Close.


Configure the IO-Link Master Chapter 6

5. The 1734-AENTR adapter appears in the Controller Organizer tree.

6. Right-click on 1734-AENTR/B Adapter, and then select New Module.


Chapter 6 Configure the IO-Link Master

7. Select “1734 IO-Link Module Profiles” and click Install.

Another screen appears showing the IO-Link Configuration screen.

8. Name the IO-Link Master and click OK.

The 871FM sensor can now be configured. To configure the sensor, a sensor-specific IODD (I/O Device Description) file is required. See Chapter 8 on page 39 for information on how to register the IODD file.

AOP Installation Verify that the Studio 5000 environment contains the 1734-4IOL IO-Link AOP. Version 20 or higher of Studio 5000 environment supports this module and AOP. To verify that the 1734-4IOL module is installed, configure a 1734-AENTR adapter and add a 1734-4IOL module from the library. If required the AOP can be downloaded from https://download.rockwellautomation.com/esd/download.aspx?downloadid=addonprofiles.


https://download.rockwellautomation.com/esd/download.aspx?downloadid=addonprofiles


Chapter 7

Connect the 871FM Sensor to the IO-Link Master

Connection Procedure Once the IO-Link master is configured, connect the sensor to the IO-Link master. Take the controller offline to add a device to the IO-Link master.

1. Go to the IO-Link tab and click Change.

2. Next click in the Change Device column for the IO-Link channel number the sensor will be added to.

A window that contains a library of all sensors that are currently registered in the IO-Link Device Library appears.


Chapter 7 Connect the 871FM Sensor to the IO-Link Master

3. Select the appropriate sensor and click Create.

If the sensor does not appear in the library, go to Chapter 8 to learn how to Register the IODD.

The sensor is now in the channel configuration window.

4. You can change the Application Specific Name, Electronic Keying, and Process Data Input configuration while the project is in the offline mode.

IMPORTANT The 871FM IO-Link does not support Application-specific Name or Process Data Input configuration when online.


Connect the 871FM Sensor to the IO-Link Master Chapter 7

Modify the information:• Application-specific Name (ASN): The purpose of the

Application-specific Name is to add a theme to distinguish the sensors within a machine and the associated project profile in the Add-on Profile. The ASN allows for easier maintenance and operation since the device is identified by its use on the machine/project.

• Electronic Keying Information: Select Exact Match or Disabled from the pull-down menu. The Exact Match and Disabled keying options in this dialog correspond to the Compatible and No Check keying options in IO-Link terminology, respectively.When Exact Match is selected, the connected IO-Link device must have the same Vendor ID, Device ID, and Revision information that has been configured for that channel. If they do not match, IO-Link communications are not established and a Keying Fault status bit is set. When Disabled is selected, key check is not performed.

• Process Data Input: Select the input data from the pull-down menu (for devices that support multiple layouts of input data).

Click OK.

5. Click Yes to confirm the sensor changes.

The module properties screen appears on the General Tab.



6. Click the IO-Link tab.

7. Locate the sensor that you added in the organization tree and select it.

The sensor can now be configured through the Add-on Profile.


Connect the 871FM Sensor to the IO-Link Master Chapter 7

8. Click Go Online to communicate with the controller and sensor.

See Review the 1734-4IOL IO-Link AOP on page 47 for a description of each 1734 AOP tab and how to use the AOP to configure the sensor.



Notes:


Chapter 8

Register the 871FM IODD

If you are not able to locate the 871FM in the IO-Link Sensor Library (as shown in Chapter 7), then you must register the IODD of the sensor. By default, the IODDs are already located in the AOP, but as new products are released it is necessary to add products to the library.

The I/O Device Description (IODD) files contain the information that is related to the sensor, integrated into the system environment. To initialize a sensor on an IO-Link Master, you must register the IODD of the sensor.

If the IODD file for the sensor cannot be located in the library, it can be downloaded from http://compatibility.rockwellautomation.com/. Once the IODD is registered, there is no need to register the IODD again unless it is deleted from the Master Tree manually.

Registration Procedure 1. Double-click 1734-4IOL in the Controller Organizer Tree.


http://compatibility.rockwellautomation.com/Pages/MultiProductDownload.aspx?crumb=112

Chapter 8 Register the 871FM IODD

2. Select the IO-Link tab.

3. On the IO-Link screen, click Change.

4. Click in the Change Device column for the IO-Link channel number that the sensor is added to.


Register the 871FM IODD Chapter 8

5. In the IO-Link Device Library window, select Register IODD.

6. Click Register IODD in the following dialog box.



7. Locate the IODD XML file and select it (multiple files can be selected). Then, click Open.

8. Click Exit.

The 871FM is now visible in the IO-Link Device Library.



9. Select the appropriate sensor and click Create.

10. Verify that the sensor appears in the channel configuration window and click OK.

You can change the application-specific name, electronic keying, and process data input configuration while the project is in the offline mode.

IMPORTANT The 871FM IO-Link does not support application-specific name or process data input configuration when online.



• Application-specific Name (ASN): The purpose of the Application-specific Name is to add a theme to distinguish the sensors within a machine and the associated project profile in the Add-on Profile. The ASN allows for easier maintenance and operation since the device is identified by how it is used on the machine/project.

• Electronic Keying Information: Select Exact Match or Disabled from the pull-down menu. The Exact Match and Disabled keying options in this dialog correspond to the Compatible and No Check keying options in IO-Link terminology, respectively. When Exact Match is selected, the connected IO-Link device must have the same Vendor ID, Device ID, and Revision information that has been configured for that channel. If they do not match, IO-Link communications is not established and a Keying Fault status bit is set. When Disabled is selected, key check is not performed.

• Process Data Input: Select the input data from the pull-down menu (for devices that support multiple layouts of input data).

Click OK.

11. Click Yes to confirm the sensor changes.

The module properties screen appears on the General Tab.



12. Click the IO-Link tab and navigate to the sensor that was added. The sensor can now be programmed through the Add-on Profile.

13. Click Go Online to communicate with the controller and sensor.

The IODD registration and connection to the IO-Link master is complete.

See Chapter 9 for a description of each 1734 AOP tab and how to use the AOP to configure the sensor.



Notes:


Chapter 9

Review the 1734-4IOL IO-Link AOP

Overview — Device Parameter Behavior

IO-Link parameters are shown in the Add-on Profile (AOP) only for IO-Link devices with IODD Advanced integration. Each parameter can have an attribute of read-only (ro), read/write (rw), or write only (wo). The behavior of parameters and the source for their values differ whether you are offline or online.

Table 4 - IO-Link Device Parameter Behavior

The 1734-4IOL AOP offers four different tabs to describe the sensor functionality and operation. These tabs are:

For a complete listing of all sensor parameters and parameter definitions, see Device Parameters on page 71.

Attribute Offline Online

Read-only (ro) Parameters are blank. Parameter values are read from the connected IO-Link device.Parameters show “??” when communication breaks.

Read-write (rw) Parameter values are read from the IODD file when the IO-Link device is added.Changes made to the parameters are applied when the “OK” and “Apply” buttons are clicked.

Parameter values can be edited and changes made to the parameters are applied when the “OK” and “Apply” buttons are clicked.Changes are sent to the Master Module, which then writes the changes to the connected IO-Link device.

Write only (wo) Parameter buttons are disabled. Parameter buttons that could potentially alter the Process Data are disabled.Other parameter buttons that are enabled, result in commands being sent to the connected IO-Link device.

Tab Page Description

Common 48 General product information about the sensor specifications and IO-link IODD information.

Identification 49 Sensor cat. no., series letter, general product description including the current product firmware, and hardware revisions.

Observation 49 Provides device monitoring parameters with signal strength ON, signal strength OFF, contrast, and gain.

Parameter 50 Different configurable parameters available in the 871FM.

Diagnosis 53 Monitor IO-Link communication characteristics.


Chapter 9 Review the 1734-4IOL IO-Link AOP

Common Tab The common tab is generated automatically to give general information about the sensor.

This tab contains the following sensor information:

Table 5 - Common Tab Information

Attribute Description

Vendor The vendor name of the product.

Vendor Text Describes additional product information.

Vendor ID Describes the vendor ID of the manufacturer of the product as designated in the IO-Link consortium.

URL The vendor URL.

Device The specific catalog number of the product.

Description Describes the sensor features and range performance.

Device ID The unique device ID as defined in the IO-Link specifications.

IO-Link Revision The current IO-Link version that the device supports.

Hardware Revision The latest sensor hardware information.

Firmware Revision The latest sensor firmware information.

Bitrate The supported bitrate for communications as defined in the IO-link 1.1 standard.

Minimum Cycle Time The response time of the sensor.

SIO Mode Whether the sensor is also designed to operate without an IO-Link connection.

IODD The complete file name of the IODD that is assigned to the product.

Document Version The version control for the IODD.

Date of Creation The date the IODD file was created.


Review the 1734-4IOL IO-Link AOP Chapter 9

Identification Tab The Identification tab shows device information such as specific Vendor ID and Device ID for the exact sensor that is configured. These fields are automatically populated according to the sensor information. These fields are read-only (ro).

Observation Tab



Parameter Tab The Parameter tab allows changes to the behavior of the output of the sensor. The IO-Link master uses these parameters for validation purposes.

The Parameter tab displays the sensor parameter settings and allows you to read data from the sensor or teach the sensor by writing new values. This tab is divided into four sections:

• Operation Configuration (page 50)• Sensor Configuration (page 51)• Counter/Timer Configuration (page 51)• Data Mapping Configuration (page 52)

Operation Configuration

In this section, operators are able to change the function of the sensor outputs while operating in IO-Link Mode. The Triggered subsection describes the parameters, which affect the sensor output.

• Setpoint: Threshold allows operators to view the signal value that is required for the sensor output to turn ON (threshold) upon target detection. The sensor signal level must be higher than the threshold for the output to turn ON. The default value for this parameter is 1000.

• Polarity changes the sensor output operation between a non-inverted and inverted state for Pin 4. For complementary (non-inverted and inverted). When the polarity changes both outputs invert.

• Hysteresis displays the sensor output hysteresis value. The real value for hysteresis is the value that is shown on this parameter that is divided by 100.



• Pin 2 Mode enables the operation of the sensor as a standard output on pin 2 in IO-Link Mode. When connecting the sensor in IO-Link mode, pin 2 is disabled by default and could be changed to either operate as Normally Open or Normally Closed contact in standard I/O application. This parameter is ideal for applications where the response time is critical for the application as IO-Link response time is not fast enough to address the application needs.

Sensor Configuration

In this section, the operator is able to change when the sensor indication indicator displays marginal conditions. Two parameters are displayed: Proximity Alarm Level and Margin Level Low Multiplier.

• Proximity Alarm Level allows you to view a signal level that is below the threshold. The default value for this parameter is 0.8 mm (0.03 in.).

• Margin Level: Low Multiplier allows you to view when the orange status indicator starts flashing to reflect a signal level that is below the threshold. The default value for this parameter is 1.1 mm (0.04 in.).

Counter/Timer Configuration

In this section, the operator is able to configure the sensor counter and timer functions. Two main parameter subsections are shown: Counter and Timer.

• Counter: When enabled, the counter counts up on any transition from OFF to ON.– Mode: Allows you to enable or disable the counter function. This

parameter is Read/Write.– Reset: Allows you to reset the counter function. This parameter is

write-only and can be enabled via the AOP or sending explicit messages. See Appendix B for Index information.

– Counter: This parameter is read only and displays the current count.• Timer: Measures the amount of time the output is present and absent up

to a maximum period of 4 seconds. – Mode: Allows you to enable or disable the timer function. This

parameter is Read/Write.– Reset: Allows you to reset the timer function. This parameter is

write-only and can be enabled via the AOP or sending explicit messages. See Appendix B for Index information.

– Duration Triggered: Displays the amount of time the target was detected. The maximum value that this parameter displays is 4095 ms. Timer must be enabled.

– Duration Not Triggered: Displays the amount of time the target was not detected. The maximum value that this parameter displays is 4095 ms. Timer must be enabled.



Data Mapping Configuration

In this section, the operator is able to configure the process data to be used. The process data consists of 4 bytes of data. The following process data maps are offered in the 871FM sensor:

• Data Map 0 (Default): Triggered, Margin, Proximity, Gain, Signal• Data Map 1: Triggered, Margin, Proximity, Gain, Contrast, Temp • Data Map 2: Triggered, Margin, Proximity, Gain, Count• Data Map 3: Triggered, Margin, Proximity, Gain, Duration

Attribute Description

Triggered Displays the status of the sensor output. This process data element is a bit that indicates when the target has been detected or not.

Margin Displays the status of the sensor margin low alarm. This process data element is a bit that indicates to the operator if the sensor signal is marginal or unstable.

Proximity Displays the status of the proximity alarm. This process data element is a bit that indicates if there is an object close to the threshold (below 1.0X) when the output is OFF.

Gain Displays the excess gain above the sensor threshold to confirm reliability of target detection.

Signal Provides the raw measurement value of the amount of light reflected from the target.

Contrast Displays the difference between the light signal levels that the sensor read the last time that the output was ON versus the last time the output was OFF.

Temp Displays the current internal temperature of the sensor. This process data element provides the internal temperature value and can increase or decrease depending on the influence of the ambient temperature on the internal sensor temperature. This element does not provide a direct and exact temperature measurement of the ambient temperature in the application.

Count Displays the sensor counter value when enabled. This process data element can count up to 65535 and can be reset via Explicit Messaging to the appropriate index. See Device Parameters on page 71for additional information about index.

Duration Displays the amount of time that the sensor output has been OFF (Duration Not Triggered) and ON (Duration Triggered).



Diagnosis Tab The Diagnosis tab shows you communication characteristics such as cycle time and IO-Link Revision ID.

The Diagnosis tab is divided into five sections:

• Device Access Locks (page 53)• Service Function (page 54)• Operating Information (page 54)• Temperature (page 55)• Communications Characteristics (page 55)

Device Access Locks

This section displays the Device Storage Lock and the User Interface Lock parameters. The Device Storage Lock is a read-only parameter that describes that data storage on the sensor cannot be locked. Therefore the Local User Interface Lock keeps unauthorized operators from changing the sensor threshold setting when using the local sensitivity adjustment.



Service Function

This section contains multiple parameters that allow operators to enable additional sensing functionality. This parameter can only be accessed through explicit messages as described in Explicit Messaging Examples on page 79.

• Restore Factory Settings: A write-only command and sets the current sensor settings to their factory default values. This parameter can only be accessed via explicit message as defined in Explicit Messaging Examples on page 79.

• Device Reset: A write-only command that performs the same function as a power cycle of the sensor.

• Location Indicator: Activates the location indication sensor functionality. When enabled, the sensor user interface (green and orange indicators) starts flashing synchronously until the operator disables this function. This parameter is useful when there are multiple sensors near each other.

• Status Indicators Enabled: This parameter allows operators to turn the user interface status indicators (green and orange) OFF or ON. This parameter is ideal to accommodate applications where the status indicators must be turned OFF.

• Error Count: Displays the number of errors.• Device Status: Displays the status of the device.• Last Event: Displays the code for the last event the sensor initiates.

Operation Information

In this section, the operator is able to monitor the sensor operating hours since inception and power up.

• Operating Hours – Since Inception: displays the total operating hours that the sensor has been running since the first time it was powered ON. This value is not lost during factory reset. The information that is displayed in this parameter is represented in hours.

• Operating Hours – Since Power Up: Displays the total operating hours that the sensor has been running since the last time the sensor power was cycled. This value is reset to zero every time that the sensor loses power.



Temperature

In this section, the operator is able to monitor the actual, minimum, and maximum internal temperature of the sensor.

• Actual – Since Power Up: Displays the current internal temperature of the sensor.

• Maximum – Since Power Up: Displays the maximum sensor internal temperature since the last time power cycle of the sensor.

• Maximum: Since Inception: Displays the maximum internal temperature of the sensor since the first time the sensor was ever powered ON. This value is retained and not lost during default factory reset.

• Minimum: Since Power Up: Displays the minimum internal temperature of the sensor since the last time the sensor was powered.

• Minimum: Since Inception: displays the maximum internal temperature of the sensor since the first time the sensor was ever powered ON. This value is retained and not lost during default factory reset.

Communication Characteristics

This section has read-only (ro) values for the Minimum Cycle Time (response time of the sensor) and the Master Cycle Time (time that is used by the master to address the sensor). You can also visualize the IO-Link revision of the sensor in this section.

Manage Parameter Differences between IO-Link Devices and Controllers

The Add-on Profile has a Refresh button that updates the read-only parameters for all channels with IO-Link devices. It also performs a Correlation check of the read-write parameters in all connected IO-Link devices and in the controller.

Differences in parameter values can happen when the device configuration is changed externally, such as through a device console during operation. If there are differences after running a Correlation check, you can choose to use the parameters that are currently in the connected IO-Link device or to use the parameters that are stored in the controller. The changes can be done on a per channel basis.

Before you proceed with this task, the Refresh function is:

• Only enabled in online mode.• Performed initially when the Add-on Profile is launched in online mode.



1. From the IO-Link tab on the working pane, click the Refresh button. If differences are detected in the RW values, a dialog box appears. The dialog box displays mismatched information per channel, including the parameters and the values present in the device and in the controller.

Communication errors (if applicable) are indicated in the dialog for each channel. A link is available for you to click to retry communication.



2. For each channel, select the checkbox for the corrective action:• Use Device Values: Uploads the parameter values that are read from

the connected IO-Link device to the project.• Use Project Values: Downloads the parameter values from the

project to the connected IO-Link device.



Triggered: This process bit toggles between one or zero depending on the polarity configuration when the sensor detects the target or not. For normally open, this bit displays a zero by default when no target is present and a one when target is present. For normally closed sensors, this bit displays a one by default and a zero when the target is present.

MarginLowAlarm: This process bit toggles between one and zero to indicate if there is enough margin to maintain reliable target detection. This bit is one when the target is marginal (signal strength is above 0.5X and below 2X). It is zero when the light levels are above the operating margin if the triggered bit is active. The following table describes the significance of both bits when evaluated together:

Proximity: Displays the status of the proximity alarm. This process data element is a bit that indicates if there is an object near the threshold (below 1.0X) when the output is OFF.

Gain: Displays the excess gain above the sensor threshold to maintain reliable detection of the target.

Signal: Provides the raw measurement value of the amount of signal reflected from the target.

Triggered MarginLowAlarm Description

0 0 No target is present

0 1 No target present, item in background is very close to the sensor threshold

1 0 Target is present and sensor signal is not marginal

1 1 Target is present and signal strength is marginal (0.5x < signal < 2X)


Chapter 10

Install the 871FM Sample Code Add-On Instruction

In this chapter, the Add-On Instruction is provided to allow you to read and change the read/write parameters of your sensor.

Download 1. In the main routine, right-click a new rung and select Import Rung.


Chapter 10 Install the 871FM Sample Code Add-On Instruction

2. Browse to the folder and click Open.

3. On the import configuration screen, click OK.

4. The AOI I then imports and a new rung is created.


Install the 871FM Sample Code Add-On Instruction Chapter 10

5. Click the Read Index ellipsis (…) to open the read index message configuration.

6. Select the Communication tab.

7. Browse to your 4IOL module and click OK.

8. Click Apply and OK to close the configuration box.



9. Repeat steps 5…8 for Write Index, Read Subindex, and Write Subindex message configurations.

10. Confirm the Input_4IOL tag Path is set to your AENTR I.status.

11. Verify the routine and confirm that there are no errors.

12. Download the program to the controller and place the controller in run mode.

AOP Operation

The Add-On Instruction has been created to allow you to read and change parameters. The control data type IO_Link_871FM_AOI is used to change and read parameters. Values can be viewed by expanding the Msg_Date data type.

Figure 1 - My_871FM


Install the 871FM Sample Code Add-On Instruction Chapter 10

1. Set the channel number that the 871FM sensor is connected to.

2. Set the Update tag to a value of 1

3. Once all parameters have been read, the update complete tag is set to a value of 1



The updated values can be viewed by expanding the My_Output_Data tag.

Figure 2 - My_Output_Data

Change Operation State

To change the state of either Location Indicator, status indicator, between NO and NC, Phy Mode, Lock simply toggle the associated bit in Msg_data AOI control data array. The status can be viewed in the My_Output_Data tag.

IMPORTANT For Timing and Counter functions, be sure that the functionality is enabled within the AOP.


Chapter 11

Troubleshooting

This guide is meant to help resolve common issues that occur when configuring the 871FM sensor.

ChecklistError Cause Remedy

Status indicator does not light up

The power supply is switched off. Check to see if there is a reason for it to be switched off (installation or maintenance work, and so on). Switch on the power supply if appropriate.


The 4-pin M12 plug is not connected to the connector on the sensor

Connect the 4-pin M12 plug to the sensor and tighten the cap nut by hand.


Fault in the splitter or control cabinet wiring.

Check the wiring carefully and repair any wiring faults.


Supply cable to the sensor is damaged.

Replace the damaged cable.

No IO-Link connection to the device

No power supply See error “Operating Indicator” status indicator does not light up.


Chapter 11 Troubleshooting

Notes:


Appendix A

Install the Add-on Profile

Introduction This appendix shows how to install the IO-Link Add-on Profile (AOP) with the RSLogix 5000® program. Add-on Profiles are files that you add to your Rockwell Automation® library. These files contain the pertinent information for configuring a device that is added to the Rockwell Automation network.

The Add-on Profile simplifies the setup of devices because it presents the necessary fields in an organized fashion. The Add-on Profile allows you to install and configure their systems in a quick and efficient manner.

The Add-on Profile is a folder that contains numerous files for the device. It comes as an installation package.

Perform the Installation 1. Download the latest IO-Link AOP file from the Add-on Profiles website. https://download.rockwellautomation.com/esd/download.aspx?downloadid=addonprofiles

2. Extract the AOP zip file, open the folder, and execute the “MPSetup” application file.

3. Click Next to install the IO-Link module profiles.




Appendix A Install the Add-on Profile

4. Accept the license agreements and click Next. Follow the module profiles installation wizard.

5. Verify that Install is selected and click Next.


Install the Add-on Profile Appendix A

6. Review the install details and click Install.

7. The installation process begins. This process can take several minutes.


Appendix A Install the Add-on Profile

8. When complete, click Next.

9. Click Finish and review the release notes for any additional information. The IO-Link AOP installation is completed.


Appendix B

Device Parameters

When using Explicit Messages to read/write 871FM parameter values, it is important to know the index number, data type, and size of the data that is transmitted and received in the message. The following tables provide this information for each of device parameter.

Identification TabParameter Name

Index Hex (Dec)

Subindex Hex (Dec)

Access Default Allowed Value Data Type (Length)

Device Information

Vendor Name 0x10(16) 0x00(0) RO Allen-Bradley Allen-Bradley StringT

Product Name 0x12(18) 0x00(0) RO 871FM-M7BA20-FD02871FM-M7BA20-E2

871FM-MV7BA20-FD02X871FM-M10BA30-FD02

871FM-M10BA30-E2871FM-MV10BA30-FD02X

871FM-MxxBAxx-xx StringT

Product ID 0x13(19) 0x00(0) RO 871FM-M7BA20-FD02871FM-M7BA20-E2

871FM-MV7BA20-FD02X871FM-M10BA30-FD02

871FM-M10BA30-E2871FM-MV10BA30-FD02X

871FM-MxxBAxx-xx StringT

Product Text 0x14(20) 0x00(0) RO MetalFlat,Shielded, 20x32x8, 7 mm range, PVC Pigtail QDMetalFlat, Shielded, 20x32x8, 7 mm range, PVC Cable, WFI

MetalFlat, Shielded, 30x52x14, 10 mm range, PVC Pigtail QDMetalFlat, Shielded, 30x52x14, 10 mm range, PVC Cable, WFI

Inductive Proximity Sensor - 871FM

StringT

Serial Number 0x15(21) 0x00(0) RO — StringT

User Specific Information

Application Specific Tag

0x18(24) 0x00(0) RW 0 — StringT

User Tag 1 0xC0(192) 0x00(0) RW 0 — UIntegerTbitLength=32

User Tag 2 0xC1(193) 0x00(0) RW 0 — UIntegerTbitLength=16

Revision Information

Hardware Revision

0x16(22) 0x00(0) RO 1.0 — StringT

Firmware Revision

0x17(23) 0x00(0) RO 1.0 — StringT


Appendix B Device Parameters

Observation TabParameter Name Index

Hex (Dec)SubindexHex (Dec)


Device Monitoring

.SignalStrength On 0x56(86) 0x01(1) RO — 0…65,535 UIntegerT(RecordT)bitLength=16bitOffset=16

.SignalStrength Off 0x56(86) 0x02(2) RO — 0…65,536 UIntegerT(RecordT)bitLength=16

bitOffset=0

Contrast 0x57(87) 0x00(0) RO — 0…255 UIntegerTbitLength=8

Excess Gain 0x59(89) 0x00(0) RO — 0…255 UIntegerTbitLength=8

Gain (only for 871FM polarized retroreflective)

0x59(89) 0x00(0) RO — 0…255 UIntegerTbitLength=8

Parameter TabParameter Name Index



User Interface Configuration

Operation Configuration

Triggered1(or Triggered)

.Set Point - Threshold 0x3C(60) 0x01(1) RW 1000 505…12923 Uinteger(RecordT)bitLength=16bitOffset=16

.Polarity 0x3D(61) 0x01(1) RW 0= Not Inverted 0 = Not Inverted1 = Inverted

Boolean (RecordT)bitLength=48bitOffset=40

.Hysteresis 0x3D(61) 0x03(3) RO 1650 Uinteger(RecordT)bitLength=16

bitOffset=0

Pin 2 Mode 0x60(96) 0x00(0) RW 0 = Disabled 0 = Disabled1 = Normally Closed2 = Normally Open

UintegerbitLength=8

Sensor Configuration

.ProximityAlarmLow 0x58(88) 0x01(1) RW 4 = 0.8 0 = 0.51 = 0.62 = 0.63 = 0.74 = 0.8

Uinteger(RecordT)bitLength=8bitOffset=8

.MarginLevel - High Multiplier

0x58(88) 0x02(2) RW 1 = 1.5 0 = 1.01 = 1.52 = 2.03 = 5.0

4 = 10.05 = 15.06 = 20.0



Device Parameters Appendix B

Counter/Timer

Counter

Mode 0x5D(93) 0x01(1) RW 0 = Disabled 0 = Disabled1 = Enabled


.Reset 0x5D(93) 0x02(2) WO — 1 = Reset Uinteger(RecordT)bitLength=8bitOffset=16

.Counter 0x5D(93) 0x03(3) RO 0 0…65,535 Uinteger(RecordT)bitLength=16

bitOffset=0

Timer

.Mode 0x5C(92) 0x01(1) RW 0 = Disabled 0 = Disabled1 = Enabled


.Reset 0x5C(92) 0x02(2) WO — 1 = Reset Uinteger(RecordT)bitLength=8bitOffset=32

.DurationTriggered 0x5C(92) 0x03(3) RO 0 0…4095 Uinteger(RecordT)bitLength=12

.DurationNotTriggered 0x5C(92) 0x04(4) RO 0 0…4095 Uinteger(RecordT)bitLength=12

Data Mapping Cofiguration

.Mode 0x50(80) 0x01(1) RW 0 = Triggered Margin,

Proximity,Gain,Signal,

0 = TriggerMarginLowAlarmProximityAlarmExcessGainLevel

ReceivedSignalStrength,1 =

TriggerMarginLowAlarmProximityAlarmExcessGainLevel ContrastLevelTemperature,

2 = TriggerMarginLowAlarmProximityAlarmExcessGainLevel

CounterValue,3 =

TriggerMarginLowAlarmProximityAlarmOnDurationOff Duration


Parameter TabParameter Name Index





Diagnosis TabParameter Name Index



Device Access Locks

Device Access Locks.Parameter (Write) Access Locks

0x0C(12) 0x00(0) RO 0=False 0=False Boolean(RecordT)bitOffset=0

Device Access Locks.Data Storage Lock 0x0C(12) 0x01(1) RO 0=False 0=False Boolean(RecordT)bitOffset=1

Device Access Locks.Local Parameterization Lock 0x0C(12) 0x02(2) RW 0=False 0=False1=True

Boolean(RecordT)bitOffset=2

Service Function

<Standard Command> Device Reset 0x02(2) 0x00(0) WO Button = “Device Reset”

Button = 128

Button = “Device Reset”

Button = 128

<Standard Command> Restore Factory Settings

0x02(2) 0x82(130) WO Button = “Restore Factory Settings”

Value = 130 UIntegerTbitLength=8

.Locator Indicator 0x5E(94) 0x01(1) RW 0= Disabled 0 = Disable(d)1 = Enable(d)


.LED Enable 5E(94) 0x0(2) RW 1= Enabled 0 = Disable(d)1 = Enable(d)


Error Count 0x20(32) 0x00(0) RO — — UIntegerTbitLength=16

Device Status 0x24(36) 0x00(0) RO 0 = Device is OK 0 = Device is OK1 = Maintenance

required2 = Out of

specification3 = Functional check

4 = Failure

UIntegerTbitLength=8

Last Event 0x6E(110) 0x00(0) RO 0 0…65,535 UIntegerTbitLength=16

Operation Information

.Operating Time - Since Inception 0x5B(91) 0x01(1) RO Uinteger(RecordT)bitLength=32bitOffset=32

.Operating Time - Since Power Up 0x5B(91) 0x0(2) RO Uinteger(RecordT)bitLength=32

bitOffset=0


Device Parameters Appendix B

Temperature

.Actual - Since Power Up 0x5A(90) 0x01(1) RO — -40…125 IntegerT(RecordT)bitLength=8bitOffset=32

.Maximum - Since Power Up 0x5A(90) 0x02(2) RO — -40…125 IntegerT(RecordT)bitLength=8bitOffset=24

.Maximum - Since Inception 0x5A(90) 0x02(3) RO — -40…125 IntegerT(RecordT)bitLength=8bitOffset=16

.Minimum Since Power Up 0x5A(90) 0x04(4) RO — -40…125 IntegerT(RecordT)bitLength=8bitOffset=8

.Minimum - Since Inception 0x5A(90) 0x05(5) RO — -40…125 IntegerT(RecordT)bitLength=8bitOffset=0

Communication Characteristics

Direct Parameters 1.Min Cycle Time 0x00(0) 0x03(3) RO 20 2 ms UIntegerTbitLength=8

bitOffset=104

Direct Parameters 1. Master Cycle Time 0x00(0) 0x02(2) RO 20 2 ms UIntegerTbitLength=8

bitOffset=112

Direct Parameters 1.IO-Link Revision ID 0x00(0) 0x05(5) RO 0x11 UIntegerTbitLength=8bitOffset=88

Diagnosis TabParameter Name Index





Process DataParameter Name Subindex Access Default Allowable Values Data Type (Length)

Triggered Depends on mode RO 0 = Not triggered 0 = Not triggered1 = Triggered

BooleanTbitLength=32

bitOffset=0

MarginLowAlarm Depends on mode RO 0 = Off 0 = Off1 = On


bitOffset=1

ProximityAlarm Depends on mode RO 0 = Off 0 = Off1 = On


bitOffset=2

Gain Depends on mode RO — 0...255 UIntegerTbitLength=8bitOffset=8

Contrast Depends on mode RO — 0...255 UIntegerTbitLength=8bitOffset=16

TemperatureInternal Depends on mode RO — -40…125 BooleanTbitLength=32bitOffset=24

DurationTriggered Depends on mode RO — 0...4095 UIntegerTbitLength=12bitOffset=20

DurationNotTriggered Depends on mode RO — 0...4095 BooleanTbitLength=32

bitOffset=8

SignalStrength Depends on mode RO — 0...65,535 UIntegerTbitLength=16bitOffset=16

Count Depends on mode RO — 0...65,535 UIntegerTbitLength=16bitOffset=16

IMPORTANT Process Data parameter allows a maximum of four bytes.


Appendix C

Error Codes and Events

When an event occurs, the device signals the presence of the event to the master. The master then reads out the event. Events can be error messages and warnings/maintenance data. Error messages are transmitted from the device to the controller via the IO-Link master. The transmission of device parameters or events occurs independently from the cyclic transmission of process data.

Error CodesError Code Instance Code Note

No error APP ZERO Only applies for response telegram

Unspecific application fault APP 0x8000

Invalid index APP 0x8011

Invalid subindex APP 0x8012

Service temporarily unavailable APP 0x8020

Service temporarily unavailable (control) APP 0x8021

Service temporarily unavailable (sensor) APP 0x8022

Access denied APP 0x8023 Write attempt to read-only address

Invalid value range, parameter APP 0x8030

Parameter value too large APP 0x8031

Parameter value too small APP 0x8032

Application error APP 0x8081 Application does not respond

Application not ready APP 0x8082 Application does not respond


Appendix C Error Codes and Events

EventsName Bit Name >>> 42EF

Temperature Hardware Fault

Voltage Overrun

Short CircuitDescription >>> No Malfunction Fault

OverloadOverrun Underrun

Event Code - See “1734-4IOL Events” tab 0x0000 0x4000 0x4210 0x4220 0x5000 0x5111 0x7710Event Location 3 0 - Device application (Remote)

1 - Master application (Local)Event Mode 0 6 0 - Reserved

1 - Event single shot2 - Event disappears3 - Event appears

1 1 3 3 3 3 3

Event Mode 1 7 2 2 2 2 2Event Qualifier - See “Event Qualifier” tabEvent Sequence Count - 1...255 (can never be 0)Event Source 0 0 0 - Unknown

1 - Physical Layer (PL)2 - Data Layer (DL)3 - Application Layer (AL)4 - Application (APP)5…7 - Reserved

Event Source 1 1Event Source 2 2Event Type 0 4 0 - Reserved

1 - Notification2 - Warning3 - Error

1 1 3 2 3 2 3

Event Type 1 5Status Bit 0 - Device OK

1 - Device Fault— — — — — — —


Appendix D

Explicit Messaging Examples

Although the parameters are configured within the Add-on Profile (AOP), it is possible to read and write parameters via Explicit Messaging. Use the device index table to establish the index number and its properties.

Table 6 details of Service Codes that are used in Explicit Messaging, these codes along with the Index and Subindex numbers are used in the configuration of the MSG instruction.

This appendix also gives index read/write examples (page 80 and page 81) and sub index read/write examples (page 82 and page 83).

Service CodesTable 6 - Service Codes

Service Code Hex (Dec)

Need in Implementation

Service Name DescriptionClass Instance

4b (75) Required Required Read Subindex Read a parameter value from the IO-Link device

4c (76) — Required Write Subindex Write a parameter value from the IO-Link device

4e (78) Required Required Read Index Read an entire index (all parameters within an index) from the IO-Link device

4d (77) — Required Write Index Writes an entire index (all parameters within an index) from the IO-Link device

Table 7 - Ladder Logic Rules (1)

Instruction Message Configuration

Array[0] Array[1] Source Length [bytes] Service Code Attribute ID

Write4IOL Channel# value 4IOL index value length + 1 4e 0

8IOL Channel# value 8IOL index value length + 1 4e 0



Read4IOL Channel# 4IOL 1 4d 0

8IOL Channel# 8IOL 1 4d 0

(1) For more information about Service Codes, see Appendix A.


Appendix D Explicit Messaging Examples

Write Index Figure 3 - Write Index


Explicit Messaging Examples Appendix D

Read Index Figure 4 - Read Index

Table 8 - Ladder Logic Rules (1)



Write4IOL Channel# value 4IOL index value length + 1 4c Subindex#

8IOL Channel# value 8IOL index value length + 1 4c Subindex#



Read4IOL Channel# 4IOL 1 4d Subindex#

8IOL Channel# 8IOL 1 4d Subindex#

(1) For more information about Service Codes, see Appendix A.



Write Subindex Figure 5 - Write Subindex


Explicit Messaging Examples Appendix D

Read Subindex Figure 6 - Read Subindex

If you want to read/write at an index level that contains multiple subindexes, you must send all subindex information when writing to read all subindex information. When you are at the index level, you must know which subindex the setpoint is located if the sensor has multiple setpoints.

Byte Swapping Allen-Bradley little-endian format for its ControlLogix® systems via Studio 5000®.

• Endian: Endian refers to where the most significant byte is in an integer value. The big-endian stores the high-order byte at the starting address while little-endian stores the low-order byte at the starting address. The low-order byte contains the bits for the lowest possible values (for example, 0…255) while the high-order byte contains the bits that specify the large values (for example, 256…65535).

• Little-endian: The low-order byte of the number is stored in memory at the lowest address, and the high-order byte at the highest address.

• Big-endian: The high-order byte of the number is stored in memory at the lowest address, and the low-order byte at the highest address.

• Byte Swapping: Messages that come from a ControlLogix system to a PLC-5® controller with a PLC-5 type message know to swap the bytes before sending the data. Messages that come from a device that worked with a PLC-5 controller previously can have an issue with bytes that swap when the information is sent to the ControlLogix system. To help arrange the byte in the proper order, the ControlLogix processor has an instruction SWPB.



Notes:


Index

Numerics1734-4IOL IO-Link AOP

review 47871FM

configure for IO-Link mode 23connect to IO-Link master 33IO-Link features 21IO-Link overview 15register IODD 39

Aabbreviations 7Add-on Profile

install 67AOI

install 871FM sample code 59AOP 67

installation 32introduction 67operation 62perform installation 67review 1734-4I0L 47

assigndevice parameters 19

automatic device configuration 16

Bbegin

new project 25behavior

device parameter 47byte swapping 83

Cchange

operation state 64characteristic

communication 55checklist

troubleshooting 65code

service 79common

tab 48communication

characteristic 55configuration

automatic device 16counter 51data mapping 52operation 50sensor 51timer 51

configureIO-Link master 29

connect871FM to IO-Link master 33

correlation 21counter

configuration 51create 25

Ddata

process 76data mapping

configuration 52data types

device data 18events 18IO-Link 18process data 18value status 18

descriptive tags 16device

access locks 53assign parameters 19data 18parameter behavior 47profile 16

diagnosistab 53, 74

diagnosticsreal-time 16

dimension 14download 59

Eerror code 77event 78events 18example

explicit messaging 79set up hardware 24

explicit messagingexample 79

Ffeatures 10function

service 54

Hhardware 23

setup example 24health status

sensor 16how does IO-Link work 16


Index

Iidentification

tab 49, 71index

read 81write 80

informationoperation 54

install 67871FM sample code Add-On Instruction 59Add-on Profile 67

installation 13AOP 32

integration 15, 20IODD

register 39registration procedure 39

IO-Link871FM sensor configuration 23AOP 47configure master 29connect 871FM to master 33data types 18how 16overview 15parameter difference 55system response time 17what 15why 15

Mmodes

operating 9mounting 11, 13

Oobservation

tab 49, 72operating modes 9operation

AOP 62change state 64configuration 50information 54

overview 9871FM with IO-Link 15

Pparameter

manage difference 55tab 50, 72

premier integration 20procedure

IODD registration 39process data 18, 76product

description 9features 10overview 9specifications 10

profiledevice 16

project 25begin new 25create 25

Rread

index 81subindex 83

real-time diagnostics and trending 16register

871FM IODD 39response time 17review

1734-4IOL IO-Link AOP 47

Sseamless integration 15sensor

configuration 51health status 16

service code 79service function 54set up hardware

example 24software 23specifications 10status

sensor health 16status indication 13subindex

read 83write 82

swappingbyte 83


Index

Ttab

common 48diagnosis 53, 74identification 49, 71observation 49, 72parameter 50, 72

tagsdescriptive 16

temperature 55timer

configuration 51transmission

quality 17rates 17

trendingreal-time 16

troubleshooting 65checklist 65

Uuser interface 13

Vvalue status 18

Wwhat is IO-Link 15why IO-Link 15wiring 14write

index 80subindex 82


Index

Notes:


Publication 871FM-UM002A-EN-P - April 2017Copyright © 2017 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.

Rockwell Automation SupportUse the following resources to access support information.

Documentation FeedbackYour comments will help us serve your documentation needs better. If you have any suggestions on how to improve this document, complete the How Are We Doing? form at http://literature.rockwellautomation.com/idc/groups/literature/documents/du/ra-du002_-en-e.pdf.

Technical Support Center Knowledgebase Articles, How-to Videos, FAQs, Chat, User Forums, and Product Notification Updates. https://rockwellautomation.custhelp.com/

Local Technical Support Phone Numbers Locate the phone number for your country. http://www.rockwellautomation.com/global/support/get-support-now.page

Direct Dial Codes Find the Direct Dial Code for your product. Use the code to route your call directly to a technical support engineer. http://www.rockwellautomation.com/global/support/direct-dial.page

Literature Library Installation Instructions, Manuals, Brochures, and Technical Data. http://www.rockwellautomation.com/global/literature-library/overview.page

Product Compatibility and Download Center (PCDC)

Get help determining how products interact, check features and capabilities, and find associated firmware. http://www.rockwellautomation.com/global/support/pcdc.page

.

Rockwell Otomasyon Ticaret A.Ş., Kar Plaza İş Merkezi E Blok Kat:6 34752 İçerenköy, İstanbul, Tel: +90 (216) 5698400

Rockwell Automation maintains current product environmental information on its website at http://www.rockwellautomation.com/rockwellautomation/about-us/sustainability-ethics/product-environmental-compliance.page.

Allen-Bradley, CompactLogix, ControlLogix, POINT I/O, Rockwell Automation, Rockwell Software, RSLogix 5000, Studio 5000, and Studio 5000 Logix Designer, are trademarks of Rockwell Automation, Inc.

Trademarks not belonging to Rockwell Automation are property of their respective companies.

http://www.rockwellautomation.com/rockwellautomation/about-us/sustainability-ethics/product-environmental-compliance.page

Date post:	02-Oct-2020
Category:	Documents
Upload:	others
View:	8 times
Download:	0 times

Miniature Metal Flat Pack Inductive Sensors with IO-Link ... · troubleshooting 871FM miniature...

Documents