Assembly Connections for POINT I/O
and ArmorPOINT I/O EtherNet/IP
Adapters
Catalog Numbers Bulletins 1734 and 1738
User Manual
Important User Information
WARNING
IMPORTANT
ATTENTION
SHOCK HAZARD
BURN HAZARD
Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application,
Installation and Maintenance of Solid State Controls (publication SGI-1.1
http://literature.rockwellautomation.com
) describes some important differences between solid state equipment and hard-wired electromechanical
devices. Because of this difference, and also because of the wide variety of uses for solid state equipment, all persons responsible for applying this
equipment must satisfy themselves that each intended application of this equipment is acceptable.
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.
available from your local Rockwell Automation sales office or online at
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.
Identifies information that is critical for successful application and understanding of the product.
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.
Labels may be on or inside the equipment, such as a drive or motor, to alert people that dangerous voltage may be present.
Labels may be on or inside the equipment, such as a drive or motor, to alert people that surfaces may reach dangerous
temperatures.
Allen-Bradley, Rockwell Automation, POINT I/O, ArmorPOINT I/O, RSView, RSLinx, RSLogix 5000 and TechConnect are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Read this preface to familiarize yourself with the rest of the manual. It provides
information concerning:
• the purpose of this manual
• related documentation
• conventions used in this manual
Why Read This Manual
Who Should Use This
Manual
About the Vocabulary
This manual is a reference guide for using Assembly Connections with
POINT I/O and ArmorPOINT I/O modules.
You must be able to program and configure industrial automation controllers
and I/O to use the connections specified in this manual. You should also be
familiar with the POINT I/O or ArmorPOINT I/O families of product to
use these connections.
We assume that you are familiar with the material presented in this manual. If
you are not, refer to product-specific documentation before you attempt to use
this manual. Related documentation for Rockwell Automation products is
listed in the table below.
In this manual, we refer to the:
• 1734 family as POINT I/O modules
• 1738 family as ArmorPOINT I/O modules
Related Documentation
The following documents contain additional information concerning Rockwell
Automation products.
ResourceDescription
Industrial Automation Wiring and Grounding Guidelines,
publication 1770-4.1
Application Considerations for Solid-State Controls
SGI-1.1
Allen-Bradley Industrial Automation Glossary AG-7.1
Getting Results with RSNetWorx for DeviceNet,
publication DNET-GR001D-EN-E
RSLogix 5000 software online helpAn online help system that accompanies the RSLogix 5000 programming
vPublication 1734-UM016A-EN-P - October 2010
In-depth information on grounding and wiring Allen-Bradley programmable
controllers.
A description of important differences between solid-state programmable
controller products and hard-wired electromechanical devices.
A glossary of industrial automation terms and abbreviations.
A getting results guide on how to effectively use the RSNetWorx for DeviceNet
software and how to access and navigate the online help.
software package.
vi Preface
ResourceDescription
POINT I/O and ArmorPOINT I/O module publicationsPublications for POINT I/O and ArmorPOINT I/O modules are available from the
Rockwell Automation Literature Library.
National Electrical Code - Published by the National Fire
Protection Association of Boston, MA.
You can view or download publications at
http://www.literature.rockwellautomation.com
technical documentation, contact your local Rockwell Automation distributor
or sales representative.
Common Techniques Used
in this Manual
The following conventions are used throughout this manual:
• Bulleted lists such as this one provide information, not procedural steps.
• Numbered lists provide sequential steps or hierarchical information.
• Italic type is used for emphasis.
An article on wire sizes and types for grounding electrical equipment.
. To order paper copies of
Publication 1734-UM016A-EN-P - October 2010
Introduction
Chapter
1
About Assembly
Connections
This document describes Assembly connections, a new connection type for
POINT I/O and ArmorPOINT I/O EtherNet/IP adapters. These adapters
currently support Rack Optimized connections between ControlLogix or
CompactLogix controllers and the discrete I/O modules in the chassis.
They are also capable of bridging direct connections between any
EtherNet/IP-capable connection originator and the I/O modules, via
the backplane. This new functionality being presented will permit the exchange
of data between an originator and all POINT I/O modules present in the
chassis in one connection.
This new Assembly connection is mutually exclusive to other connection
types, for example, Rack Optimized or Direct to module connections. In other
words, if this connection is in use by one connection originator, other
originators are prevented from making Rack Optimized or Direct Connections
to the modules in the same chassis. Furthermore, the connection is
all-inclusive; every module present in the backplane participates in the
connection.
The I/O data that is exchanged with the adapter takes the following form:
Adapter Data Exchange
T → O produced I/O dataO → T consumed I/O data
64-bit Status headerRun/Idle header
Slot 1 dataSlot 1 data
Slot 2 dataSlot 2 data
::
::
(1)
Slot N
data
(1)
N is the number of I/O modules
The 64-bit Status header is optional and the packing of the data is dependant
on the selected alignment choice. The exact method for determining the data
structure is covered in the following sections.
Choose a Connection
1Publication 1734-UM016A-EN-P - October 2010
The Assembly connection supports an optional 64-bit status header and also
supports requests from listen-only originators.
Slot N data
2 Introduction
Data Headers
In the Target to Originator (T → O) direction, the adapter can be configured
to produce a status header for the connection. The header consists of an
8-byte bitmap, where bits 1 - 63 indicate the health of each of the 63 possible
backplane connections. This is similar to existing Rack Optimized
connections. A "1" indicates that a module is not connected or that slot is not
populated. A "0" indicates that the module is actively participating in the
connection. Currently, Bit 0 is reserved and should be ignored.
When the header is used, modules may be removed and reinserted without
breaking the I/O connection to the adapter. Modules not present or that are
failed are reflected in the status header.
If the optional status header is not included, the adapter cannot support RIUP
without breaking the I/O connection. If any one I/O module fails or is
removed, the adapter will break the connection to the connection originator.
Since no status is provided, this is the only way to reflect the fact that a
problem exists with the I/O modules on the backplane.
In the Originator to Target (O → T) direction the adapter supports the 4-byte
Run/Idle header. Sending a "1" indicates that the controller is in the Run mode
and that the adapter should apply the data that was just received. Sending a "0"
indicates that the controller is in program or idle mode and that the adapter
should put the I\O modules in their idle mode.
Listen Only Connections
Using an Assembly connection will allow multiple originators to consume data
from the POINT I/O system. However, only one owner of the connection is
permitted. That one owner will control all output devices present in the chassis
as well as the configuration of the connection.
Connection Points
The following table lists the connection points that are supported for the
different connection styles discussed.
Publication 1734-UM016A-EN-P - October 2010
Supported Connection Points for Connection Styles
Introduction 3
ConnectionConfiguration
Connection Point
Consumed
Connection Point
Produced
Connection Point
Exclusive Owner102100101
Listen-only102191101
Input-only102190101
Owning with no status header102100103
Listen-only with no status header102191103
Input-only with no status header102190103
Publication 1734-UM016A-EN-P - October 2010
4 Introduction
Notes:
Publication 1734-UM016A-EN-P - October 2010
Configuration
Chapter
2
About This Chapter
This chapter describes the various configuration options that you can use to
set up assembly connections.
Configure the Connection
This connection is accepted with or without a configuration assembly present.
If a configuration assembly is present, it must contain the following minimum
information.
Minimal Adapter Configuration Assembly
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
Config 0Reserved (Set to 0)
Config 1Reserved (Set to 0)
Config 2Reserved (Set to 0)
Config 3Reserved (Set to 0)
Config 4Chassis size (Low Byte)
Config 5Chassis size (High Byte)
Config 6Alignment for Produced Assembly (T → O)
Config 7Size per slot (T→ O) (in Bytes)
Config 8Alignment for Consumed Assembly (O → T)
Config 9Size per slot (O → T) (in Bytes)
Chassis Size
Before establishing I/O connections, you must configure the 1734 adapters
for chassis size. This ensures that the correct number of modules are present
in the chassis at power up. The chassis size must include 1 count for the
adapter (Chassis Size = number of I/O modules + 1).
5Publication 1734-UM016A-EN-P - October 2010
6 Configuration
TIP
TIP
Data Alignment
Some computing devices require data to be aligned on boundaries that are
proper for their data type. There are several alignment options available to
reduce or prevent shifting operations in the originator:
Byte Boundaries
Each node's I/O data is mapped at the next available byte. Byte data can
appear at any address.
Word Boundaries
If a node's I/O data is one byte in length, it is mapped at the next available
byte. Otherwise the previous data is padded so that the node's data starts on a
16-bit boundary.
This does not mean that every slot occupies two bytes in the image.
Word data can only begin on even addresses, for example, 0, 2, 4, 8,
0xA, or 0xC.
Double Word Boundaries
If a node's I/O data is one byte in length, it is mapped at the next available
byte. If a node's data is two bytes in length, padding is added to ensure that it is
mapped to an even address. If a node's data is greater than 2 bytes in length,
padding is added to ensure that the data is mapped to a Double Word
boundary.
This does not mean that every slot occupies 4 bytes in the image.
Double Word data and array data larger than 2 bytes in size must be
aligned on addresses ending in 0, 4, 8, and 0xC.
Fixed Boundaries
The fixed boundary allows you to choose the fixed "size per slot" that each
module occupies in the I/O data. Mapping size ranges from 1…24 bytes.
The alignment choices are independently selected for each direction; O → T
and T
→ O. If Fixed Boundaries are selected, the Size per Slot choice
determines how many bytes are reserved for each slot in the I/O packet. If the
size selected is larger than a module's data, that module's data is padded with
0's out to the size selected. If the size selected is smaller than a module's data,
that module's data is truncated at the size selected.
Publication 1734-UM016A-EN-P - October 2010
Configuration 7
When Fixed Boundaries are selected, the formula for mapping is:
H+(N-1)(size per slot), where N = slot position and H is the size of the
optional status header (8 if used, 0 if not used).
The choice of alignment is highly dependent on the originator used and
application-specific requirements.
• If data size is at a premium, Byte alignment is the most efficient choice.
• If the originator can only process data on DINT boundaries (as is the
case with RSLogix controllers), then Double Word alignment should be
used.
• If ease of programming is desired, the Fixed Boundaries option allows
for easy location of the data within the data packet. Additionally the use
of Fixed Boundaries along with the 1734-ARM module will allow
modules to be added later without having the location of any slot's data
change. The ARM module will reserve data space for future modules.
Since each slot occupies the same size in the data image, when the ARM
module is replaced with a future module, the data boundaries are
preserved.
Individual Module Configuration Options
The request for an Assembly connection is accepted with or without a
configuration assembly present. If a configuration assembly is present, it must
contain the minimum information presented in the Configuring the
Connection section. See TableMinimal Adapter Configuration Assembly on
page 5. If individual module configuration is required, it can be appended to
the end of the minimum configuration structure for any or all modules that
require configuration. The construction of this configuration data structure is
a manual process.
Alternatively any tool that is capable of sending CIP packets can configure the
parameters of individual POINT I/O modules. The configuration is stored
locally in the module's non-volatile storage. When the configuration is sent
from the connection originator via the connection request, the adapter also
stores a copy of this configuration and restores it if that module is ever
replaced. This is similar to the Automatic Device Replacement feature of
DeviceNet scanners. If the configuration is sent from the connection
originator via the connection request, the configuration assembly size is
limited to the maximum packet size of 510 bytes. This may be an issue in larger
systems that require module configuration. Configuring modules through a
separate tool will allow the configuration to be sent to modules individually,
effectively eliminating the packet size limitation. Furthermore, the
configuration tool of choice may provide a rich graphical user interface,
reducing the possibility that configuration is incorrectly entered. One such tool
is RSNetWorx for DeviceNet.
Publication 1734-UM016A-EN-P - October 2010
8 Configuration
Module Configuration Sent with the Connection Request
Individual module configuration must be manually constructed and appended
to the minimal configuration assembly specified in the table Minimal Adapter
Configuration Assembly on page 5. For each module that needs to be
configured, the following information must be provided:
Module Configuration Information
FieldData TypeDescription
Slot numberUSINTThe slot number to identify modules that require
configuration data.
Configuration sizeUSINTThe size, in bytes, of the Configuration Data for the
given module. It does not include the size of the first
three fields shown here.
Configuration
assembly instance
Configuration dataArray of
UINTThe adapter reads this field to access the module
configuration assembly’s instance number.
The configuration assembly data as defined by the
BYTE
module's EDS file.
This structure may be repeated for as many modules as necessary until the
whole assembly exceeds 509 bytes. The module order is not important as long
as all module configuration follows the minimal header information from the
table Minimal Adapter Configuration Assembly on page 5.
If any part of the configuration assembly is wrong (either the minimal
assembly or a portion directed to an I/O module), the connection request will
be rejected with the General Return Code indicating an Error in the Data
Segment (0x09). The Extended Error code will indicate the byte offset into the
configuration data segment where the error was detected. The Configuration
assembly details for all of the 1734 and 1738 I/O modules are presented in
Module Assembly Information on page 31.
Module Configuration with RSNetWorx for DeviceNet
Publication 1734-UM016A-EN-P - October 2010
RSNetWorx for DeviceNet provides a rich parameter-based configuration user
interface. The POINT I/O and ArmorPOINT I/O adapters have the
capability to present their backplane as a DeviceNet subnet to RSLinx. The
subnet can be used to bridge configuration data from RSNetWorx for
DeviceNet to backplane devices. With this method, all configuration for a
POINT I/O backplane can be stored to the DeviceNet network file (.DNT)
and restored via this file if necessary.
Configuration 9
Cat #A
E
N
T
I
B
8
I
E
2
C
O
B
4
E
Slot #012 3
ModuleTx sizeRx size
IB81 – byte0
OB4E1 – byte1 – byte
IE2C6
- int
- int
- byte
- byte
0
Calculate the Connection
Size
The I/O assembly size is limited to the maximum size that can be specified in
the standard Forward_Open service (509 bytes). The size needs to be manually
calculated based on the alignment choices, inclusion of the optional status
header, and the I/O sizes for the modules present in the chassis. The adapter
validates the connection size in the forward open against what it calculates
from the backplane and the alignment choice. If the two do not match, the
connection request is rejected with extended error code 0x0109, Invalid
Connection Size.
Connection Size Calculation Example
The following system will be used to demonstrate the connection size
calculation. The adapter's produced size (T
optional status header is included. In some software the consumed size
(O
→T) does not need to account for the 4 byte Run/Idle header as it is
assumed and already included. For the example both header sizes have been
included.
POINT I/O system example
→ O) must include 8 bytes if the
T → O alignment T → O sizeO → T alignment O → T size
1Byte16 bytesByte5 bytes
status 8 bytes
slot 1 byte
slot 2 int
slot 2 int
slot 2 byte
slot 2 byte
slot 3 byte
Publication 1734-UM016A-EN-P - October 2010
run /idle 4 bytes
slot 3 byte
10 Configuration
T → O alignment T → O sizeO → T alignment O → T size
2Double Word19 bytesDouble Word5 bytes
status 8 bytes
slot 1 byte
slot 1 pad
slot 1 pad
slot 1 pad
slot 2 int
slot 2 int
slot 2 byte
slot 2 byte
slot 3 byte
In row 1, the data is packed on byte boundaries. This is the most efficient data
representation when alignment is not a concern.
In row 2 the data for slot 1 is padded so that slot 2's data began on a Double
Word bound ary.
In row 3 every slot takes up the selected size per slot regardless of whether that
module has any data to produce.
This section touches briefly on data alignment. More comprehensive examples
of data alignment are provided in Assembly Structure Examples on page 23.
Troubleshooting Connection Size Errors
If the adapter returns the Invalid Connection Size error in response to a
connection request, it is possible to query the adapter for its calculated size.
Publication 1734-UM016A-EN-P - October 2010
This section highlights a technique that can be used to help resolve connection
size errors.
The adapter cannot validate connection sizes until the request to open the
connection is received. It is within that request that the adapter receives the
alignment choice and status election. Based on all the information in the
request and the modules present, the request may be rejected by the adapter
because of a size error.
Configuration 11
1. Open the adapter's web page and select the Diagnostics folder.
2. On the Diagnostic Messaging tab, enter the Slot, Class, Instance, and
Attribute to get the adapter's calculated connection sizes.
Diagnostic Messaging Field Description
FieldDescription
ServiceGet Attribute Single
Slot Position0
Class4
Publication 1734-UM016A-EN-P - October 2010
12 Configuration
Diagnostic Messaging Field Description
FieldDescription
Instance100 (O → T data)
101 (T → O data with status)
103 (T → O data without status)
Attribute4
Response8E 00 00 00 xx xx
8E 00 — Indicates message was processed successfully
00 00 — 0 = success. Non-zero indicates an error code
xx xx — Indicates size (Little Endian format)
(1)
in Little Endian format, the least significant byte is shown first. A returned value of A2 01 should be interpreted
as 0x01A2 hex (418 decimal).
(1)
Once you have the sizes from the adapter, return to your calculations to
resolve the differences between your expected size and the size from the
adapter.
Publication 1734-UM016A-EN-P - October 2010
Using an Assembly Connection
Chapter
3
Use an Assembly
Connection with
RSNetWorx for EtherNet/IP
This section provides an illustration of the steps needed to configure the
Assembly connection using RSNetWorx for EtherNet/IP.
1. Browse the EtherNet/IP network.
2. Select the connection originator that will make the connection to the
1734-AENT. Right click that device and select Scanlist Configuration to
launch the Scanlist Configuration tool.
13Publication 1734-UM016A-EN-P - October 2010
14 Using an Assembly Connection
3. Right click the targeted adapter and select Insert Connection to display
the Connection Properties dialog.
4. On the Connection tab of this dialog, select the connection from the
Connection Name pull-down (for example, Exclusive Owner and
Listen-Only connections). Listen-Only connections are only accepted if
an Exclusive Owner connection already exists.
Publication 1734-UM016A-EN-P - October 2010
Using an Assembly Connection 15
TIP
You can also select the Requested Packet Interval and connection sizes.
For a full discussion on connections sizes, refer to the Configuration
Setting tab step that follows and Calculate the Connection Size. The
defaults reflect an empty system (with the adapter only).
In RSNetWorx, the 4-byte Run/Idle header is not considered when
calculating the Output Size. When you enter the connection size on
this dialog, make sure to subtract 4 bytes from your calculated size.
Also note that this dialog expresses the size in Words. If your
calculation was performed in Bytes, you must divide by 2.
5. In the Details tab, you can select between Point to Point and Multicast
for the Target to Scanner data.
Publication 1734-UM016A-EN-P - October 2010
16 Using an Assembly Connection
TIP
6. The Configuration Setting tab displays the configuration options for the
connection. Here, you can specify the Chassis Size and Data Alignment.
The terms T2O and O2T are abbreviations for Target to Originator and
Originator to Target.
Use an Assembly
Connection with
RSLogix5000
Remember when specifying the Chassis Size to include 1 for the
adapter.
See Data Alignment for alignment choices.
The Assembly connection can be used with RSLogix5000 and the Generic
EtherNet/IP profile. When this connection is used in RSLogix5000, there are
no intelligent Tags created for the adapter. All Input, Output, and
Configuration data are in unstructured Tag arrays.
Publication 1734-UM016A-EN-P - October 2010
Using an Assembly Connection 17
Add the Hardware to the I/O Configuration Tree
1. Add a new module to the Ethernet network in the I/O Configuration
section of the Controller Organizer pane.
2. Select a Generic Ethernet Module.
Publication 1734-UM016A-EN-P - October 2010
18 Using an Assembly Connection
Enter the Connection Parameters
In the New Module Properties dialog, enter Connection Parameters, the
Comm Format, the module's IP Address, and a name.
Enter a Name for the module that RSLogix 5000 uses in the tags that are
created for this module. The Data - SINT Comm Format should be selected,
indicating that all sizes are to be interpreted as a number of bytes. If this
connection is a Listen only connection, select the Input Data - SINT Comm
Format since it is otherwise not possible to enter an Output config assembly
size of 0.
Next, enter the Assembly Instances for the desired connection as
described in Connection Points. Enter the sizes (in bytes) for the Input and
Output instances per your calculations. See Calculate the Connection Size for
details on obtaining the sizes. If the optional status header is being used, its
size (8 bytes) must be included in the Input Size. For RSLogix 5000 the Output
Size does not include the Run/Idle header. Here the terms Input and Output
refer to the adapter's Produced and Consumed data respectively.
It is possible to make the connection without sending any
configuration data. The adapter's Chassis Size can be set from its web
page and the adapter will align produced and consumed data by
default on byte boundaries. If these options and the default configuration of all
I/O modules are acceptable, a 0 can be entered for the Configuration Size on
the Module Properties dialog. The configuration Assembly Instance must be
entered even if the size is 0. The following section will describe the steps taken
when configuration is needed.
Publication 1734-UM016A-EN-P - October 2010
Build the Configuration Tag
If any configuration is required, the minimum configuration header must be
sent and then any individual module configuration may follow. Open the
Using an Assembly Connection 19
Controller Tags by right-clicking the Controller Tags option from the
Controller Organizer pane. Select Monitor Tags.
Monitor Tags
You should see three Tags with the module's name. They will have an C, I, or
O suffix denoting Configuration, Input, or Output respectively. Note that the I
and O Tags are sized according to the sizes that were entered on the properties
page. The C Tag always has 400 bytes allocated for it regardless of the size
specified.
Add Configuration Header
Bytes 0…9 must contain the minimum configuration header information
described in Minimal Adapter Configuration Assembly. As can be seen from
the figure below, the Chassis Size is set to 0x12 (18 decimal). The produced
Publication 1734-UM016A-EN-P - October 2010
20 Using an Assembly Connection
and consumed alignment choice is Double Word alignment which is
enumerated as a 4. See the following table for valid alignment values.
Alignment choices for configuration header
Alignment ChoiceValue
Byte0
Word2
Double Word4
Fixed size per slot0xFF
Add I/O Module Configuration
If individual module configuration is required, it can be appended to
the configuration header. In the example shown below a 1734-OB4E module
is being configured. Byte 10 indicates that the data is to be sent to slot 2. Byte
11 specifies the size of the data as 8 bytes. Bytes 12 and 13 specify the OB4E
module configuration assembly instance 0x7B. The instance number is entered
in little endian (least significant byte first). In byte 16 the value of 7 indicates
that when the module is in Idle mode, Hold Last State should be enabled for
channels 0, 1, and 2 but not channel 3. If more module configuration is
needed, it could begin at byte 22 with the slot number of the next module to
be configured.
Publication 1734-UM016A-EN-P - October 2010
Using an Assembly Connection 21
For more information on configuration, see 1734/1738 I/O Module
Assembly Information.
After the configuration has been entered into the tag, remember to
save the RSLogix 5000 project. The tags are only retained upon a save. Also
remember that any configuration added here must be reflected in the
Configuration Size of the Connection Parameters entered on the Module
Properties dialog.
If any part of the configuration assembly is wrong (either the minimal
assembly or a portion directed to an I/O module), the connection request will
be rejected with the General Return Code indicating an Error in the Data
Segment (0x09). The Extended Error code will indicate the byte offset into the
configuration data segment where the error was detected.
Publication 1734-UM016A-EN-P - October 2010
22 Using an Assembly Connection
The error shown above was created by entering an invalid configuration
assembly size on the Module Properties page. A size of 18 bytes was entered.
The error here points to an offset of 0x000b (11 decimal). If we return to the
configuration tag, byte 0x000b is the location that contains the size of the I/O
module configuration. The header is 10 bytes and the module has 8 bytes of
configuration. However, we have neglected to add the 4 bytes of overhead
needed to describe the slot 2 configuration. When the adapter parsed the
configuration assembly to byte 0x000b it saw that it needed 8 more bytes of
information. It had already parsed through byte 11, therefore 18 would not be
an adequate size. The adapter returns the offset of the first byte where the
error is detected (0x000b).
Publication 1734-UM016A-EN-P - October 2010
Assembly Structure
Chapter
4
Assembly Structure
Examples
Produced Assembly, Byte Aligned
Byte, Word, and Double Word Alignment
The following chassis is used to demonstrate how the data is aligned for the
Byte, Word, and Double Word alignment options. This chassis was
intentionally assembled as shown to demonstrate as many use cases as
possible. Discrete and analog modules are intermixed. An ARM module is
used to reserve space for a future device. The 1734-IB4D module in slot 8 is
configured to produce 2 bytes while the IB4D module in slot 7 is configured
to produce 1 byte. The ASCII module in slot 10 is configured to produce
9 bytes.
Example POINT system
A
A
O
W
4
I
B
4
3
I
I
Cat #A
B
E
4
N
T
Slot #0 1234567891011121
I
B
B
8
2
O
O
S
R
E
B
B
B
B
B
C
M
2
4
4
8
4
2
C
D
D
E
E
E
I
I
I
O
ByteBit 7Bit 6Bit5Bit 4Bit 3Bit 2Bit 1Bit 0
Produce 0Slot 7 status Slot 6 statusSlot 5 status Slot 4 statusSlot 3 statusSlot 2 status Slot1 statusSlot 0 status
Produce 1Slot 15 status Slot 14 status Slot 13 status Slot 12 status Slot 11 status Slot 10 status Slot 9 status Slot 8 status
Produce 2Slot 23 status Slot 22 status Slot 21 status Slot 20 status Slot 19 status Slot 18 status Slot 17 status Slot 16 status
Produce 3Slot 31 status Slot 30 status Slot 29 status Slot 28 status Slot 27 status Slot 26 status Slot 25 status Slot 24 status
Produce 4Slot 39 status Slot 38 status Slot 37 status Slot 36 status Slot 35 status Slot 34 status Slot 33 status Slot 32 status
Produce 5Slot 47 status Slot 46 status Slot 45 status Slot 44 status Slot 43 status Slot 42 status Slot 41 status Slot 40 status
Produce 6Slot 55 status Slot 54 status Slot 53 status Slot 52 status Slot 51 status Slot 50 status Slot 49 status Slot 48 status
Produce 7Slot 63 status Slot 62 status Slot 61 status Slot 60 status Slot 59 status Slot 58 status Slot 57 status Slot 56 status
Produce 8ReservedSlot 1 Bit 3Slot 1 Bit 2Slot 1 Bit 1Slot 1 Bit 0
Produce 9Slot 2 Bit 7Slot 2 Bit 6Slot 2 Bit 5Slot 2 Bit 4Slot 2 Bit 3Slot 2 Bit 2Slot 2 Bit 1Slot 2 Bit 0
Produce 10ReservedSlot 3 Bit 1Slot 3 Bit 0
Produce 11ReservedSlot 4 Bit 1Slot 4 Bit 0
Produce 12ReservedSlot 5 Bit 3Slot 5 Bit 2Slot 5 Bit 1Slot 5 Bit 0
Produce 13Slot 6 Bit 7Slot 6 Bit 6Slot 6 Bit 6Slot 6 Bit 4Slot 6 Bit 3Slot 6 Bit 2Slot 6 Bit 1Slot 6 Bit 0
Produce 14Slot 7 Bit 7Slot 7 Bit 6Slot 7 Bit 5Slot 7 Bit 4Slot 7 Bit 3Slot 7 Bit 2Slot 7 Bit 1Slot 7 Bit 0
23Publication 1734-UM016A-EN-P - October 2010
24 Assembly Structure
Produced Assembly, Byte Aligned
ByteBit 7Bit 6Bit5Bit 4Bit 3Bit 2Bit 1Bit 0
Produce 15Slot 8 Bit 7Slot 8 Bit 6Slot 8 Bit 5Slot 8 Bit 4Slot 8 Bit 3Slot 8 Bit 2Slot 8 Bit 1Slot 8 Bit 0
Produce 16Slot 8 Bit 15Slot 8 Bit 14Slot 8 Bit 13Slot 8 Bit 12Slot 8 Bit 11Slot 8 Bit 10Slot 8 Bit 9Slot 8 Bit 8
Produce 17Slot 9 Channel 0 - Low Byte
Produce 18Slot 9 Channel 0 - High Byte
Produce 19Slot 9 Channel 1 - Low Byte
Produce 20Slot 9 Channel 1 - High Byte
Produce 21Slot 9 Channel 0 - Status
Produce 22Slot 9 Channel 1 - Status
Produce 23Slot 10 ASCII Data 1
Produce 24Slot 10 ASCII Data 2
Produce 25Slot 10 ASCII Data 3
Produce 26Slot 10 ASCII Data 4
Produce 27Slot 10 ASCII Data 5
Produce 28Slot 10 ASCII Data 6
Produce 29Slot 10 ASCII Data 7
Produce 30Slot 10 ASCII Data 8
Produce 31Slot 10 ASCII Data End of String Delimiter
Produce 32Slot 11 ARM - Reserved Byte
Produce 33ReservedSlot 13 Bit 3Slot 13 Bit 2Slot 13 Bit 1Slot 13 Bit 0
Consumed Assembly, Byte Aligned
ByteBit 7Bit 6Bit5Bit 4Bit 3Bit 2Bit 1Bit 0
Consume 0ReservedRun/Idle
Consume 1Reserved
Consume 2Reserved
Consume 3Reserved
Consume 4ReservedSlot 4 Bit 1Slot 4 Bit 0
Consume 5ReservedSlot 5 Bit 3Slot 5 Bit 2Slot 5 Bit 1Slot 5 Bit 0
Consume 6Slot 6 Bit 7Slot 6 Bit 6Slot 6 Bit 5Slot 6 Bit 4Slot 6 Bit 3Slot 6 Bit 2Slot 6 Bit 1Slot 6 Bit 0
Consume 7Slot 10 ASCII Data 1
Consume 8Slot 10 ASCII Data 2
Consume 9Slot 10 ASCII Data 3
Consume 10Slot 10 ASCII Data 4
Consume 11Slot 10 ASCII Data 5
Consume 12Slot 10 ASCII Data End of String Delimiter
Consume 13ReservedSlot 12 Bit 3Slot 12 Bit 2Slot 12 Bit 1Slot 12 Bit 0
Publication 1734-UM016A-EN-P - October 2010
Assembly Structure 25
Produced Assembly, Word Aligned
ByteBit 7Bit 6Bit5Bit 4Bit 3Bit 2Bit 1Bit 0
Produce 0Slot 7 status Slot 6 statusSlot 5 status Slot 4 statusSlot 3 statusSlot 2 status Slot1 statusSlot 0 status
Produce 1Slot 15 status Slot 14 status Slot 13 status Slot 12 status Slot 11 status Slot 10 status Slot 9 status Slot 8 status
Produce 2Slot 23 status Slot 22 status Slot 21 status Slot 20 status Slot 19 status Slot 18 status Slot 17 status Slot 16 status
Produce 3Slot 31 status Slot 30 status Slot 29 status Slot 28 status Slot 27 status Slot 26 status Slot 25 status Slot 24 status
Produce 4Slot 39 status Slot 38 status Slot 37 status Slot 36 status Slot 35 status Slot 34 status Slot 33 status Slot 32 status
Produce 5Slot 47 status Slot 46 status Slot 45 status Slot 44 status Slot 43 status Slot 42 status Slot 41 status Slot 40 status
Produce 6Slot 55 status Slot 54 status Slot 53 status Slot 52 status Slot 51 status Slot 50 status Slot 49 status Slot 48 status
Produce 7Slot 63 status Slot 62 status Slot 61 status Slot 60 status Slot 59 status Slot 58 status Slot 57 status Slot 56 status
Produce 8ReservedSlot 1 Bit 3Slot 1 Bit 2Slot 1 Bit 1Slot 1 Bit 0
Produce 9Slot 2 Bit 7Slot 2 Bit 6Slot 2 Bit 5Slot 2 Bit 4Slot 2 Bit 3Slot 2 Bit 2Slot 2 Bit 1Slot 2 Bit 0
Produce 10ReservedSlot 3 Bit 1Slot 3 Bit 0
Produce 11ReservedSlot 4 Bit 1Slot 4 Bit 0
Produce 12ReservedSlot 5 Bit 3Slot 5 Bit 2Slot 5 Bit 1Slot 5 Bit 0
Produce 13Slot 6 Bit 7Slot 6 Bit 6Slot 6 Bit 6Slot 6 Bit 4Slot 6 Bit 3Slot 6 Bit 2Slot 6 Bit 1Slot 6 Bit 0
Produce 14Slot 7 Bit 7Slot 7 Bit 6Slot 7 Bit 5Slot 7 Bit 4Slot 7 Bit 3Slot 7 Bit 2Slot 7 Bit 1Slot 7 Bit 0
Produce 15Pad
Produce 16Slot 8 Bit 7Slot 8 Bit 6Slot 8 Bit 5Slot 8 Bit 4Slot 8 Bit 3Slot 8 Bit 2Slot 8 Bit 1Slot 8 Bit 0
Produce 17Slot 8 Bit 15Slot 8 Bit 14Slot 8 Bit 13Slot 8 Bit 12Slot 8 Bit 11Slot 8 Bit 10Slot 8 Bit 9Slot 8 Bit 8
Produce 18Slot 9 Channel 0 - Low Byte
Produce 19Slot 9 Channel 0 - High Byte
Produce 20Slot 9 Channel 1 - Low Byte
Produce 21Slot 9 Channel 1 - High Byte
Produce 22Slot 9 Channel 0 - Status
Produce 23Slot 9 Channel 1 - Status
Produce 24Slot 10 ASCII Data 1
Produce 25Slot 10 ASCII Data 2
Produce 26Slot 10 ASCII Data 3
Produce 27Slot 10 ASCII Data 4
Produce 28Slot 10 ASCII Data 5
Produce 29Slot 10 ASCII Data 6
Produce 30Slot 10 ASCII Data 7
Produce 31Slot 10 ASCII Data 8
Produce 32Slot 10 ASCII Data End of String Delimiter
Produce 33Slot 11 ARM - Reserved Byte
Produce 34ReservedSlot 13 Bit 3Slot 13 Bit 2Slot 13 Bit 1Slot 13 Bit 0
Publication 1734-UM016A-EN-P - October 2010
26 Assembly Structure
Consumed Assembly, Word Aligned
ByteBit 7Bit 6Bit5Bit 4Bit 3Bit 2Bit 1Bit 0
Consume 0ReservedRun/Idle
Consume 1Reserved
Consume 2Reserved
Consume 3Reserved
Consume 4ReservedSlot 4 Bit 1Slot 4 Bit 0
Consume 5ReservedSlot 5 Bit 3Slot 5 Bit 2Slot 5 Bit 1Slot 5 Bit 0
Consume 6Slot 6 Bit 7Slot 6 Bit 6Slot 6 Bit 5Slot 6 Bit 4Slot 6 Bit 3Slot 6 Bit 2Slot 6 Bit 1Slot 6 Bit 0
Consume 7Pad
Consume 8Slot 10 ASCII Data 1
Consume 9Slot 10 ASCII Data 2
Consume 10Slot 10 ASCII Data 3
Consume 11Slot 10 ASCII Data 4
Consume 12Slot 10 ASCII Data 5
Consume 13Slot 10 ASCII Data End of String Delimiter
Consume 14ReservedSlot 12 Bit 3Slot 12 Bit 2Slot 12 Bit 1Slot 12 Bit 0
Produced Assembly, Double Word Aligned
ByteBit 7Bit 6Bit5Bit 4Bit 3Bit 2Bit 1Bit 0
Produce 0Slot 7 status Slot 6 statusSlot 5 status Slot 4 statusSlot 3 statusSlot 2 status Slot1 statusSlot 0 status
Produce 1Slot 15 status Slot 14 status Slot 13 status Slot 12 status Slot 11 status Slot 10 status Slot 9 statusSlot 8 status
Produce 2Slot 23 status Slot 22 status Slot 21 status Slot 20 status Slot 19 status Slot 18 status Slot 17 status Slot 16 status
Produce 3Slot 31 status Slot 30 status Slot 29 status Slot 28 status Slot 27 status Slot 26 status Slot 25 status Slot 24 status
Produce 4Slot 39 status Slot 38 status Slot 37 status Slot 36 status Slot 35 status Slot 34 status Slot 33 status Slot 32 status
Produce 5Slot 47 status Slot 46 status Slot 45 status Slot 44 status Slot 43 status Slot 42 status Slot 41 status Slot 40 status
Produce 6Slot 55 status Slot 54 status Slot 53 status Slot 52 status Slot 51 status Slot 50 status Slot 49 status Slot 48 status
Produce 7Slot 63 status Slot 62 status Slot 61 status Slot 60 status Slot 59 status Slot 58 status Slot 57 status Slot 56 status
Produce 8ReservedSlot 1 Bit 3Slot 1 Bit 2Slot 1 Bit 1Slot 1 Bit 0
Produce 9Slot 2 Bit 7Slot 2 Bit 6Slot 2 Bit 5Slot 2 Bit 4Slot 2 Bit 3Slot 2 Bit 2Slot 2 Bit 1Slot 2 Bit 0
Produce 10ReservedSlot 3 Bit 1Slot 3 Bit 0
Produce 11ReservedSlot 4 Bit 1Slot 4 Bit 0
Produce 12ReservedSlot 5 Bit 3Slot 5 Bit 2Slot 5 Bit 1Slot 5 Bit 0
Produce 13Slot 6 Bit 7Slot 6 Bit 6Slot 6 Bit 6Slot 6 Bit 4Slot 6 Bit 3Slot 6 Bit 2Slot 6 Bit 1Slot 6 Bit 0
Produce 14Slot 7 Bit 7Slot 7 Bit 6Slot 7 Bit 5Slot 7 Bit 4Slot 7 Bit 3Slot 7 Bit 2Slot 7 Bit 1Slot 7 Bit 0
Produce 15Pad
Produce 16Slot 8 Bit 7Slot 8 Bit 6Slot 8 Bit 5Slot 8 Bit 4Slot 8 Bit 3Slot 8 Bit 2Slot 8 Bit 1Slot 8 Bit 0
Publication 1734-UM016A-EN-P - October 2010
Assembly Structure 27
Produced Assembly, Double Word Aligned
ByteBit 7Bit 6Bit5Bit 4Bit 3Bit 2Bit 1Bit 0
Produce 17Slot 8 Bit 15Slot 8 Bit 14Slot 8 Bit 13Slot 8 Bit 12Slot 8 Bit 11Slot 8 Bit 10Slot 8 Bit 9Slot 8 Bit 8
Produce 18Pad
Produce 19Pad
Produce 20Slot 9 Channel 0 - Low Byte
Produce 21Slot 9 Channel 0 - High Byte
Produce 22Slot 9 Channel 1 - Low Byte
Produce 23Slot 9 Channel 1 - High Byte
Produce 24Slot 9 Channel 0 - Status
Produce 25Slot 9 Channel 1 - Status
Produce 26Pad
Produce 27Pad
Produce 28Slot 10 ASCII Data 1
Produce 29Slot 10 ASCII Data 2
Produce 30Slot 10 ASCII Data 3
Produce 31Slot 10 ASCII Data 4
Produce 32Slot 10 ASCII Data 5
Produce 33Slot 10 ASCII Data 6
Produce 34Slot 10 ASCII Data 7
Produce 35Slot 10 ASCII Data 8
Produce 36Slot 10 ASCII Data End of String Delimiter
Produce 37Slot 11 ARM - Reserved Byte
Produce 38ReservedSlot 13 Bit 3Slot 13 Bit 2Slot 13 Bit 1Slot 13 Bit 0
Consumed Assembly, Double Word Aligned
ByteBit 7Bit 6Bit5Bit 4Bit 3Bit 2Bit 1Bit 0
Consume 0ReservedRun/Idle
Consume 1Reserved
Consume 2Reserved
Consume 3Reserved
Consume 4ReservedSlot 4 Bit 1Slot 4 Bit 0
Consume 5ReservedSlot 5 Bit 3Slot 5 Bit 2Slot 5 Bit 1Slot 5 Bit 0
Consume 6Slot 6 Bit 7Slot 6 Bit 6Slot 6 Bit 5Slot 6 Bit 4Slot 6 Bit 3Slot 6 Bit 2Slot 6 Bit 1Slot 6 Bit 0
Consume 7Pad
Consume 8Slot 10 ASCII Data 1
Consume 9Slot 10 ASCII Data 2
Consume 10Slot 10 ASCII Data 3
Publication 1734-UM016A-EN-P - October 2010
28 Assembly Structure
Consumed Assembly, Double Word Aligned
ByteBit 7Bit 6Bit5Bit 4Bit 3Bit 2Bit 1Bit 0
Consume 11Slot 10 ASCII Data 4
Consume 12Slot 10 ASCII Data 5
Consume 13Slot 10 ASCII Data End of String Delimiter
Consume 14ReservedSlot 12 Bit 3Slot 12 Bit 2Slot 12 Bit 1Slot 12 Bit 0
Fixed Size per Slot Alignment
The following chassis is used to demonstrate how the Fixed Size per Slot
alignment option might be used. This chassis is built to show a machine that
sometimes uses 5 analog modules, but usually only needs 3 modules. In order
to maintain data structure consistency (and therefore the same control logic),
Fixed Size per Slot alignment of 6 bytes is used and the unused slots are
populated with Address Reserve Modules.
Example POINT system with unused slots
A
A
I
I
I
I
Cat #A
Slot #012345678
Produced Assembly, Fixed Size per Slot Alignment
ByteBit 7Bit 6Bit5Bit 4Bit 3Bit 2Bit 1Bit 0
Produce 0Slot 7 status Slot 6 statusSlot 5 status Slot 4 statusSlot 3 statusSlot 2 status Slot1 statusSlot 0 status
Produce 1Slot 15 status Slot 14 status Slot 13 status Slot 12 status Slot 11 status Slot 10 status Slot 9 statusSlot 8 status
Produce 2Slot 23 status Slot 22 status Slot 21 status Slot 20 status Slot 19 status Slot 18 status Slot 17 status Slot 16 status
Produce 3Slot 31 status Slot 30 status Slot 29 status Slot 28 status Slot 27 status Slot 26 status Slot 25 status Slot 24 status
Produce 4Slot 39 status Slot 38 status Slot 37 status Slot 36 status Slot 35 status Slot 34 status Slot 33 status Slot 32 status
Produce 5Slot 47 status Slot 46 status Slot 45 status Slot 44 status Slot 43 status Slot 42 status Slot 41 status Slot 40 status
Produce 6Slot 55 status Slot 54 status Slot 53 status Slot 52 status Slot 51 status Slot 50 status Slot 49 status Slot 48 status
Produce 7Slot 63 status Slot 62 status Slot 61 status Slot 60 status Slot 59 status Slot 58 status Slot 57 status Slot 56 status
Produce 8Slot 1 Channel 0 - Low Byte
Produce 9Slot 1 Channel 0 - High Byte
Produce 10Slot 1 Channel 1 - Low Byte
Produce 11Slot 1 Channel 1 - High Byte
Produce 12Slot 1 Channel 0 - Status
Produce 13Slot 1 Channel 1 - Status
I
R
R
M
B
4
E
E
E
E
M
2
2
2
N
C
C
C
T
I
B
B
4
4
Publication 1734-UM016A-EN-P - October 2010
Assembly Structure 29
Produced Assembly, Fixed Size per Slot Alignment
ByteBit 7Bit 6Bit5Bit 4Bit 3Bit 2Bit 1Bit 0
Produce 14Slot 2 Channel 0 - Low Byte
Produce 15Slot 2 Channel 0 - High Byte
Produce 16Slot 2 Channel 1 - Low Byte
Produce 17Slot 2 Channel 1 - High Byte
Produce 18Slot 2 Channel 0 - Status
Produce 19Slot 2 Channel 1 - Status
Produce 20Slot 3 Channel 0 - Low Byte
Produce 21Slot 3 Channel 0 - High Byte
Produce 22Slot 3 Channel 1 - Low Byte
Produce 23Slot 3 Channel 1 - High Byte
Produce 24Slot 3 Channel 0 - Status
Produce 25Slot 3 Channel 1 - Status
Produce 26Slot 4 ARM - Reserved Byte
Produce 27Slot 4 ARM - Reserved Byte
Produce 28Slot 4 ARM - Reserved Byte
Produce 29Slot 4 ARM - Reserved Byte
Produce 30Slot 4 ARM - Reserved Byte
Produce 31Slot 4 ARM - Reserved Byte
Produce 32Slot 5 ARM - Reserved Byte
Produce 33Slot 5 ARM - Reserved Byte
Produce 34Slot 5 ARM - Reserved Byte
Produce 35Slot 5 ARM - Reserved Byte
Produce 36Slot 5 ARM - Reserved Byte
Produce 37Slot 5 ARM - Reserved Byte
Produce 38ReservedSlot 6 Bit 3Slot 6 Bit 2Slot 6 Bit 1Slot 6 Bit 0
Produce 39Pad
Produce 40Pad
Produce 41Pad
Produce 42Pad
Produce 43Pad
Produce 44Slot 7 Bit 3Slot 7 Bit 2Slot 7 Bit 1Slot 7 Bit 0
Produce 45Pad
Produce 46Pad
Produce 47Pad
Produce 48Pad
Produce 49Pad
Produce 50Slot 8 Bit 3Slot 8 Bit 2Slot 8 Bit 1Slot 8 Bit 0
Produce 51Pad
Publication 1734-UM016A-EN-P - October 2010
30 Assembly Structure
Produced Assembly, Fixed Size per Slot Alignment
ByteBit 7Bit 6Bit5Bit 4Bit 3Bit 2Bit 1Bit 0
Produce 52Pad
Produce 53Pad
Produce 54Pad
Produce 55Pad
Publication 1734-UM016A-EN-P - October 2010
Chapter
5
1734/1738 I/O Module Assembly Information
Module Assembly
Discrete Modules
Information
POINT I/O and ArmorPOINT I/O Discrete I/O modules
Cat. NoDescriptionConfiguration
Assembly
Instance
1734-IB2
1738-IB2
1734-IB4
1738-IB4
1734-IB4D
1738-IB4D
1734-IB8
1738-IB8
1734-IV22 point DC source input103810
1734-IV4
1738-IV4
1734-IV8
1738-IV8
1734-OB2E
1738-OB2E
2 point DC sink input103810
4 point DC sink input1031610
2 point DC sink input with diagnostics103182,10
8 point DC sink input1033210
4 point DC source input1031610
8 point DC source input1033210
2 point DC source output123811
Configuration
Size
Produced Size Consumed Size
1734-OB4E
1738-OB4E
1734-OB22 point DC source output1238
1734-OB44 point DC source output123811
1734-OB88 point DC source output123811
1734-OB8E
1738-OB8E
1734-OW22 point relay output103401
1734-OW4
1738-OW4
1734-OV2E2 point 24V DC sink output123811
1734-OV4E
1738-OV4E
1734-OV8E8 point 24V DC sink output123811
1734-OX22 point Form C Relay output103401
31Publication 1734-UM016A-EN-P - October 2010
4 point DC source output123811
(1)
1
8 point DC source output123811
4 point relay output103401
4 point 24V DC sink output123811
1
32 1734/1738 I/O Module Assembly Information
POINT I/O and ArmorPOINT I/O Discrete I/O modules
Cat. NoDescriptionConfiguration
Assembly
Configuration
Size
Produced Size Consumed Size
Instance
1734-OB2EP
2 point 24V DC 2A Protected output123811
1738-OB2EP
1734-IA2
2 point 120V AC input103810
1738-IA2
1734-IA44 point 120V AC input1031610
1734-IM22 point 220V AC input103810
1734-IM44 point 220V AC input1031610
1734-OA2
2 point 120V/220V AC output103401
1738-OA2
1734-OA44-channel 120V/220V AC output103401
1738-IB1616 point 24V DC sink input10362,30
1738-OB1616 point 24V DC source input123212
1734-8CFG
1738-8CFG
(1)
While these modules (OB2, OB4, and OB8) have no meaningful data, they return a byte of 0 to be compatible with the "E" modules. In this manner they can be interchanged.
Also these modules expect the same 8-byte configuration assembly even though only the first 4 bytes are meaningful.
8 point 24V DC configurable sink
input/source output
103811
Analog and Specialty I/O Modules
POINT and ArmorPOINT Analog and Specialty I/O modules
Cat. NoDescriptionConfiguration
Assembly
Instance
1734-VHSC51 point 5V, 2 out very high speed counter1085462,2,4
1734-VHSC24
1 point 24V, 2 out very high speed counter 1085462,2,4
1738-VHSC24
1734-IJ
1 point 5V counter1231861
1738-IJ
1734-IK1 point 24V counter1231861
1734-IE2C
2 point analog current input1233860
1738-IE2C
1734-IE4C
4 point analog current input12374120
1738-IE4C
1734-IE8C8 point analog current input123146240
1734-OE2C
2 point analog current output1233624
1738-OE2C
Configuration
Size
Produced Size Consumed Size
Publication 1734-UM016A-EN-P - October 2010
POINT and ArmorPOINT Analog and Specialty I/O modules
1734/1738 I/O Module Assembly Information 33
Cat. NoDescriptionConfiguration
Assembly
Instance
1734-OE4C
1738-OE4C
1734-IT21
1738-IT21
1734-IR2
1738-IR2
1734-IR2E2 point enhanced RTD input1233860
1734-IE2V
1738-IE2V
1734-OE2V
1738-OE2V
1734-SSI
1738-SSI
1734-232ASC
1738-232ASC
1734-485ASC
1738-485ASC
1734-ARMAddress reserveN/A010
4 point analog current output1237248
2 point thermocouple input1034680
2 channel, 2point RTD input1233860
2 point analog voltage input1233860
2 point analog voltage output1233624
POINT I/O synchronous serial interface
POINT I/O RS232 ASCII interface
POINT I/O RS485 ASCII interface
12326102
103184…132
103184…132
Configuration
Size
Produced Size Consumed Size
default = 24
default = 24
4…132
default = 24
4…132
default = 24
Data Format
The POINT I/O products specify multi-byte data values in little endian
format. The term little endian refers to the ordering method in which:
• The least significant byte of a data item is ordered first.
• The most significant byte of a data item is ordered last
• All bytes in between are ordered sequentially, from least significant byte
to most significant byte.
Layout for 16 bit numbers:
TagName[Low Byte]
TabName[High Byte]
Layout for 32 bit numbers:
TagName[Low Byte]
TagName
Publication 1734-UM016A-EN-P - October 2010
34 1734/1738 I/O Module Assembly Information
TagName
TabName[High Byte]
Layout for Array data:
TagName[0]
TagName[1]
TagName[2]
: :
TabName[N]
Module Specific Details
Two-channel Discrete Input Modules
All two-channel discrete input modules use the same configuration and input
assemblies. Use the tables shown below for the following modules:
• 1734-IB2 or 1738-IB2
• 1734-IV2 or 1738-IV2
• 1734-IA2 or 1738-IA2
• 1734-IM2 or 1738-IM2
Configuration Assembly Instance 103
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Input 0 Off to On Filter Low Byte
1Input 0 Off to On Filter High Byte
2Input 0 On to Off Filter Low Byte
3Input 0 On to Off Filter High Byte
4Input 1 Off to On Filter Low Byte
5Input 1 Off to On Filter High Byte
6Input 1 On to Off Filter Low Byte
Publication 1734-UM016A-EN-P - October 2010
7Input 1 On to Off Filter High Byte
Produced Input Data Assembly 2
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0ReservedCh 1Ch 0
1734/1738 I/O Module Assembly Information 35
Four-channel Discrete Input Modules
All four channel discrete input modules use the same configuration and input
assemblies. Use the tables shown below for the following modules:
• 1734-IB4 or 1738-IB4
• 1734-IV4 or 1738-IV4
• 1734-IA4 or 1738-IA4
• 1734-IM4 or 1738-IM4
Configuration Assembly Instance 103
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Input 0 Off to On Filter Low Byte
1Input 0 Off to On Filter High Byte
2Input 0 On to Off Filter Low Byte
3Input 0 On to Off Filter High Byte
4Input 1 Off to On Filter Low Byte
5Input 1 Off to On Filter High Byte
6Input 1 On to Off Filter Low Byte
7Input 1 On to Off Filter High Byte
8Input 2 Off to On Filter Low Byte
9Input 2 Off to On Filter High Byte
10Input 2 On to Off Filter Low Byte
11Input 2 On to Off Filter High Byte
12Input 3 Off to On Filter Low Byte
13Input 3 Off to On Filter High Byte
14Input 3 On to Off Filter Low Byte
15Input 3 On to Off Filter High Byte
Produced Input Data Assembly 3
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0ReservedCh 3Ch 2Ch 1Ch 0
Eight-channel Discrete Input Modules
All eight-channel discrete input modules use the same configuration and input
assemblies. Use the tables shown below for the following modules:
Publication 1734-UM016A-EN-P - October 2010
36 1734/1738 I/O Module Assembly Information
• 1734-IB8 or 1738-IB8
• 1734-IV8 or 1738-IV8
Configuration Assembly Instance 103
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Input 0 Off to On Filter Low Byte
1Input 0 Off to On Filter High Byte
2Input 0 On to Off Filter Low Byte
3Input 0 On to Off Filter High Byte
4Input 1 Off to On Filter Low Byte
5Input 1 Off to On Filter High Byte
6Input 1 On to Off Filter Low Byte
7Input 1 On to Off Filter High Byte
8Input 2 Off to On Filter Low Byte
9Input 2 Off to On Filter High Byte
10Input 2 On to Off Filter Low Byte
11Input 2 On to Off Filter High Byte
12Input 3 Off to On Filter Low Byte
13Input 3 Off to On Filter High Byte
14Input 3 On to Off Filter Low Byte
15Input 3 On to Off Filter High Byte
16Input 4 Off to On Filter Low Byte
17Input 4 Off to On Filter High Byte
18Input 4 On to Off Filter Low Byte
19Input 4 On to Off Filter High Byte
20Input 5 Off to On Filter Low Byte
21Input 5 Off to On Filter High Byte
22Input 5 On to Off Filter Low Byte
23Input 5 On to Off Filter High Byte
24Input 6 Off to On Filter Low Byte
25Input 6 Off to On Filter High Byte
26Input 6 On to Off Filter Low Byte
27Input 6 On to Off Filter High Byte
28Input 7 Off to On Filter Low Byte
29Input 7 Off to On Filter High Byte
Publication 1734-UM016A-EN-P - October 2010
30Input 7 On to Off Filter Low Byte
31Input 7 On to Off Filter High Byte
Configuration Assembly Instance 123
1734/1738 I/O Module Assembly Information 37
Produced Input Data Assembly 4
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Ch 7Ch 6Ch 5Ch 4Ch 3Ch 2Ch 1Ch 0
Two-channel Discrete Output Modules with Status
All two-channel "enhanced" discrete output modules use the same
configuration and I/O assemblies. Use the tables shown below for the
following modules:
• 1734-OB2E or 1738-OB2E
• 1734-OV2E or 1738-0V2E
• 1734-OB2EP or 1738-OB2EP
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0ReservedFault State 1Fault State 0
1ReservedFault Value 1Fault Value 0
2ReservedIdle State 1Idle State 0
3ReservedIdle Value 1Idle Value 0
4ReservedEnable No Load 1Enable No Load 0
5ReservedReset mode 1Reset mode 0
6ReservedEnable Latched Alarms 1Enable Latched Alarms 0
7Pad
Produced Input Data Assembly 42
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0ReservedCh 1
Status
Consumed Output Data Assembly 32
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0ReservedCh 1Ch 0
Ch 0
Status
Publication 1734-UM016A-EN-P - October 2010
38 1734/1738 I/O Module Assembly Information
Two-channel Discrete Output Modules
Use the tables shown below for the following modules:
• 1734-OB2 or 1738-OB2
Configuration Assembly Instance 123
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0ReservedFault State 1Fault State 0
1ReservedFault Value 1Fault Value 0
2ReservedIdle State 1Idle State 0
3ReservedIdle Value 1Idle Value 0
4Reserved (Set to 0)
5Reserved (Set to 0)
6Reserved (Set to 0)
7Pad
Produced Input Data Assembly 42
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Reserved
Consumed Output Data Assembly 32
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0ReservedCh 1Ch 0
Four-channel Discrete Output Modules with Status
All four-channel "enhanced" discrete output modules use the same
configuration and I/O assemblies. Use the tables shown below for the
following modules:
• 1734-OB4E or 1738-OB4E
• 1734-OV4E or 1738-0V4E
Publication 1734-UM016A-EN-P - October 2010
1734/1738 I/O Module Assembly Information 39
Configuration Assembly Instance 123
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0ReservedFault State 3Fault State 2Fault State 1Fault State 0
1ReservedFault Value 3Fault Value 2Fault Value 1Fault Value 0
2ReservedIdle State 3Idle State 2Idle State 1Idle State 0
3ReservedIdle Value 3Idle Value 2Idle Value 1Idle Value 0
4ReservedEnable No Load 3 Enable No Load 2 Enable No Load 1 Enable No Load 0
5ReservedReset mode 3Reset mode 2Reset mode 1Reset mode 0
6ReservedEnable Latched
Alarms 3
7Pad
Produced Input Data Assembly 43
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Reserved
Consumed Output Data Assembly 33
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0ReservedCh 3Ch 2Ch 1Ch 0
Four-channel Discrete Output Modules
Use the tables shown below for the following modules:
• 1734-OB4 or 1738-OB4
Enable Latched
Alarms 2
Enable Latched
Alarms 1
Enable Latched
Alarms 0
Configuration Assembly Instance 123
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0ReservedFault State 3Fault State 2Fault State 1Fault State 0
1ReservedFault Value 3Fault Value 2Fault Value 1Fault Value 0
2ReservedIdle State 3Idle State 2Idle State 1Idle State 0
3ReservedIdle Value 3Idle Value 2Idle Value 1Idle Value 0
4Reserved (Set to 0)
5Reserved (Set to 0)
6Reserved (Set to 0)
7Pad
Publication 1734-UM016A-EN-P - October 2010
40 1734/1738 I/O Module Assembly Information
Produced Input Data Assembly 43
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Reserved
Consumed Output Data Assembly 33
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0ReservedCh 3Ch 2Ch 1Ch 0
Eight-channel Discrete Output Modules with Status
All eight-channel "enhanced" discrete output modules use the same
configuration and I/O assemblies. Use the tables shown below for the
following modules:
• 1734-OB8E or 1738-OB8E
• 1734-OV8E or 1738-OV8E
Configuration Assembly Instance 123
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Fault State 7Fault State 6Fault State 5Fault State 4Fault State 3Fault State 2Fault State 1Fault State 0
1Fault Value 7Fault Value 6Fault Value 5Fault Value 4Fault Value 3Fault Value 2Fault Value 1Fault Value 0
2Idle State 7Idle State 6Idle State 5Idle State 4Idle State 3Idle State 2Idle State 1Idle State 0
3Idle Value 7Idle Value 6Idle Value 5Idle Value 4Idle Value 3Idle Value 2Idle Value 1Idle Value 0
4Enable No
Use the tables shown below for the following modules:
• 1734-OB8 or 1738-OB8
Configuration Assembly Instance 123
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Fault State 7Fault State 6Fault State 5Fault State 4Fault State 3Fault State 2Fault State 1Fault State 0
1Fault Value 7Fault Value 6Fault Value 5Fault Value 4Fault Value 3Fault Value 2Fault Value 1Fault Value 0
2Idle State 7Idle State 6Idle State 5Idle State 4Idle State 3Idle State 2Idle State 1Idle State 0
3Idle Value 7Idle Value 6Idle Value 5Idle Value 4Idle Value 3Idle Value 2Idle Value 1Idle Value 0
4Enable No
Use the tables shown below for the following modules:
• 1734-IB4D or 1738-IB4DM12
Publication 1734-UM016A-EN-P - October 2010
42 1734/1738 I/O Module Assembly Information
Configuration Assembly Instance 103
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Input 0 Off to On Filter Low Byte
1Input 0 Off to On Filter High Byte
2Input 0 On to Off Filter Low Byte
3Input 0 On to Off Filter High Byte
4Input 1 Off to On Filter Low Byte
5Input 1 Off to On Filter High Byte
6Input 1 On to Off Filter Low Byte
7Input 1 On to Off Filter High Byte
8Input 2 Off to On Filter Low Byte
9Input 2 Off to On Filter High Byte
10Input 2 On to Off Filter Low Byte
11Input 2 On to Off Filter High Byte
12Input 3 Off to On Filter Low Byte
13Input 3 Off to On Filter High Byte
14Input 3 On to Off Filter Low Byte
15Input 3 On to Off Filter High Byte
16Autobaud
Disable
17Produced Assembly Instance
Enable Open
Wire Detect 3
Enable Open
Wire Detect 2
Enable Open
Wire Detect 1
Enable Open
Wire Detect 0
This POINT I/O input module produces 1 or 2 bytes of input data based on
which produced assembly is selected. The default assembly (instance 101) is 2
bytes. This module does not consume I/O data.
All two-channel relay and AC output modules use the same Consumed I/O
assembly. There are no Produced or Configuration assemblies for these
modules. Use the table shown below for the following modules:
• 1734-OW2
• 1734-OX2
• 1734-OA2 or 1738-OA2M12AC3
Consumed Output Data Assembly 32
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0ReservedCh 1Ch 0
Four-channel Relay and AC Output Modules
All four channel relay and AC output modules use the same Consumed I/O
assembly. There are no Produced or Configuration assemblies for these
modules. Use the table shown below for the following modules:
• 1734-OW4
• 1734-OW4M12 or 1738-OW4M12AC
• 1734-OA4
Consumed Output Data Assembly 32
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0ReservedCh 3Ch 2Ch 1Ch 0
Sixteen-channel Discrete Diagnostic Input Modules
Use the table shown below for the following modules:
• 1738-IB16DM12
Publication 1734-UM016A-EN-P - October 2010
44 1734/1738 I/O Module Assembly Information
Configuration Assembly Instance 103
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Input Off to On Filter Low Byte
1Input Off to On Filter High Byte
2Input On to Off Filter Low Byte
3Input On to Off Filter High Byte
4Produced Assembly
5Reserved = 0
This POINT I/O input module produces 2 or 3 bytes of input data based on
which produced assembly is selected. The default assembly instance 101 is 3
bytes. This module does not consume I/O data.
Produced Diagnostic Input Data Assembly Instance 101
All eight channel "configurable" discrete I/O modules use the same
configuration and I/O assemblies. Use the tables shown below for the
following modules:
• 1734-8CFG
• 1738-8CFGM12
• 1738-8CFGM23
• 1738-8CFGM8
Configuration Assembly Instance 103
ByteBit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Input Off to On Filter Low Byte
1Input Off to On Filter High Byte
2Input On to Off Filter Low Byte
3Input On to Off Filter High Byte
4Fault Action 7 Fault Action 6 Fault Action 5 Fault Action 4 Fault Action 3 Fault Action 2 Fault Action 1 Fault Action 0
5Fault Action 7 Fault Action 6 Fault Action 5 Fault Action 4 Fault Action 3 Fault Action 2 Fault Action 1 Fault Action 0
6Idle Action 7Idle Action 6Idle Action 5Idle Action 4Idle Action 3Idle Action 2Idle Action 1Idle Action 0
7Idle Value 7Idle Value 6Idle Value 5Idle Value 4Idle Value 3Idle Value 2Idle Value 1Idle Value 0
Produced Input Data Assembly 4
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Ch 7Ch 6Ch 5Ch 4Ch 3Ch 2Ch 1Ch 0
Publication 1734-UM016A-EN-P - October 2010
46 1734/1738 I/O Module Assembly Information
Consumed Output Data Assembly 34
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Ch 7Ch 6Ch 5Ch 4Ch 3Ch 2Ch 1Ch 0
Very High Speed Counter Modules
Use the tables shown below for the following modules:
• 1734-VHSC5
• 1734-VHSC25 or 1738-VHSC24M23
The modules support 3 different consumed output data assemblies. The
Active Output Assembly field of the Configuration assembly selects which
output assembly will be used. Assembly 105 is the default. Other produced
assemblies are possible but require separate configuration of the module. For
more information regarding the specific fields of these assemblies, consult the
product's user manual.
Produced Input Data Assembly 102
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Stored Channel Data [Low Byte]
1Stored Channel Data [1]
2Stored Channel Data [2]
3Stored Channel Data [High Byte]
4Status (Low Byte)
5Status (High Byte)
Consumed Output Data Assembly 105
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Counter Control
1Output Control
Consumed Output Data Assembly 106
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0PWM Value (Low Byte)
1PWM Value (High Byte)
Publication 1734-UM016A-EN-P - October 2010
1734/1738 I/O Module Assembly Information 47
Consumed Output Data Assembly 107
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0PWM Value (Low Byte)
1PWM Value (High Byte)
2Counter Control
3Output Control
Configuration Assembly Instance 108
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Counter Configuration
1Filter Selection
2Decimal Position
3Active Output Assembly
4Time Base or PWM Period (low byte)
5Time Base or PWM Period (high byte)
6Gate Interval
7Scalar
8Output 0 Ties
9Output 1 Ties
10Rollover Value [Low Byte]
11Rollover Value [1]
12Rollover Value [2]
13Rollover Value [High Byte]
14Preset Value [Low Byte]
15Preset Value [1]
16Preset Value [2]
17Preset Value [High Byte]
18ON Value # 1 [Low Byte]
19ON Value # 1 [1]
20ON Value # 1 [2]
21ON Value # 1 [High Byte]
22OFF Value #1 [Low Byte]
23OFF Value #1 [1]
24OFF Value #1 [2]
25OFF Value #1 [High Byte]
26ON Value # 2 [Low Byte]
27ON Value # 2 [1]
28ON Value # 2 [2]
Publication 1734-UM016A-EN-P - October 2010
48 1734/1738 I/O Module Assembly Information
Configuration Assembly Instance 108
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
29ON Value # 2 [High Byte]
30OFF Value #2 [Low Byte]
31OFF Value #2 [1]
32OFF Value #2 [2]
33OFF Value #2 [High Byte]
34ON Value # 3 [Low Byte]
35ON Value # 3 [1]
36ON Value # 3 [2]
37ON Value # 3 [High Byte]
38OFF Value #3 [Low Byte]
39OFF Value #3 [1]
40OFF Value #3 [2]
41OFF Value #3 [High Byte]
42ON Value # 4 [Low Byte]
43ON Value # 4 [1]
44ON Value # 4 [2]
45ON Value # 4 [High Byte]
46OFF Value #4 [Low Byte]
47OFF Value #4 [1]
48OFF Value #4 [2]
49OFF Value #4 [High Byte]
50PWM Safe State Value (low byte)
51PWM Safe State Value (high byte)
52Counter Control SSV
53Output Control SSV
Counter Modules
Use the tables shown below for the following modules:
Publication 1734-UM016A-EN-P - October 2010
• 1734-IJ or 1738-IJM23
• 1734-IK
The modules support 3 different consumed input data assemblies. The
produced input assembly can be set with the Requested Change of State
Produce Assembly filed of the Configuration assembly. Assembly 102 is the
1734/1738 I/O Module Assembly Information 49
default produced assembly. For more information regarding the specific fields
of these assemblies, consult the product's user manual.
Configuration Assembly Instance 123
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Counter Configuration
1Filter Selection
2Decimal Position
3Reserved
4Time Base (low byte)
5Time Base (high byte)
6Gate Interval
7Scalar
8Rollover Value [Low Byte]
9Rollover Value [1]
10Rollover Value [2]
11Rollover Value [High Byte]
12Preset Value [Low Byte]
13Preset Value [1]
14Preset Value [2]
15Preset Value [High Byte]
16Counter Control SSV
17Reserved (set to 0)
Produced Input Data Assembly 102
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Stored Channel Data [Low Byte]
1Stored Channel Data [1]
2Stored Channel Data [2]
3Stored Channel Data [High Byte]
4Status (Low Byte)
5Status (High Byte)
Consumed Output Data Assembly 105
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Counter Control
Publication 1734-UM016A-EN-P - October 2010
50 1734/1738 I/O Module Assembly Information
Two-channel Analog Input Modules
Use the tables shown below for the following modules:
0Channel 0 Data (Low Byte)
1Channel 0 Data (High Byte)
2Channel 1 Data (Low Byte)
3Channel 1 Data (High Byte)
4Channel 2 Data (Low Byte)
5Channel 2 Data (High Byte)
6Channel 3 Data (Low Byte)
7Channel 3 Data (High Byte)
8Channel 0 Status
9Channel 1 Status
10Channel 2 Status
11Channel 3 Status
Eight-channel Analog Input Modules
Use the tables shown below for the following modules:
0Channel 0 Data (Low Byte)
1Channel 0 Data (High Byte)
2Channel 1 Data (Low Byte)
Publication 1734-UM016A-EN-P - October 2010
3Channel 1 Data (High Byte)
4Channel 2 Data (Low Byte)
5Channel 2 Data (High Byte)
6Channel 3 Data (Low Byte)
7Channel 3 Data (High Byte)
1734/1738 I/O Module Assembly Information 59
Produced Input Data Assembly 101
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
8Channel 4 Data (Low Byte)
9Channel 4 Data (High Byte)
10Channel 5 Data (Low Byte)
11Channel 5 Data (High Byte)
12Channel 6 Data (Low Byte)
13Channel 6 Data (High Byte)
14Channel 7 Data (Low Byte)
15Channel 7 Data (High Byte)
16Channel 0 Status
17Channel 1 Status
18Channel 2 Status
19Channel 3 Status
20Channel 4 Status
21Channel 5 Status
22Channel 6 Status
23Channel 7 Status
Two-channel Analog Output Modules
Use the tables shown below for the following modules:
0Channel 0 Status
1Channel 1 Status
2Channel 2 Status
3Channel 3 Status
Produced Input Data Assembly 101
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Channel 0 Data (Low Byte)
1Channel 0 Data (High Byte)
2Channel 1 Data (Low Byte)
3Channel 1 Data (High Byte)
4Channel 2 Data (Low Byte)
5Channel 2 Data (High Byte)
6Channel 3 Data (Low Byte)
7Channel 3 Data (High Byte)
Publication 1734-UM016A-EN-P - October 2010
64 1734/1738 I/O Module Assembly Information
Two-channel RTD Input Modules
Use the tables shown below for the following modules:
0Channel 0 Data (Low Byte)
1Channel 0 Data (High Byte)
2Channel 1 Data (Low Byte)
3Channel 1 Data (High Byte)
4Channel 0 Status
5Channel 1 Status
6CJC Data (Low Byte)
7CJC Data (High Byte)
Synchronous Serial Interface Modules
Use the tables shown below for the following modules:
• 1734-SSI or 1738-SSIM12
Configuration Assembly Instance 123
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Run
1Gray/Binary
2SSI Word Length
3Data Rate
4Gray to Binary Conversion
5Standardization
6SSI Word Delay Time (Low Byte)
7SSI Word Delay Time (High Byte)
8Trailing bits
9Latch Input Control
10Sensor Resolution (Low Byte)
11Sensor Resolution (High Byte)
Publication 1734-UM016A-EN-P - October 2010
68 1734/1738 I/O Module Assembly Information
Configuration Assembly Instance 123
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
12Sensor Cycles (Low Byte)
13Sensor Cycles (High Byte)
14SSI Word Filter Control
15Alignment (reserved = 0)
16Comparator 1 Value [Low Byte]
17Comparator 1 Value [1]
18Comparator 1 Value [2]
19Comparator 1 Value [High Byte]
20Comparator 2 Value [Low Byte]
21Comparator 2 Value [1]
22Comparator 2 Value [2]
23Comparator 2 Value [High Byte]
24Comparator 1 Control
25Comparator 2 Control
Produced Input Data Assembly 101
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Present SSI Word [Low Byte]
1Present SSI Word [1]
2Present SSI Word [2]
3Present SSI Word [High Byte]
4Latched SSI Word [Low Byte]
5Latched SSI Word [1]
6Latched SSI Word [2]
7Latched SSI Word [High Byte]
8Module Status (Low Byte)
9Module Status (High Byte)
Consumed Output Data Assembly 102
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Master Ack Byte Output Control
1Reserved = 0
Publication 1734-UM016A-EN-P - October 2010
1734/1738 I/O Module Assembly Information 69
Address Reserve Module
Use the table shown below for the 1734-ARM. This module has no
configuration and does not consume any I/O data.
Produced Input Data Assembly 4
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Reserved = 0
ASCII Interface Modules
Use the tables shown below for the following modules:
• 1734-232ASC
• 1734-485ASC
• 1738-232ASCM12 or 1738-48ASCM12
Configuration Assembly Instance 103
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0ASCII Serial Character Format
1ASCII Serial Comm Speed
2ASCII Max Number of Receive Characters
3ASCII Receive Record Start Mode
4ASCII Receive Start Delimiter
5ASCII Receive Record End Mode
6ASCII Receive End Delimiter
7ASCII Receive String Data Type
8ASCII Pad Mode
9ASCII Pad Character
10ASCII Receive Swap Mode
11Handshake Mode
12ASCII Max Number of Transmit Characters
13ASCII Transmit End Delimiter Mode
14ASCII Transmit End Delimiter Character
Publication 1734-UM016A-EN-P - October 2010
70 1734/1738 I/O Module Assembly Information
Configuration Assembly Instance 103
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
15ASCII Consume String Data Type
16ASCII Transmit Swap Mode
17Transmit Handshake Mode
The format and length of the Produced and Consumed I/O assemblies vary
with the configuration of the module. For more information regarding the
specific fields of these assemblies and how they are impacted by the
configuration, refer to the product user manual.
Produced Input Data Assembly 101
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0RX Transaction ID
1Status
2
3
Reserved or Length
Reserved or Length
(2)
(2)
4ASCII Data (from 1 to 128 bytes)
(1)
N
(1)
(2)
<CR> Terminator
The length of the assembly depends on the amount of ASCII Data transmitted.
The meaning of these fields depends on the configuration of the module.
Consumed Output Data Assembly 102
Byte Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
0Reserved
1TX Transaction ID
2Reserved
3Length
4ASCII Data (from 1 to 128 bytes)
(1)
N
(1)
<CR> Terminator
The length of the assembly depends on the amount of ASCII Data transmitted.
Publication 1734-UM016A-EN-P - October 2010
Index
Numerics
16 bit numbers 33
16-bit boundary
1734/1738 I/O module
assembly information
1734-ARM module
6 bytes
28
6
31
7
A
AC output
modules
two-channel
Active Output Assembly
adapter
data exchange
add hardware
Address Reserve Module
alignment
Byte
Double Word
Fixed Size per Slot
option
Word
alignment options
analog I/O modules
ARM module
Array data
assemblies
configuration
data
I/O
input
produced
Assembly
assembly
configuration
data
information
output data
produced
structure
assembly connection
about
RSLogix5000
Automatic Device Replacement
43
43
46
1
17
28
6, 23
20, 23
7, 10, 20, 23
20, 28
28
20, 23
6
32
23
34
43
46
37, 38, 40
34, 35
43, 46
23
34, 46, 1, 16, 24, 26, 27, 43
34
31, 37, 38, 39, 4037, 38, 39, 40
23, 25, 26, 28
23
1, 5, 13
1
16, 13
B
boundaries 6
10, 18
byte
7
DINT
6, 7
fixed
7
boundary
16-bit
6
double word
Byte
data
6
6, 23
byte
aligned
least significant
most significant
byte boundaries
6, 10
23
3333
6
C
chassis 23
16
size
chassis size
choose a connection
CIP packets
CompactLogix
controllers
configuration
assembly instance
connection
data
header
setting tab
tag
Monitor tags
most significant byte
Multicast
multiple originators
O
O-->T 9
16
O2T
order
first
33
33
last
sequential
ordering
method
Originator to Target
originators
multiple
output
consumed
tag
output assembly
33
33
33
2
2
46
19
46
P
packet size
limitation
7
10
17
pane
Point to Point
Produced
produced assemblies
profile
EtherNet/IP
properties
connection
publications
related
15
43
43, 46
16
14
v
R
Rack Optimized 1
connections
direct connections
related documentation
related publications
relay output
two-channel
Remove and Insert Under Power
Requested Packet Interval
RIUP
2
RSLogix5000
RSNetWorx
RSNetWorx for EtherNet/IP
Run/Idle header
1, 2
1
v
v
43
15
16
7, 8, 13, 15
13
15
S
scanlist configuration 13
SINT
18
data
input data
sixteen-channel
discrete diagnostic input modules
Size
Consumed
Produced
size
connection
Size per Slot
specialty I/O modules
Status header
64-bit
status header
optional
supported
connection points
18
31
31
9
6
32
1, 2, 3
1
7, 9, 18
2
2
43, 44
Publication 1734-UM016A-EN-P - October 2010
74 Index
T
T-->O 9
T2O
16
tag arrays
unstructured
Target to Originator
troubleshooting
connection size errors
two-channel
discrete Input modules
relay and AC output modules
16
2
10
34, 37
34, 38, 37
U
unstructured tag arrays 16
V
values
33
data
43
W
word 6, 23
word boundaries
15
words
6
Publication 1734-UM016A-EN-P - October 2010
Rockwell Otomasyon Ticaret A.Ş., Kar Plaza İş Merkezi E Blok Kat:6 34752 İçerenköy, İstanbul, Tel: +90 (216) 5698400
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products.
At http://www.rockwellautomation.com/support/
application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the
best use of these tools.
For an additional level of technical phone support for installation, configuration, and troubleshooting, we offer TechConnect
support programs. For more information, contact your local distributor or Rockwell Automation representative,
or visit http://www.rockwellautomation.com/support/
Installation Assistance
If you experience a problem within the first 24 hours of installation, review the information that is contained in this manual.
You can contact Customer Support for initial help in getting your product up and running.
United States or Canada1.440.646.3434
Outside United States or
Canada
Use the Worldwide Locator
your local Rockwell Automation representative.
, you can find technical manuals, a knowledge base of FAQs, technical and
.
at http://www.rockwellautomation.com/support/americas/phone_en.html, or contact
New Product Satisfaction Return
Rockwell Automation tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility.
However, if your product is not functioning and needs to be returned, follow these procedures.
United StatesContact your distributor. You must provide a Customer Support case number (call the phone number above to obtain
Outside United StatesPlease contact your local Rockwell Automation representative for the return procedure.
one) to your distributor to complete the return process.
Documentation Feedback
You r c om me nt s will help us serve your documentation needs better. If you have any suggestions on how to improve this document,
complete this form, publication RA-DU002
, available at http://www.rockwellautomation.com/literature/.