Nexus Module
Nexus Module
1756-CLX/C
User Manual
Important User Information
Because of the variety of uses for the products described in this publication, those
responsible for the application and use of these products must satisfy themselves that all
necessary steps have been taken to assure that each application and use meets all
performance and safety requirements, including any applicable laws, regulations, codes
and standards. In no event will Allen-Bradley be responsible or liable for indirect or
consequential damage resulting from the use or application of these products.
Any illustrations, charts, sample programs, and layout examples shown in this publication
are intended solely for purposes of example. Since there are many variables and
requirements associated with any particular installation, Allen-Bradley does not assume
responsibility or liability (to include intellectual property liability) for actual use based
upon the examples shown in this publication.
Allen-Bradley publication SGI-1.1, Safety Guidelines for the Application, Installation and
Maintenance of Solid-State Control (available from your local Allen-Bradley office),
describes some important differences between solid-state equipment and
electromechanical devices that should be taken into consideration when applying products
such as those described in this publication.
Reproduction of the contents of this copyrighted publication, in whole or part, without
written permission of Rockwell Automation, is prohibited.
Throughout this publication, notes may be used to make you aware of safety
considerations. The following annotations and their accompanying statements help you to
identify a potential hazard, avoid a potential hazard, and recognize the consequences of a
potential hazard:
Product Support
Contact your Rockwell Automation representative for:
• sales and order support
• product technical training
• warranty support
• support service agreements
Technical Product Assistance
If you need to contact Rockwell Automation for technical assistance, please review the
troubleshooting information first. If the problem persists, contact a Rockwell Automation
representative at the following location:
Chapter 1 - About the 1756-CLX/C Module Chapter 2 - Install the 1756-CLX/C Module
Description of the 1756-CLX/C module Description of how to install the 1756-CLX/C
module and connect the Ethernet cable
Chapter 3 - About the NeXUS Network Chapter 4 - Configure the 1756-CLX/C Module
Overview of the NeXUS network and functions Description of how to configure the 1756-CLX/C
supported by the 1756-CLX/C module module with RSLogix 5000
Related Documentation
The following table lists related ControlLogix documentation:
Notes:
Preface
What This Preface Contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-1
Who Should Use This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-1
Purpose of This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-1
What This Manual Contains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-2
Common Techniques Used in This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . P-3
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-3
Chapter 1
About the 1756-CLX/C Module
What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
About the 1756-CLX/C Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Some Points to Remember . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
About the Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Hardware/Software Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Preventing Electrostatic Discharge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Removal and Insertion Under Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1756-CLX/C Module Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Chapter 2
Install the 1756-CLX/C Module
What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Identify Module Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
About the Jumpers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Install and Connect the Chassis and Power Supply . . . . . . . . . . . . . . . . . . . . . 2-2
Determine Module Slot Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Install the Module in the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Apply Power to the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Removal and Insertion under Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Chapter 3
About the NeXUS Network
What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Protocol Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Supported Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Network Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Supported ADP Message Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Configuration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Subnet Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
For More Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Chapter 4
Configure the 1756-CLX/C Module
What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Configure Your 1756-CLX/C Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Configuration Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Overview of the Configuration Process . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Create a New Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
View and Change Module Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Configure the Module IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Chapter 5
Status Indicators and Troubleshooting
What This Chapter Contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Use the LED Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Use the Communications Port Status Indicators . . . . . . . . . . . . . . . . . . . . . . . 5-3
Use the Alpha-numeric Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Appendix A
Specifications
Appendix B
Factory-set Jumpers
Appendix C
1756-CLX/C Web Interface
User Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Appendix D
1756-CLX/C Module Backplane Communication Tag List
About the Nexus Communication Flags (NX20 – NX91) . . . . . . . . . . . . . . . D-2
Boot /Reboot 1756-CLX/C Module Procedure. . . . . . . . . . . . . . . . . . . . D-2
1756-CLX/C Module Configuration Check Procedure . . . . . . . . . . . . . D-4
1756-CLX/C System Error Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . D-5
1756-CLX/C Module Sending Procedure . . . . . . . . . . . . . . . . . . . . . . . . D-6
1756-CLX/C Module Receiving Procedure . . . . . . . . . . . . . . . . . . . . . . D-7
Appendix E
1756-CLX/C Module Tag List
Glossary
Index
The module mounts into a ControlLogix chassis. It communicates with Logix controllers
across the ControlLogix chassis backplane. The module connects to the NeXUS network
via an Ethernet cable.
Module Features
1756-CLX/C module features include:
• NeXUS (ADP) messaging encapsulated within standard UDP/IP protocol
• interfacing via Ethernet media
• communication to and from ControlLogix controllers in the same chassis
• battery backed-up SRAM
Backplane connector
(interface to the
ControlLogix backplane)
Alpha-numeric display
Status indicators
Use only the Ethernet connector on the module. Do not use other
ATTENTION
connectors.
Hardware/Software Compatibility
The 1756-CLX/C module is compatible with the following firmware versions and
software releases. Contact Rockwell Automation if you need software or firmware
upgrades to use this equipment.
Backplane
1756-CLX/C API
Backplane
communication Backplane Windows
communication NT 4.0
1756-CLX/C (UDP/IP)
Application (ladder) module
1756-CLX/C
Tags (data) message handling
Ethernet port
Configuration Overview
The figure below shows an overview of the configuration process.
Development PC
ControlLogix tools
Logix5000 Controller
Application ladder
Setup
Tags
(DF, MCG, TCD) Created at sending
Handle (send)
Send parameters Created at startup
(DF, MCG, TCD)
(DF, TCD)
Handle (receive)
Receive parameters
(DF, TCD)
Data field (local only) and
multi-cast groups
IP Address
Parameters
(Node, TCP/IP) IP Address and mask
Data field
1756-CLX/C
module
Process Overview
The figure below shows the flow of data to and from the 1756-CLX/C module.
ControlLogix
Control Logix
Application
Application ladder
(Ladder)
Tags
TAGs
System status
Syst em Status System config.
System
Configuration
Recv.
Recvparameters
-Parametersand Send
Sendparameters
-Parametersand
NX20 ` NX51
(NX20 - NX51) (NX00
NX00- NX07)
` 07
and data NX90,91
data (NX90 and NX91) dataand data NX80
(NX90 and NX91)
Connected Data
Connected dataTransfer
transfer Unconnected Data
Unconnected dataTransfer
transfer
SystemStatus
System status
(NX20
NX20 `- NX51)
NX51
1756-CLX/C
NX/SAMmodule
Management process
Management Process
(nx_sam_man.exe)
(nx_sam_man.exe)
Shared
Shared
memory SystemStatus
System status SystemConfiguration
System config. (NX00
Memory
NX20 `- NX51 NX00 ` 07
(NX20 NX51) - NX07)
LED segment
LED Monitor
Monitor process
Process
Sys.Recv
Systemtransact. recv.
Transaction Receive process
Recv -Process Send process
Send -Process
display
Segment
(nx_sam_mon.exe) Process
(nx_sam_mon.exe) (nx_sam_mon.exe)
(nx_sam_recv.exe)
(nx_sam_recv.exe) (nx_sam_send.exe)
(nx_sam_send.exe)
Display (nx_sam_srecv .exe)
SystemTransaction
System transaction Transaction data
Transaction Data
Functions
Functions to
to Start/Stop Functions to receive
Functions Functions to send
Functions
start/stop NX Dlink
NX Dlink to receive to send
NXDlink
NX Dlink daemons
daemons and
and library
library
Windows
Windo ws NT 4.0with
NT4.0 with SP6a
SP6a(UDP/IP)
(UDP/IP)
1756-CLX/C56SAM
module
Ethernet
Ethernet Portport
Notes:
All jumpers on the 1756-CLX/C module are factory-set and should not
ATTENTION
be changed. If you change a jumper by mistake, refer to Appendix B of
this manual to reset it to the proper position.
20805-M
For information on installing these products, refer to the publications listed in the
following table.
Slot 0 Slot 2
Slot 1 Slot 3
Power Supply
Chassis
Circuit Board
31275-M
Slide the module into the chassis. Make sure the module backplane connector properly
connects to the chassis backplane. Check that the holding clips on the top and bottom of the
module are securely in the locking holes of the rack.
31276-M
1 ------ TD+
2 ------ TD-
3 ------ RD+ 8
4 ------ NC
1
5 ------ NC
6 ------ RD-
RJ 45
7 ------ NC
8 ------ NC
For detailed connnection information, refer to the EtherNet/IP Media Planning and
Installation Guide, publication ENET-IN001A-EN-P.
Ethernet port
Before you remove the module, you must disconnect the Ethernet
ATTENTION
cable.
If you are replacing an existing module with an identical one, and you
IMPORTANT
want to resume identical system operation, you must install the new
module in the same slot.
1
Push on upper and lower module tabs to
disengage them.
31277-M
2
Slide module out of chassis.
31278-M
Protocol Structure
The NeXUS network is a TCP/IP over Ethernet type LAN with a manufacturing message
transfer protocol, known as NeXUS, on top, as shown in the table below. This protocol is
known as the Autonomous Decentralized Protocol, or ADP.
Supported Services
The ADP protocol provides to application programs 2 means of message transmission:
peer-to-peer and multicast. Because the peer-to-peer message transfer requires a
connection-oriented service as an underlayer, it uses the TCP protocol.
Since multicast transmission is connectionless, multicast messages are sent and received
using the UDP protocol. As with any connectionless service, delivery and sequence of
messages is not guaranteed. Nor is there a flow control mechanism.
Network Organization
Looking from the top down, a NeXUS network is viewed as a system of islands called
domains, interconnected via a wide area network. Each domain is uniquely identified by a
domain number (DMN), which ranges from 1 to 64. The domain number must be provided
in all ADP PDU headers. DMN 0 is reserved for the domain considered within the scope
of the ADP specification.
A domain is divided into data fields. A data field is an area within which a group of logical
nodes communicates with each other via multicast or peer-to-peer messages. A domain is
uniquely identified by a data field number (DFN) which ranges from 1 through 255 and
must be provided in all ADP PDU headers. One data field is configured per network or
sub-network address of the IP address.
Only nodes belonging to the same data field can communicate with each other. A node can
belong to more than one data field. Relative to a node, a data field can be local or remote
(for example, connected to the node via a router). Only local data fields are considered
within the scope of the ADP specification.
To support multicast communication, nodes within a data field are organized into
multicast groups. A node can be a member of more than one multicast group. A multicast
group is uniquely identified as a multicast group number, or MGN, which ranges from 1 to
255. The MGN must be provided in all multicast ADP PDU headers.
Each NeXUS node, also called a logical node, is uniquely identified by a logical node
number, or LNN, which ranges from 1 to 4095. The LNN must be provided in all ADP
PDU headers.
The user normally assigns and manages DFNs, LNNs, and MGNs. DMN, DFN, and LNN
form the source address (SA). DMN, DFN, and MGN form the destination address (DA)
of an ADP PDU header.
Transmission Reception
Multicast Base-1 4.1 Supported Supported
communication
Alive signal Base-1 4.2 Supported Not supported
Configuration Requirements
Before you can use your 1756-CLX/C module, you must configure its IP address,
gateway, and subnet mask by specifying parameters NX00 through NX02 on the
Logix5000 controller. Refer to Appendices D and E of this manual for definitions of these
parameters.
IP Address
The IP address identifies each node on the TCP/IP network (or system of connected
networks). Each TCP/IP node on a network must have a unique IP address.
The IP address is 32 bits long and is composed of a net ID, host ID, and/or a multicast ID.
Each network can be a Class A, B, C, or D format. The class of the network determines
how an IP address is formatted.
0 1 8 16 24 31
Class A 0 Network ID host ID
0 1 8 16 24 31
Class B 1 0 Network ID host ID
0 1 8 16 24 31
Class C 1 1 0 Network ID host ID
0 1 16 24 31
Class D 1 1 1 0 Multicast ID host ID
Each node on the same physical network must have an IP address of the same class and
must have the same nework or multicast ID. Each node on the same network must have a
different host ID, giving it a unique IP address.
IP addresses are written as four decimal integers (0-255), separated by periods, where each
integer gives the value of one byte of the IP address.
You can distinguish the class of an IP address from the first integer in its dotted-decimal
IP address as follows:
Range of first integer Class
0 -127 A
128 -191 B
192 - 223 C
224 - 239 D
240 - 255 Experimental
For more information on Internet addressing, see Comer, Douglas E; Internetworking with
TCP-IP, Volume 1: Protocols and Architecture; Englewood Cliffs, N.J.: Prentice-Hall,
1990.
Gateways
A gateway connects individual physical networks into a system of networks. When a node
needs to communicate with a node on another network, a gateway transfers the data
between the two networks. The following figure shows gateway G connecting Network 1
with Network 2.
A
128.1.0.1
Network 1 128.1.0.2
G
B C 128.2.0.3
128.2.0.1 128.2.0.2
Network 2
When host B with IP address 128.2.0.1 communicates with host C, it knows from C’s IP
address that C is on the same network. In an Ethernet environment, B can then resolve C’s
IP address to a MAC address and communicate with C directly.
When host B communicates with host A, it knows from A’s IP address that A is on another
network (the net IDs are different). In order to send data to A, B must have the IP address
of the gateway connecting the two networks. In this example, the gateway’s IP address on
Network 2 is 128.2.0.3.
The gateway has two IP addresses (128.1.0.2 and 128.2.0.3). The first must be used by
hosts on Network 1 and the second must be used by hosts on Network 2. To be usable, a
host’s gateway must be addressed using a net ID matching its own.
Subnet Mask
Subnet addressing is an extension of the IP address scheme that allows a site to use a
single net ID for multiple physical networks. Routing outside of the site continues by
dividing the IP address into a net ID and a host ID via the class. Inside a site, the subnet
mask is used to redivide the IP address into a custom net ID portion and host ID portion.
Take Network 2 (a Class B network) in the previous example and add another physical
network. Selecting the following subnet mask would add two additional net ID bits
allowing for four physical networks:
Two bits of the Class B host ID have been used to extend the net ID. Each unique
combination of bits in the part of the host ID where subnet mask bits are 1 specifies a
different physical network.
The new configuration is:
A
128.1.0.1
Network 1 128.1.0.2
G
B C 128.2.64.3
128.2.64.1 128.2.64.2
Network 2.1
G2
D E 128.2.128.3
128.2.128.1 128.2.128.2
Network 2.2
A second network with Hosts D and E has been added. Gateway G2 connects Network 2.1
with Network 2.2. Hosts D and E will use Gateway G2 to communicate with hosts not on
Network 2.2. Hosts B and C will use Gateway G to communicate with hosts not on
Network 2.1. When B is communicating with D, G (the configured Gateway for B) will
route the data from B to D through G2.
Configuration Software
Use RSLogix 5000 software to set configuration for your 1756-CLX/C module. You have
the option of accepting default configuration for your module or writing configuration
specific to your application.
Both options are explained in detail, including views of software screens, in this chapter.
A screen appears with a list of possible new modules for your application. Select a module
from the list.
Click OK. The new module creation wizard appears. Enter information as follows:
Because the process of viewing and changing a module’s configuration tags is broader in
scope than can be addressed in this chapter, refer to Appendix D for more information and
sample tag collections.
Alpha-numeric display
Communication port
status indicators
Configu- Configuration ERR ON Error_ N/A N/A N/A N/A NX SAM See
ration Error Error Code Table 5.E
System NX DLINK is ERR ON 0x11008000 E 0x11008000 N/A N/A NXDlink Major Fault
Online inactive
Error
Data Buffer RUN OFF N/A W 0x11008001 N/A N/A NXDlink Warning
Overflowed
Data Buffer RUN OFF N/A E 0x11008002 N/A N/A NXDlink Minor Fault
Upper Limit
Data Buffer RUN OFF N/A I 0x11008003 N/A N/A NXDlink Informa-
Lower Limit tion
Receive Limit RUN OFF N/A W 0x12008004 N/A N/A N/A Warning
Over
of Data Handle
CPU Temp Over RUN OFF N/A W 0x4e000001 N/A N/A NX SAM Warning
Limit
CPU Temp RUN OFF N/A E 0x4e000002 N/A N/A NX SAM Minor Fault
Upper Limit
Send/ CPU Temp RUN OFF N/A I 0x4e000003 N/A N/A NX SAM Informa-
Receive Lower Limit tion
Error
Send Error RUN OFF N/A N/A N/A See Table 5.F NXDlink Individ-
Receive Error ual error for
each handle.
See
Table 5.F.
Notes:
Jumpers on the 1756-CLX/C module are factory-set. If you change the jumper settings by
mistake, follow this procedure to reset them.
32-bit (shown)
16-bit (shown)
1756-CLX/C CONFIGURATION
JUMPER SETTINGS
Front of module
The 1756-CLX/C module’s web page offers extensive internal and network diagnostics.
To view the web pages, enter the module’s IP address into your web browser. You can
access the following web pages.
User Screens
Figure C.1 Title screen
You can also access this screen by typing nxstat -m in a DOS window.
TIP
You can also access this screen by typing nxstat -t in a DOS window.
TIP
You can also access this screen by typing nxstat -b in a DOS window.
TIP
You can also access this screen by typing nxstat -h or nxhdl in a DOS
TIP
window.
The 1756-CLX/C module tags NX00 through NX91 are used for backplane (API)
communication, and should be defined in your ladder logic exactly as listed in Table D-A
in this Appendix. Refer to Appendix F for information on copying the tags and ladder
logic files from the .acd file supplied with the 1756-CLX/C module.
Failure to properly define the module tags NX00 through NX91 may
ATTENTION
result in unpredictable module operation.
Change Parameter
Power on
1756-CLX/C
NX47_Module_
Ready
(BOOL)
NX20_Module
_Enable
(BOOL)
NX48_Module_
Enable_Ack
(BOOL)
OFF ON OFF ON
NX40_Module_
Enabled
(BOOL)
Change Parameter
(Node Name or IP address)
ON
Power on
1756-CLX/C
NX47_Module_ ON
Ready
(BOOL) OFF
NX20_Module
_Enable
(BOOL)
NX48_Module_
Enable_Ack
(BOOL)
ON ON
NX40_Module_ OFF OFF
Enabled
(BOOL)
CLX
NX20_Module_Enable
(BOOL)
NX48_Module_
Enable_Ack
Tags (BOOL)
NX40_Module_Enabled
(BOOL)
NX46_System_Error
(BOOL)
NX60_System_Error
Code(DINT)
1756-CLX/C
NX63_Status_Level
(DINT)
NX64_Status_Code
(DINT)
1756-CLX/C
Request Sending.
(1) Sets Send_Data and Data Buffer (1) Checks NX61_Send_Error_Code has not set Error
Ladder Size NX80 tags (2) Clears NX30_Send_Request.
(2) Sets NX30_Send_Request
CLX
NX30_Send_Request
(BOOL)
Tags NX50_Send_Done
(BOOL)
NX61_Send_Error_Code
(DINT[32])
0 if success, Error code if failure
1756-CLX/C
CLX
NX31_Receive_Done
(BOOL)
NX51_Receive_
Tags Request
(BOOL)
NX62_Receive_
Error_Code
(DINT[32]) 0 if success, Error code if failure
1756-CLX/C
(1) Receiving data
NX (2) If success
Recv-Process Sets NX91_Receive_Data_xx (1) Clears NX62_Receive_Error_Code
(xx:00-31) Sets NX90_Received_Data_size[xx] (2) Clears NX51_Receive_Request
(3)Sets NX62_Receive_Error_Code
(4)Sets NX31_Receive_Request
(xx:00-31)
Notes:
Application Program (AP) An upper layer program used for application pro-
cessing, including user processes and applications. An example of an applica-
tion program is a Logix5550 program.
Ethernet A physical layer standard using Carrier sense Multiple Access with
Collision Detection (CSMA/CD) methods.
NeXUS A trade name of a plant-floor TCP/IP over Ethernet type local area net-
work with the ADP protocol on the top.
NeXUS Node or Station Any PLC, computer or other physical device con-
nected to a NeXUS network.
Protocol Data Unit (PDU) PDU refers to a data unit passed to ADP from the
lower layer protocol (UDP or TCP) and vise versa. It consists of a header and a
message.
I
About the module 1-1 Inhibit
ADP message types supported 3-4 choosing in RSLogix 5000 4-4
Alpha-numeric display 5-3 installing the 1756-ENBT module
removing or replacing the module 2-5
B Installing the module 2-1
Battery 1-4 IP address 3-4
C M
Chassis and power supply Memory map A-1
installing 2-2 Module
Configuration about 1-1
accessing module tags 4-5 apply power 2-3
creating a new module 4-2 configuring 4-1
editing configuration in RSLogix 5000 determine slot location 2-2
4-5 features 1-2
overview of the process 4-2 identify components 2-1
Configuration requirements 3-4 installing 2-1
Configuration software 4-1 remove or replace 2-5
Configuring the module 4-1 Module tags
accessing in RSLogix 5000 4-5
D
Documentation N
related P-3 NeXUS network
about 3-1
E
NeXUS network organization 3-3
Electrostatic Discharge 1-5
Error codes 5-3 P
Ethernet Protocol structure 3-1
for more information about 3-8
R
G Removal and insertion under power 1-5,
Gateways 3-6 2-4
Requested Packet Interval (RPI)
H adjusting in RSLogix 5000 4-4
Hardware/software compatability 1-4 RIUP 1-5, 2-4
RSLogix5000 4-1
S
Specifications A-1
Status indicators
communications port 5-3
LED 5-2
troubleshooting 5-1
Subnet mask 3-7
Supported services 3-2
System time
adjusting the RPI 4-4
T
Tag List
module backplane communication D-1
Tag list E-1
Time charts D-1
W
Web interface C-1
user screens C-1