GE Fanuc Automation
Programmable Control Products
Series 90®-30
Programmable Controller
DeviceNet™ Modules
GFK-2196 November 2002
Warnings, Cautions, and Notes
as Used in this Publication
Warning
Warning notices are used in this publication to emphasize that hazardous voltages,
currents, temperatures, or other conditions that could cause personal injury exist in this
equipment or may be associated with its use.
In situations where inattention could cause either personal injury or damage to
equipment, a Warning notice is used.
Caution
Caution notices are used where equipment might be damaged if care is not taken.
Note
Notes merely call attention to information that is especially significant to understanding and
operating the equipment.
GFL-002
This document is based on information available at the time of its publication. While efforts
have been made to be accurate, the information contained herein does not purport to cover all
details or variations in hardware or software, nor to provide for every possible contingency in
connection with installation, operation, or maintenance. Features may be described herein
which are not present in all hardware and software systems. GE Fanuc Automation assumes no
obligation of notice to holders of this document with respect to changes subsequently made.
GE Fanuc Automation makes no representation or warranty, expressed, implied, or statutory
with respect to, and assumes no responsibility for the accuracy, completeness, sufficiency, or
usefulness of the information contained herein. No warranties of merchantability or fitness for
purpose shall apply.
The following are trademarks of GE Fanuc Automation North America, Inc.
Alarm Master Genius PowerTRAC Series Six
CIMPLICITY Helpmate ProLoop Series Three
CIMPLICITY 90–ADS Logicmaster PROMACRO VersaMax
CIMSTAR Modelmaster Series Five VersaPoint
Field Control Motion Mate Series 90 VersaPro
GEnet PowerMotion Series One VuMaster
Workmaster
©Copyright 2002 GE Fanuc Automation North America, Inc.
All Rights Reserved.
Contents
Chapter 1
Chapter 2
Chapter 3
DeviceNet Modules for the Series 90-30 PLC ...................................................1-1
Finding Information in this Book...................................................................................... 1-1
DeviceNet Modules for the Series 90-30 PLC.................................................................. 1-2
Series 90-30 DeviceNet Master Module........................................................................... 1-3
Series 90-30 DeviceNet Slave Module .............................................................................1-5
The DeviceNet Network ................................................................................................... 1-7
DeviceNet Communications for Series 90-30 DeviceNet Modules.................................. 1-8
Installation ...........................................................................................................2-1
Power Supplies..................................................................................................................2-2
DeviceNet Cable for the Series 90-30 Modules................................................................ 2-3
Grounding ......................................................................................................................... 2-6
Installing the DeviceNet Module in the PLC Rack........................................................... 2-7
Module LEDs.................................................................................................................... 2-8
RS-232 Serial Port ............................................................................................................ 2-9
PLC Configuration for the DeviceNet Master.................................................. 3-1
Configuration Steps ..........................................................................................................3-2
Adding a DeviceNet Master Module to the PLC Configuration.......................................3-3
Configuring the Parameters of a DeviceNet Master Module............................................ 3-4
Telling the DeviceNet Master about Slaves by Adding Slaves to the Network ...............3-8
Configuring Network Settings for Slaves Added to the Master ....................................... 3-9
Configuring Network Settings for a DeviceNet Master Acting as a Slave..................... 3-16
Chapter 4
Chapter 5
Chapter 6
GFK-2196 v
PLC Configuration for the DeviceNet Slave .....................................................4-1
Configuration Steps ..........................................................................................................4-2
Adding aDeviceNet Slave Module to the PLC Configuration.......................................... 4-3
Configuring the Parameters of a DeviceNet Slave Module.............................................. 4-4
Configuring the Network Settings of a DeviceNet Slave Module.................................... 4-7
Module Operation ...............................................................................................5-1
Operation of a Series 90-30 DeviceNet Master Module................................................... 5-2
Operation of a Series 90-30 Slave (Server) DeviceNet Module .......................................5-4
Fault Table Entries for a Series 90-30 DeviceNet Module............................................... 5-5
PLC Status References for a Series 90-30 DeviceNet Module......................................... 5-6
Device Status Bits for the Series 90-30 DeviceNet Master Module................................. 5-7
Programmed Communications .......................................................................... 6-1
COMMREQs for the Series 90-30 DeviceNet Modules................................................... 6-2
Using COMMREQs to Program Communications........................................................... 6-3
Contents
COMMREQ Programming Requirements and Recommendations .................................. 6-5
Command Code 9: Reading Identification, Status, and Error Information....................... 6-8
Command Code 4: Getting the Status of a Network Device ..........................................6-12
Command Code 5: Getting Status Information of a Series 90-30 DeviceNet Slave Module
or the Server Function of a Master Module .................................................................... 6-14
Command Code 6: Getting Input Status from a Device .................................................6-16
Command Codes 1 & 7: Sending a DeviceNet Explicit Message on the Network......... 6-18
Command Codes 2, 3 & 8: Reading and Responding to Client Explicit Messages........ 6-24
Chapter 7
DeviceNet Objects for Series 90-30 Modules ....................................................7-1
Identity Object .................................................................................................................. 7-2
Message Router Object..................................................................................................... 7-3
DeviceNet Object.............................................................................................................. 7-4
Assembly Object............................................................................................................... 7-5
Connection Object ............................................................................................................7-6
PLC Data Object............................................................................................................... 7-8
Appendix A DeviceNet EDS Files ...........................................................................................A-1
Electronic Datasheet File for the DeviceNet Master Module .......................................... A-1
Electronic Datasheet File for the DeviceNet Slave Module ............................................ A-2
vi Series 90®-30 Programmable Controller DeviceNet™ Modules– November 2002 GFK-2196
ChapterChapter
DeviceNet Modules for the Series 90-30 PLC
1
Finding Information in this Book
Chapter 1: DeviceNet Modules for the Series 90-30 PLC, provides basic information about the
Series 90™-30 DeviceNet Master Module (IC693DNM200) and the Series 90-30 DeviceNet Slave
Module (IC693DNS201).
Chapter 2: Installation, discusses power requirements, cable specifications, grounding, module
installation, and LED indications.
Chapter 3: PLC Configuration for the DeviceNet Master, explains how to add a DeviceNet
Master Module to the configuration of the Series 90-30 PLC. It also explains how to configure
communications connections, the module, and the DeviceNet network.
Chapter 4: PLC Configuration for the DeviceNet Slave, explains how to add a DeviceNet Slave
Module to the configuration of the Series 90-30 PLC.
Chapter 5: Module Operation, describes how the Series 90-30 DeviceNet Master Module and the
Series 90-30 DeviceNet Slave Module function in a Series 90-30 PLC system.
Chapter 6: Programmed Communications (COMMREQs), explains how the application program
can communicate with the module for Explicit Messaging and for reading status information.
Chapter 7: DeviceNet Objects for Series 90-30 Modules, describes the information objects that are
defined for the Series 90-30 DeviceNet modules.
Appendix A: DeviceNet EDS Files, contains the Electronic Datasheet (EDS) Files that are defined
for the Series 90-30 DeviceNet Master Module and the Series 90-30 DeviceNet Slave Module.
For Detailed Information about DeviceNet
For detailed information about DeviceNet, contact the Open DeviceNet Vendor Association.
Open DeviceNet Vendor Association, Inc.
20423 State Road 7
Suite 499
Boca Raton, FL. 33498
phone: (954) 340-5412
FAX: (954) 340-5413
Internet: HTTP://WWW.ODVA.ORG
Email: <ODVA@POWERINTERNET.COM
GFK-2196 1-1
1
DeviceNet Modules for the Series 90-30 PLC
Two different Series 90-30 DeviceNet modules bring the flexibility of DeviceNet communications
to a Series 90-30 PLC:
The Series 90-30 DeviceNet Master Module (IC693DNM200) operates as the network master.
It exchanges I/O messages and custom explicit messages with up to 63 other devices on the
network. On DeviceNet networks that include a higher-level host computer, this module's
built-in server function can be used for both automatic data transfer and custom explicit
messaging with the master.
The Series 90-30 DeviceNet Slave Module (IC693DNS201) operates as a network server
(slave) only. It can automatically exchange PLC data with a network master, and respond to
custom explicit messages from the master.
Both of these modules can be installed in any rack in the Series 90-30 PLC. Each module counts as
a single node on the DeviceNet network. However, the server function of each module is easily
configured for up to two DeviceNet I/O Messaging connections and for Explicit Messaging.
1-2 Series 90®-30 Programmable Controller DeviceNet™ Modules – November 2002 GFK-2196
Series 90-30 DeviceNet Master Module
The Series 90-30 DeviceNet Master Module (IC693DNM200) allows a Series 90-30 CPU to send
and receive data over a DeviceNet network. It can act as master for up to 63 slaves on the
DeviceNet network. It can also be configured to simultaneously function as a slave to another
master on the bus.
DeviceNet Master
Module
IC693DNM200
NET POWER
MOD STATUS
NET STATUS
DEVICENET
MASTER
SERVICE RS232
5-IGND
3-TxD
2-RxD
Module
Status
LEDs
RS-232
Connector
1
V+
CAN_H
SHIELD
CAN_L
V-
DEVICENET
DeviceNet
Connector
The module's three DeviceNet-compliant LEDs show its operating and communications status. The
RS-232 serial port (a 9-pin male D-connector) is used for a computer connection during firmware
upgrades. The DeviceNet connector is a removable spring-clamp terminal. It provides bus
continuity and can be removed from the module without disrupting bus operation.
Features
Bus communications at all standard DeviceNet data rates (125k, 250k, 500k baud)
Up to 255 bytes input data transfer and 255 bytes output data transfer per slave and up to 3972
bytes of input data transfer and 3972 bytes of output data transfer per master.
Unconnected Message Manager (UCMM) with 1 proxy connection per slave
One or two I/O connections plus explicit messaging can be configured for each slave. Each
slave I/O connection can be set up for one of the following: Poll, Strobe, Cyclic or Change-ofState (COS) operation. Typically one connection is used for Polled and the other is used for
Strobe, Cyclic, or COS.
Independent configuration of update rates for Poll and COS/Cyclic I/O devices
Configurable global scan rate
PLC-application initiated Explicit messaging using COMMREQs
Status of communication with slaves available in the PLC fault table (configurable). Provides
64 network device status bits
Configurable fault behavior on loss of communication
GFK-2196 Chapter 1 DeviceNet Modules for the Series 90-30 PLC 1-3
1
Series 90-30 DeviceNet Master Module Specifications
Catalog Number IC693DNM200
Description Series 90-30 Master Module for DeviceNet networks
Mounting Location Any Series 90-30 baseplate (CPU, expansion, or remote) slot
except slot 1 of a modular CPU baseplate
Environment
Backplane Current
Consumption
Data rates Supports all standard DeviceNet data rates (125k, 250k, and 500k
Storage temperature: -40°C to 85°C
Operating temperature: 0°C to 60°C
450mA at 5VDC (typical)
Baud)
Compatibility
Compatible with any Series 90-30 CPU except IC693CPU321 and IC693CPU340.
Configuration size is limited for CPU311/313/331, as detailed in chapter 3.
Requires release 8.0 CPU firmware. Release 10 is recommended, if available for a particular
CPU.
Requires CIMPLICITY Machine Edition Logic Developer PLC version 3.0 with Service Pack
for DeviceNet, or later.
Not compatible with the VersaPro™, Control, or Logicmaster™ programming software.
The Series 90-30 Hand-Held Programmer (IC693PRG300) cannot be used to configure this
module.
1-4 Series 90®-30 Programmable Controller DeviceNet™ Modules – November 2002 GFK-2196
Series 90-30 DeviceNet Slave Module
The Series 90-30 DeviceNet Slave Module (IC693DNS201) interfaces a Series 90-30 PLC to a
DeviceNet bus that is controlled by another master device.
DeviceNet
Slave Module
1
NET POWER
MOD STATUS
NET STATUS
DEVICENET
SLAVE
SERVICE RS 232
5-IGND
3-TxD
2-RxD
V+
CAN_H
SHIELD
CAN_L
V-
DEVICENET
Module
Status
LEDs
RS-232
Connector
DeviceNet
Connector
The module's three DeviceNet-compliant LEDS show its operating and communications status. The
RS-232 serial port (a 9-pin male D-connector) is used for a computer connection during firmware
upgrades. The DeviceNet connector is a removable spring-clamp terminal. It provides bus
continuity and can be removed from the module without disrupting bus operation.
Features
Bus communications at all standard DeviceNet data rates (125k, 250k, 500k baud)
Up to 255 bytes input data transfer and 255 bytes output data transfer.
Configurable for Poll, Strobe, Cyclic and COS I/O Connections, and Explicit Messaging
Supports Unconnected Message Manager (UCMM) allowing up to 250 simultaneous explicit
messaging connections.
One or two I/O connections plus explicit messaging can be configured. Each I/O connection
can be set up for one of the following: Poll, Strobe, Cyclic or Change-of-State (COS)
operation. Typically one connection is used for Polled and the other is used for Strobe, Cyclic,
or COS.
Supports the Assembly Object and access to the input and output data for each of the
configured slave I/O areas (I/O Area 1 and I/O Area 2) with the SET_ATTRIBUTE_SINGLE
and GET_ATTRIBUTE_SINGLE services. Up to 255 bytes of attribute data may be supplied
in the SET_ATTRIBUTE_SINGLE operation.
Configurable fault behavior on loss of communication.
UCMM-capable Group 2 Server
GFK-2196 Chapter 1 DeviceNet Modules for the Series 90-30 PLC 1-5
1
Series 90-30 DeviceNet Slave Module Specifications
Catalog Number IC693DNS201
Description Series 90-30 Slave Module for DeviceNet networks
Mounting Location Any Series 90-30 baseplate (CPU, expansion, or remote)
slot except slot 1 of a modular CPU baseplate
Environment
Backplane Current
Consumption
Compatibility
Compatible with any Series 90-30 CPU except IC693CPU321 and IC693CPU340.
Requires release 8.0 CPU firmware. The latest Release 10 is recommended, if available
for the particular CPU.
Requires CIMPLICITY Machine Edition Logic Developer PLC version 3.0 with Service
Pack for DeviceNet, or later.
Not compatible with the VersaPro™, Control, or Logicmaster™ programming software.
The Series 90-30 Hand-Held Programmer (IC693PRG300) cannot be used to configure
this module.
Storage temperature: -40°C to 85°C
Operating temperature: 0°C to 60°C
450mA at 5VDC (typical)
1-6 Series 90®-30 Programmable Controller DeviceNet™ Modules – November 2002 GFK-2196
The DeviceNet Network
DeviceNet is a communications network that transmits data between control systems (for example:
PLCs, PCs, VMEbus computers, and robot controllers) and distributed industrial devices such as
switches, sensors, valve manifolds, motor starters, bar code readers, drives, displays, and operator
interfaces. The network can also link intelligent interface modules such as the VersaPoint
DeviceNet Network Interface Unit (NIU) and the VersaMax DeviceNet NIU. An NIU is the
network interface for an I/O Station of many additional modules.
The DeviceNet network has a linear structure. There is a main trunk line with drop lines routed to
the networked devices. Power and signals are carried on the same network cable. A Series 90-30
DeviceNet module can be connected directly to the trunk cable or installed as an individual drop or
as part of a daisy-chain drop.
1
Master
Series 90-30 PLC with
DeviceNet Master Module
Slaves
Series 90-30 PLC
with DeviceNet Slave
Module
GFK-2196 Chapter 1 DeviceNet Modules for the Series 90-30 PLC 1-7
1
DeviceNet Communications for Series 90-30 DeviceNet Modules
DeviceNet uses the Producer-Consumer technique of messaging. A device with data produces the
data on the network. All devices that need data listen for messages. When a device recognizes the
appropriate identifier, it consumes the data. A message is not specific to a particular source or
destination, and one message can be consumed by multiple devices. For example, one message
could control several motor starter modules.
A DeviceNet message field can range between 0 and 8 bytes. Messages longer than 8 bytes are
fragmented into packets. The Series 90-30 DeviceNet modules assure data integrity for each
network node.
I/O Messaging
I/O messaging is used for the routine and automatic exchange of data between devices. Individual
I/O messages can be up to 255 bytes in length. I/O messages provide a dedicated communication
path between a producing device and one or more consuming devices. System configuration sets up
the parameters for the connections between the producing and consuming devices. With the
connections established, communications occur automatically.
There are four basic types of I/O messages: Polled, Strobed, Cyclic, and Change-of-State (COS).
The Series 90-30 DeviceNet Master Module can be configured for up to two different types of I/O
messaging connections to each slave (for example, one Cyclic I/O messaging connection and one
Change-of-State I/O messaging connection). See chapter 3, "PLC Configuration for the DeviceMet
Master" for details.
Explicit Messaging
Explicit messaging provide a point-to-point communication link between two devices on the
network. Explicit messaging is often used for slave configuration and for diagnostics. Specific
Explicit messages are defined for the DeviceNet protocol. For the Series 90-30 DeviceNet Master
module, Communications Request (COMMREQs) are used to send Explicit messages. See chapter
6, "Programmed Communications" for more information. Received Explicit messages are
automatically processed by the DeviceNet module except for user defined Objects which require
user programmed COMMREQs support.
1-8 Series 90®-30 Programmable Controller DeviceNet™ Modules – November 2002 GFK-2196
Chapter
2
Installation
This chapter provides basic installation information for the Series 90-30 DeviceNet Modules:
Power requirements: PLC system power and DeviceNet network power
The DeviceNet cable: specifications, length, termination, taps
Grounding: DeviceNet cable, DeviceNet power supply, DeviceNet system
Installing the DeviceNet module in the PLC
The Module LEDs: Module Status, Network Status, Network Power
The RS-232 Serial Port
For Additional Information
Correct installation of cables, power supplies, and other network hardware requires a more detailed
knowledge of DeviceNet specifications than can be provided here. Readers are referred to
www.ODVA.org for additional information.
Conformance to Standards
Before installing GE Fanuc products in situations where compliance to standards or directives from
the Federal Communications Commission, the Canadian Department of Communications, or the
European Union is necessary please refer to GE Fanuc’s
Conformance to Standards
, GFK-1179.
Installation Requirements for
GFK-2196 2-1
2
Power Supplies
When using a Series 90-30 DeviceNet module, there are two separate power supplies to consider:
the PLC power supply and the DeviceNet network power supply.
PLC Power
A Series 90-30 DeviceNet module consumes 450mA at 5VDC (typical) from the PLC backplane.
A high-capacity Series 90-30 power supply such as IC693PWR330 or IC693PWR331 is
recommended when using these modules, especially for CPU models CPU350 or higher, or if the
PLC includes Ethernet adapters and/or multiple DeviceNet modules.
The PLC power supply load is automatically calculated by the CIMPLICITY Machine Edition
configuration software. Additional information about estimating power supply load can be found
in GFK-0356, the
Series 90-30 Installation and Hardware Manual
DeviceNet Power
The Series 90-30 DeviceNet modules power their network transceivers from the 24VDC DeviceNet
network power source. Linear power supplies are recommended for the DeviceNet power source.
The DeviceNet power source should
devices can cause communications errors and even create bus-off conditions.
also be used for device power. Transients caused by I/O
not
.
The DeviceNet specification recommends using a power tap to connect a power supply to the
network. The power tap should be appropriately fused for the current capacity of the bus cables.
The maximum current on the network depends on the cable type.
The Series 90-30 DeviceNet modules consume xxxma at 24VDC (typical) from the DeviceNet
Network.
Current Limit for Thick Cable
For thick cable, the maximum current on the network is 16 Amps. However, only 8 Amps is
permitted on a single network segment. 16 Amps can be drawn from a single power supply by
locating the power supply at the center point of two network segments, supplying 8 Amps to each
segment.
Current Limit for Thin Cable
For thin cable, the maximum current permitted is 3 Amps.
2-2 Series 90®-30 Programmable Controller DeviceNet™ Modules – November 2002 GFK-2196
DeviceNet Cable for the Series 90-30 Modules
Series 90-30 DeviceNet modules can be used with the either DeviceNet thick cable or thin cable.
Thick cable permits greater cable lengths and higher current levels. Generally, thick cable is used
for the trunk cable. Thin cable is normally used for shorter distances and is suitable for drop cables
and for installations where more cable flexibility is needed.
Both thick cable and thin cable are 5-wire, multi-conductor copper cable. Two wires form a
transmission line for network communications. A second pair transmits network power. The fifth
conductor forms an electromagnetic shield. Most cables have color coded leads which correspond
to the color coding on the terminals on the Series90-30 DeviceNet modules.
Cable and Network Specifications
2
Thick Cable General Specifications
Thin Cable General Specifications
Network Topology Bus with limited branching (trunkline/dropline)
Redundancy Not Supported
Network Power for Node devices Nominal 24 VDC ±4%
Allowed Nodes (Bridging excluded) 64 nodes
Data Packet Size 0-8 bytes with allowance for message fragmentation
Duplicate Address Detection Addresses verified at power-up
Error Detection / Correction
Two shielded pairs - Common axis with drain wire in center
Overall braid shield - 65% coverage; 36 AWG or 0.12mm tinned Cu
braid minimum (individually tinned)
Drain wire- #18 Copper min.; 19 strands minimum (individually tinned)
Outside diameter - 0.410 inches (min) to 0.490 inches (max.) roundness
- radius delta to be within 15% of 0.5 O.D.
Two shielded pairs - Common axis with drain wire in center
Overall braid shield - 65% coverage; 36 AWG or 0.12mm tinned Cu
braid minimum (individually tinned)
Drain wire - #22 Copper; 19 strands minimum (individually tinned)
Outside diameter - 0.240 inches (min.) to 0.280 inches (max.)
roundness - radius delta to be within 20% of 0.5 O.D.
CRC - retransmission of message if validity not acknowledged by
recipient
Bus Connector Pin Assignments
The DeviceNet connector on a Series 90-30 DeviceNet module has five color-coded screw-clamp
terminals. The connector provides bus continuity; it can be removed from the module without
disrupting bus operation.
GFK-2196 Chapter 2 Installation 2-3
CAN_H
SHIELD
CAN_L
Signal Pin Wire Color
V+
V+ 5 Red
CAN_H 4 White
Shield 3 Bare
V-
CAN_L 2 Blue
V- 1 Black
2
Bus Length
The maximum length of the trunk cable and drops both depend on the cable type and data rate.
Individual drops may not exceed 6 meters and are limited to one network node per drop. However,
the node may have multiple ports.
Data Rates 125kbps 250kbps 500kbps
thick cable, trunk length 500m (1640ft) 250m (820ft) 100m (328ft)
thin cable, trunk length 100m (328ft) 100m (328ft) 100m (328ft)
maximum drop length 6m (20ft) 6m (20ft) 6m (20ft)
total length of all drops 156m (512ft) 78m (256ft) 39m (128ft)
For each baud rate, the total drop length is the sum of all the drop lines of both cable types in the
network.
In addition, if the distance from a tap to the most distant device on its drop is longer than the
distance from the tap to the nearest terminating resistor as illustrated below, the drop line length
also counts as part of the trunk cable length (as well as the overall drop length).
Longest
Distance
to a Node
Tap
Distance to
Terminating
Resistor
Terminating
Resistor
Node
Node
Node
2-4 Series 90®-30 Programmable Controller DeviceNet™ Modules – November 2002 GFK-2196
Network Termination
121 Ohm, 1% ¼ watt terminating resistors MUST be installed at both ends of the DeviceNet
network. Each terminating resistor is placed across the data communication signals at pin 2
(CAN_L) and pin 4 (CAN_H).
Taps, Daisy-Chaining and Branches
Devices can be connected directly to the trunk cable, or to drop lines that are joined to the trunk
cable with taps. Taps can be mounted in junction boxes or panels. Drop lines and daisy-chains are
often used inside control panels where multiple devices are grouped together. When using drops
with daisy-chains and branches, the maximum length from a tap to its farthest drop is 20 feet.
2
Tap Tap
Node
Node
Node
Trunk Line
Node Node Node
Node
Drop Lines
Node
Node
Wiring to the Series 90-30 DeviceNet Master module depends on its location on the network:
If the Series 90-30 DeviceNet
module is located at either end
of the bus trunk, it is wired with
one cable connection and a
terminating resistor:
If the module is installed at the
end of a drop or drop segment,
it is wired with one cable
connection only.
If the module is installed
directly on the trunk cable or as
part of a daisy-chained drop
cable, it has both an incoming
and outgoing cable connected:
GFK-2196 Chapter 2 Installation 2-5
2
Grounding
DeviceNet Cable Grounding
All DeviceNet cable shields must be tied to ground at each device connection. This is done by
tying the bare wire of the cable to pin 3 (Shield) of the connector.
DeviceNet Power Supply Grounding
The DeviceNet network power supply must also be grounded, but only at one point. The V- signal
must be connected to protective earth ground at the power supply only. If multiple power supplies
are used, only one power supply must have V- connected to earth ground.
DeviceNet System Grounding
DeviceNet communications should only be grounded to earth at a single point. Typically this is
done in the control cabinet where the DeviceNet power supply is located.
Return for the DeviceNet power (-V), the drain (bare wire) and the cable shields must be directly
tied to earth ground. Ideally, this grounding is done at a central location. Connection should be
made using a 25mm (1in.) copper braid or a #8 AWG wire not longer than 3meters (10ft.).
The illustration below represents grounding for a network that has two power supplies. The chassis
of each power supply is connected to earth ground.
Power Supply #2
Return
+24V
V+
CAN_H
SHIELD
CAN_L
V-
Power Supply #1
Return
+24V
Ground Wire Size
The minimum size ground conductor for the DeviceNet screw-clamp terminals on a Series 90-30
DeviceNet module is a 2.5mm
may be necessary.
2
(14 AWG) wire. For other network devices, larger wire diameters
2-6 Series 90®-30 Programmable Controller DeviceNet™ Modules – November 2002 GFK-2196
Installing the DeviceNet Module in the PLC Rack
A Series 90-30 DeviceNet module can be installed in the main (CPU) rack in slot 2 or higher, or in
slot 1 or higher of any expansion rack.
1. Turn off power to the rack.
2. Place the module into its slot by hooking the top of the module on the notch above the slot and
slowly lowering the module until it snaps into place.
3. Attach the DeviceNet cable to the module.
4. Terminate the network as required.
2
Note: For details about installing Series 90-30 rack systems and modules, refer to the
90-30 Installation Manual and Hardware Manual
, GFK-0356.
Removing the Module from the Rack
To remove the module from the rack:
1. Turn off power to rack.
2. Remove all cables from the module.
3. Press the release located on the bottom of the module and slowly raise the module from
the bottom until it comes out of the slot.
Series
GFK-2196 Chapter 2 Installation 2-7
2
Module LEDs
The module's three LEDs show its operating and communications status:
NET POWER
MOD STATUS
NET STATUS
Network Power LED
LED Indicates
Red There is no power detected on the network.
Green Power detected on the network.
Module Status LED
LED Indicates
Off There is no backplane power to the module.
Green The module is operating normally.
Flashing
Green
Flashing Red Recoverable Fault
Red The module has an unrecoverable fault; it may need resetting or
Flashing Red
/ Green
The module is in standby mode. Its configuration is missing, incomplete,
or incorrect. The module may be in Standby state.
replacing.
The module is in Self Test mode.
Network Status LED
LED Indicates
Off The module is not online, or
The module has not completed the Duplicate MACID test, or
The module may not be powered. See Module Status LED.
Flashing
Green
Green
Flashing Red One or more I/O Connections are in the Timed Out state.
Red The module is not capable of communicating on the network.
Flashing Red
/ Green
2-8 Series 90®-30 Programmable Controller DeviceNet™ Modules – November 2002 GFK-2196
The module is online but has no connections in the established
state, or
The module has passed the Duplicate MACID check, is online, but
has no established connections with other nodes.
The module is online and has one or more connections in the
established state.
The module has detected a Network Access error and is in the
Communication Faulted State.
RS-232 Serial Port
The RS-232 serial port is a 9-pin male D-connector. This port is used for a computer connection
during firmware upgrades.
Upgrading the DeviceNet Module's Firmware
When future upgrades to the firmware are made available, the module can be upgraded as
described below.
1. Download the firmware upgrade to the computer that will be used to perform the upgrade.
Firmware upgrades are usually available from the GE Fanuc WEB site
www.gefanuc.com/support/plc/
SERVICE RS232
5-IGND
3-TxD
2-RxD
2
2. Connect a straight through serial cable from the computer to the serial port on the front of the
DeviceNet module. Only the RX and TX lines are used. The cable that is part of the RS232 to
RS485 kit (IC693ACC903) is suitable.
3. The computer can utilize any standard communication software to communicate with the
module. The module supports 19200 baud, no parity, 8 data bits, 1 stop bit, and no flow
control.
4. Cycle power to the Series 90-30 PLC rack that contains the DeviceNet module.
5. At the computer, press ENTER until you see the initial greeting. The greeting indicates that the
boot code is waiting for new firmware. Initiate an Xmodem send of the module firmware file
using your communication software. Note: You must press the ENTER key immediately after
the power is cycled. It is recommended you hold down the ENTER key when turning the
power back on.
6. When it finishes successfully storing the new firmware, the module automatically resets and
attempts to start the new firmware.
7. If the firmware transfer was not successful, the greeting screen reappears. Retry the transfer.
On success, disconnect the serial cable and cycle power to the Series 90-30 PLC rack.
GFK-2196 Chapter 2 Installation 2-9
Chapter
3
PLC Configuration for the DeviceNet Master
This chapter explains how to add a Series 90-30 DeviceNet Master Module (IC693DNM200) to the
configuration of the Series 90-30 PLC. It also explains how to configure communications
connections between a Series 90-30 DeviceNet Master Module and the DeviceNet network.
Configuration Steps
Adding a DeviceNet Master Module to the PLC Configuration
Configuring the Parameters of a DeviceNet Master Module
Parameters of a DeviceNet Master Module
Network Settings of a DeviceNet Master Module
Telling the DeviceNet Master about Slaves by Adding Slaves to the Network
Adding a Device's EDS File
Configuring Network Settings for Slaves Added to the Master
Assigning the MAC IDs and Baud Rate
Configuring I/O Messaging Connections
Configuring DeviceNet Explicit Messaging
Configuring Network Settings for a DeviceNet Master Acting as a Slave
Assigning the MAC IDs and Baud Rate
Configuring I/O Messaging Connections for a DeviceNet Master Acting as a Slave
Configuring DeviceNet Explicit Messaging
These configuration procedures are written for users who have a basic knowledge of the
CIMPLICITY Machine Edition Logic Developer software and the Series 90-30 PLC. For help
with using the software, please see the software’s built-in help system.
Note: The DeviceNet Master is only supported in CIMPLICITY Machine Edition Logic
Developer. The Logicmaster™, VersaPro™, and Control software do not support these
Series 90-30 DeviceNet modules.
GFK-2196 3-1
3
Configuration Steps
There are three basic steps to configuring a Series 90-30 DeviceNet Master Module:
Adding the module to the PLC rack and configuring its operating parameters.
Telling the DeviceNet Master about slaves by adding the network slaves to the Master and
configuring their network settings.
The number and type of slave devices and the amount of data they can exchange with the
master may be limited by the CPU memory available. The amount of CPU memory available
for the DeviceNet configuration depends on: the CPU model being used, the version of the
CPU firmware, the number and type of other modules in the configuration, the number and
type of slave devices configured, and the amount and type of communication in progress with
an external programmer or HMI devices. With Logic Developer-PLC, the size of the current
configuration can be read by selecting “Data View” for the hardware configuration and adding
the sizes of the components listed. LD-PLC will not allow configurations to be created that
exceed 65,535 bytes. The size of the DeviceNet configuration is also limited by the size of the
user configuration space for the models listed below:
CPU 311/313 4,736 bytes available
CPU 331 4,673 bytes available
(Optional) Configuring the network settings of the DeviceNet Master Module itself. This is
ONLY done if the DeviceNet Master Module will also operate as a server to another network
master. For example, it might exchange data relating to the operation of its slaves with a
higher-level host controller.
3-2 Series 90®-30 Programmable Controller DeviceNet™ Modules – November 2002 GFK-2196
Adding a DeviceNet Master Module to the PLC Configuration
First, add the Series 90-30 DeviceNet Master Module (IC693DNM200) to the PLC rack
configuration. The module is compatible with any Series 90-30 CPU except IC693CPU321 or
IC693CPU340. It requires release 8.0 CPU firmware as a minimum. Release 10.6 or later is
recommended, if available for your particular CPU.
1. In that configuration, in the Project tab of the Navigator, expand the Hardware Configuration
folder.
2. In the Hardware Configuration folder, right click the intended PLC Slot for the DeviceNet
Master Module. It can be any slot except slot 1 of a modular CPU rack.
3. Select Add Module from the shortcut menu.
Hardware
Configuration Folder
3
Navigator Window
Short Cut Menu
The Module Catalog dialog box appears.
4. To add a DeviceNet Master Module, click on the Bus Controller tab. The Bus Controller
module list appears. Select IC693DNM200 DeviceNet Master from the list and click OK.
GFK-2196 Chapter 3 PLC Configuration for the DeviceNet Master 3-3
3
Configuring the Parameters of a DeviceNet Master Module
The DeviceNet Master Module is added to the PLC configuration in the Navigator window, and the
module’s Parameter Editor window appears in the InfoViewer window space.
Parameters of a DeviceNet Master Module
Settings tab
Mac ID
Slave Status Bit
Array Address
Length
(of slave status
bits)
Network
Status/Firmware
ID Address
Length (of
network status
/firmware ID)
Program Mode
Transmission
The Mac ID (medium access control identification) of the master on the DeviceNet network.
Valid range: 0 - 63. Default: 0.
The starting address for an array of bits indicating the health of each node on the
DeviceNet network. It must be a non-overlapping range in %AI, %I, %Q, %G, %AQ, %R,
%T, or %M. It defaults to %I memory and uses the next available %I address.
A slave's status address equals Start Address + Station Address of the slave. For example,
if the status bits are mapped to %I00001, the status for the slave at Station Address 5
would be found at %I00001 + 5 = %I00006.
The master’s status is located in the same way as the slaves’ (Start Address + Station
Address). The master is configured as station 0 by default, but can be set to any valid
address (0-64).
(Read-only.) Length has a value of 64, corresponding to 64 network devices.
The starting address for three words of module/network status information. The default is
%AI memory and uses the next available %AI address. The Network Status/Firmware ID
Address must be a non-overlapping range in %AI, %I, %Q, %G, %AQ, %R, %T, or %M.
During system operation, the module and network status data and module firmware ID will
be stored in this memory location.
(read only) Length of the Network Status / Firmware ID Address memory location, 3 words.
When the PLC is in Program mode (Stop mode), the DeviceNet Master Module can either
send idle packets or set data to zero. The default is to send idle packets.
3-4 Series 90®-30 Programmable Controller DeviceNet™ Modules – November 2002 GFK-2196
Settings tab
Fault State
Transmission
Inputs on Loss
of Slave
Slave Status
Fault Table
Entries
Ack Timeout
(ms)
Baud Rate
(kbps)
Scan Interval
(ms)
for Strobed
connections
Reconnect Time
(ms)
Download
Names &
Descriptions
Download EDS
Files
When the DeviceNet Master Module detects a PLC fault (because the PLC has not
requested its regular I/O update from the module), the module can either send idle packets
or set data to zero. The default is to send idle packets.
If the DeviceNet Master loses communications with a slave, it can hold the module's input
reported to the CPU in its last state (the default), or clear the input data.
When slave communications status events (loss and re-establish) occur, the DeviceNet
Master Module can either report them in the fault table or not. If this setting is True (the
default), the Master makes fault table entries. If this setting is False, slave status events
are not reported to the fault table.
Number of milliseconds to wait for a CAN Acknowledge of the Duplicate MacID check
(performed during startup) before reporting an Ack (acknowledge) failure. Valid range: 0 to
65,535. The default is 2,000ms (2 seconds).
The data transmission rate for the DeviceNet Master Module. The maximum baud rate that
can be used depends on the bus length and cable type. See chapter 2 for more
information. Choose: 125K, 250K, or 500K.
The time interval between successive scans of Strobed slave connections. This defaults to
zero. A time must be specified if any slave connections are set up for strobing. The valid
range is 0 to 65,535ms. All strobed connections will be scanned at this same interval.
If a slave fails to respond to three consecutive scan cycles, the slave is flagged as not
present and the master tries to reconnect to it.
This parameter specifies how long the master should wait before attempting to reconnect.
The default time is 0. The valid range is 100 to 65535ms.
This setting determines whether or not names and descriptions that have been use in the
configuration will be downloaded to the PLC when the configuration is downloaded.
By default, this parameter is False and names and descriptions are not downloaded to the
PLC. This is the recommended choice because downloaded names and descriptions can
take up too much memory in the PLC. Names and descriptions are a convenience only.
Omitting them from the download does not affect system operation. However, if this
parameter is set to False, later uploads of the configuration from the PLC to the
programmer will contain only default names and descriptions.
If this parameter is set to True, names and descriptions that have been entered for the
slaves and the master are downloaded to the PLC and will be present in the configuration if
it is uploaded to the programmer later..
This setting determines whether or not the EDS files that have been used for the
configuration will be downloaded from the programmer to the PLC when the configuration
is downloaded.
By default, this parameter is False and EDS files are not downloaded to the PLC. This is
the recommended choice, because downloaded EDS files can consume too much memory
in the PLC. However, when this is set to False, if the configuration is later uploaded from
the PLC back to the programmer, it will not contain the EDS files. You would need another
source for the EDS files (for example, on disk) to configure more modules of a given type.
If the EDS files are no longer available, it is only possible to add more modules of that type
as generic modules.
If this parameter is set to True, the EDS files are included when the configuration is
downloaded to the PLC. If the configuration is later uploaded back to the programmer, the
EDS files will be restored to the Toolchest for use by the configuration.
3
GFK-2196 Chapter 3 PLC Configuration for the DeviceNet Master 3-5
3
Data Areas Tab
This tab shows the PLC program references assigned to the DeviceNet Master
Module's Network Settings
This TAB is optional and should only be used when the DeviceNet Master
Module is also a slave to another Devicenet master device.
Note
: Do not enter values on this tab if the DeviceNet Master Module is not
also used as a slave. Entering values on this tab when the DeviceNet Master is
not used as a slave causes the DeviceNet Master to fail to communicate with
slaves.
when it is used as a slave
:
Power Consumption Tab
Power consumption
This read-only tab shows the backplane power that will be consumed by the
DeviceNet Slave Module. This power will be used for module operation.
The DeviceNet Slave Module also draws power for its DeviceNet transceiver
from the 24VDC power supply on the DeviceNet network.
3-6 Series 90®-30 Programmable Controller DeviceNet™ Modules – November 2002 GFK-2196
Network Settings of a DeviceNet Master Module
To configure the Network Settings for a DeviceNet Master Module, right-click the DeviceNet
Master in the PLC configuration, and choose Network Settings:
The Network Settings dialog box appears.
3
The General tab allows setting a name and description for the module. On this tab, you can also
select the MACID, Baud Rate, Scan Interval, and Reconnect Time. These parameters are also
found on the Configuration Parameter screen; they can be set in either place.
The rest of the tabs are only used if the Series 90-30 DeviceNet Master Module will operate as a
server (slave) to another master on the network. If the DeviceNet Master is not a slave to another
DeviceNet master these three tabs should be left blank. Please turn to “Configuring Network
Settings” later in this chapter for detailed information about the Network Setting parameters.
GFK-2196 Chapter 3 PLC Configuration for the DeviceNet Master 3-7
3
Telling the DeviceNet Master about Slaves by Adding Slaves to the
Network
After adding the DeviceNet Master Module to the PLC rack, you need to tell the Master about the
required communication to the slave devices on the DeviceNet network by adding slaves to the
Master. There are two ways to add a slave to the network configuration:
In the Navigator window, right-click on the IC693DNM200 Master Module and choose Add
Slave.
Select the slave type from the list that appears. Click OK to select the slave. For example, to
add a Series 90-30 DeviceNet Slave Module (IC693DNS201) as a slave on the network, you
would select:
You can also drag and drop a device from the Toolchest to the DeviceNet master. Open the
Toolchest by clicking the Toolchest button on the Tools toolbar. Select the DeviceNet Devices
drawer. Choose a slave device.
If you are editing a configuration that was uploaded from the PLC, the presence of device EDS
files (and also device names and descriptions) depends on the DeviceNet Master Module
configuration, as described earlier in this chapter. If the EDS files and names and descriptions
were not downloaded, they will not be part of the uploaded configuration, and the EDS files
may no longer be present in the Toolchest.
Whether you are adding devices in the Navigator or using the drag and drop method , if you
don't see the type of device you want to add and also don't have an EDS file for the device, you
can only configure the slave as a generic device .
Adding a Device's EDS File
If the device you want to configure is not listed and is not in the Toolchest, you can provide the
EDS file, which is supplied by the device manufacturer, by clicking Have Disk. In the Open dialog
box, browse to the EDS file and click Open. (When you select an EDS file using this method, it is
added to the Slave Catalog and the DeviceNet Devices drawer of the Toolchest.)
3-8 Series 90®-30 Programmable Controller DeviceNet™ Modules – November 2002 GFK-2196
Configuring Network Settings for Slaves Added to the Master
The Network Settings include MAC IDs, baud rates, and the messaging connections between
devices on the network.
Assigning the MAC IDs and Baud Rate
Be sure the MAC IDs entered for slaves in the Machine Edition configuration match the MAC IDs
set up for the devices themselves.
Many devices have their MAC IDs set by DIP switches. Some have their MAC IDs set by
configuration commands from the master. All software-configured devices originally have the
same default MAC ID: 63. To configure a software configured device, add a generic device with
MACID 63 and enable Explicit Messaging to allow the configuration message to be sent to the
device. Therefore, assigning the MAC ID 63 to be used by a device on the network should be done
carefully, to prevent duplicate MAC ID conflicts when adding a new slave. Because all softwareconfigurable slaves originally have the same default MAC ID, such slaves should be connected to
the network one at a time. As each new slave is connected, its MAC ID should be changed using a
Send Device Explicit COMMREQ, and its operation should be checked before connecting the next
slave. Remember that the device will take on the new MAC ID after the configuration message is
sent to it.
3
Configuring the MAC ID of a Slave Device
On the Network Settings: General tab, configure the device's MAC ID. The MAC ID will default to
the next available address but will not fill in skipped addesses.The dropdown list displays MAC
IDs that have not been used in the Machine Edition configuration. In this example, IDs 2 and 3
have already been assigned, so those numbers do not appear in the list.
Name
A field is provided to give the slave an identifying name
Description
A field is provide to add a description of the slave
GFK-2196 Chapter 3 PLC Configuration for the DeviceNet Master 3-9
Loading...