Maepgetst-Eng V102 12 2009

EtherNet/IP - Getting Started
User's Manual
Version: 1.02 (December 2009)

Model No.: MAEPGETST-ENG
All information contained in this manual is current as of its creation/publication. We reserve the right to change the contents of this manual
without warning. The information contained herein is believed to be accurate as of the date of publication; however, Bernecker + Rainer
Industrie-Elektronik Ges.m.b.H. makes no warranty, expressed or implied, with regards to the products or the documentation contained
within this book. In addition, Bernecker + Rainer Industrie-Elektronik Ges.m.b.H. shall not be liable in the event of incidental or consequential
damages in connection with or resulting from the furnishing, performance, or use of these products. The software names, hardware names,
and trademarks used in this document are registered by the respective companies.
Copyright © B&R – Subject to change without notice 1
MAEPGETST-ENG_V102_12_2009.doc
EtherNet/IP - Getting Started on Rockwell Systems
User's Manual
I Table of Contents
1 General Overview ....................................................................................................... 3

1.1.1 LED Status Indicators...................................................................................................................................... 4
1.1.2 Network Address Switches.............................................................................................................................. 5
1.2 Supported 3rd Party Hardware and Software........................................................................................6
1.2.1 Supported Allen-Bradley® CPUs..................................................................................................................... 6
1.2.2 Supported Allen-Bradley® Software................................................................................................................ 6
1.3 Overview of Programming Options.......................................................................................................6
1.3.1.1 Automatic Configuration ............................................................................................................................ 6
1.3.1.2 User Configuration..................................................................................................................................... 6
1.4 System Overview – Configuration via FieldbusDESIGNER .................................................................7
2 Automatic Configuration ........................................................................................... 8

2.1.1 Step-by-Step Guide to Setting up Bus Controller ............................................................................................ 8
2.1.2 Configuration and I/O Assembly Explanation ................................................................................................ 10
2.1.3 Online with RSLogixTM 5000..........................................................................................................................11
3 User Configuration................................................................................................... 13
3.1.1 Step-by-Step Guide to Setting up Bus Controller .......................................................................................... 13
3.1.1.1 Overview.................................................................................................................................................. 13
3.1.1.2 Inserting Allen-Bradley® Hardware and Bus Controller........................................................................... 13
3.1.1.3 Configuration of Bus Controller................................................................................................................ 17
3.1.1.4 Inserting Modules into FieldbusDESIGNER ............................................................................................ 18
3.1.1.5 Configuration of Modules......................................................................................................................... 21
3.1.1.6 Building a Project..................................................................................................................................... 23
3.1.2 Going Online with RSLogixTM 5000 ............................................................................................................... 24
3.1.3 Transferring IO into Existing Projects ............................................................................................................ 25
4 Bus Controller Capabilities ..................................................................................... 28

4.1.1 Speed and Performance ............................................................................................................................... 28
4.1.2 System Size Limits ........................................................................................................................................ 28
4.1.3 Multiple Configurations .................................................................................................................................. 29
4.1.4 Guidelines for Proper Operation.................................................................................................................... 29
4.2 Integrated Web Interface ....................................................................................................................29
4.3 Optimized Performance ......................................................................................................................30
4.3.1 Setting Proper RPI and X2X Time................................................................................................................. 30
5 Module Configuration / Writing to Registers ......................................................... 32
APPENDIX: Additional Documentation ..................................................................... 34
2 Copyright © B&R - Subject to change without notice

User's Manual
1 General Overview
The EtherNet/IP bus controllers (X20BC0088 and X67BCD321.L12) allow connecting X20-, X67-, and XV-I/O
modules to any EtherNet/IP protocol scanner like an Allen-Bradley® master PLC. B&R IO can be automati-
cally configured with default module functionality directly with RSLogixTM 5000, or configured using Fieldbus-
DESIGNER. This tool features a comprehensive help system for first time users, and offers a very familiar in-
terface for experienced B&R users. With FieldbusDESIGNER, users can configure modules, get details on
I/O mapping, and even create complete project files giving easy access to user defined I/O data points in-
stead of byte arrays. FieldbusDESIGNER can be downloaded and registered for free (see included help sys-
tem and installation guidelines of setup program for more information: http://www.br-automation.com/designer
A web interface on the bus controllers provides easy access to diagnostic features and allows configuration
of several parameters like network settings and changing I/O assembly sizes. The web interface is available
for X20BC0088 Revision B4 and above as well as all X67BCD321.L12 from Rev.A1.
Existing revision B modules of X20BC0088 might be updated with firmware v1.07 to feature the web inter-
face; please contact B&R support for details.
The B&R EtherNet/IP bus controllers were created in compliance with the EtherNet/IP specification governed
by ODVA (Open DeviceNet Vendor Association). When using FieldbusDESIGNER, the default CPU for the
generated project is the 1769-L35E CompactLogix® Controller. However, the generated project can be used
for any Logix platform (see chapter 3.1.3).
This document will provide the programmer with a detailed description of the bus controller including how to
setup, configure and diagnose the module. Further information about this module can be obtained from the
document list in Section 8: Appendix.
Copyright © B&R - Subject to change without notice 3

User's Manual
1.1.1 LED Status Indicators

X20BC0088 X67BCD321.L12
LED Color Status Description

On At least one client is connected
Green
Blinking Bus controller not yet configured
Mod Status 1) On Major unrecoverable fault
Red
Blinking Major recoverable fault
Blinking green/red Initialization / Self test2)
On At least one active master (scanner) connection is established
Green
Blinking No active master (scanner) connection established
Net Status 1) On IP address is not unique
Red
Blinking Timeout on at least one connection
Blinking green/red Initialization / Self test
L / A IF1 Blinking The LED blinks when Ethernet activity is present on the bus
Green On Connection (link) established, no activity on the bus
L / A IF2 Off No physical Ethernet connection exists
Status indicator 2 Status of integrated I/O module (digital mixed I/O) – see data sheet for more details
1) ‘Mod Status’ and ‘Net Status’ LEDs are green/red dual LEDs
2) If this will not stop blinking, there is a configuration issue with your system

User's Manual
1.1.2 Network Address Switches
Network Address Function

Switch Value
$00 Use the IP address and connection parameters saved into flash memory. This
is the switch setting defined upon delivery. In position $00 the network address
switch doesn't have any effect on the system parameter.
$01 to $7F The last position of the IP address saved in flash memory is temporarily re-
placed with the station number. The IP address stored in the flash memory is
not changed.
$80 to $EF The bus controller runs in DHCP mode. A host name is generated according to
the setting of the network address switch:
"br" + "eip" + network address switch value (three decimal places)
This means that the following host name is generated for switch value $D7
(dec. 215): "breip215"
The IP address stored in the flash memory is not changed.
$F0 to $FD Reserved. Currently same as 0xFF.
$FE All bus controller parameters are initialized with default values during the boot
procedure. No values are read from the flash memory. The communication
parameters are equal to the values as with the switch setting $FF.
$FF Boots with default values:
IP address: 192.168.100.1
Network mask: 255.255.255.0
Gateway: 192.169.100.254
The IP address stored in the flash memory is not changed.
The bus controller can be addressed via Windows® NetBIOS service (only if no other routers or gateways are in
the way):
Primary NetBIOS name is “br” + MAC address (e.g. MAC address printed on enclosure is IFX 00-60-65-07-C5-AE
Æ primary NetBIOS name is br00606507c5ae).
Secondary NetBIOS name is: “br” + “eip” + network address switch value (three decimal places)
For station number 0x00 the secondary NetBIOS name is identical to primary NetBIOS name.

User's Manual
1.2 Supported 3rd Party Hardware and Software

The B&R EtherNet/IP bus controllers X20BC0088 and X67BCD321.L12 modules adhere to the EtherNet/IP
specification, so it can operate with any EtherNet/IP scanner.
1.2.1 Supported Allen-Bradley® CPUs

Allen-Bradley® CPUs from the Logix family including CompactLogix® and ControlLogix®, FlexLogix®, and
DriveLogix®. The default processor for FieldbusDESIGNER is the CompactLogix® 1769-L35E. However, the
generated project can be used for any Logix platform (see chapter 3.1.3).
1.2.2 Supported Allen-Bradley® Software

All functional testing was performed using RSLogixTM 5000 versions 15.01 and 16.03
1.3 Overview of Programming Options

There are two options for programming the B&R EtherNet/IP bus controllers: automatic configuration (default
configured) and configuration via FieldbusDESIGNER (user configured).
1.3.1.1 Automatic Configuration

Default (or “automatic”) configuration allows the programmer to stay within the RSLogixTM 5000 programming
environment, and does not require additional software (refer to Section 2: Default Setup). Each module con-
nected behind the bus controller is used in its default configuration and I/O points are manipulated through
their respective byte offsets. If configuration of modules beyond their default configuration is needed, it must
be done with explicit messages in RSLogixTM 5000, or by directly connecting to the module (e.g. Telnet inter-
face of bus controller).
1.3.1.2 User Configuration

Using B&R’s FieldbusDESIGNER allows the programmer more configuration options. Modules can be con-
figured beyond their default setups and I/O points can be assigned a descriptive name. FieldbusDESIGNER
generates an *.L5K file which can be directly imported with RSLogixTM 5000.

User's Manual
1.4 System Overview – Configuration via FieldbusDESIGNER
FieldbusDESIGNER
Allen-Bradley®
I/O configuration
Allen-Bradley® CPU
I/O device
Configuration
Assembly

User's Manual
2 Automatic Configuration
Default (or “automatic”) configuration is done completely within RSLogixTM 5000 using each I/O module’s in-
ternally stored default setup. If necessary, this default setup can be altered later using explicit messages or
by directly connecting to the bus controller. This setup mode is recommended for systems which have a lim-
ited number of digital and analogue I/O points, or systems that allow for modules to operate in their default
configuration. Additional modules can be added to a system at any time, with no (or very limited) changes to
the system required.
The following programs are required:

RSLogixTM 5000 V15 or above (programming)
RSLinxTM (online communication)
2.1.1 Step-by-Step Guide to Setting up Bus Controller

Create a new project in RSLogixTM 5000 and insert your Allen-Bradley® processor
On the Ethernet Port, under Communications, insert a generic Ethernet Module “ETHERNET-MODULE”

User's Manual
Configure new generic Ethernet module

1) Insert a name
2) Comm Format should be “Data – SINT” (differing settings require adoption of assembly sizes)
3) IP address setup according to Section 1.1.2 Network Address Switches.
4) Setup Assembly Instance and Size according to Section 2.1.2: Configuration and I/O Assembly Ex-
planation.

User's Manual
2.1.2 Configuration and I/O Assembly Explanation
Configuration Assembly
Instance ID Type Description Size in Bytes

100, 0x64 Base Configuration for the I/O modules 400*
* 400 Bytes is the maximum configuration size. When using default setup, the size for the configuration as-
sembly must be set to 0, since no configuration data is sent to the modules.
Output Assembly
Instance ID Type Description Default Size in Bytes

110, 0x6E Base Analog Output 120
111, 0x6F Base Digital Output 120
112, 0x70 Combination Analog + Digital Output 240
Input Assembly
Instance ID Type Description Default Size in Bytes

120, 0x78 Base Analog Input 120
121, 0x79 Base Digital Input 120
122, 0x7A Base Network Status 120
123, 0x7B Base Output Status 120
124, 0x7C Combination Analog Input + Digital Input + Network Status + 480
Output Status

User's Manual
2.1.3 Online with RSLogixTM 5000
When online with the CPU in RSLogixTM 5000, the input and output channels can be accessed through the
I/O assembly tags.
Digital Outputs: BC0088:O.Data[120] is the default offset for digital outputs. The first digital output in the
system is addressed to BC0088:O.Data[120].0, the second to BC0088:O.Data[120].1 and so on.
Digital Inputs: BC0088:I.Data[120] is the default offset for digital inputs. The first digital input in the system is
addressed to BC0088:I.Data[120].0, the second to BC0088:I.Data[120].1 and so on.

User's Manual
Analog Outputs: BC0088:O.Data[0] is the default offset for analog outputs. Each analog output is repre-
sented by an Integer value, or two SINT values. The first analog output in the system is addressed to SINTs
BC0088:O.Data[0] and BC0088:O.Data[1], the second to BC0088:O.Data[2] and BC0088:O.Data[3], and so
on.
Analog Inputs: BC0088:I.Data[0] is the default offset for analog inputs. Each analog input is represented by
an Integer value, or two SINT values. The first analog input in the system is addressed to SINTs
BC0088:I.Data[0] and BC0088:I.Data[1], the second to BC0088:I.Data[2] and BC0088:I.Data[3], and so on.

User's Manual
3 User Configuration
FieldbusDESIGNER is used to configure B&R I/Os behind bus controllers and provides a programming envi-
ronment very similar to B&R Automation Studio. Modules can be setup beyond their default configuration,
and unique names can be assigned to each module’s I/O points. When configuration is complete, a build is
performed which generates an *.L5K file. This file can be imported into RSLogixTM 5000.
FieldbusDESIGNER is available on the B&R website under section ‘Service Æ Material Related Downloads
Æ Automation Software Æ Automation Studio FieldbusDESIGNER’:
http://www.br-automation.com/designer
3.1.1 Step-by-Step Guide to Setting up Bus Controller
3.1.1.1 Overview
The following sections will describe in detail, how to make a project, insert and configure modules, build an
*.L5K file, and go online with an Allen-Bradley® CPU. The last section will cover how to transfer the setup
from one project to another. Transferring between projects will allow the programmer to insert the bus control-
ler into an already existing project, or to transfer the files to a different CPU type.
For further information please reference FieldbusDESIGNER help.
3.1.1.2 Inserting Allen-Bradley® Hardware and Bus Controller

Instructions for inserting Allen-Bradley® Hardware are also inside the FieldbusDESIGNER help:
1) Create a new Project

User's Manual
2) Select a Name and Path for the project, and then press next.
3) Optionally select a Name for the configuration and CPU. Unless an existing hardware configuration from
an other FieldbusDESIGNER project should be used, leave the setting to define a new hardware configu-
ration:

User's Manual
4) Select a CPU module for the new project. The CPU defaults to a CompactLogix®. If the CPU needs to be
changed, this should be done in RSLogixTM 5000. “Multi E/IP Scanners” type should only be used for
ControlLogix® environments in case more than one EtherNet/IP scanner communication module
are used:
5) Open the EtherNet/IP Hardware Tree. Right click on the CPU and select “Open EtherNet/IP.”

User's Manual
6) Insert a bus controller module. Right click in the EtherNet/IP network and select “Insert.”
7) Select the respective bus controller module, and define a station number for it. The station number is
used by FieldbusDESIGNER to distinguish the different I/O devices.

User's Manual
3.1.1.3 Configuration of Bus Controller

Instructions for configuring the bus controller are also available inside the FieldbusDESIGNER help:
8) The bus controller module can be configured by right clicking on it in the hardware tree and selecting
“Open Adapter Configuration.”
9) The IP address, X2X Cycle time, IO settings and other options can be set through the adapter configura-
tion.

User's Manual
3.1.1.4 Inserting Modules into FieldbusDESIGNER

More information about Inserting Modules is inside the FieldbusDESIGNER help:
More information about the X2X bus is inside the FieldbusDESIGNER help:

User's Manual
10) Open the X2X link to add I/O modules. Right click on the bus controller module inside the hardware tree
and select “Open X2X Link.”
11) The X2X Link is open and modules can be inserted. Pay attention that per default a power supply
module X20PS9400 is automatically inserted behind the X20BC0088 bus controller. In case a
X20PS9402 is used, make sure to delete the default power supply and to add the proper module.
See help for more information.

User's Manual
12) Right click on the X2X link and insert the modules.

User's Manual
3.1.1.5 Configuration of Modules
13) One X20DI8371 Digital Input card and one X20DO8322 Digital Output card have been inserted for this
example.
14) IO variable names different to the default name (see Channel Name column) can be inserted optionally in
the “PV or Channel Name” for each data point. Each channel has a default name. For instance, the first
input channel has the name “DigitalInput01” as its default name. If no value is inserted in the “PV or
Channel Name” column, then “DigitalInput01” is the name associated with this channel. For this example
the variable name “Input1” has been defined.

User's Manual
15) Modules can be configured by right clicking on the module within the hardware tree and selecting “Open
IO Configuration”. Each I/O module features the parameter “Function model”. If an I/O module provides
more than the “default” model, the “Insert” dialogue will ask for the model being used. This can be
changed with this parameter, too. The first two parameters under “General” should be left with default
setting as they do not have any effect: “Module supervised = on” corresponds to the default behaviour of
the bus controller, which will treat problems with I/Os as events. These events can have actions as-
signed, see parameter “Module failed” under the bus controller’s “Adapter Configuration” dialogue (see
step 8 under section 3.1.1.3). If “Module information” is switched to “on”, additonal I/O data points will be
displayed under “I/O Mapping” (SerialNumber, ModuleID, HardwareVariant, FirmwareVersion). These
data points have to be accessed as attributes of the “I/O module object” (class 0x65) and will not be part
of the I/O assemblies.

User's Manual
3.1.1.6 Building a Project

16) Once all modules have been inserted and configured, the project can be built. Press F7 or select the
build icon from the icon menu.
17) Additional information will be provided in the output window following the build.
The 4th line of text for the build (see picture above), shows the path of the generated *.L5K file:
Created RSLogix 5000 project file:
C:\projects\MyFirstProject\Output\EthernetIP_CPU1.L5K
The IP address, number of I/O modules, Requested packet interval (RPI) time, Assembly sizes, and ZIP com-
pression rate are all shown. If any assembly size exceeds the maximum, a build error will be displayed. ZIP
compression rate refers to the compression rate of the configuration assembly. Compressed configuration
data allows for more configuration settings within the 400 Bytes allowed by RSLogix. This option can be dis-
abled from the Adapter Configuration menu shown in Section 3.1.1.3: Configuration of Bus Controller.

User's Manual
3.1.2 Going Online with RSLogixTM 5000

Locate and Import the *.L5K file into RSLogixTM 5000. This can be done by double-clicking the L5K file or us-
ing RSLogixTM “FileÆOpen” menu. The L5K file will then be imported into RSLogix.
Under “Data Types Æ User-Defined” the Input and Output data types can be found. The variables names
provided in the FieldbusDESIGNER project are found here. The Configuration, Input, and Output assemblies
can all be found in the “Controller Tags” section.
The following picture shows the controller tags section:
copyInpCounter, copyOutCounter, and mainCounter are lifecycle counters

ST1:C is the configuration assembly, ST1:I is the input assembly, ST1:O is the output assembly
ST1_inp is the input data type tag, ST1_out is the output data type tag
The ST1_inp is copied to the ST1:I input assembly each cycle in the “CopyInputData” program of the Main-
Task. The ST1:O output assembly is copied to the ST1_out tag in the “CopyOutputData” program of the
MainTask.
Pay attention not to work with the I/O data directly, as this is cyclically overwritten by the copy tasks!

User's Manual
3.1.3 Transferring IO into Existing Projects

The following steps describe how to transfer the bus controller information between RSLogixTM 5000 projects.
This is useful for integrating the bus controller into existing projects, or for switching the CPU.
1) Open a second instance of RSLogixTM 5000. One instance will have the project generated by Fieldbus-
DESIGNER, and the other instance will have a new or existing project.
2) Click the “ETHERNET-MODULE ST1 from FieldbusDESIGNER project, drag and drop it into the new
project
This will copy the bus controller module and its assemblies into the new project.

User's Manual
3) If the IO channel names want to be preserved, the User-defined data types must be transferred next. The
data types can be transferred the same as the module: by drag and drop between open instances. If ac-
cess directly to the IO assembly please reference Section 2.1.3 Online with RSLogixTM 5000.
4) Within the Controller tags, define tags for the Input and Output Assemblies. Controller tags can be de-
fined or they can be dragged and dropped between instances. Also, transfer the lifecycle counters (copy-
InpCounter, copyOutCounter, and mainCounter).
5) Transfer the programs between the projects. Programs can be dragged and dropped like the bus control-
ler and data types.

User's Manual
6) Ensure the order stays the same: Copy Inputs, Execute main program, and Copy Outputs.
7) Ensure the IO structures are tied correctly to the copy function blocks.
The project is now transferred.

User's Manual
4 Bus Controller Capabilities
4.1.1 Speed and Performance

X2X cycle times as low as 0.5ms can be achieved, as well as RPI as low as 1.0ms. The number of modules
behind a bus controller is limited by the X2X cycle time and the size of the configuration assembly. The
builder in FieldbusDESIGNER will output a warning, if too much I/O data is configured for a certain X2X cycle
time. The configuration size can be minimized by grouping similar modules under one bus controller.
4.1.2 System Size Limits

The total number of modules behind a bus controller is dependent on the configuration buffer limit of the mas-
ter system and the X2X cycle time. The master is allowed 400 bytes of configuration data in the configuration
buffer. Configurations larger than 400 bytes are possible, but will require additional programming outside of
FieldbusDESIGNER to download configuration data into the corresponding configuration assemblies on the
bus controller (instances 130 to 139 or 0x82 to 0x8B of the Assembly object, class 0x4).
The amount of configuration data required for a module is dependent on the number of configuration registers
used per module. If a wide variety of modules are used, the number of modules will be severely limited. If
many of the same module type are used, compression of the configuration data allows for more modules.
If FieldbusDESIGNER is used to build a system, the size of the configuration, Output, and Input assemblies is
given upon successful project build.
If more modules are required, they can be split between multiple bus controllers. The bus controller network
can have up to a few hundred analog and a few hundred digital I/O modules (253 modules in total).
Limits (set by Allen-Bradley®):
Configuration data: 400 Bytes

Output Assembly: 496 Bytes
Input Assembly: 500 Bytes

User's Manual
Each Byte represents 8 digital I/O on a X20DI9371 or an X20DO9322 module.
4.1.3 Multiple Configurations

Downloading multiple configurations to the bus controller is possible. Multiple configurations can be
downloaded via explicit messaging or the web interface. The RSLogix 5000® project generated by Fieldbus-
DESIGNER downloads to the standard configuration (assembly instance 100 or 0x64 of class 0x4).
There are an additional 10 assembly IDs reserved for configurations (instances 130 to 139 or 0x82 to 0x8B of
the Assembly object, class 0x4). Once successfully downloaded to the bus controller, the active configuration
is set using service 0x37 of the Bus Controller object (class 0x64).
4.1.4 Guidelines for Proper Operation

The following items work without limitations:
• Standard I/O Modules (X20, X67, XV)

• All standard DC modules (X20)
• Node number modules (X20/X67)
• Switching function models
The following items work with limitations:
• Serial interfaces (X20CS10x0) can only be used behind a bus controller when operated in default
‘bus controller’ function model called “flat stream” mode
• Stepper modules (X20SMxxxx) have to be operated in “ramp” function model
Not supported at this time:
• B&R NetTime and module functions that use it

• Special module functions requiring data exchange between module and application w/o handshaking
(stream X2X communication) like transmitting scope data with an X20AIx632 – see module docu-
mentation for more details
4.2 Integrated Web Interface

The integrated web interface allows for remote access of the bus controller.
The web interface includes:
• Status information for bus controller (network information, firmware version, etc…)
• I/O assembly information and I/O mapping
• Firmware update possibilities
• Upload of configuration data
• Class instance editor (to call any service of any object on the bus controller)
• Online Help System

User's Manual
Required login for module configuration ensures module security. Please note that due to the fact that the
bus controller behaves as an EtherNet/IP adapter device, attributes and services might get changed or called
anyway.
4.3 Optimized Performance
4.3.1 Setting Proper RPI and X2X Time

The RPI (Request Packet Interval) controls the update rate for the bus controller’s I/O data. This value can be
changed within RSLogixTM 5000 by right clicking on the Generic Ethernet Module and selecting “Properties.”
The minimum value for RPI is 1 ms, and the default is 10 ms.
The X2X cycle time can be adjusted in FieldbusDESIGNER under ‘Adapter Configuration’ or through accessing
attribute ID 0x80 of the ‘bus controller’ object (class 0x64, instance 0x1). The default value is 1ms. After making
changes, the bus controller must be restarted for the changes to take effect.

User's Manual
X2X Bus Configuration

Attribute ID [hex] 0x80
Datatype UINT
Access Set
Default Value 6
Description The X2X bus cycle time and the data capacity are directly related. The following chart
should help the programmer optimize the X2X cycle time. If more modules are required
than allowed, either increase the cycle time, or increase the number of bus controllers
on the bus. The cycle time can be adjusted in FieldbusDESIGNER, or written to the bus
controller directly with the attribute ID and value.
Value Cycle Time Description
0 4ms Max 253 IO modules, max. 1400 Byte sync data
1 3.5 ms Max 253 IO modules, max. 1150 Byte sync data
2 3 ms Max 253 IO modules, max. 900 Byte sync data
To change the X2X cycle time within FieldbusDESIGNER, right click the bus controller and select “Open
Adapter Configuration”:

User's Manual
5 Module Configuration / Writing to Registers

Modules can be configured by writing to their registers. This allows for dynamic configuration of modules
within RSLogixTM 5000 by using explicit messages.
Service Code = 0x33 for write command

Class = 0x65 for I/O modules
Instance = 2 = Module location on rack (See figure below)
Attribute = 0 = can be left to 0 for this type of service
Source Length = 6 = length of address and data in bytes: address is 2 bytes, data is always 4 bytes
Source Element = array of 6 SINT: address is write_data[0…1], data is write_data[2..5]
Register addresses and configuration data can be taken from the “MAX20REGISTER-ENG” and
“MAX67ENG” document (see appendix).

User's Manual
The MSG function block’s configuration is shown below.
Configuration registers can be read by calling service 0x32 of the same object:
Source Length = 2 = length of register address in bytes
Source Element = array of 2 SINT: address is write_data[0…1]
The service will return a 4 byte value (the register’s data).

User's Manual
APPENDIX: Additional Documentation

MAEIP-ENG_V100_09_2009: EtherNet/IP User's Manual.
B&R Website Link:
http://www.br-automation.com/cps/rde/xchg/br-productcatalogue/hs.xsl/services_146521_ENG_HTML.htm
MAX20REGISTER-ENG: X20 Module Register Information Document.

B&R Website Link:
MAX67-ENG: X67 Module Register Information Document.

B&R Website Link:


Maepgetst-Eng V102 12 2009

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Maepgetst-Eng V102 12 2009

Uploaded by

Copyright:

Available Formats

EtherNet/IP - Getting Started

Version: 1.02 (December 2009)

1 General Overview ....................................................................................................... 3

2 Automatic Configuration ........................................................................................... 8

4 Bus Controller Capabilities ..................................................................................... 28

5 Module Configuration / Writing to Registers ......................................................... 32

APPENDIX: Additional Documentation ..................................................................... 34

2 Copyright © B&R - Subject to change without notice

Copyright © B&R - Subject to change without notice 3

1.1.1 LED Status Indicators

LED Color Status Description

4 Copyright © B&R - Subject to change without notice

1.1.2 Network Address Switches

Network Address Function

"br" + "eip" + network address switch value (three decimal places)

$F0 to $FD Reserved. Currently same as 0xFF.

$FF Boots with default values:

The IP address stored in the flash memory is not changed.

Copyright © B&R - Subject to change without notice 5

1.2 Supported 3rd Party Hardware and Software

1.2.1 Supported Allen-Bradley® CPUs

1.2.2 Supported Allen-Bradley® Software

1.3 Overview of Programming Options

1.3.1.1 Automatic Configuration

1.3.1.2 User Configuration

6 Copyright © B&R - Subject to change without notice

1.4 System Overview – Configuration via FieldbusDESIGNER

Copyright © B&R - Subject to change without notice 7

The following programs are required:

2.1.1 Step-by-Step Guide to Setting up Bus Controller

8 Copyright © B&R - Subject to change without notice

Configure new generic Ethernet module

Copyright © B&R - Subject to change without notice 9

2.1.2 Configuration and I/O Assembly Explanation

Instance ID Type Description Size in Bytes

Instance ID Type Description Default Size in Bytes

Instance ID Type Description Default Size in Bytes

10 Copyright © B&R - Subject to change without notice

2.1.3 Online with RSLogixTM 5000

Copyright © B&R - Subject to change without notice 11

12 Copyright © B&R - Subject to change without notice

3.1.1 Step-by-Step Guide to Setting up Bus Controller

For further information please reference FieldbusDESIGNER help.

3.1.1.2 Inserting Allen-Bradley® Hardware and Bus Controller

1) Create a new Project

Copyright © B&R - Subject to change without notice 13

14 Copyright © B&R - Subject to change without notice

Copyright © B&R - Subject to change without notice 15

16 Copyright © B&R - Subject to change without notice

3.1.1.3 Configuration of Bus Controller

Copyright © B&R - Subject to change without notice 17

3.1.1.4 Inserting Modules into FieldbusDESIGNER

18 Copyright © B&R - Subject to change without notice

Copyright © B&R - Subject to change without notice 19

20 Copyright © B&R - Subject to change without notice

3.1.1.5 Configuration of Modules

Copyright © B&R - Subject to change without notice 21

22 Copyright © B&R - Subject to change without notice

3.1.1.6 Building a Project

Copyright © B&R - Subject to change without notice 23

3.1.2 Going Online with RSLogixTM 5000

The following picture shows the controller tags section:

copyInpCounter, copyOutCounter, and mainCounter are lifecycle counters