Rightsight Photoelectric Sensors With Io-Link Interface: User Manual
Rightsight Photoelectric Sensors With Io-Link Interface: User Manual
Original Instructions
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.
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
Who Would Use This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Purpose of This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Conventions Used in This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 1
Product Overview Product Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Operation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 2
Installation User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Alignment Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Typical Response Curves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
DC Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Chapter 3
42AF RightSight Sensor with What Is IO-Link? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
IO-Link Overview Why IO-Link? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Seamless Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Real-time Diagnostics and Trending . . . . . . . . . . . . . . . . . . . . . . . . 20
Sensor Health Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Device Profiles and Automatic Device Configuration. . . . . . . . . 20
Descriptive Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
How Does IO-Link Work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Transmission Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Transmission Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Response Time of the I-O Link System . . . . . . . . . . . . . . . . . . . . . . 21
IO-Link Data Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Process Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Value Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Device Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Accessing IO-Link Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Cyclic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Acyclic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Startup of the I/O System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Assign Device Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Rockwell Automation® Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Overview and Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Premier Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
42AF IO-Link Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Chapter 4
Configure the 42AF for IO-Link Products Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Mode Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Example: Setting up the Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Chapter 5
Create a Project Steps to Begin Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
AOP Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Chapter 6
Configure the IO-Link Master Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Chapter 7
Register the 42AF IODD Initialization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Chapter 8
Connect the 42AF to the IO-Link IODD File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Master Chapter 9
Explore the 42AF IO-Link Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Parameters IO-Link Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Manage Parameter Differences between IO-Link
Devices and Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Controller Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Chapter 10
Troubleshoot Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Appendix A
Install the Add-on Profile Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Performing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Appendix B
Device Parameters Identification Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Observation Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Parameter Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Diagnostic Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Process Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Appendix C
Message Structure and Configuring a Message Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Configuration Example Example Format of a Read Message . . . . . . . . . . . . . . . . . . . . . . . . . 73
Read Data from the Sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Configuration Examples Example Format of a Write Message . . . . . . . . . . . . . . . . . . . . . . . . 76
Validation of Write. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Service Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Source Length: from Data Structure Tables. . . . . . . . . . . . . . . . . . 80
Appendix D
Error Codes and Events Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Read this preface to become familiar with the rest of the manual. It provides
information concerning:
• Who would use this manual
• Purpose of this manual
• Related documentation
• Conventions that are used in this manual
Who Would Use This Manual Use this manual if you design, install, program, or troubleshoot systems that
use the 42AF RightSight™ Photoelectric Sensors with IO-Link Interface.
You must have a basic understanding of electrical circuitry and familiarity with
safety-related systems. If you do not, obtain the proper training before using
this product.
Qualified personnel must install the light curtain and only use it on that
specific machine.
Purpose of This Manual This manual is a reference guide for the RightSight Photoelectric Sensors with IO-
Link Interface. It describes the procedures to install, wire, and troubleshoot this
sensor.
Conventions Used in This The following conventions are used throughout this manual:
Manual • Bulleted lists such as this one provide information, not procedural steps.
• Numbered lists provide steps or hierarchical information.
QD Quick Disconnect
TB Teach Background
TD Teach Dynamic
TM Teach Mark
Additional Resources These documents contain additional information concerning related products
from Rockwell Automation.
Resource Description
RightSight M30 Installation Instructions, publication Provides general guidelines for installing a RightSight
42AF-IN001 M30 sensor.
Industrial Automation Wiring and Grounding Guidelines, Provides general guidelines for installing a Rockwell
publication 1770-4.1 Automation industrial system.
Product Certifications website, rok.auto/certifications Provides declarations of conformity, certificates, and
other certification details.
Notes:
Product Overview
Product Description The Allen-Bradley® 42AF RightSight™ sensor with IO-Link features a new user
interface boosting ultra-bright status indicators, in an 18-mm base and nose
mount. Connecting the 42AF RightSight sensor to IO-Link allows you to take
advantage of advanced sensing functionality including real-time diagnostics,
Automatic Device Configuration (ADC) and access to multiple parameters.
Features • Right-angle housing with universal 30 mm (1.18 in.) threaded nose and
18 mm (0.71 in.) threaded base for maximum application flexibility
• 360° highly visible (status indicators help the operators verify proper
operation regardless of sensor installation location)
• IO-Link Features:
Installation
The Standard IO operation table provides status indicator status in the RUN
mode during operation. The sensor is always in RUN mode, except when being
taught.
Alignment Indication The green LED can also serve as a set-up alignment aid, which indicates that a
margin of 1.5, has been reached. The indication means that the sensor is
receiving at least 1.5 times the signal strength back from the target that is
required to trigger an output signal. In general, it is desirable to have a higher
margin to help overcome any deteriorating environmental conditions, for
example, dust build-up on the sensor lens. When aligning the sensor, the
preferred performance can be obtained if this margin indicator is illuminated
with the target in place. When aligning diffuse mode sensors, be sure that the
sensitivity is set at its maximum setting (use the single-turn adjustment knob
on the front panel). Pan the sensor left, right, up, and down to center the beam
on the target. It could then be necessary to decrease this setting to help prevent
the sensor from detecting a background object. If this problem persists, the
application requires the use of a background suppression, sharp cutoff diffuse,
or retroreflective sensing mode.
Table 3 - Specifications
Attribute Value
User Interface
Electrical
Discrete Output
DC: 1 ms
Response time
AC/DC: 15 ms max
IO-Link
Specifications 1.1
Mechanical
Reliability Data
Attribute Value
T10d 78.76
T10d 111.9875
T10d 291.9285467
T10d 291.9285467
Environmental
Enclosure type rating IP67 and IP69 per IEC 60529 rated enclosure
(1) The sensing range for all sensing modes can be reduced up to 20% when operated between -40…-25 °C (-40…-13 °F).
Mounting Securely mount the sensor on a firm, stable surface, or support. An application,
which is subject to excessive vibration or movement, can cause intermittent
operation. For installation convenience, Rockwell Automation® offers a wide
range of brackets for mounting.
33.8 (1.33)
12.8 (0.5)
11.2 (0.44)
9.8 (0.39)
48.9
(1.92)
4.9 (0.19)
M30 x 1.5 thread
12.2 12.8
(0.48) (0.5) M1 8 x 1 thread
26
(1.02)
23.3(0.92)
34.9 (1.37) M12 x 1 thread 21 (0.83)
12.67 (0.5)
6.35 (0.25)
Typical Response Curves Figure 6 - Visible Red Polarized Retroreflective — 10 m Margin Curve
80.000
70.000
60.000
50.000
40.000
30.000
20.000
10.000
0.000
0.01 0.1 1 10
(0.03) (0.33) (3.28) (32.81)
Distance [cm]
5
0
-5
-10
-15
-20
-25
-30
0 2 4 6 8 10 12
(6.56) (13.12) (19.68) (26.25) (32.81) (39.37)
Distance [m (ft)]
10000
Operating Margin
1000
100
10
1
0.1 1 10 100
(0.33) (3.28) (32.81) (328.08)
Sensing Distance [m (ft)]
5
0
-5
-10
-15
-20
-25
-30
0 2 4 6 8 10 12
(6.56) (13.12) (19.68) (26.25) (32.81) (39.37)
Distance [m (ft)]
Wiring The quick-disconnect connector is shown in Figure 10. The pin numbers
correspond to the male connectors on the sensor.
Figure 10 - Pinouts
DC Models
Figure 11 - Polarized Retroreflective (42AF-P2MPB1-x) Light Operate and Dark Operate
(Auto PNP or NPN)
Brown (1)
+V
White (2) Dark Operate (Auto PNP/NPN)
Black (4) Light Operate (Auto PNP/NPN)
Blue (3)
-V
Light-emitting diode Disable -For normal operation, the white wire needs no connection.
To disable the light source, connect the white wire to +V.
Frequency Select - For normal operation, the white wire needs no connection.
To change the emitter operating frequency, connect the black wire to +V. This feature is supported in future
firmware revisions of the Transmitted Beam Receiver.
IMPORTANT For Transmitted Beam Emitter only: Do not connect pin 2 and pin 4 for
normal operation. Unless a change in frequency is required when working
with a receiver, these two pins remain unconnected when wiring the
Transmitted Beam Emitter sensor to an Allen-Bradley® ArmorBlock® I/O
module.
Notes:
• Increased uptime/productivity
Why IO-Link? IO-Link Offers a Full Range of Advanced Features and Functions
Seamless Integration
• Detect damaged sensors and pinpoint their exact location for quick
troubleshooting through Application Specific Name parameter
Descriptive Tags
How Does IO-Link Work? IO-Link delivers data over the same standard field cabling used today. By
connecting an IO-Link sensor to an IO-Link master, the field-device data and
diagnostics are accessible. Go beyond product detection on the machine—now
the health of the machine can be MONITORED as it runs.
1 L+ 24V
3 L- Ground
4 C/Q Communication/
switching signal
IMPORTANT It’s possible that the response time of an IO-Link system is not fast enough
for high-speed applications. It is possible to monitor/configure the sensor
through IO-Link on pin four of the sensors while connecting pin two (if the
sensor offers a second output) of the sensor to a standard input card.
Transmission Rates
Transmission Quality
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 addresses 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 accordingly for these devices. When configuring the
master, you can specify a fixed cycle time and the device-specific minimum
cycle time that’s 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 Table 3 on page 12 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 allows for
selection of 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.
Acyclic Data
Startup of 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.
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 To configure 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.
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).
36
The Studio 5000 Logix Designer° environment combines design and engineer
elements in one interface, which enables users to access IO and configuration
data across the Integrated Architecture system. Rockwell Automation
solutions, provide a smooth, consistent integration of Allen-Bradley IO-Link
enabled devices into the system.
42AF IO-Link Features The 42AF RightSight™ M30 communicates parameters via IO-Link.
• Sensor Heartbeat feature helps deliver excellent reliability operation by
indicating to the PLC if a sensor has lost connectivity due to sensor
failure or faulty wiring.
• Margin Low Alarm minimizes downtime by indicating when the sensor
is about to fail due to insufficient light being reflected.
• Signal Strength provides the raw measurement value of the amount of
light that reflects from the target.
• Margin Levels display the excess gain above the sensor threshold to help
confirm achieve detection of the target.
• Contrast Levels displays the difference between the light signal levels
that the sensor reads the last time that the output was ON versus the last
time that the output was OFF. This display helps identify that there is
enough difference between the target and the background.
• Margin Low and High Indication Multipliers allow for specifying the
minimum margin levels when the local indication light-emitting diode
indicates marginal conditions and stable conditions.
• Location Indication helps locate the sensors in large machines where
there are several units close to each other.
ADC
Sensor
Configuration
Application Specific Name (ASN): The ASN parameter within each sensor
makes it easy to identify the sensor during commissioning and the lifetime of
the machine when collecting data. The name resides in the project and the
sensor itself.
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
used.
Notes:
This chapter shows the physical hardware and software that is required to
configure the 42AF through IO-Link and provides a simple guide to installing
the hardware.
Software
• Studio 5000 environments, version 20 and higher
• Sensor-specific IODD
• 1734-4IOL IO-Link Add-on Profile (AOP)
Example: Setting up In this example, we are showing an Allen-Bradley® POINT I/O chassis with a
1734-AENTR adapter and a 1734-4IOL IO-Link master module in the first
the Hardware slot. The 1734-AENTR is communicating with a CompactLogix™ controller
via EtherNet/IP.
42AF
IMPORTANT Once the sensor adapter and the master module have been configured in
the Controller Organizer Tree and the 42AF has been wired to the master
module, the green LED indicator on the sensor flashes at a 1 Hz rate. The
green indicator associated with the channel that the sensor is wired into on
the right-hand side of the master module also pulses at a 1 Hz rate.
Notes:
Create a Project
Steps to Begin Project To begin a new project in Studio 5000®, follow these steps.
5. Once the project opens up, set up the IP address of the controller to help
confirm communication. To set the IP address, click the browsing icon.
6. Select the controller that is being used for the project. In this example,
we are using a 1769-L36ERM CompactLogix.
AOP Installation Next, verify that Studio 5000 contains the 1734-4IOL IO-Link AOP. Version
20 or higher of Studio 5000 supports this module and AOP. To verify that the
1734-4IOL is installed, helps confirm the 1734 AENT(R) contains the
1734–4IOL in the library. If the AOP is required to be downloaded, reference
Appendix A for more information.
Notes:
Controller 1. Make sure that the controller is offline to configure the IO-Link Master.
3. The module window pops up and shows the available modules. 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 set-up the
adapter IP address. Click OK and then Close.
5. The 1734 AENTR now appears in the Controller Organizer tree.
Initialization To initialize a sensor on an IO-Link Master, register the IODD of the sensor.
The IO Device Description (IODD) files contain the information that is
related to the sensor, integrated into the system environment.
If the IODD file for the 42AF cannot be in the library, it can be downloaded
from http://compatibility.rockwellautomation.com/Pages/
MultiProductDownload.aspx. Once the IODD is registered, there’s no need to
register the IODD again unless it is manually deleted from the Master Tree.
3. Right-click the left section of the screen where the channel information
is located and click “Register IODD.”
4. Select the IODD file that is needed for the sensor being configured and
double-click.
IODD File Once the IODD file is registered, the sensor must be connected to the
IO-Link master. The controller must be off line to add a device to the IO-Link
Master.
1. Right-click the channel number where the sensor is configured and click
“Change.”
Chapter 6 and Chapter 7 describe each tab of the 1734-4IOL AOP in detail
and how to teach the sensor.
Overview The 42AF offers four different tabs to describe the sensor functionality and
operation. These tabs are:
Tab Description
Common Tab Provides general product information about the sensor specifications and IO-link IODD
information.
Observation Tab Provides device monitoring parameters with signal strength ON, signal strength OFF,
contrast, and gain.
Identification Tab Provides the sensor catalog number, series letter, general product description including
the current product firmware, and hardware revisions.
Parameter Tab Displays and allows you to change the IO-Link parameters offered by the 42AF VisiSight™
Sensor.
Diagnosis Tab Offers the different teach functions available in the 42AF.
Tab Description
Vendor Provides the vendor name of the product.
Vendor Text Field used to describe additional product information.
Vendor ID Describes the vendor ID of the manufacturer of the product as designated in the IO-Link
consortium.
URL Displays the vendor URL.
Device Provides the specific catalog number of the product.
Tab Description
Description Describes the sensor features and range performance.
Device ID Displays the unique device ID as defined in the IO-Link specifications.
IO-Link Revision Displays the current IO-Link version that is supported by the device.
Hardware Revision Displays the latest sensor hardware information.
Firmware Revision Displays the latest sensor firmware information.
Bitrate Displays the supported bitrate for communications as defined in the IO-link 1.1 standard.
Tab Description
SIO Mode Describes if the sensor is also designed to operate without an IO-Link connection.
IODD Displays the complete file name of the IODD that is assigned to the product.
Document Version Displays the version control for the IODD.
Date of Creation Displays the IODD file was created.
The Device Information shows us the Vendor Name, Product Name, Product
Text, Product ID, and Serial Number of the exact sensor that is configured.
These fields automatically populate according to the sensor information. These
fields are read-only (RO).
The parameter tab displays the sensor parameter settings, and enabling you to
read data from the sensor or teach the sensor by writing new values.
Setpoint – Threshold allows operators to enter the signal value that is required
for the sensor output to turn ON (threshold) upon target detection. That
means that the sensor signal level must be higher than the threshold for the
output to turn ON. The default value for this parameter is 1000 with
acceptable values from 505…12923.
Hysteresis displays the sensor output hysteresis value. The real value for
hysteresis is this value that is shown on this parameter that is divided by 100.
Pin 2 Mode enables the operation of the 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 Light Operate or Dark Operate. This
parameter is ideal for applications where the response time is critical for the
application as IO-Link response time must not be fast enough to address the
application needs.
Sensor Configuration: In this section, the operator is able to change when the
sensor Indication LEDs can display marginal conditions. Two parameters are
displayed: Margin Level Low Multiplier and Margin Level High Multiplier
Margin Level – Low Multiplier allows you to define when the green LED
should start flashing to reflect a signal level that is below the threshold. The
default value for this parameter is 0.8 with multiple selection options from 0.5
to 0.8 in increments of 0.1X.
Margin Level – High Multiplier allows you to define when the green LED can
stop flashing to reflect a signal level that is higher than the threshold. The
default value for this parameter is 1.5 with multiple selections that could reach
a maximum of 20X. This value means that the sensor must have at least 20
times the amount of light for the Green LED to stop flashing.
Counter: When enabled, the counter counts up on any transition from OFF to
ON until a maximum of 65,535 detections.
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 on page 65 for Index information).
Timer: Measures the amount of time the output is present and absent up to a
maximum period of four seconds.
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 Not Triggered: Displays the amount of time the target was not
detected. The maximum value that this parameter displays is 4095 ms.
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 achieve reliable
detection of the target.
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 must 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 Appendix B for additional information about index.
Duration: Displays the amount of time that the sensor output has been OFF
(Duration Not Triggered) and ON (Duration Triggered).
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 and
the Local User Interface Lock keeps unauthorized operators from changing the
sensor threshold.
Restore Factory Settings: This setting is 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 Appendix A.
Device Reset: This reset is a write-only command that performs the same
function as cycling power in the sensor.
LEDs Enabled: This parameter allows operators to turn OFF or turn ON the
User Interface LEDs (green and orange LEDs). This parameter is ideal for
applications where turning OFF the LEDs is desired to accommodate the
application.
Alignment Mode: This parameter changes the sensor user interface to operate
in alignment mode. The alignment mode uses the green and orange LEDs of
the sensor to visually indicate the strength of the light signal that is reflected
back from the object. The green LED has low visibility if no target is present
(or no reflector is seen) and slowly dims to a brighter state until a maximum
brightness is reached. The indication depends on how much light is reflected
back from the target. When the maximum brightness is reached, the orange
LED changes duty cycle from 10…90%. Table 38 describes the User Interface
behavior while operating in Alignment Mode.
Last Event: Displaces the code for the last event that is initiated by the sensor.
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 Inception: 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.
Actual – Since Power Up: Displays the current internal temperature of the
sensor.
Manage Parameter 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
Differences between IO-Link Correlation check of the read/write parameters in all connected IO-Link
Devices and Controllers 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 device parameters 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, take note that the Refresh function:
• Is only enabled in online mode.
• Is 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 becomes 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.
3. Click “OK.” If you click the “OK” button without fixing the errors, the
read/write parameters of the affected channels are displayed.
Figure 42 - Parameter Tab
Controller Tags
In the Controller Tag view, it is possible to view the status of the sensor process
data (The process data values are not viewable in the Add-on Profile.).
Triggered: This process bit toggles between one or zero depending on the
polarity configuration when the sensor detects the target or not. For diffuse
sensors, this bit displays a zero by default when no target is present and a one
when target is present. For Polarized Retroreflective and Transmitted Beam
sensors, this bit displays a one by default and a zero when the target is blocking
the reflector and the target.
MarginLowAlarm: This process bit toggles between one and zero to indicate if
there is enough margin to achieve reliable target detection. This bit is 1 when
the target is marginal (signal strength is above 0.5X and below 2X). This bit is
zero when the light levels are above the operating margin if the triggered bit is
active. Table 6 on page 55 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 achieve reliable
detection of the target.
Signal: Provides the raw measurement value of the amount of light reflected
from the target.
Notes:
Troubleshoot
This guide is meant to help resolve common issues that occur when
configuring the Bulletin 42AF.
Checklist
Error Cause Remedy
Power indicator The power supply is switched off. Check to see if there’s a reason for it to be switched off (installation or
LED does not light up maintenance work, and so on). Switch on the power supply if
appropriate.
Power indicator The 4-pin M12 plug is not connected to the Connect the 4-pin M12 plug to the sensor and tighten the cap nut by
LED does not light up connector on the sensor hand.
Power indicator Wiring fault in the splitter or control cabinet. Check the wiring carefully and repair any wiring faults.
LED does not light up
“Operator indicator” Supply cable to the sensor is damaged. Replace the damaged cable.
LED does not light up
No IO-Link connection to the device The C/Q communication port on the sensor is not Make sure that the C/Q communication port is connected to the IO-Link
connected to the IO-Link master master.
No IO-Link connection to the device No power supply See error “Operator indicator” LED does not light up.
Push button does not respond to user interface Local operation has been de-activated. Activate local operation.
Notes:
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 users add to their
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 for set-up and
configuration of 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.
Performing 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. Select “Next” in order to install the IO-Link module profiles, accept the
license agreements, select “Next” and follow the module-profiles installation
wizard.
4. Be sure the “Install” option is selected, select “Next,” review the install details
and select “Install.”
5. The installation process begins. The process can take several minutes. Once
completed the “Next” button is available, select “Next.”
6. Select “Finish” and review the release notes for any additional information.
The IO-Link AOP installation is completed.
Notes:
Device Parameters
When using Explicit Messages to read/write parameter values from/to the 42AF,
it’s important to know the Index Number, Data Type, and Size of the Data that
is transmitted/received in the message. The Identification table provides this
information for each of the Device Parameters.
Identification Tab
Index Sub-index
Parameter Name Hex(Dec) Hex (Dec) Access Default Allowed Value Data Type (Length)
Device Information
Vendor Name 0x10(16) 0x00(0) RO Allen-Bradley Allen-Bradley StringT
Product Catalog Number
Product Name 0x12(18) 0x00(0) RO 42AF-D2xxxx-x4 or 42AF-x2xxx-xx StringT
42AF-P2xxxx-x4
42AF-D2xxxx-x4 Series D
Product ID 0x13(19) 0x00(0) RO or 42AF-xxxxx-xx StringT
42AF-P2xxxx-x4 Series D
42AF RightSight™
Product Text 0x14(20) 0x00(0) RO StringT
Diffuse, P-Retro Photoelectric Sensor
Serial Number 0x15(21) 0x00(0) RO — StringT
User-Specific Information
Application-Specific 0x18(24) 0x00(0) RW 0 — StringT
Tag
UIntegerT
User Tag 1 0xC0(192) 0x00(0) RW 0 —
bitLength=32
UIntegerT
User Tag 2 0xC1(193) 0x00(0) RW 0 —
bitLength=16
Revision Information
Hardware Revision 0x16(22) 0x00(0) RO 1.0 — StringT
Firmware Revision 0x17(23) 0x00(0) RO 1.0 — StringT
Observation Tab
Index Sub-index
Parameter Name Hex(Dec) Hex (Dec) Access Default Allowed Value Data Type (Length)
Device Monitoring
UIntegerT(RecordT)
.SignalStrength On 0x56(86) 0x01(1) RO — 0…65,535 bitLength=16
bitOffset=16
UIntegerT(RecordT)
.SignalStrength Off 0x56(86) 0x02(2) RO — 0…65,536 bitLength=16
bitOffset=0
UIntegerT
Contrast 0x57(87) 0x00(0) RO — 0…255
bitLength=8
UIntegerT
Excess Gain 0x59(89) 0x00(0) RO — 0…255
bitLength=8
Gain (only for 42AF polarized UIntegerT
0x59(89) 0x00(0) RO — 0…255
retroreflective) bitLength=8
Parameter Tab
Index Sub-Index
Parameter Name Hex(Dec) Hex (Dec) Access Default Allowed Value Data Type (Length )
User Interface Configuration
Operation Configuration
Triggered1(or Triggered)
Uinteger(RecordT)
.Set Point - Threshold 0x3C(60) 0x01(1) RW 1000 505…12923 bitLength=16
bitOffset=16
Boolean (RecordT)
0 = Not Inverted,
.Polarity 0x70(112) 0x01(1) RW 1= Inverted bitLength=48
1 = Inverted
bitOffset=40
Uinteger(RecordT)
.Hysteresis 0x3D(61) 0x03(3) RO 1650 bitLength=16
bitOffset=0
0 = Disabled
Uinteger
Pin 2 Mode 0x60(96) 0x00(0) RW 0 = Disabled 1 = Light Operate
bitLength=8
2 = Dark Operate
Sensor Configuration
0 = 0.5
1 = 0.6 Uinteger(RecordT)
.MarginLevel - Low Multiplier 0x58(88) 0x01(1) RW 4 = 0.8 2 = 0.6 bitLength=8
3 = 0.7 bitOffset=8
4 = 0.8
0 = 1.0
1 = 1.5
2 = 2.0 Uinteger(RecordT)
.MarginLevel - High Multiplier 0x58(88) 0x02(2) RW 1 = 1.5 3 = 5.0 bitLength=8
4 = 10.0 bitOffset=0
5 = 15.0
6 = 20.0
Counter/Timer
Counter
Uinteger(RecordT)
0 = Disabled
Mode 0x5D(93) 0x01(1) RW 0 = Disabled bitLength=8
1 = Enabled
bitOffset=24
Uinteger(RecordT)
.Reset 0x5D(93) 0x02(2) WO — 1 = Reset bitLength=8
bitOffset=16
Uinteger(RecordT)
.Counter 0x5D(93) 0x03(3) RO 0 0…65,535 bitLength=16
bitOffset=0
Uinteger(RecordT)
0 = Disabled
.Mode 0x5C(92) 0x01(1) RW 0 = Disabled bitLength=8
1 = Enabled
bitOffset=40
Uinteger(RecordT)
.Reset 0x5C(92) 0x02(2) WO — 1 = Reset bitLength=8
bitOffset=32
Uinteger(RecordT)
.DurationTriggered 0x5C(92) 0x03(3) RO 0 0…4,095
bitLength=12
Uinteger(RecordT)
.DurationNotTriggered 0x5C(92) 0x04(4) RO 0 0…4,095
bitLength=12
Data-Mapping Cofiguration
0=
TriggerMarginLowAlarmProximityAlarmExcessGainLevel
ReceivedSignalStrength,
1=
0= TriggerMarginLowAlarmProximityAlarmExcessGainLevel Uinteger(RecordT)
Triggered,Margin, ContrastLevelTemperature,
.Mode 0x50(80) 0x01(1) RW bitLength=8
Proximity,Gain,Si
gnal, 2= bitOffset=0
TriggerMarginLowAlarmProximityAlarmExcessGainLevel
CounterValue,
3 = TriggerMarginLowAlarmProximityAlarmOnDurationOff
Duration
Diagnostic Tab
Index Sub-index
Parameter Name Hex(Dec) Hex (Dec) Access Default Allowed Value Data Type (Length)
Device Access Locks
Device Access Locks.Parameter (Write) Access Boolean(RecordT)
0x0C(12) 0x00(0) RO 0=False 0=False
Locks bitOffset=0
Boolean(RecordT)
Device Access Locks.Data Storage Lock 0x0C(12) 0x01(1) RO 0=False 0=False
bitOffset=1
0=False Boolean(RecordT)
Device Access Locks.Local Parameterization Lock 0x0C(12) 0x02(2) RW 0=False
1=True bitOffset=2
Service Function
Button = "Device Reset" Button = "Device Reset"
<Standard Command> Device Reset 0x02(2) 0x00(0) WO
Button = 128 Button = 128
Button = "Restore UIntegerT
<Standard Command> Restore Factory Settings 0x02(2) 0x82(130) WO Value = 130
Factory Settings" bitLength=8
Uinteger(RecordT)
0 = Disable(d)
.Locator Indicator 0x5E(94) 0x01(1) RW 0= Disabled bitLength=8
1 = Enable(d)
bitOffset=8
Uinteger(RecordT)
0 = Disable(d)
.LEDs Enable 5E(94) 0x0(2) RW 1= Enabled bitLength=8
1 = Enable(d)
bitOffset=0
Device Status
0 = Disable(d) UIntegerT
Alignment Mode 0x5F(95) 0x00(0) RW 0= Disabled
1 = Enable(d) bitLength=8
UIntegerT
Error Count 0x20(32) 0x00(0) RO — —
bitLength=16
0 = Device is OK
1 = Maintenance
required UIntegerT
Device Status 0x24(36) 0x00(0) RO '0 = Device is OK 2 = Out of specification bitLength=8
3 = Funtional chek
4 = Failure
UIntegerT
Last Event 0x6E(110) 0x00(0) RO 0 0…65,535
bitLength=16
Operation Information
Uinteger(RecordT)
.Operating Time - Since Inception 0x5B(91) 0x01(1) RO bitLength=32
bitOffset=32
Uinteger(RecordT)
.Operating Time - Since Power Up 0x5B(91) 0x0(2) RO bitLength=32
bitOffset=0
Process Data
Parameter Name Sub-index Access Default Allowable Values Data Type (Length)
BooleanT
0 = Not Triggered
Triggered Depends on mode RO 0 = Not Triggered bitLength=32
1 = Triggered
bitOffset=0
BooleanT
0 = Off
MarginLowAlarm Depends on mode RO 0 = Off bitLength=32
1 = On
bitOffset=1
BooleanT
0 = Off
ProximityAlarm Depends on mode RO 0 = Off bitLength=32
1 = On
bitOffset=2
UIntegerT
Gain Depends on mode RO n/a 0...255 bitLength=8
bitOffset=8
UIntegerT
Contrast Depends on mode RO — 0...255 bitLength=8
bitOffset=16
BooleanT
TemperatureInternal Depends on mode RO — -40 to 125 bitLength=32
bitOffset=24
UIntegerT
DurationTriggered Depends on mode RO — 0...4095 bitLength=12
bitOffset=20
BooleanT
DurationNotTriggered Depends on mode RO — 0...4095 bitLength=32
bitOffset=8
UIntegerT
SignalStrength Depends on mode RO — 0...65535 bitLength=16
bitOffset=16
UIntegerT
Count Depends on mode RO — 0...65535 bitLength=16
bitOffset=16
Process Data parameter allows a maximum of four bytes.
Notes:
Configuring a Message This appendix provides additional information and examples that explain how to
configure a Message Instruction.
Instruction
In the examples that we show, we are assuming the use of the ControlLogix®
controller. A ControlLogix® controller can accommodate both downloading
Explicit Message Requests and uploading Explicit Message Responses. The
Message Instruction dialog blocks must be formatted as shown in the examples
shown.
Some of the data that are required to complete the Message Configuration dialog
box comes from Appendix B. Appendix B shows the Index Number, Data Type,
and Size of all the Parameters that are available in the 42AF. To complete the
dialog box, the Service Code and Source Length must be provided.
A table of the different Read and Write Service Codes and their associated
Source Lengths are shown on page 80.
The following table identifies the data that are required to complete the Message
Configuration dialog box to Read the “Vendor Name” from the 42AF:
The Message Configuration dialog box that shows all the information that is
necessary to Write to the Application Specific Name Parameter in the 42AF. To
open the Message Instruction dialog box, click the blue square box in the
Message Instruction.
The following table identifies the data that are required to complete the Message
Configuration dialog box to Write “Test” to the Application Specific Name in
the 42AF:
Validation of Write
Once the Message Instruction dialog box has been populated; trigger the rung of
logic that contains the message instruction. The word “Test” is written from the
“Write_Assembly” to the Application Specific Name Parameter Index in the
42AF.
The data is validated when reading the value of Index 24 in the sensor or when
viewing the 1734-4IOL configuration. To view the configuration of the
1734-4IOL, follow these steps:
2. A popup box is displayed and advises that changes within the sensor have
been detected. Expand the settings and to see that the Application Specific
Name has changed to Test.
3. Click “Upload” then “OK” and the new parameter values are uploaded into
the controller. The new Application Specific Name can be seen when
viewing the Identification Tab of the AOP for the 42AF sensor.
Service Code
The table that is shown is used to determine the Service Code that is needed for a
specific Message Instruction.
Need in Implementation
Service Code (Hex Class Instance Service Name Description of Service
4B Required Required Read Subindex Reads a parameter value from the IO-Link device
4C — Required Write Subindex Writes a parameter value from the IO-Link device
Reads an entire index (all parameters within an index)
4D Required Required Read Subindex from the IO-Link device (uses subindex 0)
Writes an entire index (all parameters within an index)
4E — Required Write Subindex from the IO-Link device (uses subindex 0)
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.
Events
42AF
Event Code - See “1734-4IOL Events” tab 0x0000 0x4000 0x4210 0x4220 0x5000 0x5111 0x7710
0 - Device application (Remote)
Event Location 3
1 - Master application (Local)
0 - Reserved
1 - Event single shot
Event Mode 0 6 1 1 3 3 3 3 3
2 - Event disappears
3 - Event appears
Event Mode 1 7 2 2 2 2 2
Event Source 2 2
0 - Reserved
1 - Notification
Event Type 0 4 1 1 3 2 3 2 3
2 - Warning
3 - Error
Event Type 1 5
0 - Device OK
Status Bit — — — — — — —
1 - Device Fault
Notes:
Technical Support Center Knowledgebase Articles, How-to Videos, FAQs, Chat, User https://rockwellautomation.custhelp.com/
Forums, and Product Notification Updates.
Local Technical Support Phone Numbers Locate the phone number for your country. http://www.rockwellautomation.com/global/support/get-support-now.page
Find the Direct Dial Code for your product. Use the code to
Direct Dial Codes route your call directly to a technical support engineer. http://www.rockwellautomation.com/global/support/direct-dial.page
Documentation Feedback
Your 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.
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, ArmorBlock, CompactLogix, ControlLogix, Integrated Architecture, POINT I/O, RightSight, Rockwell Automation, Rockwell Software, and RSLogix 5000 are trademarks of Rockwell Automation, Inc.
EtherNet/IP is a trademark of ODVA, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Rockwell Otomasyon Ticaret A.Ş., Kar Plaza İş Merkezi E Blok Kat:6 34752 İçerenköy, İstanbul, Tel: +90 (216) 5698400