Parker PSSCDM12A User manual

Pneumatic
Isysnet
DeviceNet
Adapters
PSSCDM12A,
PSSCDM18PA
User Manual

Publication PSS-UM001A-EN-P – June 2005
Important User Information
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 E116P available online at www.parker.com/pneu/isysnet)
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 Parker Hannifin Corporation 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, Parker
Hannifin Corporation cannot assume responsibility or liability for
actual use based on the examples and diagrams.
No patent liability is assumed by Parker Hannifin Corporation 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 Parker Hannifin Corporation is prohibited.
Throughout this manual, when necessary, we use notes to make
you aware of safety considerations.
!
!
WARNING Identifies information about practices or
circumstances that can cause an explosion in
a hazardous environment, which may lead to
personal injury or death, property damage, or
economic loss.
IMPORTANT
Identifies information that is critical for successful
application and understanding of the product.
ATTENTION Identifies information about practices or
circumstances that can lead to personal injury
or death, property damage, or economic loss.
Attentions help you:
• Identify a Hazard
• Avoid a Hazard
• Recognize the Consequence
SHOCK HAZARD Labels may be located on or inside the
equipment (e.g. drive or motor) to alert people
that dangerous voltage may be present.
BURN HAZARD Labels may be located on or inside the
equipment (e.g. drive or motor) to alert people
that surfaces may be at dangerous temperatures.
Environment and Enclosure
This equipment is intended for use in overvoltage Category II
applications (as defined in IEC publication 60664-1), at altitudes
up to 2000 meters without derating. This equipment is
considered Group 1, Class A industrial equipment according
to IEC/CISPR Publication 11. Without appropriate precautions,
there may be potential difficulties ensuring electromagnetic
compatibility in other environments due to conducted as well
as radiated disturbance. This equipment is supplied as
“enclosed” equipment. It should not require additional system
enclosure when used in locations consistent with the enclosure
type ratings stated in the Specifications section of this
publication. Subsequent sections of this publication may contain
additional information regarding specific enclosure type ratings,
beyond what this product provides, that are required to comply
with certain product safety certifications.
NOTE: See NEMA Standards publication 250 and IEC
publication 60529, as applicable, for explanations of the degrees
of protection provided by different types of enclosure. Also,
see the appropriate sections in this publication, as well as the
publication E115P (“Industrial Automation Wiring and Grounding
Guidelines”), for additional installation requirements pertaining
to this equipment.
!
ATTENTION
Preventing Electrostatic Discharge
This equipment is sensitive to electrostatic discharge, which
can cause internal damage and affect normal operation. Follow
these guidelines when you handle this equipment:
• Touch a grounded object to discharge potential static.
• Wear an approved grounding wriststrap.
• Do not touch connectors or pins on component boards.
• Do not touch circuit components inside the equipment.
• If available, use a static-safe workstation.
• When not in use, store the equipment in appropriate static-
safe packaging.
!
ATTENTION

Publication PSS-UM001A-EN-P – June 2005
Preface 1
Purpose of This Manual
This manual describes how to install, configure, and operate
your Isysnet DeviceNet™ Adapters, catalog numbers
PSSCDM12A and PSSCDM18PA.
See the Following Sections: Page:
Who Should Use This Manual P-1
What the Manual Contains P-2
Related Terms P-3
Related Products and Documentation P-4
Guidelines for Using Your Adapter P-4
Conventions Used in This Manual P-4
IMPORTANT
In this manual, we use Isysnet DeviceNet adapters to refer to
all the DeviceNet adapter modules (PSSCDM12A and
PSSCDM18PA). We use the specific catalog number (e.g.,
PSSCDM12A) to refer to a specific module.
In the rest of this manual (except Chapter 4), we refer to the
Isysnet I/O DeviceNet adapters as the adapters.
In Chapter 4, we refer to the Isysnet I/O DeviceNet adapter as
the scanner because the chapter describes how to configure
the adapter on the subnet.
Who Should Use This Manual
You must be able to use RSNetWorx for DeviceNet™ software,
or a similar configuration software, to configure your adapter.
In this manual, we assume you know how to configure an
adapter. If you do not, refer to your software user manuals, or
online help, before attempting to use these adapters.
We also assume you are familiar with the Isysnet I/O product
line, including other fieldbus interfaces, I/O modules, and power
supplies. If you are not familiar with these components, you can
read some of the Isysnet I/O documents listed in the Related
Products and Documentation section.

Publication PSS-UM001A-EN-P – June 2005
Chapter 3 - Use Auto Start Mode Or Chapter 4 - Configure the DeviceNet Scanner Subnet
Description of how to use the Auto Start Mode on your Description of how to configure your
adapter to quickly get your system up and running adapter on the subnet
What the Manual Contains
This manual contains the following sections:
Chapter 1 - Install the Isysnet DeviceNet Adapters Chapter 2 - What Is the Isysnet DeviceNet Adapter?
Description of how to install and wire the adapter Overview of the adapter’s features and functionality
DeviceNet Out
PSSCDM12A
DeviceNet In
X10
PWR
X1
Adapter
Status
DeviceNet
Status
PointBus
Status
System
Power
Adapter
Power
Chapter 5 - Add the Isysnet DeviceNet Adapter Chapter 6 - Troubleshoot the
to the DeviceNet Scanner’s Scanlist Isysnet DeviceNet Adapter
Description of how to configure the DeviceNet adapter Description of how to use the status indicators
and how to add it to the scanlist and how to troubleshoot your adapter
Appendix A - Specifications Appendix B - Default Data Maps
Listing of the Isysnet adapters’ specifications Listing of the default data maps for Isysnet I/O modules
Publication PSS-UM001A-EN-P – April 2005
Chapter 5
Add the IsysNet DeviceNet Adapter to
the DeviceNet Scanner's Scanlist
This chapter describes how to custom configure your adapter
for use with DeviceNet devices.
See the Following Sections: Page:
Configuration Overview 5-1
Add the Adapter toYour Network 5-1
Set the Adapter's Parameters 5-2
Go On Line 5-4
Chapter Summary 5-4
Your adapter works on two networks simultaneously and must
be configured for each separately, which means that you will
have two separate RSNetWorxfor DeviceNet software files.
This chapter explains configuration of the adapter for use on the
primary DeviceNet network. For information on how to configure
the adapter for use on the Subnet, see Chapter 4, Configure the
DeviceNet Scanner Subnet.
Configuration Overview
Youmust use the RSNetWorx for DeviceNet software to configure
your adapter. Youcan configure the adapter while it is:
On line
Off line
This chapter shows configuration in the offline mode. Configuration
screens appear the same in both modes. Note that some screen
options are unavailablein offline mode. The only difference is that if
you make changes off line, you must take the adapter on line
before the configuration changes take effect.
Youmust follow these steps during configuration:
1. Add the adapter to your network
2. Set the adapter’s parameters
3. Add the DeviceNet adapter’s scanlist (see the Quick Start,
Appendix B)
4. Go on line
Add the Adapter to Your Network
Follow these steps:
1. Start the RSNetWorx for DeviceNetsoftware.
2. Add the adapter as shown below.
1. Expand
the list of
communication
adapters.
2. To add the
adapter, you
can double click
on the adapter,
or click and drag
the adapter
name onto
the network.
Publication PSS-UM001A-EN-P – April 2005
Chapter 6
Troubleshoot the IsysNet
DeviceNet Adapter
This chapter describes how to troubleshoot your adapter.
See the Following Sections: Page:
Use the Status Indicators 6-1
Guidelines for UsingYour Adapter 6-2
Chapter Summary 6-2
Use the Status Indicators
Youcan use the status indicators to troubleshoot your adapter. The
following graphicshows the adapter’s status indicators.
Use the table below to troubleshoot youradapter.
DNet
Out
PSSCDM18PA
Adapter
Status
DeviceNet
Status
PointBus
Status
System
Power
Adapter
Power
DNet
In
X10
PWR
X1
PSSCDM18PA
AdapterStatus
Indicator
DeviceNetStatus
Indicator
PointBusStatus
Indicator
SystemPower
Indicator
AdapterPower
Indicator
Indication Probable Cause
PointBus Status
Off Device is not on line:
- Device has not completed
dup_MAC-id test
- Device not powered- check module
status indicator
Flashing Green Device is on line but has no
connections in the established state
Green Device is on line and has
connections in the established state
Flashing Red One or more I/O connections in
timed-out state
Red Critical link failure - failed
communication device. Device
detected error that prevents it from
communicating on the network.
(Possible duplicate MACID or baud
rate mismatch).
Flashing Red/Green
Communication faulted device- the
device has detected a network access
error and is in communication faulted
state.Device has received and accepted
an Identity Communication Faulted
Request - long protocol message.
Indication Probable Cause
System Power
Off Not active - Field power is off or
dc-dc converter problem.
Green System power on - dc-dc converter
active (5V).
Indication Probable Cause
Adapter Power
Off Not active - Field power is off.
Green System power on, 24V present.
Indication Probable Cause
DeviceNet Status
Off Device is not on line:
- Device attempting to Autobaud
- Device has not completed
dup_MAC-id test
- Device not powered- check module
status indicator
Flashing Green Device is on line but has no
connections in the established state
Green Device is on line and has
connections in the established state
Flashing Red One or more I/O connections in
timed-out state
Red Critical link failure - failed
communication device. Device
detected error that prevents it from
communicating on the network.
(Possible duplicate MACID or baud
rate mismatch).
Indication Probable Cause
Adapter Status
Off No power applied to device
Green Device operating normally
Flashing Red Recoverable fault
Red Unrecoverablefault -
may require device replacement
Flashing Red/Green Device is in self-test
Publication PSS-UM001A-EN-P – April 2005
Appendix A
Specifications
Following are specifications for the DeviceNetadapters.
DeviceNet Adapters - PSSCDM12A,PSSCDM18PA
Expansion I/O Capacity DeviceNet adapter backplane current output = 1.0A maximum.
See the list below for backplane current consumption foreach I/O catalog number and
the current consumption for each of the modules connected to the DeviceNet adapter.
Verify that it is below1.0A.
Backplanecurrent can be extended beyond 1.0A with a PSSSE24A Backplane
Extension PowerSupply. The PSSSE24A can supply up to an additional 1.3A of
backplane current.
MultiplePSSSE24A modules can be used to reach the
maximum of 63 modules.
Cat. No. PointBus Current Requirements
PSSN8xxx 75 mA
PSSP8xxx 75 mA
PSST8xxx 75 mA
PSSTR4M12A 90 mA
PSSNACM12A 75 mA
PSSNAVM12A 75 mA
PSSTACM12A 75 mA
PSSTAVM12A 75 mA
PSSS23A 75 mA
PSSV32A 75 mA
DeviceNet Communication Rate 125K bit/s (500m maximum)
250K bit/s (250m maximum)
500K bit/s (100m maximum)
DeviceNet PowerSpecifications
PowerSupply Note: In order to comply with CE LowVoltage Directives (LVD), you must use either a
NEC Class 2, a Safety Extra LowVoltage (SELV) or a Protected ExtraLow Voltage (PELV)
power supply to power this adapter.A SELV supply cannot exceed 30V rms, 42.4V peak
or 60VDC under normal conditions and under single fault conditions.A PELV supply has
the same rating and is connected to protected earth.
Input VoltageRating 24VDC nominal
DeviceNet InputVoltage Range 11-25VDC DeviceNet specification
Input Overvoltage Protection Reversepolarity protected
DeviceNet PowerRequirements 24VDC (+4% = 25VDC) @ 30 mA maximum
Power SupplySpecifications
PowerSupply Note: In order to comply with CE LowVoltage Directives (LVD), you must use either a
NEC Class 2, a Safety Extra LowVoltage (SELV) or a Protected ExtraLow Voltage (PELV)
power supply to power this adapter.A SELV supply cannot exceed 30V rms, 42.4V peak
or 60VDC under normal conditions and under single fault conditions.A PELV supply has
the same rating and is connected to protected earth.
Input VoltageRating 24VDC
10-28.8VDC range
Input Overvoltage Protection Reversepolarity protected
Inrush Current 6A maximum for 10ms
PointBus Output Current 1A maximum @ 5VDC +5% (4.75-5.25)
Field Side PowerRequirements, Maximum 24VDC (+20% = 28.8VDC) @ 400 mA
Interruption Output voltage will stay within specifications when input drops out for
10ms at 10V with maximum load
General Specifications
LED Indicators 1 green/red Adapter status
1 green/red DeviceNet status
1 green/red PointBus status
1 green System Power(PointBus 5V power)
1 green Adapter Power(24V from field supply)
Publication PSS-UM001A-EN-P – April 2005
Appendix B
Default Data Maps
I/O messages are sent to (consumed) and received from
(produced) the IsysNet I/O modules. These messages are
mapped into the processor’s memory. This appendix lists the
default data maps for 1738 IsysNet I/O modules.
For the Default Data Map of: See Page:
PSSN8 Sink Input Module B-1
PSSP8 Source Input Module B-1
PSST8 Electronically Protected Output Module B-2
PSSTR4 Relay Sink/Source Output Module B-2
PSSNAC Analog Current Input Module B-2
PSSNAV Analog Input Module B-3
PSSTACAnalog Current Output Module B-3
PSSTAVAnalog Output Module B-4
PSSS23A ASCII Module B-4
PSSN8 Sink Input Module
Message size: 1 Byte
76543210
Produces (scanner Rx) Ch7 Ch6 Ch5 Ch4 Ch3 Ch2 Ch1 Ch0
Consumes (scanner Tx) No consumed data
Where: Ch0 = input channel 0, Ch1 = input channel 1, Ch2 = input channel 2, Ch3 = input channel 3, Ch4 = input channel 4, Ch5 = input channel 5,
Ch6 = input channel 6, Ch7 = input channel 7; 0 = OFF, 1 = ON
PSSP8 Source Input Module
Message size: 1 Byte
76543210
Produces (scanner Rx) Ch7 Ch6 Ch5 Ch4 Ch3 Ch2 Ch1 Ch0
Consumes (scanner Tx) No consumed data
Where: Ch0 = input channel 0, Ch1 = input channel 1, Ch2 = input channel 2, Ch3 = input channel 3, Ch4 = input channel 4, Ch5 = input channel 5,
Ch6 = input channel 6, Ch7 = input channel 7; 0 = OFF, 1 = ON
2 Preface

Publication PSS-UM001A-EN-P – June 2005
Related Terms
This manual uses the following terms:
Term Definition
Adapter The adapter interfaces between DeviceNet
devices and Isysnet I/O modules. Isysnet
I/O DeviceNet adapters include the
PSSCDM12A and PSSCDM18PA.
Auto
The Isysnet I/O DeviceNet adapter supports
Catalog the swapping of two identical modules connected
Replace to the adapter. That is, if a PSSN8M8A is in slot 3
and another PSSN8M8A is in slot 7, the two
modules can be removed from the Isysnet
system and the slot 3 module placed into slot 7,
and vice-versa. When Automatic Device
Replacement (ADR) is active, the swapped
modules will be reconfigured to match the
previous module in their new slot. When ADR is
not active, the configuration parameters will not
be modified, the swapped modules must have
identical configuration and values for their EDS
file parameters.
Auto This refers to the ADR feature of a ControlLogix
Device System on DeviceNet. With ADR active, any
Replacement device on the DeviceNet link may be removed
(ADR) and replaced with an out-of-the-box checkmark
compliant DeviceNet device. The ADR feature
will result in downloading the values of the
configuration parameters of the EDS file of the
removed device to the new device.
Auto A feature that lets the Isysnet I/O system get “up
Start and running” without the prerequisite to configure
Mode any of the EDS parameters for the PointBus™ or
Isysnet I/O modules. Using Auto Start Mode will
result in a scan list within the adapter that stores
the modules identity information.
Autobaud A feature in devices (e.g., Isysnet I/O modules)
on the DeviceNet network that causes them to
listen to communications on the network and set
their own baudrate to match the network rate.
Backplane The PointBus that consists of Isysnet I/O modules
connected to the Isysnet DeviceNet adapter.
Baudrate Rate of communications between devices on the
DeviceNet network. Backplane baudrate is used
for the PSSCMD12A and PSSCDM18PA.
Change DeviceNet communications method in which the
of State adapter sends data based on detection of any
(COS) changed value within the input data. Data is
independently received based on a change of
state from the sender. Data in both directions can
be acknowledged or unacknowledged depending
on the run-time configuration of the system.
Commissioning The period in time associated with post startup
activities. Commissioning implies that the
system has been validated and all configuration
parameters are correct, all modules are in
good operating condition, and the adapter
scanlist is complete.
ControlFlash™ Utility software you can use to update the
adapter’s firmware with the most current boot
and application code.
Term Definition
Cyclic DeviceNet communications method in which
the adapter sends data cyclically based on a
configured time value. Data is independently
received cyclically from the sender. Data in
both directions can be acknowledged or
unacknowledged depending on the run time
configuration of the system.
MACID Media Access Control Identifier
(DeviceNet network address).
Master A DeviceNet network device (e.g., Rockwell
Automation 1771-SDN) that initiates
communication with DeviceNet slave devices
(e.g., Isysnet I/O modules) to retrieve data.
The master only receives unprompted data
when the slave is enabled for COS and there
is a change in the device’s operating state.
Offline State of the adapter when it is not powered or
maintaining normal communication exchanges
with other DeviceNet devices.
Online State of the adapter when it is powered and
maintaining normal communication exchanges
with other DeviceNet devices.
PointBus The Isysnet I/O backplane PointBus maintains
all DeviceNet network protocol, but also offers
configuration capabilities.
Polled DeviceNet communications method in which
a module sends data in response to
received data.
Primary The primary DeviceNet network is defined as
Network the DeviceNet link that provides the direct
connection between the Isysnet DeviceNet
adapter and a DeviceNet scanner.
RSNetWorx for Configuration software for the adapter and
DeviceNet Subnet modules.
Scanlist The list of Subnet modules connected to the
adapter. When ADR is active, the scanlist
stores the configured values of each of the
Subnet modules’ configurable parameters.
When ADR is not active, the scanlist stores
only the module identity information.
Scanner Operating state of the Isysnet DeviceNet
adapter when it retrieves I/O data from
Subnet modules.
Slave A DeviceNet network device that cannot initiate
communication (except when configured with
COS enabled) but responds to a DeviceNet
master device.
Strobe Adapter sends data in response to the strobe
command. The single bit allocated to the
adapter in the strobe message is not used.
If the configured size of the input data (sent
from the adapter) is greater than 8 bytes, the
strobe connection establishment will fail. In this
case, the input size must be reconfigured to
8 bytes or less.
Preface 3

Publication PSS-UM001A-EN-P – June 2005
Related Products and Documentation
The following table lists related Isysnet I/O products and documentation:
If you need more information on these products, contact your local
distributor, integrator or sales office for assistance.
Guidelines for Using Your Adapter
Remember the following operational guidelines when using your
Isysnet DeviceNet adapter.
• Do not leave spaces in the I/O. Instead, install all Isysnet I/O
modules adjacent to each other.
• Populate every position on the mounting base.
• Isysnet does not support removal and insertion under power
(RIUP). When an I/O module is removed, the IP67 seal is
broken and the backplane bus is interrupted.
4 Preface
Description Catalog Number Publication
Isysnet Serial Bus System Selection Guide N/A PSS-SG001
Isysnet 32 Point Valve Driver Installation Instructions PSSV32A E100P
Isysnet DeviceNet Adapters Installation Instructions PSSCDM12A, PSSCDM18PA E101P
Isysnet DeviceNet Adapter User Manual PSS-UM001
Isysnet PROFIBUS Adapter Installation Instructions PSSCPBA E102P
Isysnet PROFIBUS Adapter User Manual PSS-UM002
Isysnet ControlNet Adapter Installation Instructions PSSCCNA E103P
Isysnet ControlNet Adapter User Manual PSS-UM003
Isysnet EtherNet/IP Adapter Installation Instructions PSSCENA E104P
Isysnet EtherNet/IP Adapter User Manual PSS-UM004
Isysnet I/O 24VDC Expansion Power Supply Installation Instructions PSSSE24A E105P
Isysnet 24VDC Input Modules Installation Instructions PSSN8, PSSP8 E106P
Isysnet 24VDC Output Modules Installation Instructions PSST8 E107P
Isysnet Relay Output Modules Installation Instructions PSSTR4M12A E109P
Isysnet 24VDC Analog Input Modules Installation Instructions PSSNA E110P
Isysnet 24VDC Analog Output Modules Installation Instructions PSSTA E111P
Isysnet RS232 ASCII Module Installation Instructions PSSS23A E112P
Industrial Automation Wiring and Grounding Installation Instructions N/A E115P
Safety Guidelines for the Application, Installation and Maintenance of N/A E116P
Solid State Control
PSSCDM12A, PSSCDM18PA
PSSCPBA
PSSCCNA
PSSCENA
Conventions Used In This Manual
The following conventions are used throughout this manual:
• Bullet lists (such as this one) provide information, not
procedural steps
• Numbered lists provide sequential steps
• Text written like this identifies screen, menu, toolbar names,
field names, buttons, and check boxes on screens
• A menu item in this format File>Save identifies the submenu
item after the caret (>) that is accessed from the main menu
(name before the caret)
• Pictures of symbols and/or screens represent the actual
symbols you see or the screens you use

Publication PSS-UM001A-EN-P – June 2005
Table of Contents i
Chapter 1
Install the Isysnet Mount the Adapter and I/O Base ................................................................ 1-1
DeviceNet Adapters Set the Node Address ................................................................................ 1-1
Wire the DeviceNet Adapters ..................................................................... 1-2
PSSCDM12A ....................................................................................... 1-2
PSSCDM18PA ..................................................................................... 1-2
DeviceNet Auxiliary Power ................................................................... 1-2
Chapter Summary and What’s Next ........................................................... 1-2
Chapter 2
What Is the Isysnet Use the Adapter ......................................................................................... 2-1
DeviceNet Adapter? Set Subnet/Backplane Baudrate .......................................................... 2-2
Set Subnet/Backplane I/O Module Addresses ..................................... 2-2
Configure the Subnet I/O ..................................................................... 2-2
Configure the Primary DeviceNet Network .......................................... 2-2
Remove and Reinsert Modules on the Backplane ............................... 2-2
Understand the DeviceNet Network and Subnet ........................................ 2-3
DeviceNet Network .............................................................................. 2-3
Backplane/Subnet Network ................................................................. 2-3
Adapter Features ....................................................................................... 2-4
Communicate Through the Adapter ........................................................... 2-8
Map the Data ....................................................................................... 2-8
Overview of the Communication Process ............................................ 2-8
Image Table Mapping ........................................................................... 2-9
Communicate With I/O Modules ............................................................... 2-10
Use Diagnostic Tables .............................................................................. 2-11
Chapter Summary and What’s Next ......................................................... 2-12
Chapter 3
Use Auto Start Mode Why Use Auto Start Mode? ........................................................................ 3-2
What Does Auto Start Mode Do? ........................................................ 3-2
How Is I/O Data Mapped Using Auto Start Mode? .............................. 3-2
Requirement To Using Auto Start Mode .............................................. 3-2
Install the I/O Module ................................................................................. 3-3
Remove the Module From the Mounting Base ..................................... 3-3
Use RSNetWorx for DeviceNet .................................................................. 3-4
Begin Auto Start Mode ............................................................................... 3-5
Use Custom Configuration ......................................................................... 3-6
Chapter Summary and What’s Next ........................................................... 3-6

Publication PSS-UM001A-EN-P – June 2005
Chapter 4
Configure the DeviceNet Configuration Overview .............................................................................. 4-1
Scanner Subnet Add the Scanner To Your Network ....................................................... 4-1
Add I/O Modules To Your Network ....................................................... 4-1
Set the Scanner’s Parameters ............................................................. 4-2
Go On Line .......................................................................................... 4-6
Chapter Summary and What’s Next ........................................................... 4-6
Chapter 5
Add the Isysnet DeviceNet Configuration Overview .............................................................................. 5-1
Adapter to the DeviceNet Add the Adapter to Your Network ......................................................... 5-1
Scanner’s Scanlist Set the Adapter’s Parameters .............................................................. 5-2
Go On Line .......................................................................................... 5-4
Chapter Summary ...................................................................................... 5-4
Chapter 6
Troubleshoot the Isysnet Use the Status Indicators ........................................................................... 6-1
DeviceNet Adapter Guidelines for Using Your Adapter .............................................................. 6-2
Chapter Summary ...................................................................................... 6-2
Appendix A
Specifications
Appendix B
Default Data Maps PSSN8 Sink Input Module .......................................................................... B-1
PSSP8 Source Input Module ..................................................................... B-1
PSST8 Electronically Protected Output Module ......................................... B-2
PSSTR4 Relay Sink/Source Output Module .............................................. B-2
PSSNAC Analog Current Input Module ...................................................... B-2
PSSNAV Analog Input Module ................................................................... B-3
PSSTAC Analog Current Output Module .................................................... B-3
PSSTAV Analog Output Module ................................................................. B-4
PSSS23A ASCII Module ............................................................................ B-4
PSSV32A 32 Point Valve Driver Module..................................................... B-4
ii Table of Contents

Publication PSS-UM001A-EN-P – June 2005
Chapter 1
Inches
(mm)
Adapter
2.0
(50)
2.0
(50)
1.9
(47.2)
4.02
(102)
1.81
(46)
4.32
(109.8)
5.39
(137.0)
Drill and Tap
for M4 Screw
2.39
(60.7)
3.02
(76.6)
3.13
(79.4)
5.98*
(151.9)
0.87
(22)
Drill and Tap
for M6 Screw
Install the Isysnet DeviceNet Adapters
This chapter describes how to install and wire your adapter.
See the Following Sections: Page:
Mount the Adapter and I/O Base 1-1
Set the Node Address 1-1
Wire the DeviceNet Adapters 1-2
Chapter Summary and What’s Next 1-2
Mount the Adapter and I/O Base
To mount the Isysnet adapter on a wall or panel, use the screw
holes provided in the adapter.
A mounting illustration for the Isysnet adapter with I/O bases is
shown below.
Install the Mounting Base as Follows:
1. Lay out the required points as shown in the drilling dimension
drawing.
2. Drill the necessary holes for #8 (M4) machine or self-tapping
screws.
3. Mount the adapter and I/O bases using #8 (M4) screws.
4. Ground the system using the ground lug connection in the I/O
base. (The ground lug connection is also a mounting hole.)
Set the Node Address
Valid node addresses are 00 through 63.
Set the node address using either the rotary switches, RSNetWorx
for DeviceNet™, DeviceNetManager™, or another software
configuration tool. Setting the switches at any number from 64
through 99 lets the software have address control.
Each module is shipped with the switches set for node address 63.
Remove the caps on the front of the module to access the switches
(refer to the X10 and X1 on the front of the module). The two
switches are:
• X10 (most significant digit) – left side of module
• X1 (least significant digit) – right side of module
This example shows the
node address set at 63.
* Depending on the type and number of manifolds, this dimension
may vary. Refer to Catalog 0600P-# for additional information.
To reset the node address, use a small blade screwdriver to rotate
the switches. Line up the small notch on the switch with the number
setting you wish to use and then cycle power.
The rotary switches are read periodically. If the switches have been
changed since the last time they were read and they no longer
match the on line address, a minor fault will occur, which is indicated
by a flashing red Adapter Status LED. Settings of 64 through 99
cause the module to use the last valid node address stored
internally. For example, the last setting internally was 40. If a
change is made to 68, and then you power up, the address will
default to 40.
The module is equipped with AutoBaud detect. AutoBaud lets the
module read the settings already in use on your DeviceNet network
and automatically adjusts to follow those settings.

Publication PSS-UM001A-EN-P – June 2005
1-2 Install the Isysnet DeviceNet Adapters
Wire the DeviceNet Adapters
Following are wiring instructions for the DeviceNet Adapters.
Male In Connector
PSSCDM12A
Female Out Connector
(view into connector)
Pin 1 - Drain
Pin 2 - +V
Pin 3 - -V
Pin 4 - CAN_High
Pin 5 - CAN_Low
Male In Connector
PSSCDM18PA
Female Out Connector
(view into connector)
Pin 1 - Drain
Pin 2 - +V
Pin 3 - -V
Pin 4 - CAN_High
Pin 5 - CAN_Low
Male In Connector
DeviceNet Auxiliary Power
(view into connector)
Pin 1 - User Power +
Pin 2 - Adapter Power +
Pin 3 - Adapter Power -
Pin 4 - User Power -
Chapter Summary and What’s Next
In this chapter, you learned how to install and wire
your DeviceNet adapter. Move to Chapter 2 to learn
about the Isysnet DeviceNet adapters.
Make sure all connectors and caps are securely tightened to
properly seal the connections against leaks and maintain
IP67 requirements.
!
ATTENTION

Publication PSS-UM001A-EN-P – June 2005
Chapter 2
What Is the Isysnet DeviceNet Adapter?
This chapter describes the Isysnet I/O DeviceNet adapter,
including descriptions of the adapter’s features and functionality.
See the Following Sections: Page:
Use the Adapter 2-1
Understand the DeviceNet Network
and Subnet 2-3
Adapter Features 2-4
Communicate Through the Adapter 2-8
Communicate With I/O Modules 2-10
Use Diagnostic Tables 2-11
Chapter Summary and What’s Next 2-12
Use the Adapter
The adapter resides on the primary DeviceNet network and the
Subnet simultaneously.
IMPORTANT
The PointBus maintains all DeviceNet network protocol, but
also offers configuration capabilities.
The adapter interfaces between DeviceNet devices and Isysnet I/O
modules. The graphic below shows the adapter on the DeviceNet
network and PointBus.
0
1
2
3
02
13
46
57
4
5
6
7
MOD
NET
PSST8M12A
24V dc Out
0
1
2
3
02
13
46
57
4
5
6
7
MOD
NET
PSSN8M12A
24V dc In
Mod
PSSV32A
Net
Fault
PSSCDM12A
Adapter
Status
DeviceNet
Status
PointBus
Status
System
Power
Adapter
Power
DeviceNet Out
DeviceNet In
PWR
x1
6
0
82
4
x10
6
0
82
4
Computer with PLC
Programming Software
ControlNet Network
ControlLogix
Chassis 1784-PCD
PCMCIA
Card
PSSCDM12A
Adapter
DeviceNet Network
Computer with
RSNetWorx for
DeviceNet Software
Isysnet I/O Modules
See page 2-8 for an
explanation of the
number sequence.
After you have installed your adapter into a Isysnet I/O system, you
must perform the following tasks:
1. Set Subnet/Backplane Baudrate
2. Set Subnet/Backplane I/O Module Addresses
3. Configure the Subnet I/O
4. Configure the Primary DeviceNet Network
The steps mentioned above are explained briefly here, and then in
greater detail throughout this manual. You must complete the steps
for the adapter to work with DeviceNet masters (e.g. Rockwell
Automation 1756-DNB) on the primary network and Subnet modules.

Publication PSS-UM001A-EN-P – June 2005
2-2 What is the Isysnet DeviceNet Adapter?
1. Set Subnet/Backplane Baudrate
The adapter and Subnet/Backplane modules must use the same
baudrate to communicate with each other. Use one or both of the
following to set a Subnet/Backplane baudrate.
• Enable or disable the Backplane Autobaud feature for Isysnet
I/O modules. Isysnet I/O modules have Autobaud enabled
as the default - See page 2-5.
• Set the adapter baudrate for the Subnet. The default for the
PSSCDM12A and PSSCDM18PA is 1Mbaud.
You set the backplane baudrate for the PSSCDM12A and
PSSCDM18PA.
2. Set Subnet/Backplane I/O Module Addresses
Once the adapter and Isysnet I/O modules are communicating at
the same rate on the backplane, you must make sure all modules
use a valid MACID.
Set the Auto Address feature for Isysnet I/O modules - See
page 2-5.
3. Configure the Subnet I/O
In the first two steps, you set a consistent communication rate and
made sure each module uses valid addresses for communication.
Next you must configure the PointBus (e.g., set scan list).
You can configure the PointBus using one of two methods:
• Auto Start Mode (ASM) or
• Manually For more information on configuring the PointBus,
see Chapter 3 for ASM or see Chapter 4 for manual
configuration.
4. Configure the Primary DeviceNet Network
Finally, you must configure the adapter for communication with a
master (e.g., Rockwell Automation 1756-DNB).
For more information on configuring the DeviceNet network, see
Chapter 5, Add the Isysnet DeviceNet Adapter to the DeviceNet
Scanner’s Scanlist.
You must understand all of the adapter’s features to effectively use
it in your Isysnet I/O system. Keep these four steps in mind as you
read this manual:
1. Set Subnet/Backplane Baudrate
2. Set Subnet/Backplane I/O Module Addresses
3. Configure the Subnet I/O
4. Configure the Primary DeviceNet Network
Remove and Reinsert Modules on the Backplane
Removal and Insertion Under Power (RIUP) is not recommended in
a Isysnet System because of the following reasons.
• Removing a module breaks the IP67 seal.
• Removing a module breaks the backplane bus. Modules to
the right of the removed module will be ‘lost’ to the adapter.
Also, the terminating resistor will be removed, causing
system uncertainty.
• Inserting a module under power may cause the adjacent
module to reset due to the addition of a large capacitive load
on the power bus.
IMPORTANT
If the module is removed while it is under power, all the modules
to the right of the removed module will disconnect from the
PointBus and field power until the module is reinstalled.
If you must remove and reinsert modules, we recommend the following:
• Do not move I/O modules to different locations on the
mounting base after they have been installed and configured.
• If adjacent modules (i.e., 2 or more) are removed from the
backplane, replace all of them before attempting to operate
the Isysnet I/O system. Input data will hold last state until all
previously removed modules are replaced.
–If adjacent modules are removed and all but one is
returned, the adapter cannot verify the location of the
returned modules. For example, if modules are removed
from nodes 3 and 4 and only the module from node 4 is
returned, the adapter cannot verify the location. In this
case, the adapter alerts you via a flashing red PointBus
status LED that it cannot verify the presence of modules
in the affected locations. I/O data will not be exchanged
with this node until both modules have been reinserted.
–If modules of different types are removed and returned
to the wrong locations, the adapter identifies the returned
modules and alerts you (via RSNetWorx for DeviceNet)
that the error has occurred and must be corrected.
–If modules of the same type are removed and returned to
the wrong locations, the adapter identifies the returned
modules, updates their MACIDs, and continues operation.
IMPORTANT
The removal and return scenario exists whether the system is
under power or not. If the system is under power, the scenario
arises immediately. If the system is not under power, the
scenario arises in the next power cycle.Also, the example
above shows removal of two adjacent modules. The scenario
described exists anytime 2 or more adjacent modules are
removed and all are not returned.
IMPORTANT
Care must be taken when replacing backplane I/O modules.
Each I/O module stores its configuration parameters in internal
non-volatile memory.You must either enable ADR for all modules
or manually configure each module in a non-manufacturing
environment when the module is being replaced or placed on
the network for the first time. Failure to do so could result in
inadvertent control attributed to different configuration settings.

Publication PSS-UM001A-EN-P – June 2005
What is the Isysnet DeviceNet Adapter? 2-3
Understand the DeviceNet
Network and Subnet
DeviceNet Network
Your adapter serves as a slave to DeviceNet masters. The adapter
receives data from, and returns data to, the master through the
following I/O connections:
• Change of State (COS)
• Cyclic
• Polled
• Strobe
Backplane/Subnet Network
On the Backplane/Subnet, your adapter acts as a scanner and is
the master of the Subnet modules. The adapter performs the
following functions:
• Exchanges I/O data with devices on the Backplane/Subnet
•
Collects I/O data from the Backplane/Subnet and sends it to
devices on the DeviceNet network (e.g., scanners or controllers)
• Supplies power to the backplane I/O modules (See Appendix
A for power supply rules regarding I/O modules power
requirements.)
Data Collection
The adapter collects I/O data from up to 63 modules via the
Backplane/Subnet. The I/O modules appear on the primary
DeviceNet network as a single node, though, and require only one
DeviceNet node address.
IMPORTANT
If Automatic Device Replacement (ADR) is enabled on the
adapter, you can only connect up to 62 modules via the Subnet.
For more information on ADR, see page 2-6.
Module Power
The adapter supplies 5V logic power to Isysnet I/O modules by
converting 24VDC field power to PointBus 5V power.
You can connect up to 63 I/O modules to each adapter and you can
power the backplane I/O modules from the adapter (with a maximum
of 10A of field power). You may use the integrated, isolated 24VDC
expansion power unit (PSSSE24A) to power additional I/O modules,
as shown below.
For more information on the PSSSE24A expansion power unit, see
the Isysnet I/O 24VDC Expansion Power Supply Installation
Instructions, publication E105P.
0
1
2
3
02
13
46
57
4
5
6
7
MOD
NET
PSST8M12A
24V dc Out
0
1
2
3
02
13
46
57
4
5
6
7
MOD
NET
PSSN8M12A
24V dc In
0
1
2
3
02
13
46
57
4
5
6
7
MOD
NET
PSST8M12A
24V dc Out
0
1
2
3
02
13
46
57
4
5
6
7
MOD
NET
PSSN8M12A
24V dc In
0
1
2
3
02
13
46
57
4
5
6
7
MOD
NET
PSSN8M12A
24V dc In
Mod
PSSV32A
Net
Fault
0
1
2
3
02
13
46
57
4
5
6
7
MOD
NET
PSST8M12A
24V dc Out
0
1
2
3
02
13
46
57
4
5
6
7
MOD
NET
PSST8M12A
24V dc Out
0
1
2
3
02
13
46
57
4
5
6
7
MOD
NET
PSSN8M12A
24V dc In
0
1
2
3
02
13
46
57
4
5
6
7
MOD
NET
PSST8M12A
24V dc Out
0
1
2
3
02
13
46
57
4
5
6
7
MOD
NET
PSSN8M12A
24V dc In
0
1
2
3
02
13
46
57
4
5
6
7
MOD
NET
PSST8M12A
24V dc Out
0
1
2
3
02
13
46
57
4
5
6
7
MOD
NET
PSSN8M12A
24V dc In
PSSSE24A
24V dc Power Supply
SYSTEM
POWER
P
O
W
E
R
A
U
X
FIELD
POWER
PSSCDM12A
Adapter
Status
DeviceNet
Status
PointBus
Status
System
Power
Adapter
Power
DeviceNetOut
DeviceNetIn
PWR
x1
6
0
82
4
x10
6
0
82
4
PSSCDM12A
Adapter
PSSSE24A
Expansion
Power Unit Isysnet I/O
Modules
Isysnet I/O
Modules
PSSV32A
32 Point
Valve Driver Valves

Publication PSS-UM001A-EN-P – June 2005
2-4 What is the Isysnet DeviceNet Adapter?
Adapter Features
Your adapter uses the following features on both the DeviceNet
network and the PointBus:
• Self-Test
• Field Upgradable Firmware
• Fully Configurable Software
• Connections
• Baudrates
Self-Test
When power is applied to the adapter, the adapter performs a self-
test. The adapter tests various internal and programmatic memories
and checks the status indicators (LEDs).
Field Upgradable Firmware
You can update the adapter’s firmware with the ControlFlash Utility
software. This feature lets you always use the most current firmware.
Fully Software Configurable
The adapter is fully software configurable using RSNetWorx for
DeviceNet. You must configure the adapter to be used with a
DeviceNet master (e.g. 1756-DNB) and separately to be used with
Subnet devices.
For more information on how to configure your adapter to use with
a DeviceNet master, see Chapter 5, Add the Isysnet DeviceNet
Adapter to the DeviceNet Scanner’s Scanlist.
For more information on how to configure your adapter to use with
Subnet modules, see Chapter 4, Configure the DeviceNet Scanner
Subnet.
Connections
Your adapter supports the following connections on both the primary
DeviceNet network and Subnet:
• I/O connections:
–Polled
–Strobe
–Cyclic
–COS
• Explicit connections
You can use I/O mapping to determine the data contained in each
connection.
The adapter supports Master/Slave connection types on the
DeviceNet network. On the Subnet, the adapter functions as a
scanner device, exchanging data with I/O modules.
Baudrates
Choose baudrates for the adapter in the RSNetWorx for DeviceNet
software. The adapter supports these rates:
• 125Kbaud
• 250Kbaud
• 500Kbaud
• Autobaud – The adapter detects the primary DeviceNet
network baudrate and automatically sets its own baudrate to
match the network.
• For the PSSCDM12A and PSSCDM18PA, the PointBus can
be configured to operate at 1Mbaud (1000Kbaud).
Auto Start Mode
Auto Start Mode lets you easily get your adapter installed and
operating. In this mode, the adapter’s configurable features operate
as they were most recently configured. For example, if Autobaud
on DeviceNet was enabled in the adapter’s last configuration, it will
be enabled when Auto Start Mode is used.
For a more detailed explanation of how to use Auto Start Mode, see
Chapter 3.
Auto Catalog Replace
Auto Catalog Replace corrects errors that might occur when
backplane modules of the same type are removed and replaced in
the wrong location. If modules of the same type are removed and
returned to the wrong locations, the adapter identifies the returned
modules, updates their MAC IDs, and continues operation.
IMPORTANT
If modules of different types are removed and returned to the
wrong locations, the adapter identifies the returned modules
and alerts you (via RSNetWorx for DeviceNet, the Node Status
Table, and the Faulted Node Table) that the error has occurred
and must be corrected.
Backplane (PSSCDM12A and PSSCDM18PA) Baudrate
EDS parameter Backplane Baudrate is accessible from the primary
DeviceNet and sets a specific baudrate for all backplane I/O modules.
Set this parameter in RSNetWorx for DeviceNet to one of the
following baudrates:
• 125 Kbaud
• 250 Kbaud
• 500 Kbaud
• 1 Mbaud (available for both Isysnet DeviceNet adapters)
When you download this parameter, the adapter sends a command
to reset all present I/O modules on the backplane to the new
baudrate. If additional modules are connected to the adapter, you
must download the Backplane/Subnet Baudrate to make sure the
new modules use the same rate as the others.

Publication PSS-UM001A-EN-P – June 2005
What is the Isysnet DeviceNet Adapter? 2-5
The baudrate may not take effect until power is recycled or the I/O
modules are reset.
IMPORTANT
Changes to the Backplane Baudrate parameter only take effect
if they are downloaded on an individual basis. (For example, if
you change the Backplane Baudrate and download the changes
with additional changes to other features, the Backplane
Baudrate remains at the previous setting.)
Also, this parameter should be set to ‘Do Nothing’ when you
download all parameters, or when Automatic Device
Replacement is enabled for the adapter.
If you want to set an I/O module to use a specific baudrate
(i.e., 125, 250, 500), you must first disable Backplane Autobaud
for that module.
Backplane Baudrate performs the following functions:
• Sets the adapter’s Subnet baudrate
• Sends a message to all connected backplane I/O modules.
If an I/O module is set to autobaud, it receives the message,
but ignores the new baudrate.
Backplane Autobaud
The adapter itself never autobauds on the Subnet. Backplane
Autobaud automatically enables or disables Autobaud for all I/O
modules currently attached to the backplane. The adapter does not
set a specific rate though (as with Backplane Baudrate).
If you enable Backplane Autobaud in the adapter or the EDS
parameter access that you set from the primary DeviceNet, the
adapter only enables the Autobaud in all backplane I/O modules.
When the modules listen to communications on the DeviceNet
network, they detect the rate of communication and automatically
set their own baudrates to match the network rate.
The module does not automatically detect the backplane baudrate
until power is cycled or the module is reset.
TIP
Autobaud, when enabled, is useful if you swap Isysnet I/O modules
between networks that are operating at different baudrates.
Enable Backplane Baudrate in RSNetWorx for DeviceNet.
IMPORTANT
Changes to the Backplane Autobaud parameter only take effect
if they are downloaded on an individual basis. (For example, if
you enable the Backplane Autobaud setting and download the
change with additional changes to other features, the Backplane
Baudrate remains disabled.)
This parameter should be set to ‘Do Nothing’ when you
download all parameters, or when Automatic Device
Replacement is enabled for the adapter.
If you want to set an I/O module to use a specific baudrate (i.e.,
125, 250, 500), you must first disable Autobaud for that module.
Auto Address
The EDS parameter Auto Address is available from the primary
DeviceNet and lets the user sequentially order the node addresses
of backplane I/O modules. This parameter is not a mode, but occurs
on a single occurrence only. The node address selected is assigned
to the module closest to the adapter. The next closest module is
assigned the next numerically higher value. The numbering pattern
continues for all connected backplane I/O modules.
Enable this parameter in the RSNetWorx for DeviceNet software.
IMPORTANT
Changes to the Auto Address parameter only take effect if they
are downloaded on an individual basis. (For example, if you
enable the Auto Address and download the changes with
additional changes to other features, the node addresses of
the I/O modules remains disabled.)
This parameter should be set to ‘Do Nothing’ when you
download all parameters, or when Automatic Device
Replacement is enabled for the adapter.
Physical List Acquire Status
The adapter maintains a physical list that indicates the order of the
node addresses of all Isysnet I/O modules present on the backplane.
Physical List Acquire Status shows the status of this physical list
acquire process.
The adapter requires that each backplane I/O module has a MACID
greater than that of its neighbor to its immediate left. The list is
created when power is applied to the adapter and each time a
module is inserted on the backplane.
The valid values are:
• Idle
• Busy
• Auto Start Mode

Publication PSS-UM001A-EN-P – June 2005
2-6 What is the Isysnet DeviceNet Adapter?
Cycling Node Status
Using the Cycling Node Status parameter, you can easily determine
the status of any Isysnet I/O modules with which the adapter is
experiencing problems. A corresponding text string appears,
including the MAC ID, and a description of the status code reported
in the Node Status Table. For more information on the Node Status
Table, see page 2-11.
For the connection sizes mentioned below, the I/O connection sizes
on DeviceNet are dependent on the scanlist configuration on the
backplane.
Poll/COS Connection Consume Size
Poll/COS Connection Consume Size shows the size (number of
data bytes) consumed by the poll/COS (Instance 2) I/O connection
on the primary DeviceNet.
Poll Connection Produce Size
Poll Connection Produce Size shows the size (number of data
bytes) produced by the polled (Instance 2) I/O connection on the
primary DeviceNet.
COS/Cyclic Connection Produce Size
COS Produce Size shows the size (number of data bytes) produced
by the Change of State I/O connection on the primary DeviceNet.
Strobe Connection Produce Size
The Strobe Produce Size shows the size (number of data bytes)
produced by the Strobe I/O connection on the primary DeviceNet.
Cycling I/O Mapping
Cycling I/O Mapping is an EDS parameter, accessible from the
primary DeviceNet, that shows you how data is mapped in the
adapter’s scanlist. The data, as shown below, is listed in order of
active modules in the scanlist.
The data format is NN OBBB:b-BBB:b,IDBBB:b-BBB:b, where:
• NN = node number
• O or I = data type (output or input)
• BBB = byte number
• b = bit number
• D = DeviceNet connection (C [COS/cyclic], S [strobe], or
P [poll])
IMPORTANT
If an I/O module’s data has multiple mappings, you must use
RSNetWorx for DeviceNet to browse to the backplane to view
the mappings.
Automatic Device Replacement
With Automatic Device Replacement (ADR), the adapter
automatically configures a new replacement module.
IMPORTANT
The replacement module must match the original module (i.e.,
same vendor I.D., device type, product code, major and minor
revision) for ADR to work. The parameters that must match
are those selected in the electronic keying portion of the scanlist.
You determine the level of electronic keying.
The backplane configuration parameters (e.g., Auto Address)
should be set to ‘Do Nothing’.

Publication PSS-UM001A-EN-P – June 2005
What is the Isysnet DeviceNet Adapter? 2-7
The adapter is capable of holding approximately 64K of
configuration data for Isysnet I/O modules connected to it. The
adapter sends configuration data to an I/O module each time
connections are created with that module (i.e., power cycle or
module insertion to backplane).
You can exchange an old module for a new one if the following
conditions are met:
• ADR is enabled in the adapter.
• The new module matches the old one (i.e., electronic keying).
• The new module is inserted in the proper location (only for
modules using the backplane).
If the conditions listed above are met, the new module’s MACID is
changed to the appropriate value, if necessary, and the configuration
information is subsequently downloaded to the module.
Physical Ordering
When power is applied, or when an I/O module is inserted, the
adapter detects the backplane I/O modules’ order, based on MACID.
With Physical Ordering, the adapter detects if any Isysnet I/O
modules connected to it are out of order. If this condition is detected,
the adapter changes the MACIDs of any new modules.
IMPORTANT
If any backplane I/O modules are missing when power is
applied, none of the backplane modules enter run mode.
The adapter’s MACID is always 0 on Subnet. The MACIDs of each
attached backplane I/O module must be sequentially ordered (i.e.,
each module’s MACID is greater than the left adjacent module).
Interscan Delay (ISD)
Interscan Delay is the time delay between consecutive I/O scans of
polled devices. The default setting is 10ms. The ISD=4ms for Auto
Start Mode. You can change this parameter in the Module window
of the scanner in the RSNetWorx for DeviceNet software.
The scanner uses this period of time to perform non-time-critical
communications on the DeviceNet network, such as communicating
with RSNetWorx for DeviceNet software. Setting this parameter to
a very low value increases the latency for non-time-critical scanner
operations, including the time required to respond to RSLinx software
and configuration functions. Setting this parameter to a very large
value reduces the freshness of the I/O data being collected by the
scanner and is not advisable.
Foreground to Background Poll Ratio
Foreground to Background Poll Ratio is the ratio of foreground to
background polls. You can set this parameter in the Module window
of the scanner in RSNetWorx for DeviceNet software.
Devices can be polled on every I/O scan (foreground), or they can
be polled less frequently (background). Whether a particular device
will be polled in the foreground or in the background is determined
by its Poll Rate parameter on the Edit I/O Parameters dialog box,
which is accessed from the Scanlist property page.
The poll ratio sets the frequency of poll I/O messages to a device in
relation to the number of I/O scans. For example, if the poll ratio is
set to 5, the scanner will poll the selected devices once every six I/
O scans. We recommend that you use a poll ratio of 1.
Expected Packet Rate
Expected Packet Rate is the rate at which the packets will be
expected to be received by the scanner. You set this parameter in
the Module window (from the Advanced button) of the scanner in
RSNetWorx for DeviceNet software.
IMPORTANT
We recommend that you do not change the Expected Packet
Rate unless you are instructed to do so by a Rockwell
Automation technical support representative.
Transmit Retries
Transmit Retries are the maximum number of times that the scanner
will attempt to send an I/O message to a device before it times out
and generates an error message. You set this parameter in the
Module window (from the Advanced button) of the scanner in
RSNetWorx for DeviceNet software.
IMPORTANT
We recommend that you do not change the Transmit Retries
unless you are instructed to do so by a Rockwell Automation
technical support representative.

Publication PSS-UM001A-EN-P – June 2005
2-8 What is the Isysnet DeviceNet Adapter?
Communicate Through the Adapter
As described previously in this manual, the adapter resides on the
DeviceNet network and the PointBus simultaneously. The adapter’s
functions are as follows:
• DeviceNet – adapter serves as a slave device that exchanges
I/O data with another DeviceNet scanner device (e.g., 1771-
SDN) via DeviceNet messages
• PointBus – adapter serves as master for up to 63 I/O modules,
using DeviceNet messages to consume from or produce
data to each module.
IMPORTANT
If Automatic Device Replacement (ADR) is enabled on the
adapter, you can only connect up to 62 modules via the PointBus.
For more information on ADR, see page 2-6.
Map the Data
Your adapter must store data temporarily before transferring it
between devices. You must map data to your adapter’s memory
before transferring it.
For a detailed description of the mapping process, see page 2-9.
Overview of the Communication Process
In a typical configuration, the adapter acts as an interface between
a DeviceNet scanner (e.g., Rockwell Automation 1756-DNB) and
Isysnet I/O modules. The following example graphic shows
information transferred from a 1756-DNB to Isysnet I/O modules.
IMPORTANT
Although information is exchanged between the Logix5555
and 1756-DNB, this diagram (nor this chapter) is not designed
to explain such an exchange.
Four data transfers are shown in the diagram, including:
1. Scanner to adapter
2. Adapter to I/O modules
3. I/O modules to adapter
4. Adapter to scanner
Because the adapter simultaneously resides on the DeviceNet
network and on PointBus, it serves as a slave to the processor (i.e.,
steps 1 and 4) and a master to the I/O modules (i.e., steps 2 and 3).
The four data transfers are not necessarily sequential. Transfers 2
and 3 typically occur more frequently than transfers 1 and 4.
The computers and PCMCIA card shown in the diagram are required
to configure the processor, adapter, and I/O modules.
Although the PCMCIA card is used in this example, you can use
other communications cards, such as PCID and KFD cards.
Key Points About Scanner to Adapter Transfer (Step 1)
1. Scanner initiates transfer
2. Scanner uses DeviceNet I/O messaging to write data to adapter.
Data may contain:
• device output data
• configuration data
Key Points About Adapter to Output Module Transfer (Step 2)
1. Adapter initiates transfer
2. Adapter produces data for I/O module to consume.
Data may contain:
• device output data
• configuration data
Key Points About Input Module to Adapter Transfer (Step 3)
Adapter consumes data I/O module has produced.
Data may contain:
• device input data
• status data
Key Points About Adapter to Scanner Transfer (Step 4)
SDN consumes I/O data produced by adapter.
Data may contain:
• device input data
• status data
0
1
2
3
02
13
46
57
4
5
6
7
MOD
NET
PSST8M12A
24V dc Out
0
1
2
3
02
13
46
57
4
5
6
7
MOD
NET
PSSN8M12A
24V dc In
Mod
PSSV32A
Net
Fault
PSSCDM12A
Adapter
Status
DeviceNet
Status
PointBus
Status
System
Power
Adapter
Power
DeviceNet Out
DeviceNet In
PWR
x1
6
0
82
4
x10
6
0
82
4
Computer with PLC
Programming Software
ControlNet Network
Logix5555 Controller
The Logix5555 controller sits in the backplane.
The 1756-DNB contained in the controller
communicates with the Isysnet adapter.
1784-PCD
PCMCIA Card
PSSCDM12A
Adapter
DeviceNet Network
Computer with
RSNetWorx for
DeviceNet
Software
Isysnet I/O Modules

Publication PSS-UM001A-EN-P – June 2005
DeviceNet
Scanner
DeviceNet
Subnet
DeviceNet
DeviceNet Poll Buffer
DeviceNet Strobe Buffer
DeviceNet COS/CYC Buffer
248 bytes
+ 2 bytes status
248 bytes
+ 2 bytes status
Isysnet DeviceNet Adapter OUTPUT DATAINPUT DATA
Poll OR COS (inst 2)
248 + 2 bytes
6 + 2 bytes
I/O MAPPING
Subnet Modules
What is the Isysnet DeviceNet Adapter? 2-9
Image Table Mapping
Your adapter receives data from:
•master devices (e.g., scanners) - output data is then passed to
Isysnet I/O modules
•input modules - input data is passed to the scanner
The adapter must map the data it receives to its internal memory
before passing it to the appropriate device. The I/O map for a
module is divided into:
•read bytes - input and status bytes
•write bytes - output and configuration bytes
The data is mapped by 3 buffers for input data (each representing
an I/O connection on the primary DeviceNet) and 1 buffer for output
data (representing data sent for Poll or COS connections on the
primary DeviceNet).
The number of read bytes or write bytes can be 2 or more. The
length of each I/O module’s read bytes and write bytes vary in size
depending on module complexity. Each I/O module supports at
least 1 input byte or 1 output byte. Status and configuration are
optional, depending on the module.
The following graphic shows how the adapter maps information.

Publication PSS-UM001A-EN-P – June 2005
2-10 What is the Isysnet DeviceNet Adapter?
Communicate With I/O Modules
The adapter module supports multiple communication choices.
These choices all use the default I/O structure previously described.
The adapter’s master (e.g., 1756-DNB) makes the actual
communication choice. The choices are:
• Polled – Adapter sends data in response to received data.
•
Strobe – Adapter sends data in response to the strobe
command. The single bit allocated to the adapter in the strobe
message is not used. If the configured size of the input data
(sent from the adapter) is greater than 8 bytes, the strobe
connection establishment will fail. In this case, the input size
must be reconfigured to 8 bytes or less (only 6 bytes are I/O
data because the first 2 bytes are the status word).
• Change of State – Adapter sends data based on detection
of any changed value within the input data. Data is
independently received based on change of state from the
sender. Data in both directions can be acknowledged or
unacknowledged depending on the run time configuration of
the system.
• Cyclic – Adapter sends data cyclically based on a configured
time value. Data is independently received cyclically from
the sender. Data in both directions can be acknowledged or
unacknowledged depending on the run time configuration of
the system.
The adapter uses these messages to solicit data from or deliver
data to each device. Data received from the devices (i.e., input
data) is organized by the adapter and retransmitted to the master.
Data received from the master (i.e., output data) is organized in the
adapter and sent on to the I/O modules.
Run - The adapter maps output
data to each module on PointBus.
Idle - Output data with zero length
is sent to I/O modules.
Device Failure - One or more of the
devices in the scanlist has failed to
communicate with the adapter.
Communications Failure - The
adapter has entered the BUSOFF
state on the Subnet. Another
Subnet device is configured with
the wrong baud rate.
Duplicate Node Address Failure -
There is another node with the
same address (0) as the scanner
on the Subnet and the adapter has
failed its Dup_MAC_ID test.
See the I/O Status Word Bit Definitions table for definitions of the first
2 bytes of each I/O message produced by the adapter on DeviceNet.
I/O Status Word Bit Definitions
Byte Bit Operating Mode Operating Mode Description
00 0 = Run mode
1 = Idle mode
01 1 = Device failure
(at least one
device failed)
02 1 = Communication
failure
03 1 = Duplicate node
address failure
04 Reserved
05 Reserved
06 Reserved
07 Reserved
10 Reserved
11 Reserved
12 Reserved
13 Reserved
14 Reserved
15 Reserved
16 Reserved
17 Reserved
The first 2 bytes of output data on the DeviceNet network that are
sent to the adapter are reserved as a command word. No bits have
been defined.