Setting Up Micro800 Controllers For Implicit (Class 1) Communications With POINT I/O Modules Configured As Generic Devices
Setting Up Micro800 Controllers For Implicit (Class 1) Communications With POINT I/O Modules Configured As Generic Devices
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).
Identifies information that is useful and can help to make a process easier to do or easier to understand.
Rockwell Automation recognizes that some of the terms that are currently used in our industry and in this publication are not in alignment
with the movement toward inclusive language in technology. We are proactively collaborating with industry peers to find alternatives to such
terms and making changes to our products and content. Please excuse the use of such terms in our content while we implement these
changes.
Preface
About This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Download Firmware, AOP, EDS, and Other Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Chapter 1
Configuration Procedure Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
What You Need . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Follow These Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Chapter 2
Connection Configuration Example – Exclusive Owner Connection Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Example Using the POINT I/O
Generic Device Configurator
Chapter 3
Connection Configuration Example – Exclusive Owner Connection Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Examples Using Manual Example Listen-only Connection Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Example Input-only Connection Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Reference
Notes:
Summary of Changes
This publication contains the following new or updated information. This list includes substantive updates only and is not intended to reflect
all changes.
Topic Page
Updated Before You Begin 7
Updated What You Need 8
Updated Follow These Steps 8
Added Connection Configuration Example Using the POINT I/O Generic Device Configurator 11
Additional Resources
These documents contain additional information concerning related products from Rockwell Automation. You can view or download
publications at rok.auto/literature.
Additional Resources
Resource Description
Micro830, Micro850, and Micro870 Programmable Controllers User Manual, Describes how to install, configure, use, and troubleshoot your Micro830®, Micro850, and
publication 2080-UM002 Micro870 controllers.
Provides specifications and information to help you select POINT I/O adapters, I/O modules,
POINT I/O Modules Selection Guide, publication 1734-SG001 and accessories based on your requirements.
Describes how to install, configure, and maintain an EtherNet/IP™ control system that
POINT I/O EtherNet/IP Adapter Module User Manual, publication 1734-UM011 communicates with POINT I/O modules through a 1734-AENT adapter.
Assembly Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP Describes how to use Assembly Connections with POINT I/O and ArmorPOINT I/O modules.
Adapters User Manual, publication 1734-UM016
POINT I/O and ArmorPOINT I/O Dual-port EtherNet/IP Adapters User Manual, Describes how to install, wire, configure, troubleshoot, and use a 1734-AENTR series C and
publication 1734-UM017 1738-AENTR series B adapter.
Describes how to install, wire, configure, troubleshoot, and use a 1734-AENT series C
POINT I/O EtherNet/IP Adapter User Manual, publication 1734-UM018 adapter.
Configuration Procedure
You must enable macros to use the POINT I/O Generic Device Configurator.
b. Verify that there are no errors under the Remarks column and the Check column.
c. In the Tag Mapping sheet, review the table to see which words in the generic predefined tags belong to which module.
d. In the Assembly database sheet, select Update to populate the table with the module assembly element values and definitions of
the modules that you have selected.
e. Complete the configuration using the information from the POINT I/O Generic Device Configurator tool.
2. Once the Generic Device configuration is complete, download the project to the controller and verify that the connection status goes
to Running. If not, verify that you entered in the correct Generic Device configuration parameters and the correct chassis size.
Alternatively, you can complete the configuration procedure manually.
1. Complete the Generic Device configuration.
a. Exclusive owner connections to the POINT I/O adapter are configured using the Data-SINT comm format. Input-only and listen-only
connections are configured using the Input Data-SINT comm format. One controller must have an exclusive owner connection that
is made before other controllers can successfully make listen-only connections.
b. For the POINT I/O adapter, the Assembly Instance is always 101 for Input and 102 for Configuration. For the Output Assembly
Instance, exclusive owner connections use 100, input-only connections use 190, and listen-only connections use 191. The Assembly
Instance values are found in Table 2 in Chapter 1 of the Assembly Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP
Adapters User Manual, publication 1734-UM016. In this context, produced is another name for input and consumed is another name
for output.
c. Determine the total sizes of input and output bytes for the adapter and I/O modules.
• Always include 8 input bytes for the adapter in the total input size. These 64 bits provide the status of POINT I/O slots 0…63. If
the bit is 0, there is a functioning module present in the slot corresponding to that bit. Because POINT I/O modules support
removal and insertion under power (RIUP), these bits make it possible to monitor whether any modules have been removed.
• For the number of input and output bytes for each I/O module to include for the size totals, see Tables 17 and 18 in Chapter 5 of
the Assembly Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP Adapters User Manual, publication 1734-UM016.
d. Connections can be made without configuration (0 bytes), with configuration for the adapter alone, or with configuration for the
adapter and any combination of I/O modules.
e. It is recommended to start with a configuration that includes only the adapter configuration. Once a successful connection has
been established, you can add more I/O module configurations one by one.
• Begin by setting the configuration size to 10. For the 10-byte Adapter Configuration Assembly structure, see Table 3 in Chapter 2
of the Assembly Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP Adapters User Manual, publication 1734-UM016. The
first ten bytes of the Generic Device configuration array are used for the adapter. Only the fifth element, “Chassis Size (Low
Byte),” must be set to a nonzero initial value. The POINT I/O chassis size is 1 + the number of installed I/O modules.
2. Once the Generic Device configuration is complete, download the project to the controller and verify that the connection status goes
to Running. If not, verify that you entered in the correct Generic Device configuration parameters and the correct chassis size.
3. If you desire to configure any of the I/O modules at connection time, do that one module at a time. (If no configuration bytes are
included for an I/O module, then that module uses whatever settings were last configured for it, which would be the default settings if
its configuration has never been changed.)
a. For the number of configuration bytes for the I/O module to add to the size total, see Tables 17 and 18 in Chapter 5 of the Assembly
Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP Adapters User Manual, publication 1734-UM016.
b. For every I/O module that includes configuration, an additional four bytes must be added to the configuration size.
• These first four bytes are the slot number that the module is installed in, the configuration data size in bytes (found in Tables 17
and 18), and the low byte and high byte of the Configuration Assembly Instance number (also found in Tables 17 and 18), as
described in Table 4 in Chapter 2 of the Assembly Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP Adapters User
Manual, publication 1734-UM016.
c. To determine what each byte means for a particular I/O module, see the Configuration Assembly Instance tables in Chapter 5 of the
Assembly Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP Adapters User Manual, publication 1734-UM016.
d. To determine the valid and default configuration byte values for each of the I/O modules, see Appendix C (POINT I/O Module and
RSLogix 5000® Software Controller Tag Reference) of the POINT I/O EtherNet/IP Adapter Module User Manual, publication
1734-UM011. When integer values are listed, those 16-bit integer values must be converted into two 8-bit signed integers (SINTs) to
be entered in as global variable initial values in the Connected Components Workbench software project.
Notes:
3. Create a Micro850 or Micro870 controller project, version 21 or later, in Connected Components Workbench software.
4. Under Ethernet > Modules, select Add.
5. Under General, enter a Name for the POINT I/O adapter and enter its IP Address. Leave the other fields under General and Connection
at their default settings.
6. Under Comm Config, enter the values that are generated in the POINT I/O Generic Device Configurator, then select OK.
7. Three new Global/Controller variables are automatically created based on the Generic Device name and appended with ‘_C’ for
configuration, ‘_I’ for input, and ‘_O’ for output.
8. Expand the configuration (_C) variable and enter the chassis size that is specified in the POINT I/O Generic Device Configurator into
the _C[4] element’s Initial Value.
9. From the Tag Mapping sheet, enter the values that are shown into the configuration (_C) variable byte element Initial Values.
10. On the Assembly database sheet, select Update. The sheet populates with the module configuration that you have selected in the
Config sheet.
11. Complete the configuration of the 1734-IB8 module by entering the Initial Values for configuration elements _C[14] to _C[45] with the
byte 0…31 Default values listed.
These configuration values can be adjusted later once you have finished the configuration and verified that the project is working.
12. Scroll down to the 1734-OB4E module listings and enter the Initial Values for configuration elements _C[50] to _C[57] with the byte
0…7 Default values listed.
13. Scroll down to the 1734-IE2C module listings and enter the Initial Values for configuration elements _C[62] to _C[99] with the byte
0…37 Default values listed.
14. Scroll down to the 1734-OE2C module listings and enter the Initial Values for configuration elements _C[104] to _C[139] with the byte
0…35 Default values listed.
There should now be Initial Values that are assigned for configuration elements _C[0] to _C[139].
15. Verify that the controller has a configured IP address, then download the project to the controller and, once connected, verify that the
Connection status indicates Running.
2. Under General, choose a Name for the POINT I/O adapter and enter its IP Address. Leave the other fields under General and Connection
at their default settings.
3. Under Comm Config, set the Comm Format to Data – SINT, the Input Assembly Instance to 101, the Output Assembly Instance to 100 and
the Configuration Assembly Instance to 102. In this context, produced is another name for input and consumed is another name for
output.
Table from Assembly Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP Adapters User Manual, publication 1734-UM016.
4. Determine the total sizes of input and output bytes for the adapter and I/O modules.
a. 1734-AENTR = 8 Input/0 Output
b. 1734-IB8 = 1 Input/0 Output
c. 1734-OB4E = 1 Input/1 Output
Table from Assembly Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP Adapters User Manual, publication 1734-UM016.
Table from Assembly Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP Adapters User Manual, publication 1734-UM016.
Therefore:
- The total input size is 8 + 1 + 1 + 6 + 2 = 18
- The total output size is 0 + 0 + 1 + 0 + 4 = 5
5. Set the configuration size to 10 for the adapter.
Table from Assembly Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP Adapters User Manual, publication 1734-UM016.
The AENTR_O, AENTR_I, and AENTR_C arrays are automatically created (with naming based on the Name that is entered for the
Module).
Table from Assembly Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP Adapters User Manual, publication 1734-UM016.
Table from Assembly Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP Adapters User Manual, publication 1734-UM016.
Table from Assembly Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP Adapters User Manual, publication 1734-UM016.
Use the COP copy instruction to copy each two bytes of channel data into individual integer array elements.
Table from Assembly Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP Adapters User Manual, publication 1734-UM016.
Table from Assembly Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP Adapters User Manual, publication 1734-UM016.
Table from Assembly Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP Adapters User Manual, publication 1734-UM016.
Use the COP copy instruction to copy individual integer array elements into the two bytes of channel data.
9. Chassis size is 1 + 4 = 5. Set the Initial Value of AENTR_C[4] to 5. Leave the other Initial Values blank or set to zero.
Table from Assembly Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP Adapters User Manual, publication 1734-UM016.
10. Download the project to the controller and once connected, verify that the Connection status indicates Running.
11. To configure the first I/O module, the 1734-IB8, go offline with the controller and add the number of configuration bytes for the I/O
module to the Configuration size. See Tables 17 and 18 in Chapter 5 of the Assembly Connections for POINT I/O and ArmorPOINT I/O
EtherNet/IP Adapters User Manual, publication 1734-UM016. The table also includes the Configuration Assembly Instance, which is
needed in a later step.
Always add four bytes plus what is found in the table for each I/O module. The total size is 10 + 32 + 4 = 46.
Table from Assembly Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP Adapters User Manual, publication 1734-UM016.
13. The adapter configuration occupies AENTR_C[0…9], so the 1734-IB8 configuration directly follows in AENTR_C[10…55].
The first four bytes are:
- Slot Number = 1
- Configuration Size = 32
- Configuration Assembly Instance (low byte) = 103
- Configuration Assembly Instance (high byte) = 0
Table from Assembly Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP Adapters User Manual, publication 1734-UM016.
14. Each of the eight inputs uses four bytes to configure the input filter settings.
Table from Assembly Connections for POINT I/O and ArmorPOINT I/O EtherNet/IP Adapters User Manual, publication 1734-UM016.
15. To determine the configuration setting values for the 1734-IB8 module, see Appendix C of the POINT I/O EtherNet/IP Adapter Module
User Manual, publication 1734-UM011. Although the 1734-IB8 module is not listed in this manual, we can assume that the configuration
setting values are the same as for the 1734-IB4 module.
Table from POINT I/O EtherNet/IP Adapter Module User Manual, publication 1734-UM011.
16. The default setting is 1000 microseconds (which is 1 millisecond). If the desired input filter setting is 2000 microseconds (which is 2
milliseconds), this INT value must be converted into two SINTs to get the low byte and high byte.
One method to accomplish the conversion is to use a converter such as:
Integer converter: Translate between 8, 16 and 32-bit ints - cryptii.
For 2000 microseconds, the low byte is -48 and the high byte is 7.
17. Alternate between -48 (input filter low byte) and 7 (input filter high byte) for the 32 Initial Values in AENTR_C[14…45].
18. As an alternative to entering the configuration byte values directly, you can program the COP instruction to copy an array of the input
filter integer values into the configuration array byte values.
19. Download the project to the controller and once connected, verify that the Connection status indicates Running.
20. Repeat steps 11…19 to configure any of the other three I/O modules.
Table 1 - Configuration for 1734-AENTR and I/O Modules (with default configurations) (Continued)
Byte# Parameter Value Byte# Parameter Value
74 High High Alarm Channel 0 (low byte) -103 (16793) 95 Alarm Latch Channel 1 0 (disabled)
75 High High Alarm Channel 0 (high byte) 65 96 Alarm Disable Channel 1 0 (disabled)
76 Range Channel 0 3 (4…20 mA) 97 Notch Filter 2 (60 Hz)
77 Alarm Latch Channel 0 0 (disabled) 98 Update Rate (low byte) 100 (100 ms)
78 Alarm Disable Channel 0 0 (disabled) 99 Update Rate (high byte) 0
1734-OE2C (with firmware revision 3.001) – 2 Input/4 Output/40 Configurable
100 Slot Number 4 120 Alarm Disable Channel 0 0 (disabled)
101 Configuration Size (in bytes) 36 121 Alignment (reserved) 0
102 Assembly Instance (low byte) 123 122 Fault Data Channel 1 (low byte) 0
103 Assembly Instance (high byte) 0 123 Fault Data Channel 1 (high byte) 0
104 Fault Data Channel 0 (low byte) 0 124 Idle Data Channel 1 (low byte) 0
105 Fault Data Channel 0 (high byte) 0 125 Idle Data Channel 1 (high byte) 0
106 Idle Data Channel 0 (low byte) 0 126 Low Engineering Channel 1 (low byte) 102 (1638)
107 Idle Data Channel 0 (high byte) 0 127 Low Engineering Channel 1 (high byte) 6
108 Low Engineering Channel 0 (low byte) 102 (1638) 128 High Engineering Channel 1 (low byte) -1 (8191)
109 Low Engineering Channel 0 (high byte) 6 129 High Engineering Channel 1 (high byte) 31
110 High Engineering Channel 0 (low byte) -1 (8191) 130 Low Clamp Channel 1 (low byte) 0 (-32768)
111 High Engineering Channel 0 (high byte) 31 131 Low Clamp Channel 1 (high byte) -128
112 Low Clamp Channel 0 (low byte) 0 (-32768) 132 High Clamp Channel 1 (low byte) -1 (32767)
113 Low Clamp Channel 0 (high byte) -128 133 High Clamp Channel 1 (high byte) 127
114 High Clamp Channel 0 (low byte) -1 (32767) 134 Range Channel 1 0 (4…20 mA)
115 High Clamp Channel 0 (high byte) 127 135 Fault Action Channel 1 1 (go to Low Clamp)
116 Range Channel 0 0 (4…20 mA) 136 Idle Action Channel 1 1 (go to Low Clamp)
117 Fault Action Channel 0 1 (go to Low Clamp) 137 Alarm Latch Channel 1 0 (disabled)
118 Idle Action Channel 0 1 (go to Low Clamp) 138 Alarm Disable Channel 1 0 (disabled)
119 Alarm Latch Channel 0 0 (disabled) 139 Alignment (reserved) 0
The input assignments are the same as in the exclusive owner example (Table 1):
• AENTR_I[0].0…AENTR_I[7].7: 1734-AENTR slot 0…63 status (0 = module present in slot# = bit#)
• AENTR_I[8].0…AENTR_I[8].7: 1734-IB8 discrete inputs 0…7 data
• AENTR_I[9]: 1734-OB4E (reserved)
• AENTR_I[10]: 1734-IE2C channel 0 data (low byte)
• AENTR_I[11]: 1734-IE2C channel 0 data (high byte)
• AENTR_I[12]: 1734-IE2C channel 1 data (low byte)
• AENTR_I[13]: 1734-IE2C channel 1 data (high byte)
• AENTR_I[14]: 1734-IE2C channel 0 status
• AENTR_I[15]: 1734-IE2C channel 1 status
• AENTR_I[16]: 1734-OE2C channel 0 status
• AENTR_I[17]: 1734-OE2C channel 1 status
The configuration values for AENTR_C[0…3] and AENTR_C[5…45] are the same as in the exclusive owner example (Table 1).
The initial value of AENTR_C[4] should be set to the chassis size in this example of 2 (for the adapter plus one input module).
Notes:
Documentation Feedback
Your comments help us serve your documentation needs better. If you have any suggestions on how to improve our content, complete the
form at rok.auto/docfeedback.
At the end of life, this equipment should be collected separately from any unsorted municipal waste.
Rockwell Automation maintains current product environmental compliance information on its website at rok.auto/pec.
Allen-Bradley, ArmorPOINT, Connected Components Workbench, expanding human possibility, FactoryTalk, Micro800, Micro830, Micro850, Micro870, POINT I/O, Rockwell Automation,
RSLogix 5000, and TechConnect are trademarks of Rockwell Automation, Inc.
Microsoft and Excel are trademarks of Microsoft Corporation.
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 EEE Yönetmeliğine Uygundur