DeviceNet Motor Control Centers (MCCs) · 2019. 8. 15. · To achieve maximum performance of an IntelliCENTER MCC, 500K baud should be used. 50 50 Baud Rate Trunk Drop(2) (2) No single

i Publication 2100-TD019C-EN-P—March 2006

Technical Data

DeviceNet Motor Control Centers (MCCs)

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2DeviceNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2DeviceNet in MCCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Node Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Cable Length Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3Trunk Cable Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Series M Sections (May 2001 and later) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Series L Sections (through May 2001) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Determining Cable Lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Calculating Cable Lengths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6MCC Cable Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Terminating Resistors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Installing Terminating Resistor Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Installing Terminating Resistor Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Installing Terminating Resistors with all Devices Internal to the MCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Adding a Motor Control Center Unit to a DeviceNet System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Splicing DeviceNet Communication Cables in Motor Control Centers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19DeviceNet Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Connecting Power Supplies—Remote or in the MCC Line-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Series M Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Series L Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Network Grounding at the Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Best Grounding Practice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Connecting Two Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Start-Up and Training Aids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

IntelliCENTER MCC Design, Start-Up and Training Course. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Field Support Kit for DeviceNet MCCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Training Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

System Design Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30DeviceNet Software Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30How to Find Electronic Data Sheets (EDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Definition of EDS Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Necessary EDS Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Installing EDS Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Finding EDS Files for Other Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Uploading EDS Files from the Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Publication 2100-TD019C-EN-P—March 2006

ii DeviceNet Motor Control Centers (MCCs)

1 Publication 2100-TD019C-EN-P—March 2006

DeviceNet™ Motor Control Centers

Table A Publications

Table B Websites

Table C Technical Support

Title Description Publication Number

Bulletin 2100 CENTERLINE®

Motor Control Centers Brochure 2100-BR002x-EN-P*

Integrated Intelligence within an MCC—IntelliCENTER® Brochure PCP-BR001x-EN-P*

IntelliCENTER Software User Guide User Manual 2100-UM002x-EN-P*

Integrated, Intelligent Motor Control Centers White Paper 2100-WP001x-EN-P*

Joining and Splicing Vertical Sections Instructions 2100-IN010x-ENP

DeviceNet Product Overview System Overview DN-2.5

DeviceNet Selection Guide Selection Guide DNET-SG001x-EN-P*

DeviceNet Media Design Installation Guide User Manual DNET-UM072x-EN-P

KwikLink Radiated Immunity Testing White Paper 1485-WP001x-US-P*

KwikLink Connection System Brochure Brochure 1485-CG001x-EN-P

* x is a placeholder for the revision letter of the publication. When referencing publication via The Literature Library (www.rockwellautomation.com/literature) always use the latest revision available.

Topic Internet Web Address

IntelliCENTER http://www.ab.com/intellicenter

Motor control centers http://www.ab.com/mcc

Electronic Publications http://www.rockwellautomation.com/literature

Ordering publications http://www.rockwellautomation.com/dox

DeviceNet (Allen-Bradley) http://www.ab.com/networks

Electronic data sheets (EDS) files http://www.ab.com/networks/eds

Open DeviceNet Vendor Association (ODVA) http://www.odva.org

Type of support Access at

Telephone 440.646.5800

Fax 414.382.0505

E-mail [email protected]

Internet website http://www.ab.com/mcc


2 DeviceNet™ Motor Control Centers

Overview This document describes cable system construction and components associated with a DeviceNet network that is factory installed in Bulletin 2100 CENTERLINE® and IntelliCENTER® motor control centers (MCCs).

DeviceNet DeviceNet is a low-cost communication link to connect industrial devices (such as limit switches, photoelectric sensors, motor starters, push buttons, variable frequency drives, and operator interfaces) to a network and eliminate time-consuming and costly hardwiring.

DeviceNet is a simple, open networking solution based on the producer/consumer model, the latest in network technology. This technology allows for real-time control, data exchange, configuration capabilities, and collection of data at regular intervals or on demand. The network specifications and protocol are open—managed by the Open DeviceNet Vendor Association (ODVA)—meaning that vendors are not required to purchase hardware, software, or licensing rights to connect devices to a system. This has resulted in over 300 vendors offering DeviceNet products and over a half million installed nodes worldwide.

DeviceNet in MCCs DeviceNet is ideally suited for MCC applications with respect to cost and performance. This document details the applications of DeviceNet in MCCs, including cable system construction and common DeviceNet components.

System Architecture When designing DeviceNet systems, it is necessary to consider the following factors:

• Node Count• Cable Type and Lengths• Terminating Resistors with Internal and External Devices

Node Count

DeviceNet can accommodate 64 nodes. Typically, three nodes are reserved for the scanner, PC and a new device.

ATTENTION

!Before performing any service or maintenance activities on MCC sections, disconnect all power sources.


DeviceNet™ Motor Control Centers 3

Node count is also affected by performance, needs and future expandability. To ensure this, use following the table to set node count guidelines.

Cable Length Limitations

Cable lengths are calculated for two types of types of cables: trunk and drop. Trunk cable is all cable directly between terminating resistors. All other cable is drop cable.

Trunk Cable Routing

Series M Sections (May 2001 and later)

The DeviceNet trunk line assembly is typically mounted in a channel above the horizontal power bus bars. If a neutral bus is mounted in the upper channel, the trunk line assembly will be mounted below the horizontal power bus bars. The trunk line continues vertically, behind the vertical wireway, joined to the horizontal portion via a DeviceNet connector.

In a standard MCC section, the vertical segment of trunk line has six DeviceNet ports directly connected to it, built into the back of the vertical wireway. Units with communicating devices have a DeviceNet drop line from the device, plugged into the ports. Each port is independent, allowing any unit to be plugged in and removed without affecting adjacent units. If a unit with a communicating device occupies a full section, only one DeviceNet port is supplied.

The trunk line terminates with a DeviceNet plug on the left side and a receptacle on the right side. It is accessible from any unattached side of a section by removing the center end cover plate.

Baud Rate DeviceNet MCC IntelliCENTER MCC

125K 50 Not Supported

250K 50 35

500K(1)

(1)To achieve maximum performance of an IntelliCENTER MCC, 500K baud should be used.

50 50

Baud Rate Trunk Drop(2)

(2)No single drop can exceed 20 ft (6m) in length

125K 1378 ft (420m) 512 ft (156m)

250K 656 ft (200m) 256 ft (78m)

500K(1)

(1)To achieve maximum performance of an IntelliCENTER MCC, 500K baud should be used.

246 ft (75m) 128 ft (39m)



Figure 1 Typical Single MCC Section (Series M)

Series L Sections (through May 2001)

The DeviceNet trunk line assembly typically is mounted in a channel above the horizontal power bus bars. If a neutral bus is mounted in the upper channel, the trunk line assembly will be mounted below the horizontal power bus bars.

The DeviceNet drop line is located behind the vertical wireway and attaches to the trunk line via a DeviceNet connector. It has six DeviceNet ports directly connected to it, that are built into the back of the vertical wireway. Units with connecting devices have a DeviceNet drop line from the device that plugs into the ports. Each port is independent, allowing any unit to be plugged in and removed without affecting adjacent units. If a communicating device is present in a unit occupying a full section, one DeviceNet port is supplied.

The trunk line terminates with a DeviceNet plug on the leftmost side and a receptacle on the rightmost side of a shipping block. It is accessible from the unattached left and right sides of a shipping block by removing the center end cover plate.

DeviceNet Trunk Line

Linking Plug Linking Receptacle

3-Phase Horizontal Power Bus

Trunk line behind the vertical wireway and six (6) DeviceNet ports in the wireway



Figure 2 Typical Two-Section Shipping Block (Series L)

Determining Cable Lengths

To help determine cable lengths for your application, each MCC is shipped with documentation identifying the trunk and drop length used within the MCC.

Figure 3 DeviceNet Network Specifications

DeviceNet trunk lineLinking PlugLinking Receptacle

3-Phase Horizontal Power Bus

Drop line behind the vertical wireway and six (6) DeviceNet ports in the wireway



Calculating Cable Lengths

Cable lengths can also be calculated using the following guidelines.

• Series L MCC– 2 feet trunk per section (do not include frame-mounted sections)– 7 feet drop per section (plus unit drop cables)

• Series M MCC– 14 feet trunk per section (do not include frame-mounted sections)– If using a terminating resistor or extending the trunk from the top

port: • Add 3 feet drop and subtract 3 feet trunk

– If using a terminating resistor or extending the trunk from the bottom port

• Add 5 feet drop and subtract 5 feet trunk• All series

– 3 feet trunk for each frame-mounted section– Measure each unit drop cable or estimate 2 feet per unit drop cable– Add all trunk and drop cable lengths external to the MCC

Cable to the left of the terminating resistor is drop cable

Cable to the right of the terminating resistor is drop cable



MCC Cable Types

Three types of media (cable) are used in MCCs for DeviceNet communication:

NOTE: If the cable has a shield it must be grounded at one end only

ATTENTION

!Do not apply high voltage to any installed DeviceNet cable system or its connectors. The high voltage will destroy internal capacitors in the connectors. Test equipment such as a meggar or hi-pot will damage the internal capacitors.

ATTENTION

!The Rockwell Automation media checker (catalog number 1788-MCHKR) can be used with MCC DeviceNet installations. The cable length calculation will not be accurate because of the internal capacitors in the connectors.

Type Flat• Class 1, 600 Volts, 8 amps• 4 conductor—unshielded

Round• Class 1, 600 Volts, 8 amps• 4 conductor—unshielded

Round• Class 1, 600 Volts, 8 amps • 4 Conductor—shielded

Use Trunk lines (and drop lines in series L sections)

Connecting units to DeviceNet ports (unit drop lines)

Trunk line for extending trunk beyond MCC

Part Number 1485C-P1E75 (75 m spool)1485C-P1E200 (200 m spool)1485C-P1E420 (420 m spool)

2100H-DNRC1 (50 m spool) Belden 7897A, 7896A1485C-P1BS75 (75m spool)

Flat Cable Round Drop Cable Round Trunk Cable

ATTENTION

!If the cable has a shield, it must be grounded at one end only.



.

Terminating Resistors

Terminating resistors are necessary at the ends of trunk lines to reduce reflections of the communication signals on the network. The DeviceNet network will operate correctly only when there are exactly two terminating resistors, one at each end of the trunk line. Terminating resistors must be equal to 121 ohms 1%, 1/4W, metal film (terminating resistor part number 1485A-C2).

MCC line-ups ship with a clear bag containing 2, five-terminal plug connectors with terminating resistors installed and two DeviceNet splitter connectors (kit part number 2100H-DNTR1). The resistors are inserted in the second terminal from each end (connected to the white and blue conductors) of both plugs (See Figure 4). The DeviceNet splitter connector is used to plug two DeviceNet connectors into one wireway port.

IMPORTANT It is not recommended to use both Class 1- and Class 2-rated cables within the same DeviceNet system. These two cable types are not compatible because the following properties are different:

• Insulation class• Overcurrent protection requirements• Network transmission

Using Class 1- and Class 2-rated cables within the same DeviceNet system can result in application, code, and communication problems.

ATTENTION

!Before performing any service or maintenance activities on MCC sections, disconnect all power sources.



Figure 4 Five-terminal Plug Connector, Plug Number 22112-215-01, with jack screws

The bag is attached to a wireway tie bar, in the vertical wireway of the section that contains documentation (identified by a label on the horizontal wireway cover of this section). The vertical wireway door of this section will also have an identifying label: “DEVICENET TERMINATING RESISTOR KIT LOCATED BEHIND THIS DOOR” (See Figure 5). If the section does not contain a vertical wireway, the bag will be attached to a wireway tire bar on the right hand side of the section and the label will be located on the door of the section.

Jack Screw Jack Screw

Terminating Resistor

Black

BlueWhite

Red

Shield wire, ground shield at one end only



Figure 5 DeviceNet Terminating Resistor Kit

Terminating Resistor KitPart # 2100H-DNTR1



Installing Terminating Resistor Guidelines

When installing terminating resistors, apply the following two rules:

1. Use only two terminating resistors in any network

2. Install terminating resistors at the ends (communication and/or physical) of the trunk line

Incorrect placement of terminating resistors and/or using more than two will cause improper network operation and result in communication losses.

For visibility, accessibility, and safety, the ideal locations for terminating resistors within a DeviceNet MCC are the vertical wireway ports closest to the physical ends of the total trunk line. In a leftmost section, this is the topmost port; in a rightmost section, this is the bottommost port (see example below). When connecting a DeviceNet MCC to remote equipment, the trunk line may end at a device, such as a PLC card. In these instances, a terminating resistor should be installed in the final connector to that device.

IMPORTANT The portion of the MCC trunk line that is to the left of the leftmost terminating resistor and to the right of the rightmost terminating resistor is considered drop cable and must be included in the total drop cable calculations. See Calculating Cable Lengths.

Topmost Port

Bottommost Port

When the rightmost section is one end of the trunk line, install the terminating resistor in the bottommost port

When the left is one end of the trunk line, install the terminating resistor in the topmost port

Cable to the left of the terminating resistor is now drop cable.

Cable to the right of the terminating resistor is now drop cable.



Installing Terminating Resistor Examples

When installing resistors the type of DeviceNet Architecture must first be determined. There are two types of architecture.

• All devices internal to the MCC• Devices internal and external to the MCC

Installing Terminating Resistors with all Devices Internal to the MCC

This architecture is the simplest. Since all devices are internal to the MCC, no special wiring needs to be done.

Figure 6, Figure 7 and Figure 8 show typical designs and placements of terminating resistors.

Figure 6 shows an MCC with a DeviceNet scanner located in a section with no plug-in units. In this section there are no wireway plugs.

Figure 6 DeviceNet scanner installed in a section; no other plug-in unitsOne DeviceNet Network

DeviceNet Scanner



Figure 7 shows a typical MCC with the DeviceNet scanner located in a plug-in unit.

Figure 7 DeviceNet scanner installed in a plug -in unit One DeviceNet network

Figure 8 shows an MCC with two DeviceNet scanners and two different networks. When an MCC has two networks, four terminating resistors are needed.

Figure 8 DeviceNet scanner installed in a plug-in unitTwo DeviceNet networks

DeviceNet Scanner

DeviceNet Scanners

Do not splice trunk lines between two separate DeviceNet networks

First DeviceNet Network Second DeviceNet Network



Installing Termination Resistors with Devices Internal and External to the MCC

This architecture is more complex, because external devices must be wired to the internal network of the MCC. Careful attention must be given to the type of cable selected and the method of installation.

Figure 9, Figure 10, Figure 11 and Figure 12 show where to place the terminating resistors when external devices are used.

Figure 9 has a DeviceNet scanner remote from the MCC. In this example the cable from the scanner to the MCC wireway port is an extension of the DeviceNet trunk.

Figure 9 DeviceNet scanner remote from MCCOne DeviceNet network

DeviceNet Scanner



Figure 10 shows a single MCC with two DeviceNet networks and two remote scanners. When an MCC has two networks, four terminating resistors are needed. In this example the cable from the scanner to the MCC wireway port is an extension of the DeviceNet trunk.

Figure 10 DeviceNet scanner remote from MCCTwo DeviceNet networks

DeviceNet Scanners

Do not splice trunk lines between two separate DeviceNet networks

Second DeviceNet NetworkFirst DeviceNet Network



Figure 11 show two MCC lineups connected as one network with one remote scanner. The cable connecting to the two MCCs must be trunk cable. Also, the cable from the scanner to the MCC wireway port is an extension of the DeviceNet trunk.

Figure 11 DeviceNet scanner remote from MCCsOne DeviceNet network; divided MCC line-up

DeviceNet Scanner



Figure 12 shows a remote scanner and a remote device. This is a single network and all cable external to the MCC must be trunk cable.

Figure 12 DeviceNet scanner remote from MCCsOne DeviceNet network

PowerFlexDrive

DeviceNet Scanner



NOTE: If the terminating resistor is being placed at a device which is remote from the MCC, it will be necessary to remove the resistor from the supplied plug and installing it in an open row of terminals on a ten-terminal plug.

Adding a Motor Control Center Unit to a DeviceNet System

General

Use this section to add Bulletin 2100 units to a DeviceNet MCC. Each DeviceNet component is factory wired within the unit and has a communication cable that plugs into the device on one end and generally into a vertical wireway DeviceNet port on the other end.

Procedure

For a CENTERLINE MCC with a Class 1 DeviceNet cabling system:

1. Determine the proper length of patch cable by measuring from the DeviceNet device in the unit to the DeviceNet port in the vertical wireway.

Terminating Resistor

Ten-terminal plug connector with terminating resistor plugged into a DeviceNet module

Shield wire if used

Terminating resistor position in open row of terminals on a ten-terminal plug connector

ATTENTION

!Before performing any service or maintenance activities on MCC units or sections, disconnect all power sources



NOTE: Cable can be made as short as is practical, since excessive drop lengths can lower data transmission rates. Refer to DeviceNet Selection Guide, publication DNET-SG001x-EN-P, for specific design parameters.

2. Cut the cable to the desired length by removing material from the end of the cable that has no connector plug. Strip the cable and attach the separate five-terminal plug connector. The wire is color coded for simplified wiring.

3. Plug the one connector into the DeviceNet component in the unit. Plug the other plug connector into the DeviceNet port in the vertical wireway. Torque the screws on both connectors to 5 lb.-in. (0.55 Nm).

4. If there is a need to plug in more devices than available DeviceNet ports in the vertical wireway use a DeviceNet splitter connector (Catalog Number: 1485P-P1J5-UU5 or Part Number 42122-304-51). This allows two devices to be plugged into one port.

Figure 13 Connecting the unit DeviceNet cable to the DeviceNet port in the back of the vertical wireway

Splicing DeviceNet Communication Cables in Motor Control Centers

General

This section describes the recommended procedure for splicing DeviceNet communication cables (trunk lines) in MCCs. It must be used in conjunction with publication 2100-IN010x-EN-P, Joining and Splicing Vertical Sections. Cable can be spliced to the leftmost or rightmost section of an MCC lineup.



Procedure

1. Join the sections, following steps 1 through 7 on pages 1 and 2 of publication 2100-IN010x-EN-P. To access splice connections, remove the red bus cover through the vertical wireway opening.

2. Splice the horizontal bus, following steps 1 through 4 on pages 10 through 11 of publication 2100-IN010x-EN-P. Do not replace covers or plates at this time.

3. To splice DeviceNet trunk lines between separate sections, connect the linking plug from the right section into the left section linking receptacle. Torque connector screws to 5 lb.-in. (0.6 Nm).

4. When joining new sections to an existing MCC, remove the terminating resistor from the original final section (the one to which new sections were just spliced). Install the terminating resistor according to the information supplied in the sections “Terminating Resistors” and “Installing Terminating Resistors” beginning on page 8.

5. Follow step 5 on page 11 of publication 2100-IN010x-EN-P.

6. When new sections are added, always do the following design calculations:• Check the total number of nodes. See System Architecture beginning

on page 2. If the number of nodes exceeds the guidelines, add a network.

• Recalculate the total power consumption. If it exceeds 8 A, add a power supply.

• Verify the cumulative trunk length. See System Architecture.• Verify the cumulative drop length. See System Architecture



Figure 14 MCC Section (Series M)

Figure 15 MCC Section (Series L)

DeviceNet Trunk line

Typical single MCC section (Series M)

Front view of DeviceNet splice (Series M)

3-phase horizontal power bus

Linking Plug

Linking Receptacle

Linking Receptacle

3-phase horizontal power bus

Linking PlugDeviceNet Trunk line

Typical Single MCC Section (Series L)

Front view of DeviceNet splice (Series L)



DeviceNet Power Supply

A power supply unit that meets all DeviceNet requirements can be supplied with the MCC—catalog number 2100-DPS__ (consult your local Rockwell Automation salesperson or Allen-Bradley distributor). It is available in three configurations: with circuit breaker or fusible disconnect and control transformer; or with no disconnecting means, requiring a separate 110–120 V source. Redundant configurations are also available. A cable connects the output of the power supply to a DeviceNet port in the back of the vertical wireway. The cable is already connected when the power supply unit ships installed in the MCC.

Remote power supplies should meet the following requirements, per ODVA:

• Rated 24 Vdc (±1%)• Rise time of less than 250 milliseconds to within 5% of 24Vdc at full

load of 8 amps• Current limit protection of 8 amps continuos and 10 amps for the first

250 mSec• Sized correctly to provide each device with its required power—each

device typically requires 90–165 mA • Derated for temperature using the manufacturer’s guidelines

Connecting Power Supplies—Remote or in the MCC Line-Up

Connecting power supplies according to these guidelines will minimize voltage drops in the DeviceNet system and ensure proper supply voltage to system devices. Refer to the Media Design Installation Guide, DNET-UM072x-EN-P, for detailed connecting instructions.

Series M Sections

For line-ups with more than eight sections, connect the power supply to the DeviceNet system within one section, either way, of the middle of the line-up.

IMPORTANT The DeviceNet cable system requires a 24Vdc power source to operate. The power supply must:

• Meet NEC Class 1 requirements as outlined in Article 725

• Be DeviceNet compatible as specified in the ODVA requirements

IMPORTANT: Power supplies that do not satisfy both points listed above can result in damage to the DeviceNet signal and components, as well as failure to comply with NEC, local codes, and inspection.



For line-ups with eight or fewer sections, connect the power supply to the DeviceNet system where it is convenient (no location restrictions).

Series L Sections

Connect the power supply to the DeviceNet system where it is convenient (no location restrictions).

Network Grounding at the Power Supply

The DeviceNet cable must be grounded at only one location. The ideal choice is at the power supply. Ground the power supply and 24 Vdc common (black wire) using #8 AWG wire.

Best Grounding Practice

• If the power supply comes installed in the MCC, the black 24 Vdc common terminal is grounded within the unit. To improve the grounding, use #8 AWG green wire and ground the black 24Vdc common terminal to a very stable ground external to the MCC (or to an optional TE ground inside the MCC).

• If the power supply is external, the same grounding recommendations apply.



Connecting Two Power Supplies

An additional 24 Vdc Class 1 power supply must be installed for MCC line-ups with more than 17 sections. When using two supplies, the red conductor between the power supplies must be broken. Locate a linking connector between sections and disconnect the red conductor (See Figure 16).

Ground only ONE of the two power supplies.

Figure 16 Connecting Two Power Supplies

Position each power supply to ensure that it feeds a maximum of eight sections to the left or right (refer to the sample line-up below).

MCC line-ups with more than 17 sections could exceed the 75 meters (246 feet) trunk length limit to support 500 kbps communications. When the trunk length exceeds this limit, 250 kbps communications should be specified.

Power SupplyPower Supply

Red V+

White CAN_H

Blue CAN_L

Black V- (common)

BREAK

Power SupplyPower Supply

Motor Control Center line-up with more then 17 sections

Break Red Conductor



Start-Up and Training Aids IntelliCENTER MCC Design, Start-Up and Training Course

Course Description

This course provides the concepts, knowledge and tools necessary to design, specify, install, troubleshoot, and use an IntelliCENTER MCC or DeviceNet MCC.

Content

• Basics of communication and Rockwell Automation networks• Control and communication architecture overview with sample

architecture problems solved in class (selecting networks, network devices, network speeds, etc.)

• DeviceNet MCC structure, units and wiring technical details for both low voltage and medium voltage MCCs

• Demonstration of software associated with DeviceNet MCCs (RSLinx and RSNetworkx for DeviceNet)

• Necessary steps for a successful start-up including installing EDS files• Maintenance issues, such as adding MCC units to IntelliCENTER

MCCs, replacement of DeviceNet devices and reommended tools• Network configuration, mapping of scanners, and PLC programming in

a DeviceNet MCC system, including hands-on exercises with a ControlLogix system

Who Should Attend

This course is intended for control engineers, electrical technicians and system integrators who will be involved in designing, installing and using IntelliCENTER/DeviceNet MCCs.

Prerequisites

Familiarity with Windows and PLC programming



Topical Outline

Course Dates and Prices

Refer to www.rockwellautomation.com/trainingSelect course CCI 105.

Field Support Kit for DeviceNet MCCs

The Allen-Bradley DeviceNet and IntelliCENTER MCCs provide users with a DeviceNet network that is wired, commissioned and tested, resulting in a true plug-and-play integrated solution. As with any control system, through a successful installation requires the proper tools. This kit includes an assortment of DeviceNet-related components that will prove helpful for:

• Starting up a DeviceNet system• Commission DeviceNet nodes (setting baud rate and node number)• Testing DeviceNet devices• Training on DeviceNet

• Basics of DeviceNet• NetLinx Overview• RSLinx and RSNetworkx • DeviceNet wiring• Receiving and installing

DeviceNet MCC sections• IntelliCENTER software

configuration• Installing and registering EDS

files• Adding MCC units to

IntelliCENTER MCCs

• Replacement of DeviceNet devices

• Hands-on IntelliCENTER lab• Support resources• Mapping scanners -

introduction, examples, hands-on

• Programming PLCs connected to DeviceNet - introduction, examples, hands-on with a ControlLogix system



The kit includes a mini network, a DeviceNet configurator tool and assorted components.

Mini Network

• Trunk line with three DeviceNet ports and terminating resistors

• 10 foot patch cable• 1.5 foot patch cable• 24 Vdc power supply

DeviceNet Configurator Tool

• DeviceView Handheld Configurator (193-PCT) with 1 meter cable

Assorted Components for DeviceNet

• (5) Terminating Resistors• (10) 5-Terminal Plug Connectors• (5) 10-Terminal Plug Connectors• (2) 5-Terminal Male Connectors• 10 foot Round Class 1 DeviceNet

Cable • Narrow-tip Screwdriver for

DeviceNet Connectors• DeviceNet Y-Header



Applications

Mini-network wall plug (with male connector)

DeviceNet Configurator (or laptop computer) Configurator

cable

10-terminal plug with terminating resistor plugged into a port

1.5 foot or 10 foot patch cable (with connectors)

10-terminal plug with terminating

resistor

Mini Network

Connecting to a DeviceNet MCC

10 foot patch cable (with connections)

Laptop computer with 1784-PCD

DeviceNet card and cable (not included)

Mini-network wall plug power supply (with male connector)

E3 Electronic Overload Relay (not included)

Configurator cable

1.5 foot patch cable (with connectors)

DeviceNet ConfiguratorInternal terminator resistor programmed “IN”Y-Header (splitter)

Stand Alone Configurator Tool

DeviceNet Device

(not included)



The following items are suggested for IntelliCENTER and DeviceNet MCC installation and maintenance:

• Field Support kit for DeviceNet MCCs, 2100H-DFSK1• Hand tools—high-quality side-cutter, needle nose pliers, wire stripper• Short length of Class 1, 8 A round adapter cable with five-terminal

receptacle on each end• Ten foot (3 m) personal computer (PC) cable with five-terminal plug on

each end—part number 2100H-ICPC120• Digital multi-meter—Fluke 79 or equivalent• ODVA DeviceNet monitor — order form available at

http://www.ab.com/intellicenter/instructions or contact product support

• Laptop personal computer with the following software:– RS Networx for DeviceNet– RS Linx– ControlFlash update software– RS Logix 5 for PLC/5– RS Logix 500 for SLC and MicroLogix– RS Logix 5000 for ControlLogix– IntelliCENTER software

Training Cases

For the ultimate in-house training - two styles of IntelliCENTER training cases are available

2-Unit Training Case

• Starter with E3 electronic overload relay

• Starter with DeviceNet Starter Auxiliary

• Motor• Load

1-Unit Training Case

• Starter with E3 electronic overload relay

• Load for each phase



System Design Installation Checklist

When installing a DeviceNet MCC, use the following checklist before applying power to the network:

• Number of nodes does not exceed 64, with three nodes reserved for scanner (node 00), PC (node 62), and new device (node 63)

• Individual drop lengths do not exceed 20 feet (6 m)• Cumulative drop length does not exceed the desired network baud rate

limit: 128 feet (39 m) at 500 kbps, 256 feet (78 m) at 250 kbps or 512 feet (156 m) at 125 kbps

• Total trunk length does not exceed the maximum allowable per the network baud rate: 246 feet (75 m) at 500 kbps, 656 feet (200 m) at 250 kbps, or 1378 feet (420 m) at 125 kbps

NOTE: For IntelliCENTER, 500 kbps provides optimum performance, but 250 kbps may be used (125 kbps is not recommended).

• Verify that all devices are programmed to the same baud rate. Autobaud can be used for each device. The scanner will then set the baud rate for the entire system

• Verify that terminating resistors are in place at the trunk line terminations and measure for proper resistors (121 ohms, 1/4 W, 1%, metal film)

• Verify that the power supply for the system is 24 Vdc• Total power load and distribution points do not exceed 8 A• The system has one, and only one, earth ground for the V-• There is an earth ground connection• All connections are inspected for loose wires, opens, and shorts

DeviceNet Software Installation Checklist

The following general steps, along with references for more information, are provided to assist with the DeviceNet software installation process.

1. Install the communication card in your personal computer.

2. Load the Windows hardware drivers for the communication card.

3. Load RSNetworx™ for DeviceNet and RSLinx software.

4. Configure the RSLinx driver.– Within the RSWho function, make sure no unrecognized devices (i.e.,

“?” symbols) appear for any devices. If an unrecognized device appears, load the Electronic Data Sheet (EDS) file. See the “How to Find Electronic Data Sheets (EDS)” section below for further details.



5. Use RSNetworx for DeviceNet to program and configure devices (e.g., full load current, acceleration rate, etc.).

Do not download to a device before uploading from that device. Otherwise, the node and baud rates will be overwritten, requiring each device to be individually manually reprogrammed.

Make sure to set communication-loss behavior for each device.

6. Use RSNetworx for DeviceNet to program the DeviceNet scanner.

7. Write the PLC program.

8. If IntelliCENTER software is provided, load per the IntelliCENTER Software User Guide (publication 2100-UM002x-EN-P).

How to Find Electronic Data Sheets (EDS)

Background

After installing IntelliCENTER software, an Electronic Data Sheet (EDS) file must be registered for each unique device in the MCC. This section details how to perform that task.

IMPORTANT Do not leave the RSWho constantly browsing. Be sure to close the RSWho screen or disable the Autobrowse.

IMPORTANT RSNetworx for DeviceNet can also be used to change baud rates and node numbers, but remember that the devices are normally pre-programmed at the factory.

IMPORTANT When using a 2100-GK61 communication module, keep in mind there are two extra bytes of receive data for the inputs on the 2100-GK61. Make sure the number of bytes in the scanner configuration corresponds with the number of bytes in the device. See the 2100-GK61 user manual (publication 2100-UM001x-EN-P, chapter 4) for more details.



Definition of EDS Files

EDS files are simple text files used by network configuration tools—such as RSNetworx, and IntelliCENTER software—to help identify products and easily commission them on a network. EDS files describe a product’s device type, product revision, and configurable parameters on a DeviceNet network.

Necessary EDS Files

For IntelliCENTER MCCs the data CD contains a directory (:\\\EDS) of all EDS files necessary for the devices in your IntelliCENTER. The EDS files will be automatically registered by the installation program.

For IntelliCENTER and DeviceNet MCCs, a separated “EDS file” CD is provided. This CD contains EDS files for all DeviceNet products found in MCCs.

Installing EDS Files

The EDS files are installed with a program from Rockwell Software that is also on the IntelliCENTER data CD (in the same directory as the EDS files). This program is called “RSHWare.exe.”

To install the EDS files:

1. Run the program RSHWare.exe.

2. Click Add/Remove.

3. Select Register an EDS file. Click Next.

4. Select Register a directory of EDS files.

5. Browse to the EDS directory on the data CD.

6. Click Next.

7. The Installer will display the test results. Click Next to continue.

8. The Installer will allow you to change the graphic image for each device. Click Next to continue.

9. The Installer will display the final task summary. Click Next to continue.

10. Click Finish when completed.



Finding EDS Files for Other Devices

EDS files can be obtained at http://www.ab.com/networks/eds.

Uploading EDS file from the Device RSNetworx for DeviceNet can also be used to upload an EDS file directly from the device. If an EDS file cannot be found by other methods, refer to the RSNetworx help file for steps to upload an EDS file.

Uploading EDS Files from the Device

RSNetworx for DeviceNet can also be used to upload an EDS file directly from the device. If an EDS file cannot be found by other methods, refer to the RSNetworx help file for steps to upload an EDS file.

www.ab.com/mcc

Publication 2100-TD019C-EN-P—March 2006 PN-2516234Supersedes Publication 2100-TD019B-EN-P—May 2003 Copyright © 2006 Rockwell Automation, Inc. Printed in the U.S.A.

www.ab.com/mcc

Intro

Details of the Rockwell Automation Print Specifications sheet

This print specifications sheet is designed with multiple purposes.- It is a vehicle to get the most accurate print specifications to RA-approved print vendors.- It provides authors with an explanation of all necessary fields to complete before attaching the sheet to your PDF.- It provides separate tabs so that an author can fill in all fields related to the publication on the Generic tab or publication-specific template-type tabs to minimize the number of fields an author must complete.

To facilitate the most efficient use of this sheet, we recommend that you click on the publication-specific tab that most closely fits you publication and use that to complete the print specifications.

IMPORTANT: Because this sheet was constructed using a sheet that RR Donnelley (RRD) uses to load print specifications, there are some columns hidden. For example, the first field you must complete is Column E, or Publication Number. Columns A to D are used for RRD purposes and with information only representatives of that RA-approved printer can complete.

DO NOT delete any hidden columns from the tab you choose to use.

Definitions of Each Tab in Sheet

Generic pub print specsSingle sheet with all required columns for necessary specifications. None of the columns are completed. All must be completed before attaching the sheet to your PDF.

This tab has 44 blank fields you must complete via free text type or pull-down menus.

IN, RN pub type specsTemplates with many fields already completed according to typical default settings. We intend you use this tab with publications similar to installation instructions (IN) and release notes (RN). However, you can use this sheet for other publications that are similar to INs and RNs.

This sheet has 31 fields already completed and, if your publication uses the default values already completed, you must complete the additional 13 fields.

UM, RM, PM pub type specsTemplates with many fields already completed according to typical default settings. Use this tab with publications similar to user manuals (UM), reference manuals (RM) and programming manuals (PM). However, you can use this sheet for other publications that are similar to UMs, RMs and PMs.


AP, PP pub type specsTemplates with many fields already completed according to typical default settings. Use this tab with publications similar to application solutions (AP) and product profiles (PP). However, you can use this sheet for other publications that are similar to APs and PPs.


BR pub type specsTemplates with many fields already completed according to typical default settings. Use this tab with publications similar to brochures (BR). However, you can use this sheet for other publications that are similar to BRs.


Field definitionsDescription of information fields used throughout the spreadsheet tabs that may not be immediately obvious to a user.

Attach Print Specs to PDF

For Acrobat 7.0, follow these steps:1. Open the PDF.2. Click on the Attachments tab next to the publication's bookmarks. A new section appears at the bottom of the PDF.3. Click on the Add button in the bottom section of the PDF.4. Browse to the MS Excel file with the print specs and add them to the PDF.

For Acrobat 6.0, follow these steps:1. Open the PDF.2. Go to the backcover of the PDF.3. Click on the Tools pull-down menu.4. Click on this sequence of menu options - Advanced Commenting, Attach, Attach File Tool. A paper clip appears.5. Click to put the paper clip somewhere on the backcover. The browse window appears.6. Browse to the MS Excel file with the print specs and add them to the PDF.

IMPORTANT: If you are using Acrobat 5.0 or earlier, please upgrade. If you are using Acrobat 8.0, please contact RRD about attaching print specs because RA has not tested this software version yet.

Generic pub print specs

IN, RN pub type specs

UM, RM, PM pub type specs

AP, PP pub type specs

BR pub type specs

Field definitions

Generic pub print specs

Corp #17501

Bill To69

dPrint?Content/Comp #Split Shipment Indicator FlagWCSS Item NumberCustomer Item NumberItem DescriptionProducing PlantJob NumberReplenishing PlantPlant CodeProduct CodePackaging/Ordering UOMQty per Packaging/Ordering UOMList Price Per EaTransfer Cost per EaSell Price per EaStandard Cost (per Ea)Min Order Qty (in eaches)Multiple Order Qty (in EachesChargeback PriceItem Reference #1Item Reference #2Revision FieldMax Order Qty (in eaches)Sequentially Numbered Item?Sequentially Numbered Item - DetailsPriced for Digital or OffsetContent File LocationItem Category Form (F) Book (B)Item SubtypeOrientationSides PrintedCSS/JLS Stock ComponetPaper Size WidthPaper Size LengthNo of Forms to a SheetPage QtySheets QtyCSS/JLS Production StockPaper Stock TypePaper Stock WeightPaper Stock ColorStack OffsetTab Size# of TabsBinder SizeBinder ColorBinder Ring TypeBinder Transparency (clearview or matt)Thermal Tape ColorTrim Size WidthTrim Size LengthStitching LocationDrilling SizeDrilling LocationGlue Location# / PadFold TypeFold At# / Poly# / BoxCommentsCross Reference Item Number 1

Publication NumberPublication TitlePackaging/Ordering Unit Of MeasureQty per Packaging/Ordering Unit of MeasureMin Order QtyMultiple Order QtyBusiness GroupCost CenterRevision DateMax Order QtyItem CategoryForm (F) or Book (B)Binding/StitchingOrientationSides PrintedPrinting Paper Size WidthPrinting Paper Size LengthNumber of Forms to a SheetPage Count of PublicationNumber of Sheets Required to PrintCSS/JLS Production StockPaper Stock TypePaper Stock WeightPaper Stock ColorStack OffsetTab SizeNumber of Tabs NeededBinder SizeBinder ColorBinder Ring TypeBinder TransparencyThermal Tape ColorFinished Trim Size WidthFinished Trim Size LengthStitching LocationDrill Hole SizeNumber and Location of Drill HolesGlue LocationNumber of Pages per PadFold TypeFold AtNumber of Pieces per Poly wrapNumber of Pieces per BoxCommentsPart Number

Are these items being setup on dPrint? (Yes or No). If yes, Inv Mgmt to check "Print Management" flag on item setup.The content/Comp # will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item #). The content/comp# must be hardcoded to the Item message Field in WCSS. Must be a 10 Digit number that starts with an 8.Required. Setting this to yes will allow warehouse product to ship out before the JIT item is completed. Setting this to no will hold all warehoused items until the printing of this item is complete. Please indicate Y or N.** Note: Each item with a Y will always ship separately even if produced at the same time as like items.Optional. 15 Characters Max. If the WCSS number provided already exists in the system, then Inventory Management will assign a random WCSS number.30 characters maximum.Cannot use quote symbol, that is--"--.Required. Which plant/Print Center will produce this item?Required. To be provided from the producing plant for JIT s/uRequired: What is the plant code of the plant that has owning rights to the dPrint files? If produced at multiple plants there can be only one owning plant.Required. What is the plant code of the facility that will produce this item? (see "Plant and Whse Codes" tab below)Required. Enter one of the applicable product.Method of packaging for publication shipment

Click here for explanation of each value in the pull-downRequired. This field auto-calculates (transfer cost divided by .5). Used to determine Standard Cost on WCSS (which is 50% of the list price for these product codes).Required. Transfer Cost per ordering/packaging unit of measure.Required. Price that will be billed to customer upon order. If Price Breaks, enter "Price Breaks" and note them on separate spreadsheet.Required. Replacement Cost per Packaging/ordering UOM.Click here for an explanation of this field; otherwise, type NA.Optional. Used to assist customer with internal Chargebacks to end users. (per packaging/ordering UOM)IMPORTANT: This information must match the DocMan record.

Click here for explanation of each value in the pull-down menu.IMPORTANT: This information must match the DocMan record.IMPORTANT: This information must match the DocMan record.

Date on the publication.Click here for explanation of each value in the pull-down menu.Indicate Yes or No. Enter Yes if the item is a sequentially numbered item.Describe the details behind the sequentially numbered item, such as:- Record Sequence Shipped: whse will record the sequence numbers that shipped- Ship in Sequence Record: required to ship products in particular sequence and the whse records the numbersRequired: Enter the word DIGITAL or the word OFFSET, which ever one describes the production pricing used for this itemRequired: If PDF is to be retained in the DAS enter DAS in this field, if item is part of eCreate or Custom Docs put CUSTOM in this field.Typically a Book.

Click here for explanation of each value in the pull-down menu.Click here for explanation of each value in the pull-downClick here for explanation of each value in the pull-down menu.Optional: Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book.IMPORTANT: Not Trim Size width

This is the width of the paper on which the publication is printed.IMPORTANT: Not Trim Size length

This is the length of the paper on which the publication is printed.Click here for explanation of how to determine the information required.Click here for explanation of how to determine the information required.Optional: Use when product is being printed on Shell Stock. Provide warehoused WCSS Item nu,mber of product to be used in the production of JIT item.Click here for explanation of how to determine the information required.The pull-down menu lists the most common choices.

Click here for a full list of the available choices.

If you use a choice not in the pull-down list, type the value in the cell below the pull-down menu.If item uses tabs; otherwise, NA.If needed; otherwise type NA.If item used in a binder; otherwise, NA.If item used in a binder; otherwise, NA.If item used in a binder; otherwise, NA.If item used in a binder; otherwise, NA.If publication is thermal tape bound; otherwise, NA.Click here to see the available finished trim sizes.

The sizes are listed - width x length.Click here to see the available finished trim sizes.

The sizes are listed - width x length.If publication is Book [B] and stapled; otherwise, NA.Click here for a list of possible drill locationsIf publication uses padding; otherwise, NA.If publication is a notepad or message pad; otherwise, NA.Click here for explanation of each value in the pull-down menu.Click here for explanation of each value in the pull-down menu.Use this column to list:- Cover Stock- Text Stock- Cover Ink- Text Ink

Also use to indicate any other production or finishing requirements not provided in previous columns

Click here for an explanation of the available Cover Stock, Cover Ink and Text Ink values.List only if pubication is used in manufacturing; otherwise, leave blank.

See DocMan for the Cost Center selections associated with each Business Group.RRD must provide this informationRRD must provide this informationRRD must provide this informationRRD must provide this information

&CItem Setup Sheet for Conversion Transfers

&LJIT-D-print Spreadsheet&CREF046&R&D &T

Click here for explanation of each value in the pull-down

Method of packaging for publication shipment


IMPORTANT: This information must match the DocMan record.

Click here for explanation of each value in the pull-down menu.


Typically a Book.



Click here for explanation of how to determine the information required.



The pull-down menu lists the most common choices.


If you use a choice not in the pull-down list, type the value in the cell below the pull-down menu.

Click here to see the available finished trim sizes.

The sizes are listed - width x length.



Click here for a list of possible drill locations



Use this column to list:- Cover Stock- Text Stock- Cover Ink- Text Ink


Click here for an explanation of the available Cover Stock, Cover Ink and Text Ink values.

Click here for an explanation of this field; otherwise, type NA.

IN, RN pub type specs
















2100-TD019C-EN-PDeviceNet Motor Control Centers (MCCs)EAMarketing CommercialCMKMKE Intelligent Motor Control - 1900903/01/20065BSADDLEPORTRAITHEAD2HEADRRD must provide this informationRRD must provide this information4369PLAIN20#WhiteRRD must provide this informationNANANANANANANA8.511SIDENANANANANANARRD must provide this informationText Stock = 20# White Opaque BondText Ink = Black, 8.5 x 11 saddle stitch. Cover Stock = 90#.25162







Typically a Book.




















UM, RM, PM pub type specs
















2100-UM003D-EN-PIntelliCENTER How to Contact Us CardEA1Marketing Commercial1900911/01/20015FNALANDSCAPEHEAD2HEADRRD must provide this informationRRD must provide this information121CARD110#WhiteRRD must provide this informationNANANANANANANA7.39NANAnaNANANANARRD must provide this informationRed Bleed across top of front and backText Stock = 110# WhiteFinal page size 7.3 (w) x 9.0 (h)Text Ink = BlackNA







Typically a Book.




















AP, PP pub type specs
















PK1See DocMan for the Cost Center selections associated with each Business Group.NAPORTRAITHEAD2HEADRRD must provide this informationRRD must provide this informationGLOSS TEXT80#WhiteRRD must provide this informationNANANANANANANA8.2511NANANANANARRD must provide this informationNANA







Typically a Book.




















BR pub type specs

dPrint?Content/Comp #Split Shipment Indicator FlagWCSS Item NumberCustomer Item NumberCannot use quote symbol, that is--"--.Producing PlantJob NumberReplenishing PlantPlant CodeProduct CodePackaging/Ordering UOMQty per Packaging/Ordering UOMList Price Per EaTransfer Cost per EaSell Price per EaStandard Cost (per Ea)Min Order Qty (in eaches)Multiple Order Qty (in EachesChargeback PriceItem Reference #1Item Reference #2Revision FieldMax Order Qty (in eaches)Sequentially Numbered Item?Sequentially Numbered

Documents

DeviceNet Motor Control Centers (MCCs) · 2019. 8. 15. · To achieve maximum performance of an IntelliCENTER MCC, 500K baud should be used. 50 50 Baud Rate Trunk Drop(2) (2) No single