Modular DeviceNet Starter Auxiliary I/O · 2014. 12. 11. · Figure 1.3 Modular DSA I/O System Mounted on DIN Rail The Modular DSA I/O System provides specially designed modules that

Modular DeviceNet Starter Auxiliary™ I/OBulletin 198 Series C

User Manual

Important User InformationBecause of the variety of uses for the products described in this publication, those responsible for the application and use of this control equipment must satisfy themselves that all necessary steps have been taken to assure that each application and use meets all performance and safety requirements, including any applicable laws, regulations, codes and standards.

The illustrations, charts, sample programs and layout examples shown in this guide are intended solely for purposes of example. Since there are many variables and requirements associated with any particular installation, Allen-Bradley does not assume responsibility or liability (to include intellectual property liability) for actual use based upon the examples shown in this publication.

Allen-Bradley publication SGI-1.1, Safety Guidelines for the Application, Installation and Maintenance of Solid-State Control (available from your local Allen-Bradley office), describes some important differences between solid-state equipment and electromechanical devices that should be taken into consideration when applying products such as those described in this publication.

Reproduction of the contents of this copyrighted publication, in whole or part, without written permission of Rockwell Automation, is prohibited.

Throughout this manual we use notes to make you aware of safety considerations:

Attention statements help you to:

• identify a hazard• avoid a hazard• recognize the consequences

Allen-Bradley, RSNetWorx, PLC, SLC, Distributed Starters, and Modular DSA are registered trademarks of Rockwell Automation

DeviceNet is a trademark of the Open DeviceNet Vendor Association (ODVA).

ATTENTION

!Identifies information about practices or circumstances that can lead to personal injury or death, property damage or economic loss

IMPORTANT Identifies information that is critical for successful application and understanding of the product.

European Union Directive ComplianceIf this product has the CE mark it is approved for installation within the European Union and EEA regions. It has been designed and tested to meet the following directives.

EMC DirectiveThis product is tested to meet Council Directive 89/336/EEC Electromagnetic Compatibility (EMC) using the following standards, in whole or in part, documented in a technical construction file:

• EN 50081-2 EMC — Generic Emission Standard, Part 2 — Industrial Environment• EN 50082-2 EMC — Generic Immunity Standard, Part 2 — Industrial Environment

This product is intended for use in an industrial environment.

Low Voltage DirectiveThis product is also designated to meet Council Directive 73/23/EEC Low Voltage, by applying the safety requirements of EN 60947-5-1 — Low Voltage Switchgear and Control Gear — Control Circuit Devices and Switching Elements — Electromechanical Control Circuit Devices.

This equipment is classified as open equipment and must be mounted in an enclosure during operation to provide safety protection.

Publication 198-UM002A-EN-P December 2001

Preface

Manual ObjectivesThe purpose of this manual is to provide you with the necessary information to apply the Bulletin 198 Modular DeviceNet™ Starter Auxiliary (Modular DSA I/O System). Described in this manual are methods for installing, configuring, and troubleshooting the Bulletin 198 System of components.

Intended AudienceThis manual is intended for qualified personnel responsible for the setup and service of these devices. You must have previous experience with and a basic understanding of communications terminology, configuration procedures, required equipment, and safety precautions.

You should understand the DeviceNet™ network operations, including how slave devices operate on the network and communicate with a DeviceNet™ master.

You should be familiar with the use of the RSNetWorx™ for DeviceNet™ Software (Cat. No. 9357-DNET L3) for network configuration. This software package is referred to often in this manual.

IMPORTANT Read this manual in its entirety before installing, operating, servicing, or configuring the Bulletin 198 Modular DSA I/O System.

IMPORTANT Read the DeviceNet™ Cable System Planning and Installation Manual, Pub. No. 1485-6.7.1, in its entirety before planning and installing a DeviceNet™ System. If the network is not installed according to this document, unexpected operation and intermittent failures can occur.

If this manual is not available, please contact either the local Allen-Bradley Distributor or sales Office to request a copy. Copies may also be ordered from the Rockwell Automation Bookstore. The Bookstore can be contacted via the Internet from the Allen-Bradley home page at http://www.ab.com.

Preface vi


VocabularyNote the following references throughout this manual:

• Bulletin 198 with its options is referred to as the Modular DSA I/O System or MDSA.

• DeviceNet is referred to as Dnet or DNET.• The Programmable Logic Controller is referred to as the Programmable controller,

PLC controller, or SLC controller.• Earth Ground is referred to as GND.• The National Electrical Code is referred to as NEC.

Reference Manuals

ATTENTION

!Only personnel familiar with DeviceNet devices and associated equipment should plan or implement the installation, start-up, configuration, and subsequent maintenance of the Modular DSA I/O System. Failure to comply may result in personal injury and/or equipment damage.

Product Reference Manuals

For RSNetWorx for DeviceNet Software Pub. No. 1787-6.5.3(RSNetWorx Software Manual,)

For SLC 500 and 1747-SDN Pub. No. 1747-5.8(DeviceNet Scanner Module Installation Instructions)

For PLC-5 and 1771-SDN Pub. No. 1771-5.14(DeviceNet Scanner Module Installation Instructions)

For DeviceNet Cables and Components Pub. No. DN-2.5(DeviceNet Overview)

vii Preface


Table of Contents

PrefaceManual Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vIntended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vVocabulary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viReference Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Chapter 1 — Product OverviewChapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1System Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Cat. Nos. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4DeviceNet Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Chapter 2 — InstallationChapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Storage and Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Electrostatic Discharge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Remove Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Approximate Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Module Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4DIN Rail Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4Gland Plate Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Wiring Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Chapter 3 — OperationChapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Basic Configuration (Accepting I/O Module Configuration) . . . . . . . . . . . . . . . . . . . . . . . . 3-1DeviceNet MAC ID (Node Address) Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Autobaud Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Choosing the I/O Assembly Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Mapping to the Scanner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10Advanced Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

Registering Unrecognized Devices in RSNetWorx . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12COS Mask Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18Input Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20DeviceNet Explicit Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20I/O Modules and DeviceNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21Mod/Net Status LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26I/O Status LED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26

ix Table of Contents


Chapter 4 — ProgrammingChapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1I/O Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Verifying the Input Assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4Verifying the Output Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6Programming Explicit Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Chapter 5 — Specifications198-DNG, 198-DN (DeviceNet Modules) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Mod/Net Status LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1I/O Status LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3198-DNP (Mini DIN Pass-Through) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6198-IB2S (Sensor Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8198-IB4 (4-Input DC Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11198-IB4S Series A (4-Input DC Module DS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14198-IA2 (2-Input AC Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17198-IA2-G4 Series A (AC Sensor Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20198-IA1-G4 9000 Series A (9000 Sensor Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23198-OW2S (2-Relay Output Gland) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26198-OW2 Series A (2-Relay Output DIN Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28198-OW2-G4 Series A (Relay Valve Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31198-OW2S-Q5 Series A (DeviceNet Valve Module). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34198-IA2XOW1 Series A and B (AC Starter Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36198-IB2XOB1 Series A and B (DC Starter Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42198-IB2XOW1 Series A and B (DC Input Relay Output Module) . . . . . . . . . . . . . . . . . . 5-49198-IB2XOB5S Series A (Drive Preset Speed Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56198-IB2XOB2S-Q5 Series A (Drive Preset Speed Module) . . . . . . . . . . . . . . . . . . . . . . . . 5-62198-G1P (Gland Plates) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67

Chapter 6 — TroubleshootingChapter Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Red I/O Light . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Red I/O Light — Noise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2DeviceNet Connection and Autobaud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Low DeviceNet Voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Excessive Number of Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Invalid ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Checksum Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Discontinuity Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3I/O Module Current Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Table of Contents x


Sensor Undervoltage Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4Shorted and Open Sensor Detection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Appendix A — DeviceNet InformationProduct Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Product Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1Product Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

DeviceNet Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Power-up Reset Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2Run Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3Error Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3I/O Error Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3I/O Idle Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

DeviceNet Object Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4Identity Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4Message Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6DeviceNet Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6

Assembly Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7I/O Modules and “Byte-wise” I/O Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7Byte-wise Output (Consumed) Assembies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10Byte-wise Input (Produced) Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14I/O Modules and “Nibble-wise” I/O Assemblies. . . . . . . . . . . . . . . . . . . . . . . . . . . A-16Nibble-wise Output (Consumed) Assembies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-18Nibble-wise Input (Produced) Assembies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-19Custom Parameter Based “Word-wise” I/O Assemblies . . . . . . . . . . . . . . . . . . . . . A-19“Word-wise” Bit-Packed Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-20Assembly Object Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-23I/O Assembly Instance Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-24

Connection Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-25Discrete Input Point Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-28Discrete Output Point Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-29Discrete Input Group Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-30Discrete Output Group Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-30Acknowledge Handler Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-31DeviceNet Interface Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-31

xi Table of Contents


Appendix B — Motor Starter OperationSetting the Motor Starter Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2Motor Starter I/O Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

Standard Distributed Starter I/O Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3Inverter Type Distributed Starter I/O Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5

Distributed Starter Specific DeviceNet Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5Control Supervisor Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6Overload Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6


Chapter 1

Product Overview

Chapter ObjectivesThis chapter contains the following information:

• System description• DeviceNet compatibility• European Union Directive compliance

System DescriptionThe Bulletin 198 Modular DSA I/O System is a cost-effective, glandular I/O system designed specifically for Distributed Starters (Figure 1.2) and general starter panels. The Modular DSA I/O System consists of a DeviceNet module followed by up to 16 I/O modules. The modules can be arranged in any combination and appear as one node on a DeviceNet network. Since the Modular DSA I/O System was designed specifically for Distributed Starters, it not only provides the ability to control and monitor devices such as motor starters, sensors, solenoids and load feeders, but also provides for cable connections to those devices, eliminating the expense and problems of traditional wiring.

1-2 Product Overview


Figure 1.1 Typical Distributed Starter — Modular DSA I/O System Modules Mounted on a Gland Plate in an Enclosed Combination Motor Starter

The Modular DSA I/O System can be mounted traditionally on a DIN Rail or on a Gland Plate to accrue benefits of wire simplification.

The Modular DSA I/O System mounted to a gland plate allows for easy connection from outside the enclosure for DeviceNet, standard sensors, and other auxiliary devices via M12 micro quick-disconnect connectors.

Figure 1.2 Modular DSA I/O System Mounted on a Gland Plate198-DNG

198-IB2XOW1 or similar

198-IB2S

Product Overview 1-3


Figure 1.3 Modular DSA I/O System Mounted on DIN Rail

The Modular DSA I/O System provides specially designed modules that provide many benefits in a distributed architecture. The Sensor Module (198-IB2S) is specifically designed to interface standard photoelectric and proximity sensors from the area surrounding the enclosure. Since the connection for standard sensors is available outside the enclosure via an M12 connector, and power is sourced from DeviceNet, no additional wiring is necessary.

The Starter Modules (198-IA2XOW1, 198-IB2XOB1, and 198-IB2XOW1) are designed to provide a fast, effective way to control and gather the basic information from either a DC operated or an AC operated starter.

The connections to specific 190D/191D Compact Combination Starters are made via cable harnesses, such as Cat. No. 198-MSACBL6. Additionally, the 198-IB2XOW1 module sources input power from DeviceNet. This allows many applications to turn off control power and still be able to read the inputs for diagnostics.

198-DN

198-IB2XOW1 or similar

198-IB4

1-4 Product Overview


Cat. Nos.The catalog numbering scheme for the Modular DSA I/O System is explained in Figure 1.4 and Figure 1.5 below. Note that all cat. nos. begin with 198, which stands for Bulletin 198 Modular DSA I/O System.

Figure 1.4 Modular DSA — DeviceNet Cat. No.

Figure 1.5 Modular DSA I/O System — I/O Module Cat. No.

DeviceNet CompatibilityThe Modular DSA I/O System communicates as a Group 2 slave device via DeviceNet Protocol. It supports the Explicit, Polled I/O, Cyclic I/O, and Change of State (COS) I/O messaging of the predefined master/slave connection set and two additional explicit connections available through Group 1 or Group 3.

G Gland Plate

No Selection DIN Mount

DN DeviceNet

Bulletin No.

198 – DNG

No. of Inputs

No. of Outputs

OutputAND

Input

Bulletin No.

Input Type

A AC

B DC

Output Type

W Relay

B DC

DeviceNet Sourced

Q5 M12 1-Key 5-Pin

G4 1/2" 2-Key 4-Pin

198 – IB2XOB2S-Q5


Chapter 2

Installation

Chapter ObjectivesThis chapter contains information about:

• Device storage and operating environment• Mounting• Connecting and wiring

Storage and OperationTo prolong the product life, take the following precautions:

• Store within an ambient temperature range of –40…+85°C (–40…+185°F).• Store within a relative humidity range of 0…95%, non-condensing.• Avoid storing or operating the device where it could be exposed to a corrosive

atmosphere.• Protect from moisture and direct sunlight.• Operate at an ambient temperature range of –25…+60°C (–4…+140°F). The

Modular DSA I/O System enclosure is suitable for an ambient of –25…+40°C.

Modular DSA I/O System is suitable for use in an industrial environment when installed in accordance with these instructions. Specifically, this equipment is intended for use in a clean, dry environment (Pollution Degree 2 ➊) ➋.➊ Pollution Degree 2 is an environmentally where, normally, only non-conductive pollution occurs except

occasionally a temporary conductivity caused by condensation shall be expected.➋ Pollution Degree 2 is an International Electrotechnical Commission (IEC) designations.

2-2 Installation


Electrostatic Discharge

Remove Power

IMPORTANT Electrostatic discharge can damage integrated circuits or semiconductors if you touch bus connector pins. Follow these guidelines when you handle the module.

• Touch a grounded object to discharge static potential.• Do not touch the bus connector or connector pins.• Do not touch circuit components inside the module.

IMPORTANT Remove power before removing or inserting a module in the I/O line-up. When you remove or insert a module with power applied, an electrical arc may occur. An electrical arc can cause personal injury or property damage by:

• Sending an erroneous signal to your system’s field devices• Causing damage to the product

Electrical arcing causes excessive wear on module contacts Worn contacts may create electrical resistance.

Installation 2-3


Approximate DimensionsDimensions are in millimeters (inches).

Figure 2.1 DIN Module Mounting Dimensions

IMPORTANT Maintain spacing from enclosure walls, wireways, adjacent equipment, etc. Allow 25 mm (1 in.) of space on all sides for adequate ventilation, as shown:

85 (3-11/32)

77 (3-1/16)

18 (11/16)

98 (3-27/32)

78 (3-1/16)

78 (3-3/32)

76 (2-31/32)

Vent Side

Connector Side

EndEnd

Dev

iceN

et

M

od-D

SA I

/O

M

od-D

SA I

/O

M

od-D

SA I

/O

M

od-D

SA I

/O

ConnectorSide

End

25mm (1 in)

25mm(1 in)

VentSide

End

25mm (1 in)

25mm(1 in)

2-4 Installation


Module InstallationThe I/O System can be mounted either on a DIN Rail or a Gland Plate.

DIN Rail MountingThe Modular DSA I/O System modules can be mounted using either the 35 x 7.5 mm (EN 50 022-35 x 7.5) or 35 x 15 mm (EN 50 022-35 x 15) DIN Rail.

Figure 2.2 DIN Rail Mounting and Removal

IMPORTANT During gland plate or DIN Rail mounting of all devices, be sure that debris (metal chips, wire strands, etc.) do not fall into the module. Such debris could cause damage on power-up.

IMPORTANT When attaching I/O modules, it is very important that the modules are fully seated on either the DIN Rail or the gland plate. This ensures that the module-to-module connectors are properly mated and that the modules are properly grounded.

ClickClick

1

12

23

198-DN

Installation 2-5


Gland Plate MountingGland plates may also be referred to as cable plates. These plates are designed to cover rectangular holes in standard enclosures, and to allow easy power and signal access to the enclosure.

Figure 2.3 Plastic Gland Plate

Refer to Chapter 5 for a complete list of gland plate specifications.

2-6 Installation


ATTENTION

!The gland plate must be on a flat secure surface and safety glasses must be worn when opening the knockouts.

Click

198-DNG

198-IB2S198-OW2S198-DNG

1.12 - 1.35 N-m(10 - 12 lb-in)

1

1 3

4

5

3

54

2

2

12

1

Click

2

1

3

1492-SM8X9

2.25 - 2.8 N-m(20 - 25 lb-in)

• No more than two DIN Modules between Gland Modules• No more than one DIN Module to the right of the Gland Module• Consult Allen-Bradley for information on exceeding these

specifications

Installation of Gland Plate and Modular DSA I/O System in Enclosure

Installation 2-7


Figure 2.4 Physical Diagram of Connecting Control Power to I/O Modules

Wiring DiagramsRefer to appropriate module in Chapter 5 for wiring information.

.324 - 2.08 mm2

22 - 14 AWG

198-IA2XOW1198-IB2XOB1198-IB2XOW1198-OW2S

1

2


Chapter 3

Operation

Chapter ObjectivesThis chapter contains the following information:

• Configuring the Modular DSA I/O System• DeviceNet Explicit Messaging• Mod/Net Status LED• I/O Status LED

Basic Configuration (Accepting I/O Module Configuration)This section will provide the user with the basic steps for configuring an MDSA on DeviceNet. It also contains specific examples of how to configure a device using RSNetWorx for DeviceNet.

The first step to setting up a system that contains an MDSA is to power up the MDSA DeviceNet module. Once it is powered up, it will attempt to determine the network baud, and set its baud rate appropriately. While the MDSA DeviceNet module is determining the network baud rate, the Mod/Net Status LED will blink green for ¼ second, red for ¼ second, then turn off. This pattern will be repeated until the baud rate is determined.

Once the proper baud rate is set, the Mod/Net Status LED will either blink green or turn solid green. If the Mod/Net Status LED turns solid red, it has most likely failed its “Duplicate MAC ID Check”, which means that the MDSA DeviceNet module has detected another device on the network with the same node address or “MAC ID”. Note that automatic baud rate detection can be disabled to allow a baud rate to be manually configured (see Advanced Topics on page 3-12)

The first time that an MDSA DeviceNet module is powered up, the I/O Status LED will turn solid red. This indicates that the configuration of the I/O modules has not been accepted.

IMPORTANT If there is no traffic on the network, the device will not be able to determine the network baud rate. The Mod/Net Status LED will to continue to repeat the green/red/off blinking pattern until network traffic is detected

Operation 3-2


Accepting the configuration of the I/O modules is a part of the device configuration process outlined below.

To begin the configuration of DeviceNet, execute the RSNetworx software and complete the following procedure.

1. From the �� menu, choose ��. After “online” has been selected you will see the following screen:

2. Choose the appropriate DeviceNet/PC interface and click OK. RSNetWorx will tell the user to upload or download devices before viewing configuration.

3. Select the button. RSNetWorx will now browse the network and display all of the nodes it has detected on the network.

RSNetWorx will display an icon and the name and node address of each device on the network. The figure below shows the RSNetWorx window after browsing the network.

If the name of the device shows up as “Unrecognized Device” it means that the device is not registered. (see Advanced Topics on page 3-12).

3-3 Operation


The user is now able to configure the MDSA. The following steps outline how to accept the configuration of the I/O modules. This will result in the I/O Status LED changing from solid red to off.

1. Double click on the MDSA icon. RSNetWorx will verify the identity of the device, and then display the following screen:

2. Select the “Parameter” tab. RSNetWorx will prompt the user to upload the parameters from the device. Select the �� button. The following screen appears:

3. From the screen shown, verify that the number of I/O modules and the names of the modules recognized are correct. Select the Accept Config parameter (parameter 48 or 58). Double click the value of that parameter. A drop-down list of options will appear. Select the Accept Config option.

4. Select the �� button. RSNetWorx will ask you whether it should download the changes to the device. Select ��. The device will reset, and the I/O Status LED will turn off. The MOD/NET status LED will be flashing green, waiting to establish connections to other nodes.

Operation 3-4


DeviceNet MAC ID (Node Address) ConfigurationThe DeviceNet node address may be set to a value from 0…63. Note that in most DeviceNet systems, node address 0 is usually reserved for the master device. Node address 63 is generally the factory default for slave devices. Node addresses can be changed in three different ways. The first two ways outlined below are accomplished via DeviceNet using the software setting, while the third is done by setting the hardware switches that reside on the MDSA DeviceNet module.

1. The first manner of changing the node address is accomplished by double clicking on the existing node number. The user will then be able to erase the existing node number and enter the desired node number. Once the desired node number has been entered, deselect the device and the following screen will appear:

2. From the above screen, select the ��button and the node number will be changed.

The second way of changing a node address can be done by following the steps shown below.

1. From the �� menu, choose �� The following screen will appear:

IMPORTANT The MDSA must be offline before performing the following procedures.

3-5 Operation


2. Click the �� button to upload the network. The following screen will appear:

3. From this screen select the appropriate PC interface. For our example we will use the 1770-KFD-1. After the appropriate interface is chosen the following screen appears:

Operation 3-6


4. Select the MDSA device and press the button. After RSNetworx has finished updating the network the following screen will appear:

5. Choose the desired node address and click the Apply button.

6. Click the Exit button. The unit will reset and power up at the new node address.

7. Re-browse the network. The MDSA should appear at the new node address.

The final way to set the node address is by directly setting the node address switches found on the MDSA DeviceNet module.

0

46

8 20

46

8 2

Node Address

MSB LSB

Address 63 Shown

3-7 Operation


Autobaud ConfigurationAutomatic baud rate detection can be enabled/disabled by setting the value of the Autobaud parameter (parameter 14).

1. To change the setting of the Autobaud parameter, click the pull down tab for that parameter in the parameter window as shown below:

2. After choosing the desired setting, click the �� button. You will then be asked to download the configuration to the device. Click ��.

When the Autobaud parameter has the value Enable, the MDSA DeviceNet module will attempt to match the network baud rate at power up. When the parameter has the value Disabled, the powerup auto-baud feature is disabled. When the Autobaud parameter is changed, the new value will be applied when the power is cycled after saving the value to the device.

ATTENTION

!Injury or damage may occur when parameters are not set according to the application requirements

Operation 3-8


Choosing the I/O Assembly Data FormatConsumed Assemblies (sometimes referred to as Output Assemblies) define the format of I/O message data that is consumed by the MDSA. The MDSA generally consumes I/O messages to command the state of its outputs.

Choosing the size and format of the I/O data that is consumed by an MDSA is done by choosing a Consumed Assembly instance number. This instance number is written to the Consumed IO Assy parameter (parameter 34 in the Cat. No. 198-DN; parameter 24 in the Cat. No. 198-DNG). Refer to Appendix on page A-1 to determine which Consumed Assembly instance to select. The different instances/formats allow flexibility for different systems. The screen below shows the Consumed IO Assy parameter in the parameter list of a Cat. No. 198-DNG module.

After the Consumed IO Assembly has been chosen and downloaded to the MDSA, select �� and �� . This will update the I/O Consumed Size parameter value (parameter 48 or 38). Record this value to be used later in the Scanner I/O mapping.

Produced Assemblies (sometimes referred to as Input Assemblies) define the format of the I/O message data that is produced by the MDSA. The MDSA generally produces I/O messages that contain the fault status of the MDSA, and the state of the MDSA’s inputs.

Choosing the size and format of the I/O data that is produced by an MDSA is done by choosing a Produced Assembly instance number. This instance number is written to the Produced IO Assy parameter (parameter 35 in the Cat. No. 198-DN; parameter 25 in the Cat. No. 198-DNG). Refer to Appendix on page A-1 to determine which Produced Assembly instance to select. The different instances/formats allow flexibility for different systems. The

IMPORTANT The Consumed IO Assy parameter value can not be changed while the MDSA is online with a scanner. Any attempts to change the value of this parameter while online with a scanner will result in the error message “Object State Conflict”.

3-9 Operation


screen below shows the Produced IO Assy parameter in the parameter list of a Cat. No. 198-DNG module.

After the Produced IO Assembly has been chosen and downloaded to the MDSA, select �� and �� . This will update the I/O Produced Size parameter value (parameter 49 or 39). Record this value to be used later in the Scanner I/O mapping.

IMPORTANT The Produced IO Assy parameter value can not be changed while the MDSA is online with a scanner. Any attempts to change the value of this parameter while online with a scanner will result in the error message “Object State Conflict”.

Operation 3-10


Mapping to the ScannerTo map the MDSA in the scanlist of a scanner, double-click on the scanner icon in RSNetWorx for DeviceNet. The following screen will appear:

1. Select the “Scanlist” tab. The user will be asked to upload the configuration to the device. Press the �� button to allow RSNetWorx to upload the scanlist from the scanner. When the uploading is complete, the following screen will appear:

3-11 Operation


2. You will see a list that contains all of the available devices in the scanlist screen. Highlight the device you wish to map (in this example, the MDSA is selected from the Available Devices box), and press the “>” button. This will cause the device (in this case, the MDSA) to appear in the Scanlist box as shown below:

3. Highlight the MDSA in the Scanlist box, and select the !��"�#�� button. The following screen will appear:

4. Enter the value of the Consumed IO Size parameter in the “Tx Size” box. Enter the value of the Produced IO Size parameter in the “Rx Size” box. Click .

5. Select the ��$ �� button in the Scanlist screen. The following screen appears:

Operation 3-12


6. Select the $�� $ ��%� �� button to download single devices in the scanlist. Select the ��%� �� radio button to download the entire scanlist. Click the �� button. The user will be prompted to download to the device. Select �� to allow the download.

Advanced Topics

Registering Unrecognized Devices in RSNetWorxWhen performing a network Browse in RSNetWorx for DeviceNet, if a device shows up as an “Unrecognized Device”, it means that an Electronic Data Sheet (EDS) file for that device has not been registered. RSNetWorx ships with the EDS files for most devices pre-registered. When a new device is released, its EDS file must be registered.

EDS files are specifically formatted ASCII files that provide all of the information necessary for a configuration tool such as RSNetWorx to access and alter the parameters of a device. Information about each parameter such as parameter minimum, maximum and default values, and parameter names are contained in EDS files.

There are specific EDS files that describe all of the parameters of the Series C MDSA DeviceNet module. RSNetWorx associates specific EDS files with specific devices by using a device’s product code, vendor code, device type, and revision number. Table 3.1 on page 3-13 lists the EDS files that are available for Series C MDSA DeviceNet Modules.

3-13 Operation


➊ Revision 4.xxx and higher includes DeviceLogix. Be sure that the last three digits of the EDS file name are at least “400” or the EDS file will not work with a Series C MDSA.

➋ These are the catalog numbers for distributed motor starters. These three catalog numbers reported by a 198-DNG module when the “Motor Starter Type” attribute in the DeviceNet Interface object is set to a value of 1, 2 or 3. This results in the MDSA reporting a Device Type of 22 (Motor Starter). For a complete description of Motor Starter Type operation, refer to Appendix B

After obtaining the needed EDS file(s), do the following:

1. From the �� menu, choose !�$�&�'��. The following screen appears:

Table 3.1 Series C MDSA EDS files

Vendor Code

Device Type

Product Code

Revision ➊ Cat. No. EDS file

1 12 67 4.xxx 198-DN 0001000C00430400.eds ➊

1 12 98 4.xxx 198-DNG 0001000C00620400.eds ➊

1 22 1 4.xxx 190D➋ 0001001600010400.eds ➊

1 22 2 4.xxx 191D➋ 0001001600020400.eds ➊

1 22 3 4.xxx 160D➋ 0001001600030400.eds ➊

IMPORTANT The EDS files listed in the table above can be obtained via the internet at: http://www.ab.com/networks/eds. Make sure that the EDS file revision number matches the revision code printed on the MDSA module.

Operation 3-14


2. Click the ��(� button. The following screen appears:

3. From the above screen, select %��!�$�)��*�+ and click the ��(� button.

4. The Registration Screen shown below will appear. In this screen, select %��. (If you are registering more than one file, you can select %�� !�$��).

3-15 Operation


5. Click the �� button and select the appropriate EDS file to be registered. Once you’ve selected the EDS file to be registered, click the ��(� button. The following screen will appear:


Each of the five catalog numbers listed in Table 3.1 on page 3-13 has a unique icon image that can be associated with it for display by RSNetWorx. These icon files can be downloaded via the internet from the same web site that the EDS files are on: http://www.ab.com/networks/eds. To associate an icon with an EDS file, click the �,��" �… button. A screen full of icons like the one following will appear.

Operation 3-16


1. To choose an icon from a file (instead of choosing an icon from the above screen), click the �� button and select a new icon file. In the screen below, the icon for the 198-DNG has been selected.

3-17 Operation



3. Click ��(�. The following screen appears:

4. Click )��,. After a short while, RSNetWorx will update your online screen by replacing the Unregistered Device with the device name given in the EDS file you have just registered.

Operation 3-18


COS Mask ParametersThe Series C MDSA DeviceNet module contains 2 COS (Change of State) parameters:

IO Mod COS Mask

The I/O Module Change of State Mask – Each bit in this 16-bit word enables/disables Change of State messages in response to changing inputs for each I/O module on the back-plane. The IO Mod COS Mask is shown in the screen below.

To change the value of the IO Mod COS Mask, click on the value of the parameter. The following screen appears:

3-19 Operation


Net Out COS Mask

The Network Output Change of State Mask – Setting bits in this 16-bit word enables Change of State messages in response to changing Network Outputs in a DeviceLogix program. The Net Out COS Mask is shown in the screen below.

To change the value of the IO Mod COS Mask, click on the value of the parameter. The following screen appears:

IMPORTANT The I/O Module COS Mask works differently than the COS Mask parameter in the Series B MDSA. Setting a bit in the I/O/Module COS mask enables COS messaging for the corresponding I/O module. In Series A and B MDSA modules, setting a bit in the COS mask disabled COS messaging for the corresponding I/O module.

Operation 3-20


Input FilteringThe MDSA contains an “Off-to-On Delay” parameter (parameter 22 for Cat. No. 198-DNG; parameter 32 for Cat. No. 198-DN) and an “On to Off Delay” parameter (parameter 23 for Cat. No. 198-DNG; parameter 33 for Cat. No. 198-DN). These parameters define time constants for input filters.

The internal resolution of the input filters is 2 ms. Even-numbered time constants between 0…64 ms may be written to these parameters.

The on-to-off transition and the off-to-on transitions of each individual input on is filtered separately.

DeviceNet Explicit MessagingDeviceNet Explicit Messages are generally used to configure a DeviceNet device. Configuration tools such as the “DeviceNet Manager” or “RSNetworx” use explicit messages when communicating with a device. Some tools, such as Rockwell Software’s “RSServer for DeviceNet” use explicit messages to help build custom DeviceNet system user interfaces for a PC. When using such a tool, it is often useful to be able to control the outputs of the Modular DSA system and also read the status information and the inputs of the

3-21 Operation


Modular DSA system using explicit messaging. Explicit messages contain the following information:

• Service – Tells the device what action to take in response to the message. Service reads information from a device and for writes information to a device.

• Class – Tells the device which object class to send the service to. Classes are identified by their numeric “class code”. Appendix A contains a complete list of the classes that are implemented in the Modular DSA system.

• Instance – Each object class can contain one or more “instances” of that class in a given device. Instances are numbered starting with instance 1. The value “0” refers to the class itself, not any individual instance of that class. Appendix A contains a complete list of instances that are implemented for each class in the Modular DSA system.

• Attribute – An attribute is a single piece of information related to an object class or instance. Attributes are numbered starting at attribute number 1. Note that attributes need to be numbered sequentially. Appendix A contains a complete list of attributes for each class and instances implemented in the Modular DSA system.

I/O Modules and DeviceNetThe discrete inputs and discrete outputs of the MDSA I/O modules are modeled on DeviceNet by DeviceNet Discrete Input Point Objects (DIPs) and DeviceNet Discrete Output Point Objects (DOPs), respectively. Each DIP and each DOP is assigned an instance number based on the physical location of its I/O module on the MDSA back-plane. Instance numbers are assigned starting with instance number 1, which is the first DIP or DOP that is on the I/O module closest to the MDSA DeviceNet module (Cat. Nos. 198-DN, 198-DNG) on the back-plane.

EXAMPLE

Sample Module Assembly

Table 3.2 Sample Module Assembly

Mod 0 Mod 1 Mod 2 Mod 3 Mod 4 Mod 5 Mod 6

Mod/Net Out 1 In 1 In 1 In 1 In 1 In 1

I/O Out 2 In 2 In 2 In 2 In 2 In 2

In 3 Out 1 Out 1

In 4

Cat. No.198-DNG

Cat. No.198-OW2

Cat. No.198-IB4

Cat. No.198-IB2XOW1

Cat. No.198-IB2XOB1

Cat. No.198-IA2

Cat. No.198-IB2S

Operation 3-22


In the example shown, you can see that the first module on the left is the DeviceNet Module. The DeviceNet Module doesn’t have any DIP or DOP instances. The next module is Mod 1. It contains the first output (Out 1) and the second output (Out 2), which are recognized as Discrete Output Point Object (DOP) instances 1 and 2, respectively. In 1 on Mod 2 is the first input seen from the left, therefore it becomes Discrete Input Point Object (DIP) instance 1. Similarly, In 2 of Mod 3 is the sixth input seen from the left, therefore it becomes DIP instance 6. The table below shows the instance numbers of all the inputs and outputs in the above example. It is followed by a blank table for you to record your lineup.

Table 3.3 Instance Table

Module Description Discrete Input Instances Discrete Output Instances

Slot Cat. No. In 1 In 2 In 3 In 4 Out 1 Out 2

0 198-DNG — — — — — —

1 198-OW2 — — — — 1 2

2 198-IB4 1 2 3 4 — —

3 198-IA2XOW1 5 6 — — 3 —

4 198-IB2XOB1 7 8 — — 4 —

5 198-IA2 9 10 — — — —

6 198-IB2S 11 12 — — — —

3-23 Operation


Configuration of Output Fault and Idle Behavior

Each Discrete Output Point can be configured to turn on, turn off, or hold its last state in the event of a communication fault or a communication idle condition. Configuration of individual outputs is accomplished by writing to the attributes of the Discrete Output Point Object instances. Table 3.5 summarizes the Discrete Output Point instance attributes.

Table 3.4 Blank Table

Module Description Discrete Input Instances Discrete Output Instances

Mod. Slot

Cat. No. In 1 In 2 In 3 In 4 Out 1 Out 2

0 198-DNG

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

Operation 3-24


The above attributes can be configured using the “Class Instance Editor” in the Device Menu of RSNetWorx. Following is an example of how to configure an output from the above lineup.

EXAMPLE

See previous example on page 3-21The following example will set the Idle Action of Out 1 of the Cat. No. 198-IB2XOB1 (DOP instance 4) to “Hold Last State”.

1. Invoke the “Class Instance Editor” in the Device Menu of RSNetWorx. The following screen appears:

Please read this screen carefully. Click Yes if you wish to continue. The following screen will appear:

Table 3.5 Discrete Output Point Instance Attributes

Class ID

Service Code

Attribute Name Data Size (bytes)

Description

9 Get 3 Value 1 The value of the output0 = OFF1 = ON

9 Get/Set 5 Fault Action 1 This attribute, in conjunction with attribute 6, defines how the output will behave when a network fault occurs.0 = Set the output value to the Fault Value contained in attribute 61 = Hold the output value prior to the DeviceNet fault occurrence.

9 Get/Set 6 Fault Value 1 This attribute determines the state that the output will assume when a network fault occurs.0 = OFF1 = ON

9 Get/Set 7 Idle Action 1 This attribute, in conjunction with attribute 8, defines how the output will behave when a network idle condition occurs.0 = Set the output value to the Idle Value contained in attribute 81 = Hold the output value prior to the DeviceNet idle occurrence.

9 Get/Set 8 Idle Value 1 This attribute determines the state that the output will assume when a network idle condition occurs.0 = OFF1 = ON

3-25 Operation


2. Enter the following as shown below. a. Class = 9b. Instance = 4c. Attribute = 7d. Service Code = “Set Single Attribute”e. Transmit Data Size = “Byte”f. Data Sent to the Device = 1

3. After the screen above appears, click the !(� -�� button. Upon successful execution, the message “The execution was completed” will appear in the “Data received from the device” box.

Operation 3-26


Mod/Net Status LEDThe Module/Network Status LED is a bi-colored (red/green) LED that provides status information on DeviceNet communications. Table 3.6 on page 3-26 summarizes the operation of the LED.

I/O Status LEDThe I/O status LED is a bi-colored (red/green) LED that provides status information on communications between the I/O module.

Table 3.6 LED Operation

For this state: MS/NS LED is: To indicate:Powerup and Autobaud Flashes

green-red-offWhen power is connected, the LED will flash this pattern one time. When waiting to detect the baud rate, the LED will flash this pattern about every 3 seconds.

Not Powered/Not On-line/Device is not on-line

Off The device has not completed the Dup_MAC_ID test yet. The device may not be powered.

Device Operational AND On-line, Connected

Green The device is operating in a normal condition and the device is on-line with connections in the established state.

Device Operational AND On-line, Not Connected or Device On-line AND needs commissioning

Flashing Green The device is operating in a normal condition and the device is on-line with no connections in the established state. The device has passed the Dup_Mac_ID test, is on-line, but has no established connections to other nodes.

Minor Fault and/or Connection Time-Out

Flashing Red Recoverable fault and/or one or more I/O connections are in the Timed-Out state.

Critical Fault or Critical Link Failure

Red The device has an unrecoverable fault; may need replacing. Failed communication device. The device has detected an error that has rendered it incapable of communicating on the network (Duplicate MAC ID, or Bus-off).

Communication Faulted and Received and Identify Comm Fault Request- Long Protocol

Flashing Red & Green

A specific Communication Faulted device. The device has detected a Network Access error and is in the Communication Faulted state. The device has subsequently received and accepted an Identify Communication Faulted Request- Long Protocol message

Table 3.7 I/O Status LED

For This State: I/O Status LED is:

To indicate:

Off Off No power or All outputs in the inactive state. Configuration of I/O modules good.

I/O Idle Flashing Green The DeviceNet network has caused the outputs to be in their idle state. Idle/Program mode.

I/O Run Green Outputs are active.I/O Recoverable Fault Flashing Red A connection controlling the outputs has timed out.

I/O Unrecoverable Fault

Red Configuration of I/O Module does not match saved configuration.Power-up initialization of bus power failed.CSUM Error at the module “X”.Invalid Module ID “X”.


Chapter 4

Programming

Chapter ObjectivesThis chapter will provide an overview of the steps necessary to use devices with a DeviceNet Scanner.

I/O MappingYou must map the inputs and the outputs to the SLC before programming it. This will allow the programmer to identify which particular bits are the inputs and which are the outputs. These particular bits will vary depending on the input and output assemblies used (Input and Output assemblies can be found in Appendix A). For this example we will be using the following lineup and assemblies:

Cat. No. 198-DNG

Cat. No. 198-OW2

Cat. No. 198-IB4

Cat. Nos. 198-IA2X, 198-OW1

Cat. Nos. 198-IB2X, 198-OB1

Cat. Nos. 198-IB2X, 198-OB5S

Cat. No. 198-IB2S

Mod/Net Out 1 In 1 In 1 In 1 F/Rev In 1

I/O Out 2 In 2 In 2 In 2 Sp0 In 2

In 3 Out 1 Out 1 Sp1

In 4 Sp2

In 1

In 2

Programming 4-2


The following is the default input assembly for the Cat. No. 198-DNG DeviceNet Control Module.

The following is the default output assembly for the Cat. No. 198-DNG DeviceNet Control Module.

Table 4.1 Instance 105 Data Format for Input Assembly

Module Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

— 0 Module Error Number 1

Module Error Number 0

I/O Module Status 6

I/O Module Status 5

I/O Module Status 4

I/O Module Status 3

I/O Module Status 2

I/O Module Status 1

— 1 Error Code 6

Error Code 5

Error Code 4

Error Code 3

Error Code 2

Error Code 1

Error Code 0

Module Error Number 1

1 2 X X X X X X X X

2 3 X X X X Input 4 Value

Input 3 Value

Input 2 Value

Input 1 Value

3 4 X X X X X X Input 2 Value

Input 1 Value

4 5 X X X X X X Input 2 Value

Input 1 Value

5 6 — — — — X X Input 2 Value

Input 1 Value

6 7 — — — — Open Short Input 2 Value

Input 1 Value

Table 4.2 Instance 104 Data Format for Input Assembly

Module Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

1 0 X X X X X X Output 2 Value

Output 1 Value

2 1 X X X X X X X X

3 2 X X X X X X X Output 1 Value

4 3 X X X X X X X Output 1 Value

5 4 X Speed 3 Speed 2 Speed 1 X X Reverse Forward

6 5 X X X X X X X X

4-3 Programming


To map the assemblies to the SLC, we first double click on the scanner icon in RSNetworx and press the Scanlist tab. The following screen will appear:

You must first map the MDSA to the SLC by following the procedures outlined in Chapter 3 (Mapping to Scanner).

Programming 4-4


The MDSA will be displayed in the scanlist if it has been mapped correctly. Once you have determined that the MDSA is mapped to the scanner, you must verify that you have mapped the correct input and output assemblies. To verify that you have the correct input assembly, select the ��-��tab on the above screen. The following screen will appear:

You can see that each byte is mapped to a certain address. For example, the above diagram shows bytes 1 and 2 at I:1.1(the I indicates that it is an input and the 1.1 is the input address).

Verifying the Input AssemblyCompare the above screen to the input assembly that was chosen. For our purposes we will compare the above screen to input assembly 105.

Note that input assembly 105 requires 8 bytes and that the assembly shown in the previous screen has 8 bytes. If the size does not match, you will need to edit the I/O parameters. If your assembly matches the input assembly seen in RSNetworx, you may skip to Verifying the Output Assembly (page 4-6).

4-5 Programming


To edit the I/O parameters we click the $ ��tab and select the !��".�#�� button. The following screen will appear:

In the Polled section on the screen above, enter the size of the bytes received (Rx) for your assembly. The size can be found on the input assembly or in the device parameters of the MDSA as “I/O Prod. Size”.

After making the appropriate changes, click the button.The following screen appears:

Select the �� button.

You then will be prompted with another screen telling you that the changes made will result in additional I/O data that is not mapped, and asks whether you would like to Automap this data. Select the ��button.

If you look at the mapped inputs (by selecting the "�-��tab), you will notice that the data has changed and that it corresponds to the input assembly chosen.

Select the �� button to download the changes to the device.

Programming 4-6


Verifying the Output AssemblyTo verify the output assembly select the -��-��/. The following screen will appear:

Compare the above screen to the selected output assembly. For our purposes, we will compare the above screen to output assembly 104.

Notice that both output assembly 104 and the assembly shown in the above screen both require 6 bytes. In this instance, you will not need to edit the I/O parameters. If your assembly matches the output assembly seen in RSNetworx, you may skip to the next section.

4-7 Programming


To edit the I/O parameters, click the $ ��tab and select the !��".�#�� button. The following screen will appear:

In the Polled section on the screen above, enter the size of the bytes transmitted (Tx) for your assembly. The size can be found on the output assembly table or in the device parameters of the MDSA as “I/O Cons. Size”.

After making the appropriate changes click the button. The following screen appears:

Select the �� button.

You then will be prompted with another screen telling you that the changes made will result in additional I/O data that is not mapped, and asks whether you would like to Automap this data. Select the ��button.

If you look at the mapped outputs (by selecting the -��-��tab) you will notice that it has changed and that it corresponds to the output assembly chosen. You can see from the example that there are 2 bytes, which match the number of bytes for output assembly 100.

Select the �� button to download the changes to the device.

8

Programming 4-8


Programming Explicit MessagesNow that the input and output assemblies are mapped correctly, you can program explicit messages. This manual will cover programming using RSLinx and RSLogix 500.

Before programming, you must first execute RSLinx. Once RSLinx is open configure a driver for your system.

To configure a driver, go to ��-� �� and select ��-��. The following screen will appear:

In Available Driver Types field, select the pull down tab. A list of drivers will drop down. Select the appropriate driver for your system and click the �� button.

4-9 Programming


You will then be asked to enter a name for your driver choose a name and select . The following screen will appear:

In the above screen, configure your driver to the appropriate parameters for your system. For this example we will be using an SLC and select “SLC-CHO/Micro/Panelview” under the �� pull down tab.

After selecting the proper device, press the �-��0��-��button to find an acceptable baud rate. When Auto-Configure is completed you will see a message that says the Auto-Configuration was successful. Once you have seen this message, click the button.

Programming 4-10


The configure screen will appear; select the �� button. The following screen will remain:

In the above screen highlight the driver you have configured. Go to ��-� �� and select %$&,�. This will allow RSLinx to browse the network and refresh the screen with all devices found, an example of which follows:

4-11 Programming


Now that you have configured a driver, you can launch RSLogix 500 to begin programming. In RSLogix you will be able to write explicit messages in SLC ladder logic. You will also be able to monitor our input and output bits.

To begin, click “new” under the file menu. You will be prompted to select the type of processor that you would like to use. Select the appropriate processor and click .

Next you will have to configure the I/O. Double click on ".��-�� under the ��folder on the left panel of the screen. The following screen will be displayed:

You can see from the above screen that the process card is the only slot recognized. To acknowledge other cards in your system, highlight the appropriate card in the “current cards available” field and drag it over into the desired slot in the lower left window. The module will now be recognized.

Programming 4-12


Close window and begin coding for the program. An example program in which an MDSA turns on an AC starter for 10 seconds follows.

Notice that each of the bits in the program is labeled with the same address as those mapped to the scanner. For example, input assembly 105 shows that the first two bytes are for status, which leaves the last six bytes for the inputs. According to what was mapped to the scanner, the last two bytes are located at address I: 1.2, I: 1.3 and I: 1.4, which are the same addresses used in the above program. The same can be seen for the output assembly.

The inputs and outputs can also be monitored by the use of RSLogix. To monitor an input, select "�-�� under the �� folder in the left panel of the screen. A data table with the addresses of all the inputs in the system will be displayed. As you change system inputs, you will see the bit at that particular address change. For example, when the program above is in run mode and the Auto switch is on, bit I: 1.3/1 will change from 0 to 1. You can also monitor the outputs in a similar fashion.

It is important to use the I/O Module Status bits for the modules on the MDSA. Use these bits to ensure that the program only executes when these bits are zero. If these bits are ever set to “1”, the MDSA has encountered a major fault and the data being gathered by the scanner is invalid.


Chapter 5

Specifications

198-DNG, 198-DN (DeviceNet Modules)Figure 5.1 198-DNG and 198-DN DeviceNet Modules

The DeviceNet module is a DeviceNet adapter module that also serves as the host for the MDSA I/O modules. The 198-DN module comes with a DIN mount head. The 198-DNG is designed for gland plate mounting. Both the 198-DN and 198-DNG are full-featured DeviceNet units. For a complete description, refer to Chapter 3 and Appendix A.

Mod/Net Status LEDThe Module/Network Status LED is a bi-colored (red/green) LED that provides status information on DeviceNet communications. Mod/Net Status LED summarizes the operation of the LED.

Specifications 5-2


Table 5.1 Mod/Net Status LED

For this state: MS/NS LED is: To indicate:

Powerup and Autobaud Flashes green-red-off

When power is connected, the LED will flash this pattern one time.When waiting to detect the baud rate, the LED will flash this pattern about every 3 seconds.

Not Powered/Not On-LineDevice is not on-line

Off The device has not completed the Dup_MAC_ID test yet.The device may not be powered.

Device Operational and On-line, Connected

Green The device is operating in a normal condition and the device is on-line with connections in the established state.

Device Operational and On-line, Not Connected or Device On-line and needs commissioning

Flashing Green The device is operating in a normal condition and the device is on-line with no connections in the established state. The device has passed the Dup_MAC_ID test, is on-line, but has no established connections to other nodes.

Minor Fault and/or Connection Time-Out

Flashing Red Recoverable fault and/or one or more I/O Connections are in the Timed-Out state.

Critical Fault or Critical Link Failure

Red The device has an unrecoverable fault; may need replacing. Failed communication device. The device has detected an error that has rendered it incapable of communicating on the network (Duplicate MAC ID, or Bus-off).

Communication Faulted and Received an Identify Comm Fault Request — Long Protocol

Flashing Red and Green

A specific Communication Faulted device. The device has detected a Network Access error and is in the Communication Faulted state. The device has subsequently received and accepted an Identify Communication Faulted Request — Long Protocol message.

5-3 Specifications


I/O Status LEDThe I/O status LED is a bi-colored (red/green) LED that provides status information on communications between the I/O modules.

Table 5.2 I/O Status LED

For This State: I/O Status LED is:

To Indicate:

OFF Off No power or All outputs in the inactive state. Configuration of I/O modules good.

I/O Idle Flashing Green The DeviceNet network has caused the outputs to be in their idle state. Idle/Program mode.

I/O Run Green Outputs are active.

I/O Recoverable Fault Flashing Red A connection controlling the outputs has timed-out.

I/O Unrecoverable Fault Red Configuration of I/O Modules does not match saved configuration.Power-up initialization of bus power failed.CSUM Error at module X.Invalid Module ID at module X.

Specifications 5-4


Figure 5.2 198-DN and 198-DNG Electrical and Application Schematic

Table 5.3 198-DN and 198-DNG General Specifications

Terminal Block (5.08 mm Pitch 5-Position)

CANH (White) (4)

24V+ Red (5)

CANL (Blue) (2)24V- (Black) (1)

Shield (Bare) (3)

198-DN

Class I Power Limited NEC 725

198-DNG

Class I Power Limited NEC 725

CANH (White) (4)24V+ Red (5)

CANL (Blue) (2)24V- (Black) (1)

Shield (Bare) (3)

(3)(4)

(1) (2)

(5)center

Wiring Diagrams

5-5 Specifications


Connection Capacity

Solid wire 0.13…1.5 mm2 (24…16 AWG)

Flexible wires 0.13…2.5 mm2 (24…14 AWG)

Flexible wires with ferrules 0.5…2.5 mm2 (20…14 AWG)

Plastic collar 1.5 mm2 (16 AWG)

Wire Type Use 75 C copper wire min.

Tightening Torque 0.5…0.6 Nm (4.4…5.3 lb-in.)

Connector (M12 Male 5-Pin)

M12 Mounting Hole 16 mm (5/8 in.)

M12 Thread M12 x 1 mm

M12 Connector Torque 1.4 Nm (12 lb-in.)

Electrical

DeviceNet Supply Voltage 11.0…25.0V DC

DeviceNet Input Current (no options) 55 mA max.

DeviceNet Input Current Max. 1.8 A

DeviceNet Input Current Surge 15 A for 250 μS

Environmental

Ambient Temperature Operating –25…+40°C (–4…+104°F)

Storage –40…+85°C (–40…+185°F)

Relative Humidity 0…95% (non-condensing)

Shock Operating 30 g peak acceleration

Non-Operating 50 g peak acceleration

Operating Vibration 10 g @ 58…2000 Hz0.030 in. peak-to-peak displacement 2…57 HzPer IEC 68-2-6

DeviceNet Communications

Baud Rates 125, 250, 500 kbps

Distance Max. 500 m (1630 ft) @ 125 kbps200 m (656 ft) @ 250 kbps100 m (328 ft) @ 500 kbps

Approvals

Agency Certification cULus ListedCE Marked for all applicable directives

Table 5.4 DeviceLogix Information

Maximum Function Blocks 48

Table 5.3 198-DN and 198-DNG General Specifications (Continued)

Specifications 5-6


198-DNP (Mini DIN Pass-Through)The 198-DNP is designed to provide a connection from the outside of an enclosure to internally-mounted DeviceNet products such as a DIN Rail-Mounted Modular DSA I/O System.

Boolean Function Blocks AND 2, 3 or 4 inputs

OR 2, 3 or 4 inputs

NOT 1 input

NAND 2, 3 or 4 inputs

NOR 2, 3 or 4 inputs

XNOR 2, 3 or 4 inputs

XOR 2, 3 or 4 inputs

RS Latch Reset Dominant

SR Latch Set Dominant

Counter Function Blocks Up CounterDown Counter

Timer Function Blocks Pulse TimerOn Delay TimerOff Delay Timer

Execution Time 16 function blocks per millisecond

Table 5.4 DeviceLogix Information

5-7 Specifications


Figure 5.3 198-DNP Electrical and Application Schematic

Table 5.5 M12 Mini DeviceNet Connector

Thread M12*1 Voltage 24V

Current 5 A

Mounting Hole 16 mm (5/8 in.)

Torque M12 Connector 1.4 Nm (12 in.-lb)

198-DNP

24V, 8A Max

CAN H (White) (4)

24V+ Red (5)

CAN L (Blue) (2)24V- (Black) (1)

Shield (Bare) (3)

Wiring Diagram

Typical Installation

Specifications 5-8


198-IB2S (Sensor Module)Figure 5.4 198-IB2S Sensor Module

The sensor input module 198-IB2S is designed to interface with hard contacts as well as 2- and 3-wire sensors. In addition to supporting two 2-inputs via the M12 micro connector, it also supports open cable and shorted sensor monitoring via the +24V DC output pin. The power for the sensor is supplied by DeviceNet and is not isolated but is short-circuit protected. Since the DeviceNet power supply may vary between 25 and 11V, only inputs which are rated for this range of operation should be attached to the port. The 198-DN and 198-DNG modules support a sensor voltage warning bit, which will activate if the voltage on the DeviceNet bus falls below 18V. The input status of 2-wire sensors is not guaranteed below this point, and system designers should use this information to affect the appropriate action. The module includes a sink/source switch that allows the user to select either mode of operation.

5-9 Specifications


Assembly Instances 104 and 105 are default for 198-DNG. Assembly Instances 106 and 107 are default for 198-DN.

Figure 5.5 198-IB2S Electrical and Application Schematic

Table 5.6 198-IB2S I/O Produced/Consumed Data

Input Data — Assembly Instance 103, 105, or 107

Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

— — — — Open Short Input 2 Input 1

Input Data — Assembly Instance 101

Bit 3 or 7 Bit 2 or 6 Bit 1 or 5 Bit 0 or 4

Open Short Input 2 Input 1

Output Data — Assembly Instance 102, 104, or 106


— — — — — — — —

Output Data — Assembly Instance 100


Compressed format, no data sent

Table 5.7 198-IB2S Specifications

Connector (M12 Female 5-Pin)

M12 Mounting Hole 16 mm (5/8 in.) M12



Electrical

Cable

1 2

34

2 1

43

Female Male

Sensor

2 1

43

Male

LOAD- +

-

+VOp en/ShortLo gic

Input 1

Input 2

198-IB2S

+V DC OUT

1 2

34

Female

Typical 3-wire sourcing proximity sensor connected to 198-IB2S module

Typical Wiring

Specifications 5-10


➊ These specifications are for reference only. Refer to sensor specification for exact values.

Module Voltage Rating 24V DC

Module Operating Voltage Range 11…25V DC

Module Current Draw w/o Sensor 26 mA @ 24V DC

Input Voltage Rating 24V DC

Input On-State Voltage 10…26V DC

Input On-State Current 3.0 mA @ 10V DC7.2 mA @ 24V DC

Input Off-State Voltage 0…5V DC

Input Off-State Current < 1.5 mA

Short Circuit Detect Level < 2V DC

Open Circuit Detect Level < 100 μA

Module Isolation Non-isolated mis-wire protected

Input Filter — Software Selectable (with two I/O modules)

Off to On 1, 2, 4, 8, 16 ms

On to Off 1.3, 2, 4, 8, 16 ms

Input Compatibility IEC 1+

Sensor

Sensor Operating Voltage Typ. 3-wire ➊ 11…25V DC

Typ. 2-wire 18…25V DC

Sensor Current Draw Max. ➊ 100 mA

Environmental


Storage –40…+85°C (–40…+185°F)

Relative Humidity 0…95% non-condensing




Approvals

Agency Certification(when product is marked)

cULus ListedCE marked for all applicable directives

Table 5.7 198-IB2S Specifications (Continued)

5-11 Specifications


198-IB4 (4-Input DC Module)Figure 5.6 198-IB4 4-Input DC Module

The 4-input DC module 198-IB4 is designed to allow four 24V DC inputs to be monitored. These inputs are isolated from the DeviceNet network. This module comes with a DIN Rail mount base, but can be mounted next to any gland plate-mounted device. The inputs can be operated in either sink or source mode.

Specifications 5-12



Figure 5.7 198-IB4 Electrical and Application Schematic

Table 5.8 198-IB4 I/O Produced/Consumed Data



— — — — Input 4 Input 3 Input 2 Input 1



Input 4 Input 3 Input 2 Input 1



— — — — — — — —




24V 0V

Input contacts or solid state switch


198-IB4IN 1

IN 2

N

N

IN 3

IN 4

Typical Wiring (Series A)

5-13 Specifications


Table 5.9 198-IB4 Specifications

Terminal Block (5.08 mm Pitch 6-Position — Series A, 5.08 mm Pitch 8-position — Series B)

Connection Capacity






Tightening Torque Spring clamp

Electrical



Module Current Draw without Sensor 17 mA @ 24V DC


Input On-State Voltage Range 10…26V DC


Input Off-State Voltage Range 0…5V DC

Input Off-State Current <1.5 mA

Module Isolation 132V AC working voltage1500V AC for 1 s


Off to On 1, 2, 4, 8, 16 ms

On to Off 1.3, 2, 4, 8, 16 ms


Environmental


Storage –40…+85°C (–40…+185°F)





Approvals



Specifications 5-14


198-IB4S Series A (4-Input DC Module DS)Figure 5.8 198-IB4S Series A 4-Input DC Module DS

The 4-Input DC module DS 198-IB4S is designed to allow four 24V DC inputs to be monitored. These inputs are isolated from the DeviceNet network. Each input has an associated +24V DC output. These outputs are not general purpose and are designed for contact closure between the +24V DC supply and the associated input. The +24V DC supply is isolated from the DeviceNet power via a DC-to-DC converter. This module comes with a DIN mount base, but can be mounted next to any gland plate mounted device.

5-15 Specifications



Figure 5.9 198-IB4S Electrical and Application Schematic

Table 5.10 198-IB4S I/O Produced/Consumed Data



— — — — Input 4 Input 3 Input 2 Input 1



Input 4 Input 3 Input 2 Input 1



— — — — — — — —




Table 5.11 198-IB4S Specifications


Connection Capacity





In4

In3

In1

In2

+V out

+V DC

0V +V out

+V out

+V out

DC

DC

ContactClosure

Specifications 5-16




Electrical



Module Current Draw 21 mA with no inputs on 24V DC51 mA with all inputs on 24V DC








Off to On 1, 2, 4, 8, 16 ms

On to Off 1.3, 2, 4, 8, 16 ms


Environmental


Storage –40…+85°C (–40…+185°F)





Approvals



Table 5.11 198-IB4S Specifications (Continued)

5-17 Specifications


198-IA2 (2-Input AC Module)Figure 5.10 198-IA2 2-Input AC Module

The 2-input AC module 198-IA2 is designed to allow two 120V AC inputs to be monitored. These inputs are isolated from the DeviceNet network. This module comes with a DIN Rail-Mount base, but can also be mounted next to any gland plate-mounted device.


Table 5.12 198-IA2 I/O Produced/Consumed Data



— — — — — — Input 2 Input 1



— — Input 2 Input 1



— — — — — — — —




Specifications 5-18


Figure 5.11 198-IA2 Electrical and Application Schematic

Table 5.13 198-IA2 Specifications


Connection Capacity







Electrical



Module Current Draw 10 mA @ 24V DC

Input Voltage Rating 120V AC

Input On-State Voltage Range 79…132V AC

Input On-State Current 11 mA @ 79V AC16 mA @ 120V AC

Input Off-State Voltage Range <20V AC




Off to On 1, 2, 4, 8, 16 ms

On to Off 1.3, 2, 4, 8, 16 ms


198-IA2

L

IN 1

IN 2

N

N

N


Typical Wiring

5-19 Specifications


Environmental


Storage –40…+85°C (–40…+185°F)





Approvals



Table 5.13 198-IA2 Specifications (Continued)

Specifications 5-20


198-IA2-G4 Series A (AC Sensor Module)Figure 5.12 198-IA2-G4 Series A AC Sensor Module

The AC Sensor input module 198-IA2-G4 is designed to interface with hard contacts as well as standard AC sensors. In addition to supporting two 2-inputs via the M12 micro connector, the inputs are also available inside the enclosure via a 4-point plug. These inputs are isolated from the DeviceNet network. This module comes with a gland mount base for mounting on the gland plate.


Table 5.14 198-IA2-G4 I/O Produced/Consumed Data

Input Data — Assembly Instance 103, 105, or 107Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0— — — — — — Input 2 Input 1

Input Data — Assembly Instance 101Bit 3 or 7 Bit 2 or 6 Bit 1 or 5 Bit 0 or 4— — Input 2 Input 1Output Data — Assembly Instance 102, 104, or 106Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0— — — — — — — —

Output Data — Assembly Instance 100Bit 3 or 7 Bit 2 or 6 Bit 1 or 5 Bit 0 or 4


5-21 Specifications


Figure 5.13 198-IA2-G4 Electrical and Application Schematic

Table 5.15 198-IA2-G4 Series A Specifications

Terminal Block (5.08 mm Pitch 4-Position)Connection Capacity

Solid wire 0.13…1.5 mm2 (24…16 AWG)Flexible wires 0.13…2.5 mm2 (24…14 AWG)

120V AC

21

4

PEPE

L

N

IN 1

IN 2

3

FEMALE

21

4

3

MALE

32

1

3 2

1

FEMALE

LOAD32

132

13 2

1

LOAD3 2

1

3 2

1

321

FEMALEMALE

MALEFEMALEMALE

MALE

MODULE

SensorT-Connector Cables

120V AC

21

4

PEPE

L

N

IN 1

IN 2

3

FEMALE

21

4

3

MALE

32

1

3 2

1

FEMALE

LOAD321

321

3 21

FEMALEMALEMALE

198-IA2-G4

Sensor

T-ConnectorAdd Cap to side not used.

120V AC

21

4

PEPE

L

N

IN 1

IN 2

3

FEMALE

21

4

3

MALE

LOAD321

3 21

FEMALE MALE

198-IA2-G4

Sensor

Custom Cable

Specifications 5-22



Plastic collar 1.5 mm2 (16 AWG)Wire Type Use 75 C copper wire min.Tightening Torque Spring clampTerminal Block (1/2 x 20 Female 4-Pin)M12 Mounting Hole 16 mm (5/8 in.)M12 Thread 1/2 x 20 in.M12 Connector Torque 1.4 Nm (12 lb-in.)ElectricalModule Operating Voltage Range 11…25V DCModule Voltage Rating 24V DCModule Current Draw 11 mA @ 24V DCInput Voltage Rating 120V ACInput On-State Voltage Range 79…132V ACInput On-State Current 11 mA @ 79V AC

16 mA @ 120V ACInput Off-State Voltage Range <20V ACInput Off-State Current <3.5 mAModule Isolation 132V AC working voltage

1500V AC for 1 s


Off to On 1, 2, 4, 8, 16 msOn to Off 1.3, 2, 4, 8, 16 ms

Input Compatibility IEC 1+EnvironmentalAmbient Temperature Operating –25…+40°C (–4…+104°F)

Storage –40…+85°C (–40…+185°F)Relative Humidity 0…95% non-condensingShock Operating 30 g peak acceleration

Non-Operating 50 g peak accelerationOperating Vibration 10 g @ 58…2000 Hz

0.060 in. peak-to-peak displacement 2…57 HzPer IEC 68-2-6

ApprovalsAgency Certification(when product is marked)


Table 5.15 198-IA2-G4 Series A Specifications (Continued)

5-23 Specifications


198-IA1-G4 9000 Series A (9000 Sensor Module)Figure 5.14 198-IA1-G4 9000 Series A 9000 Sensor Module

The AC Sensor input module 198-IA1-G4 9000 is designed to interface with hard contacts as well as the 9000 series of AC sensors. In addition to supporting one input via the M12 micro connector, the inputs are also available inside the enclosure via a 4-point plug. These inputs are isolated from the DeviceNet network. This module comes with a gland mount base for mounting on the gland plate.

Specifications 5-24



Figure 5.15 Electrical and Application Schematic

Table 5.16 198-IA1-G4 9000 I/O Produced/Consumed Data



— — — — — — — Input 1



— — — Input 1



— — — — — — — —




Table 5.17 198-IA1-G4 9000 Series A Specifications

Terminal Block (5.08 mm Pitch 4-Position)Connection Capacity

Solid wire 0.13…1.5 mm2 (24…16 AWG)Flexible wires 0.13…2.5 mm2 (24…14 AWG)

Flexible wires with ferrules 0.5…2.5 mm2 (20…14 AWG)Plastic collar 1.5 mm2 (16 AWG)

Wire Type Use 75 C copper wire min.Tightening Torque Spring clamp

120V ACL

N

2

1

43

Not Used

Comm

Female

Sensor

2

1

43

2

1

43

2

1

43

2

1

43

2

1

43

2

1

43

Female MaleMale

Cable

198-IA1-G4-9 000

5-25 Specifications


Terminal Block (1/2 x 20 Female 4-Pin)

M12 Mounting Hole 16 mm (5/8 in.)M12 Thread 1/2 x 20 in.M12 Connector Torque 1.4 Nm (12 lb-in.)ElectricalModule Operating Voltage Range 11…25V DCModule Voltage Rating 24V DC

Module Current Draw 11 mA @ 24V DCInput Voltage Rating 120V ACInput On-State Voltage Range 79…132V ACInput On-State Current 11 mA @ 79V AC

16 mA @ 120V ACInput Off-State Voltage Range <20V ACInput Off-State Current <3.5 mAModule Isolation 132V AC working voltage

1500V AC for 1 sInput Filter — Software Selectable (with two I/O modules)

Off to On 1, 2, 4, 8, 16 msOn to Off 1.3, 2, 4, 8, 16 ms

Input Compatibility IEC 1+EnvironmentalAmbient Temperature Operating –25…+40°C (–4…+104°F)

Storage –40…+85°C (–40…+185°F)Relative Humidity 0…95% non-condensingShock Operating 30 g peak acceleration

Non-Operating 50 g peak accelerationOperating Vibration 10 g @ 58…2000 Hz

0.060 in. peak-to-peak displacement 2…57 HzPer IEC 68-2-6

ApprovalsAgency Certification(when product is marked)


Table 5.17 198-IA1-G4 9000 Series A Specifications (Continued)

Specifications 5-26


198-OW2S (2-Relay Output Gland)Figure 5.16 198-OW2S 2-Relay Output Gland

The relay output gland module 198-OW2S is designed to provide two general-purpose relay DC-rated output contacts through the gland plate.

Note: This product is superseded by 198-OW2-G4 (shown above).


Table 5.18 198-OW2S I/O Produced/Consumed Data

Input Data — Assembly Instance 103, 105, or 107Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0— — — — — — — —Input Data — Assembly Instance 101Bit 3 or 7 Bit 2 or 6 Bit 1 or 5 Bit 0 or 4


Output Data — Assembly Instance 102, 104, or 106Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0— — — — — — Output 2 Output 1Output Data — Assembly Instance 100Bit 3 or 7 Bit 2 or 6 Bit 1 or 5 Bit 0 or 4— — Output 2 Output 1

5-27 Specifications


Figure 5.17 198-OW2S Electrical and Application Schematic

Table 5.19 198-OW2S Specifications





Electrical




Output Voltage Rating 120V AC

Output Load Current 4 A total (Out A + Out B)

Switching Device Relay — B300, AC15


Environmental


Storage –40…+85°C (–40…+185°F)





Approvals



Common

Out B

Out A

321

Lo r+ V

N or 0V

12 0V ACor 24V DC

198-OW2S

2

1

3

Male

LOAD BLOAD A

Cable

Female

Typical Wiring

Specifications 5-28


198-OW2 Series A (2-Relay Output DIN Module)Figure 5.18 198-OW2 Series A 2-Relay Output DIN Module

The relay output DIN module 198-OW2 is designed to provide two general purpose relay output contacts.


Table 5.20 198-OW2 I/O Produced/Consumed Data



— — — — — — — —






— — — — — — Output 2 Output 1



— — Output 2 Output 1

5-29 Specifications


Figure 5.19 198-OW2 Electrical and Application Schematic

Table 5.21 198-OW2 Specifications

Terminal Block

Connection Capacity







Electrical





Output Load Current 5 A per output



198-OW2

L o r 24V

Ou t A

Ou t A

N or 0V

Ou t B

Ou t B

Load

Load

120V ACor

24V DC

Typical Wiring

Specifications 5-30


Environmental


Storage –40…+85°C (–40…+185°F)





Approvals



Table 5.21 198-OW2 Specifications (Continued)

5-31 Specifications


198-OW2-G4 Series A (Relay Valve Module)Figure 5.20 198-OW2-G4 Series A Relay Valve Module

The Relay Valve module 198-OW2-G4 is designed to provide two output contacts to operate up to two pneumatic valves. The power for the pneumatic valves is supplied separately via a 2-point insulation displacement connector.


Table 5.22 198-OW2S I/O Produced/Consumed Data



— — — — — — — —






— — — — — — Output 2 Output 1



— — Output 2 Output 1

Specifications 5-32


Figure 5.21 198-OW2-G4 Electrical and Application Schematic

Table 5.23 198-OW2-G4 Specifications

Connector (1/2 in. x 20 Female 4-Pin)


M12 Thread 1/2 in. x 20


Electrical





Output Load Current 4 A total (Out A + Out B)

Switching Device Relay — B300, AC15, DC13


3

41

120V AC(24V DC)

PEPE

PEPE

Out B

Out A

L (+V )

N(0V)

2

21

4

3

MALE

32

1

3 2

1

FEMALE

321

3 2

1

MALE

MALE

DI N V alve

T-Connector

3

41

120V AC(24V DC)

PEPE

PEPE

Out

B

Out

A

L ( +V )

N (0V )

2

2

1

3

2

1

3

DI N V alve

Typical Installation and Wiring

Typical Wiring for Relay Valve Module 198-OW2-G4 to Two DIN Valves

5-33 Specifications


Environmental


Storage –40…+85°C (–40…+185°F)





Approvals



Table 5.23 198-OW2-G4 Specifications (Continued)

Specifications 5-34


198-OW2S-Q5 Series A (DeviceNet Valve Module)Figure 5.22 198-OW2S-Q5 Series A DeviceNet Valve Module

The DeviceNet Valve module 198-OW2S-Q5 is designed to provide two output contacts to operate up to two 24V DC pneumatic valves. The +24V DC supplied by the module is sourced from the DeviceNet power supply. The +24V DC supply is isolated from the DeviceNet power via a DC-to-DC converter. Since the DeviceNet power supply may vary between 25…110V, only outputs that are rated for this range of operation should be attached to the port. The 198-DN and 198-DNG modules support a voltage warning bit, which will activate if the voltage on the DeviceNet bus falls below 18V. The output status of the valve is not guaranteed below this point, and system designers should use this information accordingly.


Table 5.24 198-OW2S-Q5 I/O Produced/Consumed Data


Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0— — — — — — — —Input Data — Assembly Instance 101Bit 3 or 7 Bit 2 or 6 Bit 1 or 5 Bit 0 or 4

Compressed format, no data sentOutput Data — Assembly Instance 102, 104, or 106

Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0— — — — — — Output 2 Output 1Output Data — Assembly Instance 100Bit 3 or 7 Bit 2 or 6 Bit 1 or 5 Bit 0 or 4— — Output 2 Output 1

5-35 Specifications


Figure 5.23 198-OW2S-Q5 Electrical and Application Schematic

Table 5.25 198-OW2S-Q5 Specifications


M12 Mounting Hole 16 mm (5/8 in.) M12



Electrical




Output Voltage Rating 24V DC

Output Load Current 0.5 A total (Out A + Out B)



Environmental


Storage –40…+85°C (–40…+185°F)





Approvals



1 2

34

5

NotUsed

0V

24V DC

PEPE

PEPE

Ou t BOu t A

Typical Installation and Wiring

Specifications 5-36


198-IA2XOW1 Series A and B (AC Starter Module)Figure 5.24 198-IA2XOW1 Series A and B AC Starter Module

The AC starter module 198-IA2XOW1 is designed to control and monitor the basic information from an AC starter. It consists of one relay output and two isolated AC inputs. This module comes with a DIN Rail-Mount base, but can be mounted next to any gland plate-mounted device.

Series A to Series B Changes

• L out terminal added• 4-point connector changes to a 2- and 3-point connector

5-37 Specifications



➊ Input 1 represents the disconnect status of the distributed starter. Input 2 represents the contactor feedback of the preset speed module. If this bit is set, the disconnect or contactor is closed. If this bit is not set, the disconnect or contactor is open.

Figure 5.25 Cat. No. 198-IA2XOW1 Typical Wiring

Table 5.26 198-IA2XOW1 I/O Produced/Consumed Data



— — — — — — Input 2 ➊ Input 1 ➊



— — Input 2 ➊ Input 1 ➊



— — — — — — — Output 1



— — — Output 1

Typical Wiring for Series A Typical Wiring for Series B

IN1IN2Out AN

NL

Input 1

Input 2

Output 1

Lout

120V AC

Out A

L

N

In1

In2

N

Specifications 5-38


Figure 5.26 Cat. No. 198-IA2XOW1 Typical DOL wiring for Series B, Series A AC Starter Module Wired to Bulletin 190 Compact Starter

A2A1

13 14

AC StarterModule

13

M

MS

M

L N

23 24

MS

120V AC

14

In 2

Out A

N

N

L

In 1

120V ac

Lout

M – contactorMS – manual starter

AC Starter DOL33

34

43

44

MSMS

Typical DOL Wiring for Series B

AC Starter Module Wired to 190 Compact Starter (Series A)

5-39 Specifications


Figure 5.27 Typical Reversing Wiring for Series B, Hand-Off-Auto Wiring for Series A AC Starter Module (Cat. No. 198-IA2XOW1) Wired to Bulletin 190 Compact Starter

A2A1

13 14

13

F

MS

F

LN

23 24

MS

120V AC

14

AC Starter Reversing

A2A1R

13 14

R


21 22

F

21 22

R

In 2

Ou t A

N

N

L

In 1

120V AC

L out

In 2

Ou t A

N

N

L

In 1

120V AC

L out

Forward

Reverse

33

34

43

44

Typical Reversing Wiring for Series B

6

7OF F

L

AUTO

HAND

Hand-Off-Auto Wiring for Series A AC Starter Module Wired to 190 Compact Starter

Specifications 5-40


Figure 5.28 Replacing Cat. No. 198-IA2XOW1 Series A module with Series B

ATTENTION

!Make sure all power has been removed from the modules and all other components inside the enclosure.

A2A1

13 14

AC Starter Module 13

M

MS

M

L N

23 24

MS

IN1

IN2

Out A

N

N

L

14

120V ac

1

2

3

4

6 7

- Designates Terminal connectionson the 190 Compact starter


Step 1- Remove Plugs

Step 2- Remove Module

In 2

Out A

N

N

L

In 1

120V ac

Lout

A2A1

13 14

13

M

MS

M

N

23 24

MS

14 1

2

3

5

6 7

Step 5- RemoveJumper betweenpoint 4 and 5

L

Step 3- Insert new Series B moduleStep 4- Remove wires one at a time then place in tothe series B connector “L out” will be left blank at thistime

Step 6- Add wirebetween point 4 and“L out”

Step 7- Insert all three plugs intomodule

5

4

5-41 Specifications


Table 5.27 Cat. No. 198-IA2XOW1 Specifications


Connection Capacity








Connection Capacity — Flexible wire 0.13…1.5 mm2 (24…16 AWG)


Tightening Torque Insulation displacement

Electrical




Input Voltage Rating 120V AC

Input On-State Voltage Range 79…132V AC

Input On-State Current 11 mA @ 79V AC16 mA @ 120V AC

Input Off-State Voltage Range <20V AC



Off to On 1, 2, 4, 8, 16 ms

On to Off 1.3, 2, 4, 8, 16 ms






Environmental


Storage –40…+85°C (–40…+185°F)





Approvals



Specifications 5-42


198-IB2XOB1 Series A and B (DC Starter Module)Figure 5.29 Cat. No. 198-IB2XOB1 Series A and B DC Starter Module

The DC starter module 198-IB2XOB1 is designed to control and monitor the basic information from a DC starter. It consists of one relay output and two isolated DC inputs. This module comes with a DIN Rail-Mount base but can be mounted next to any gland plate-mounted device.


• +V out terminal added• Output changed from sinking to sourcing• +V and 0V terminal swapped for consistency with other starter modules

5-43 Specifications



➊ Input 1 represents the disconnect status of the distributed starter. Input 2 represents the contactor feedback of the preset speed module. If this bit is set, the disconnect or contactor is closed. If this bit is not set, the disconnect or contactor is open.

Figure 5.30 Cat. No. 198-IB2XOB1 Typical Wiring

Table 5.28 Cat. No. 198-IB2XOB1 I/O Produced/Consumed Data



— — — — — — Input 2 ➊ Input 1 ➊






— — — — — — — Output 1




Typical Wiring Series A Typical Wiring Series B

IN1IN2Out A+Vout

+V0V

Input 2

Output 1

Input 1

0V

0V

+V

Out A

In2

In1

+Vout

24V DC

Specifications 5-44


Figure 5.31 Cat. No. 198-IB2XOB1 Typical DOL Wiring (Series B), DC Starter Module wired to Bulletin 190 Compact Starter (Series A)

A2A1

13 14

DC StarterModule

13

M

MS

M

+DC-DC

23 24

MS

In 2

Out A

0V

0V

+V

24V dc

14


In 1

24V dc

+Vout

DC Starter DOL33

34

43

44

Figure O.3 198-IB2XOB1 TypicalTypical DOL Wiring Series B

A2A1

13 14

DC StarterModule

13

M

MS

M

+DC -DC

23 24

MS

In 2

Out A

+V out

+V

0V

24V DC

14


In 1

24V DC

1

2

3

4

7 6

5

Series A DC Starter Module Wired to 190 Compact Starter

5-45 Specifications


Figure 5.32 Cat. No. 198-IB2XOB1 Typical Reversing Wiring (Series B), Hand-Off-Auto Wiring for Series A DC Starter Module Wired to Bulletin 190 Compact Starter

Typical Reversing Wiring Series B

6

7OFF

0V

AUTO

HAND

Hand-Off-Auto Wiring for Series A DC Starter Module Wired to 190 Compact Starter

Specifications 5-46


Figure 5.33 Replacing Cat. No. 198-IB2XOB1 Series A Module with Series B Module

ATTENTION


Replacing Series A Module with Series B Module

5-47 Specifications


Table 5.29 198-IB2XOB1 Specifications


Connection Capacity











Electrical










Off to On 1, 2, 4, 8, 16 ms

On to Off 1.3, 2, 4, 8, 16 ms




Switching Device Solid-State — N300, DC14


Specifications 5-48


Environmental


Storage –40…+85°C (–40…+185°F)





Approvals



Table 5.29 198-IB2XOB1 Specifications (Continued)

5-49 Specifications


198-IB2XOW1 Series A and B (DC Input Relay Output Module)Figure 5.34 Cat. No. 198-IB2XOW1 Series A and B DC Input Relay Output Module

The DC input relay output module 198-IB2XOW1 is designed to control an AC starter with coil voltage up to 250V AC. It consists of one relay output and two isolated DC inputs. The two isolated DC inputs allow for status monitoring even when an E-stop has been executed. The additional terminal is a +24V DC output. The output is not general purpose and is designed for contact closure between the +24V DC output and the 198-IB2XOW1 module’s inputs. The +24V DC output is isolated from the DeviceNet power via a DC-to-DC converter. This module comes with a DIN Rail-Mount base but can be mounted next to any gland plate-mounted device.


• V out terminal added• Inputs changed from sourcing to sinking

Specifications 5-50



➊ In a typical Distributed Starter, Input 1 represents the disconnect status. Input 2 represents the contactor status. If this bit is set, the disconnect or contactor is closed. If this bit is not set, the disconnect or contactor is open.

Figure 5.35 Cat. No. 198-IB2XOW1 Typical Wiring

Table 5.30 198-IB2XOW1 I/O Produced/Consumed Data



— — — — — — Input 2 ➊ Input 1 ➊






— — — — — — — Output 1




120/240V ac

IN1

Out AN

N

DC

DC

IN2

L (+V)

+VoutIN 1

IN 2

Out A

N

N

L120/240V AC

DC

DC

Typical Wiring Series A Typical Wiring Series B

5-51 Specifications


Figure 5.36 Cat. No. 198-IB2XOW1Typical DOL and Reversing Wiring (Series B)

A2A1

13 14

DC Input Relay output

13

M

MS

M

L N

23 24

MS

240V ac

14


In 2

Out A

N

N

L

In 1

120/240V ac

+VoutDC

DC

DC Input Relay Output

33

34

43

44

Typical DOL Wiring Series B

Typical Reversing Wiring Series B

Specifications 5-52


Figure 5.37 Cat. No. 198-IB2XOW1 DC Input Relay Output Series A Module Wired to 190 Compact Starter, Hand-Off-Auto Wiring for DC Input Relay Output Series A Module Wired to Bulletin 190 Compact Starter

A2A1

13 14

DC Inpu t Relay Output 13

M

MS

M

L N

23 24

MS

IN

IN 2

Ou tA

N

N

L

14

12 0/240 V AC

1

2

3

4

6 7

Designates Terminal connectionson the 190 Compact starter

M – contactorMS – manual s tarter

DCDC

x

DC Input Relay Output Series A Module Wired to 190 Compact Starter

6

7OFF

L

AUTO

HAND

Hand-Off-Auto Wiring for DC Input Relay Output Series A Module Wired to 190 Compact Starter

5-53 Specifications


Figure 5.38 Replacing Cat. No. 198-IB2XOW1 Series A module with Series B module

Table 5.31 198-IB2XOW1 Specifications


Connection Capacity




ATTENTION


Specifications 5-54









Electrical










Off to On 1, 2, 4, 8, 16 ms

On to Off 1.3, 2, 4, 8, 16 ms






Table 5.31 198-IB2XOW1 Specifications (Continued)

5-55 Specifications


Environmental


Storage –40…+85°C (–40…+185°F)





Approvals



Table 5.31 198-IB2XOW1 Specifications (Continued)

Specifications 5-56


198-IB2XOB5S Series A (Drive Preset Speed Module)Figure 5.39 198-IB2XOB5S Series A Drive Preset Speed Module

The Preset Speed module 198-IB2XOB5S is specifically designed to work with the Bulletin 160 Drive. The module has five open-collector outputs and two isolated DC inputs, which are powered from the DeviceNet +24V via a DC-to-DC converter. The DC-to-DC converter provides isolation between the inputs and outputs, and the DeviceNet power. IN1 is intended to bring back the status of the relay of the drive, while IN2 is intended to bring back the status of the disconnect means.

5-57 Specifications



➊ When wired as shown in the following diagrams. Typical in a Distributed Starter. Input 1 represents the disconnect status. Input 2 represents the fault status of the 160 drive.

Table 5.32 198-IB2XOB5S I/O Produced/Consumed Data



— — — — — — Input 2 ➊ Input 1 ➊




Output Data — Assembly Instance 100, 102, 104, or 106


— Speed 3 Speed 2 Speed 1 — — Run Reverse Run Forward

Drive Control ➊

Run Reverse

Run Forward

DriveControl

Run Reverse

Run Forward

DriveControl

0 0 Stop 1 0 Run Reverse

0 1 Run Forward 1 1 Stop

Output Data Speed Settings ➊

Speed 3 Speed 2 Speed 1 Setting Speed 3 Speed 2 Speed 1 Setting

0 0 0 Speed Setting 1








Specifications 5-58


Figure 5.40 198-IB2XOB5S Electrical and Application Schematic

Speed 1

Speed 2

ForwardReverseSpeed 3

Comm

Stop

+24V

IN2

IN1+24V

DC

DC

ForwardO ut

DRIVE

DRIVE MODULESpeed1O ut

Speed2O ut

Speed3O ut

Stop

Speed1

Speed2

Speed3

Reverse

Forward

Stop

CommComm

IN2

IN1

+24V DC out

+24V DC out

ReverseO ut

Disconnect

Typical Wiring Series A

Series A Typical Wiring to Bulletin 160 Drive

5-59 Specifications


Figure 5.40 198-IB2XOB5S Electrical and Application Schematic (Continued)

Note: Reverse command can also be disabled via the program.

Series A Typical Wiring to Bulletin 160 Drive with Hand-Auto Forward Only

Forward Out

DRIVEDRIVE MODULE

Speed 1 Out

Speed 2 Out

Speed 3 Out

Stop

Speed 1

Speed 2

Speed 3

Reverse

Forward

Stop

CommComm

IN2

IN1

+24V DC out

+24V DC out

Reverse Out

Disconnect

AutoHand

S1Au to Open Drive runs per Drive moduleHand Closed Dr ive runs at last programmed speed

S1 1

Specifications 5-60


Figure 5.40 198-IB2XOB5S Electrical and Application Schematic (Continued)

Note: Reverse command can also be disabled via the program.

Table 5.33 198-IB2XOB5S Specifications


Connection Capacity

Solid wire 0.13…0.5 mm2 (# 28…20 AWG)

Flexible wires 0.13…0.5 mm2 (# 28…20 AWG)

Flexible wires with ferrules 0.25…0.5 mm2 (# 20 AWG)

Plastic collar 0.25…0.5 mm2 (# 20 AWG)


12 3Auto closed closed Drive runs per Drive moduleOf f open open Drive doesnot runHand closed

openopenclosed closed Dr ive runs at programmed speed

Forward Out

Reverse Out

DRIVE

DRIVE MODULESpeed1 Out

Speed2 Out

Speed3 Out

Stop

Speed1

Speed2

Speed3

Reverse

Forward

Stop

CommComm

IN2

IN1

+24V DC out

+24V DC out

Disconnect

AutoHand

S1 1

2

Of f

3

Series A Typical Wiring to Bulletin 160 Drive with Hand-Off-Auto Forward Only

5-61 Specifications



Electrical




Input Voltage Rating 24V DC (sourced from module)






Off to On 1, 2, 4, 8, 16 ms

On to Off 1.3, 2, 4, 8, 16 ms



Output Load Current 5 mA per output

Switching Device Solid-State

Module Isolation 132V AC working voltage1500V AC for 1 min.

Environmental


Storage –40…+85°C (–40…+185°F)





Approvals



Table 5.33 198-IB2XOB5S Specifications (Continued)

Specifications 5-62


198-IB2XOB2S-Q5 Series A (Drive Preset Speed Module)Figure 5.41 198-IB2XOB2S-Q5 Series A Drive Preset Speed Module

The Drive Follower module 198-IB2XOB2S-Q5 is specifically designed to work with the Bulletin 160 Drive. The module has two open-collector outputs and two isolated DC inputs, which are powered from the DeviceNet +24V via a DC-to-DC converter. The DC-to-DC converter provides isolation between the inputs and outputs and the DeviceNet power. IN1 is intended to bring back the status of the relay of the drive, while IN2 is intended to bring back the status of the disconnect means. The micro connector provides a convenient way to connect a voltage or current speed command from the outside of the enclosure to the drive.

5-63 Specifications



➊ When wired as shown in the following diagrams. Typical in a Distributed Starter. Input 1 represents the disconnect status. Input 2 represents the fault status of the 160 drive.

Table 5.34 198-IB2XOB2S-Q5 I/O Produced/Consumed Data



— — — — — — Input 2 ➊ Input 1 ➊






— — Run Reverse Run Forward



— — — — — — Run Reverse Run Forward

Drive Control

Run Reverse

Run Forward

DriveControl

Run Reverse

Run Forward

DriveControl

0 0 Stop 1 0 Run Reverse

0 1 Run Forward 1 1 Stop

Specifications 5-64


Figure 5.42 198-IB2XOB2S-Q5 Electrical and Application Schematic

2

35

4/20 mA

Forward

Reverse

CommStop

+24V DC

DC

DC

IN2

IN1

+24V DC

+V

V in

1

4

Typical Wiring Series A

Common

Forward O ut

DR IVE

DRIVE MODULE+10V

V in

4/20 mA

Stop

+10V

V in

4/20 mA

Reverse

Forward

Stop

CommComm

IN2

IN1

+24V DC out

+24V DC out

Reverse Out

Disconnect

2

3 45

1

Series A Typical Wiring to Bulletin 160 Drive

5-65 Specifications


Figure 5.42 198-IB2XOB2S-Q5 Electrical and Application Schematic (Continued)

AutoHand

S1Auto open Drive runs per Drive moduleHand closed Drive runs at las t programmed speed

S1 1

Common

Reverse Out

DRIVE DRIV EMODULE

+10V

V in

4/20 mA

Stop

+10V

V in

4/20 mA

Reverse

Forward

Stop

CommComm

IN2

IN1

+24V DC out

+24V DC out

Forward Out

Disconnect

2

3 45

1

Series A Typical Wiring to Bulletin 160 Drive with Hand-Auto Forward Only

Specifications 5-66


Figure 5.42 198-IB2XOB2S-Q5 Electrical and Application Schematic (Continued)

Table 5.35 198-IB2XOB2S-Q5 Specifications


Connection Capacity



Flexible wires with ferrules 0.25…0.5 mm2 (20 AWG)

Plastic collar 0.25…0.5 mm2 (20 AWG)



Common

Reverse Out

DRIVE

DRIVE MODULE+10V

V in

4/20 mA

Stop

+10V

V in

4/20 mA

Reverse

Forward

Stop

CommComm

IN2

IN1

+24V DC out

+24V DC out

Forward Out

Disconnect

2

3 45

1

12 3Auto closed open closed Drive runs per Drive moduleOf f open open open Drive doesnot runHand closed closed closed Drive runs at programmed speed

AutoHand

S1 1

2

Of f

3

Series A Typical Wiring to Bulletin 160 Drive with Hand-Off-Auto Forward Only

5-67 Specifications


198-G1P (Gland Plates)Gland plates may also be referred to as cable plates. These plates are designed to cover rectangular holes in standard enclosures and to allow easy power and signal access to the enclosure.

Electrical




Input Voltage Rating 24V DC (sourced from module)






Off to On 1, 2, 4, 8, 16 ms

On to Off 1.3, 2, 4, 8, 16 ms



Output Load Current 5 mA per output

Switching Device Solid-State

Module Isolation 132V AC working Voltage1500V AC for 1 min.

Environmental


Storage –40…+85°C (–40…+185°F)





Approvals



Table 5.35 198-IB2XOB2S-Q5 Specifications (Continued)

Specifications 5-68


Figure 5.43 198-G1P Plastic Gland Plate, 45 mm x 133 mm

Figure 5.44 Gland Plate Mounted on an Enclosure

Table 5.36 Gland Plate Specifications

Environmental


Storage –40…+85°C (–40…+185°F)





2

1

3

1492-SM8X9

2.25 - 2.8 N-m(20 - 25 lb-in)

5-69 Specifications


Mounting Screws Thread Forming Torque

1.3…2.0 Nm (11.5…17.7 lb-in.)(For enclosure wall thickness of 2 mm (0.079 in.) and 4.57 mm (0.180 in.) hole diameter)

Assembly Torque

2.8 Nm (25 lb-in.)

Ratings NEMA 1/3/3R/4/12, IP66

Approvals Agency Certification

cULus Listed

Table 5.36 Gland Plate Specifications (Continued)

Environmental

Specifications 5-70


Figure 5.45 Gland Plate Cutout Specifications

Table 5.37 Gland Plate Cutout Specifications

Dim. mm(in.)

Dim. mm(in.)

Dim. mm(in.)

Dim. mm(in.)

A 1305.12

C 12.150.48

E 642.52

G 4.570.18 (#15 Drill)

B 154.36.07

D 56.352.22

F 4.3250.17

— —

IMPORTANT • While use of the Rockwell Automation gland plates makes achieving an IP66 or NEMA 4 rating easy because of its inherent seal, it can also be achieved by meeting the specific guidelines below. If a Greenlee #730-5/8 punch or hole saw is used to make holes, these guidelines will be difficult to meet. The enclosure may have an IP20/NEMA 1 rating.

• Custom gland plates can be constructed using machine shop tools to achieve an acceptable hole-pattern per Custom Gland Plate Drill Pattern and Ground Targets. Alternatively, a hole pattern can be put in an enclosure wall using MDSA Drill Pattern for Enclosure Walls and Ground Targets.

• On a self-implemented gland plate or enclosure wall hole pattern, care must be taken to ensure the integrity of the seals for an IP66 or NEMA 4 rating.

A C

B

D E

FG (4 Places)

5-71 Specifications


Figure 5.46 Custom Gland Plate Drill Pattern and Ground Targets

Figure 5.47 MDSA Drill Pattern for Enclosure Walls and Ground Targets

Table 5.38 Custom Gland Plate Cutout Specifications

Dim. Measurementmm (in.)

Tolerancemm (in.)


Tolerancemm (in.)

A 22 (0.866) ± 0.1 (0.004) F 23.37 (0.920) ± 0.2 (0.007)

B 18 (0.709) ± 0.1 (0.004) G 5.20 (0.205) ± 0.2 (0.007)

C 16 (0.630) ± 0.2 (0.007) H 4.5 (0.177) ± 0.2 (0.007)

D 154 (6.063) ± 0.2 (0.007) I 31 (1.220) ± 0.2 (0.007)

E 56.35 (2.218) ± 0.2 (0.007) J 9 (0.354) ± 0.2 (0.007)

Table 5.39 MDSA Cutout Specifications


Tolerancemm (in.)


Tolerancemm (in.)

A 22 (0.866) ± 0.2 (0.007) D 4.5 (0.177) ± 0.2 (0.007)

B 18 (0.709) ± 0.2 (0.007) I 40 (1.575) ± 0.2 (0.007)

C 16 (0.630) ± 0.2 (0.007) J 9 (0.354) ± 0.2 (0.007)

B

A

C

D

E

F

G

Ground contact area. Must be clear ofpaint or any other nonconductive material

HH

J

I

B B

D

C

B

A

D

J

I


Chapter 6

Troubleshooting

Chapter ObjectivesThe purpose of this chapter is to help troubleshoot the Modular DSA I/O System.

DiagnosticsThe MDSA System contains a number of diagnostic features. While it is not possible for this manual to cover all possible scenarios, this chapter covers the basic diagnostic features of the product.

Red I/O LightDuring the MDA configuration sequence, the I/O error code 1, Modules Added, is commonly encountered. Whenever a module is added to the current configuration, the I/O light on the DeviceNet module will turn red. Attributes 34…49 of the DeviceNet interface object (class 180) may be used to verify the correct module was located in the desired position. If the configuration is correct, then sending a 1 to Attribute 27 of the DeviceNet interface object (class 180) will cause the DeviceNet module to accept the configuration and store it in EEprom. The validity of the data in the EEprom is checked and if an unrecoverable error occurs, the I/O error code 9, EEprom error, is generated. This error requires the replacement of the DeviceNet module to correct.

During normal operation, if the DeviceNet module cannot verify that a module in the configuration list is still active in the system, the error code 02, Module Removed, will be generated. This message may result from an improperly installed module, damaged connections, or possible internal module damage. Attribute 26 of the DeviceNet interface object (class 180) points to the location where the module response has ceased. When investigating this error, be sure to check the connections to the module immediately preceding the module as well as the module that is directly identified. Loose or damaged connections in the previous module can cause this error message.

IMPORTANT Accepting the configuration will cause I/O configuration parameters to be reset to default values such as input filter times.

6-2 Troubleshooting


The MDSA system constantly checks the validity of the module combination that it controls. If the DeviceNet Module finds the correct number of modules, but the order or mix is incorrect, it will generate an I/O error code 3, Module Different. This typically occurs after some maintenance activity. Again, the location of the different module can be found by reading Attribute 26 of the DeviceNet interface object (class 180). Powering down and correcting the module order will reset the fault condition. If the new configuration is desired, then accept the configuration and it will be stored.

Red I/O Light — NoiseIf the I/O light turns on after a large coil such as a contactor has been turned on, the problem may be that high frequency noise is finding its way into the product. This typically happens when the same power supply is used for DeviceNet power as well as control power for the coil. However, there are scenarios where tracing the high frequency noise is more difficult. In both scenarios, it is recommended that a diode suppressor be installed across the terminals of the coil. Rockwell Automation contactors with integrated diodes are recommended for ease and simplicity.

DeviceNet Connection and AutobaudThe first area of interest is to be sure that the DeviceNet connection has been properly made. Upon the application of power, both LEDs on the DeviceNet Module appear green followed by red. This indicates that the DeviceNet board has powered up and is functioning. While the unit is determining the network baud rate, the Mod/Net status LED will blink green for ¼ second, red for ¼ second, then turn off.

Once the proper baud rate is set, the Mod/Net LED will either blink green, or turn solid green if a connection is established between it and another device. The Mod/Net LED will turn red if the unit is attached to a network with the incorrect baud rate, or if a duplicate MAC ID is found. Once the master node has made a connection with the module, the Mod/Net LED will be solid green.

Low DeviceNet VoltageThere are a number of events that could cause a unit to go off-line. One possible cause would be that the DeviceNet Bus voltage would drop below 11V. This would be indicated by both status LEDs going to the Off state. When the bus voltage drops below this minimum level,

IMPORTANT If there is no traffic on the network, the device will not be able to determine a network baud rate. The Mod/Net status LED will continue to execute the above sequence until network traffic is detected.

Troubleshooting 6-3


many products fail to function properly, and can begin to corrupt other messages on the network. This product contains a bus voltage monitor at Attribute 30 of the DeviceNet interface object (class 180) in the DeviceNet Interface Object. This value can be read and used to reposition or add power supplies so that low voltage conditions do not occur on the bus. If they do occur, the MDSA product will stop transmitting at approximately 10V, and will execute a reset sequence when the voltage returns to approximately 11V.

Excessive Number of ModulesThe MDSA has a built-in auto-configuration identification system that allows the customer to order the modules in virtually any way. However, there are a few limitations to this system. The first is that the MDSA system only supports 16 I/O modules in addition to DeviceNet module. If this number is exceeded, Attribute 25, I/O error code, of the DeviceNet interface object will return a 6, Too Many Modules. The present module offerings can be mixed in any quantity up to 16.

Invalid IDFrom time to time, Rockwell Automation will be introducing new modules. As a consequence, if a new module type is added to an existing system, it might not be supported. The I/O error code is 4, Invalid ID. This means that the MDSA module recognizes the presence of a module, but does not have the necessary software to properly operate the module. Contact your local Allen-Bradley Sales Office for DeviceNet module upgrade information.

Checksum ErrorThe MDSA system constantly monitors the signals going to and from the various modules. Whenever possible, the source and most likely cause is identified. I/O error code 7, CSUM error, is produced whenever highly transient interruption of the signal occurs. Environments that have excessive vibration or shock, or where continuous voltage transients occur would most likely cause this error to occur. Attribute 26, error location, of the DeviceNet interface object (class 180) points to the most likely source of the problem. When investigating an I/O error code 7, begin by inspecting the module immediately preceding it for physical damage or discontinuity. Then begin to check the environment for vibration and electrical transients.

Discontinuity ErrorI/O error code 8, Discontinuity, is generated whenever one or more of the signal paths in the system appears to be open. This could occur from improper module installation, or connector damage.

6-4 Troubleshooting


I/O Module Current ErrorsThe MDSA system is designed to connect a large number of modules and their various loads to the DeviceNet power system. The maximum continuous loading of the connection is about 1.75 A. There are a number of fault codes that indicate problems encountered with this power distribution bus. If for some reason the bus cannot be powered up, an I/O error code 10, Unable to Power Bus, will occur. The most likely cause of this type of error is multiple short circuits due to mis-wiring. This unit also has an instantaneous overcurrent protection which prevents damage to the control circuitry in the DeviceNet module in the event that there is a dead short on the bus. This would show up as an I/O error code 12, Overcurrent. If this fault occurs, the offending module must be isolated and replaced before attempting to restart the system. I/O error code 13, Short Term Over-Temperature, indicates that an extremely high current is being drawn by the modules attached to the DeviceNet module. This condition indicates that some load on the system is drawing a high level of current. This system should be checked for abnormal loads prior to resetting the fault. Finally, there is an I/O error code 14, Long Term Over-Temperature. This fault indicates that a minor but persistent overcurrent condition exists. Attribute 32, I/O bus current, returns the value of the current flowing in the bus. Using this information, the loads on the system can be adjusted so that the 1.75 A level is avoided. The DeviceNet module should not be damaged by the overload condition.

Sensor Undervoltage ErrorI/O error code 11, and pneumatic valves Undervoltage, indicates that the bus voltage has dropped below 19V. Some two wire sensors may not be able to operate properly below this voltage. Typically, 2-wire sensors that require a minimum of 10V to operate will begin to have data problems around 18V. If 3- or 4-wire sensors are used, then this warning can be ignored. When this condition exists, the I/O status bits for the sensor module and the DeviceNet supplied valve module will indicate invalid data. The data from a 2-wire sensor and status of the pneumatic valve should be ignored, and the system should be moved to a safe operational state.

Shorted and Open Sensor DetectionThe Sensor Modules support both open and short circuit protection indication. In the event of a load short on the +24V supply, the PTC in the sensor module will transition and indicate a short on the sensor. This indication should be coordinated with input from this module to place the system in a safe state. The open cable detection measures the current drawn from the +24V, and if it falls below about 100 υA, the module will indicate a missing cable. In some applications, it is possible to draw no current from the +24V supply. In this case, the open signal will activate, but can be ignored. This normally will not be the case when sensors are used with this module.


Appendix A

DeviceNet Information

Product Identification

Product TypeBoth the Cat. No. 198-DN and 198-DNG modules will support the communication adapter profile. The device type is 12 (0x0C).

Product CodeThe DeviceNet Control module, Cat. No. 198-DN, has a product code of 67. and Cat. No. 198-DNG has a product code of 98.

DeviceNet ImplementationThe DeviceNet implementation in MDSA DeviceNet module is compliant with the DeviceNet Specification version 2.0 errata 3. It resides on a DeviceNet network as a Group 2 slave type device. Explicit messaging is supported for device configuration on the network. Polled I/O messaging, Change of State (COS) messaging, and Cyclic I/O messaging are supported to pass control/status from/to a DeviceNet master device.

An auto-baud rate identification algorithm is executed on powerup (if enabled).

A Group 4 recovery of faulted node algorithm is available for execution if the device fails its powerup Duplicate MAC ID test and the address switches are set so that the MAC ID is software settable.

A-2 DeviceNet Information


Operating ModesThe MDSA DeviceNet module has five modes of operation:

• Power-up Reset Mode• Run Mode• Error Mode• I/O Error Mode• I/O Idle Mode

Power-up Reset ModeDuring power-up reset the MDSA DeviceNet module does the following:

1. Performs a CRC check on the ROM. If this test fails, the product will attempt to turn the Mod/Net status LED solid red and go to the unrecoverable fault state.

2. The Mod/Net Status LED and the I/O status LED flash green for ¼ second, red for ¼ second and then extinguish while the module finishes initialization.

3. Performs a CRC check on the EEPROM values in order to verify the configuration data integrity. If these tests fail, the Mod/Net Status LED flashes red and goes to the Error Mode.

4. Identifies the I/O modules attached to the MDSA DeviceNet module. Compares the I/O modules present with the module array that is stored from previous sessions. If they are different, the unit enters the I/O error mode, and the I/O status LED on the unit illuminates solid red. The factory default is “no I/O modules attached”. If I/O modules attached match the stored array of I/O modules, the I/O Status LED is off.

5. Performs other power-up initialization functions. If any of these initialization functions fail, the MDSA DeviceNet module enters the Error Mode and the Mod/Net Status LED turns solid red.

6. Performs auto-baud rate identification (if enabled). While the unit executes the auto-baud rate algorithm, the Mod/Net status LED continues to blink green for ¼ s., then red for ¼ s.

Once the baud rate has been established, the unit performs a Duplicate MAC ID check to verify that another node is not assigned the same DeviceNet address. If a Duplicate MAC ID error occurs, the unit enters the Error Mode, and the Mod/Net LED turns solid red.

If the Duplicate MAC ID check is successful, the unit enters the Run Mode and the Mod/Net Status LED flashes green.

DeviceNet Information A-3


Run ModeIn Run Mode, the MDSA DeviceNet module operates as a slave device to a master device. When in Run Mode, the Mod/Net Status LED blinks green if there are not DeviceNet connections established with a master device. When one of more connections are established, the Mod/Net Status LED will turn solid green. In Run Mode, the MDSA DeviceNet module will:

• Accept messages form a master on the DeviceNet network.• Send response messages and COS messages to a master.• Gather data from all I/O module• If a DeviceNet bus error is detected, the module enters Error Mode.• If error is detected when gathering information from the attached I/O modules, the

unit enters the I/O Error Mode.

Error ModeIn Error Mode, the Mod/Net Status LED turns red, or in the case of minor faults such as connection time-outs, flashes red. For a full definition of the LED conditions, refer to Mod/Net Status LED on page 5-1. In Error Mode, the outputs will go to the state specified in the “fault action” and “fault value” attributes of the various DeviceNet Discrete Output Point Object instances.

I/O Error ModeIn I/O Error Mode, the MDSA DeviceNet module will assert the “outputs off” pin on the I/O module back-plane connector to drive all outputs to their off state. The I/O Status LED will be solid red. In the event of a DeviceNet communication fault, the I/O Status LED will be flashing red, and the outputs will go to the state specified in the “fault action” and “fault value” attributes of the various DeviceNet Discrete Output Point Object instances. For a full definition of the I/O Status LED conditions, refer to the I/O Status LED on page 5-3.

I/O Idle ModeIn I/O Idle Mode, the outputs will be set to the state specified in the “idle action” and “idle value” attributes of the various DeviceNet Discrete Output Point Object instances. The I/O Status LED will flash green. For a full definition of the I/O Status LED conditions, refer to the I/O Status LED on page 5-3.



DeviceNet Object DefinitionsThe following object classes are supported.

➊ The Control Supervisor Object and the Overload Objects must be supported as part of the “Motor Starter” Device Profile defined in the DeviceNet Specification. These two objects are only functional when the “Motor Starter Type” attribute in the DeviceNet Interface object is set to a value greater than zero. This results in the MDSA reporting a Device Type of 22 (Motor Starter). For a complete description of Motor Starter Type operation refer to Appendix B.

Identity Object CLASS CODE 0x0001

The following class attributes will be supported for the Identity Object:

Table A.1

Class Object Class Object0x0001 Identity 0x002B Acknowledge Handler0x0002 Message Router 0x002C* Overload Object0x0003 DeviceNet 0x00B4 DN Interface Object0x0004 Assembly 0x0307 Boolean Function Block0x0005 Connection 0x0308 Bistable Function Block0x0008 Discrete Input Point 0x0309 Counter Function Block0x0009 Discrete Output Point 0x030A Timer Function Block0x001D Discrete Input Group 0x030E Logic Supervisor0x001E Discrete Output Group 0x030F Produced Network Data0x0029 ➊ Control Supervisor

Table A.2

Attribute ID Access Rule Name Data Type Value1 Get Revision UINT 1



A single instance (instance 1) of the Identity Object is supported. The following instance attributes are supported.

➊ The value of the Distributed Starter Type attribute (attribute 63) in the DeviceNet Interface Object (Class code 0xB4) at power up determines the product type, product code and name string that the MDSA reports in attributes 2, 3 and 7 of the Identity object. Note that the Distributed Starter Type attribute only exists for Cat. No. 198-DNG units. The values of identity object attributes 2, 3 and 7 are given in the table below.

The following common services are implemented for the Identity Object.

Table A.3

Attribute ID Access Rule

Name Data Type Value

1 Get Vendor ID UINT 12 ➊ Get Device Type UINT 123 ➊ Get Product Code UINT 67 for 198-DN

98 for 198-DNG4 Get Revision

Major Revision Minor Revision

Structure of: USINT USINT

41

5 Get Status WORD Bit 0 - 0=not owned; 1=owned by masterBit 2 - 0=Factory Defaulted; 1=ConfiguredBit 8 - Minor Recoverable faultBit 9 - Minor Unrecoverable faultBit 10 - Major Recoverable faultBit 11 - Major Unrecoverable fault

6 Get Serial Number UDINT unique number for each device7 ➊ Get Product Name

String Length ASCII String

Structure of: USINT STRING

11“Modular DSA”

9 Get Configuration Consistency Value

UINT Unique value depending on output of the parameter checksum algorithm.

Table A.4

Motor Starter Type

Description Vendor ID

Product Type(att #2)

Product Code(att #3)

Name String

0 Not a Standard Starter 1 12 98 Modular DSA1 190-D Distributed Starter 1 22 1 Bulletin 190-D2 191-D Reversing Distributed Starter 1 22 2 Bulletin 191-D3 160-D Inverter Type Distributed Starter 1 22 3 Bulletin 160-D4 150-D Soft Start Type Distributed Starter 1 22 4 Bulletin 150-D

Table A.5

Service Code Implemented for: Service NameClass Instance

0x0E No Yes Get_Attribute_Single0x05 No Yes Reset



Message RouterCLASS CODE 0x0002

No class or instance attributes are supported. The message router object exists only to rout explicit messages to other objects.

DeviceNet ObjectCLASS CODE 0x0003

The following class attributes are supported for the DeviceNet Object:

A single instance (instance 1) of the DeviceNet Object is supported. The following instance attributes are supported.

➊ Allocation_byte

Bit 0 Explicit messaging

Bit 1 Polled I/O

Bit 4 COS I/O

Bit 5 Cyclic I/O

Bit 6 Acknowledge Suppression

Table A.6

Attribute ID Access Rule Name Data Type Value1 Get Revision UINT 2

Table A.7

Attribute ID Access Rule Name Data Type Value1 Get/Set Node Address USINT 0 - 632 Get/Set Baud Rate USINT 0=125K

1=250K2=500K

5 Get Allocation Info Allocation Choice Master Node Addr

Structure of: BYTE USINT

Allocation_byte ➊0-63 = address255 = unallocated

6 Get MAC ID Switch Changed BOOL 0=No Change1=Changed since last reset of power-up

8 Get MAC ID Switch Value BOOL 0-63100 Get/Set Auto Baud Disable BOOL 1=Disable

0=Enable



The following services are implemented for the DeviceNet Object.

Assembly ObjectCLASS CODE 0x0004

The following class attributes are supported for the Assembly Object:

I/O Modules and “Byte-wise” I/O AssembliesWhen “Byte-Wise” I/O Assemblies are chosen, each I/O Module on an MDSA back-plane generates one byte of data in the assemblies. The “byte-wise position” within the assembly is dependent upon the I/O module position on the back-plane. The I/O module that is physically closest to the DeviceNet Module appears at the lowest “byte-wise position” within each assembly.

The following table lists the “Output” or “Consumed” byte-wise data for each I/O Module type

Table A.8


0x0E Yes Yes Get_Attribute_Single0x10 No Yes Set_Attribute_Single0x4B No Yes Allocate_Master/Slave _Connection_Set0x4C No Yes Release_Master/Slave _Connection_Set

Table A.9

Attribute ID Access Rule Name Data Type Value2 Get Max Instance UINT 190



The following table indicates the object mapping for the above Output Assembly components:

Table A.10 Output Data per I/O Module

Module Type Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0IB2SIB4IB4SIA2IA2-G4IA1-G4-9000 Out 2 Out 1OW2S Out 2 Out 1OW2 Out 2 Out 1OW2-G4 Out 2 Out 1OW2SQ5 Out 1IA2XOW1 Out 1IB2XOB1 Out 1IB2XOW Out 1IB2XOB2S Preset 3 Preset 2 Preset 1 Run Rev Run FwdIB2XOB2S-Q5 Run Rev Run Fwd

Table A.11

Data Component Name

Class Instance AttributeName Number Name Number

Out 1 Discrete Output Point 09hex X Value 3Out 2 Discrete Output Point 09hex X + 1 Value 3Run Fwd Discrete Output Point 09hex X Value 3Run Rev Discrete Output Point 09hex X + 1 Value 3Preset # Discrete Output Point 09hex X + 1 + Preset # Value 3



The following table lists the “Input” or “Produced” byte-wise data for each I/O Module type

The following table indicates the I/O Assembly Data Attribute mapping for Input Assemblies.

Table A.12 Input Data per I/O Module

Module Type Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0IB2S Open Circuit Short Circuit Input 2 Input 1IB4 Input 4 Input 3 Input 2 Input 1IB4S Input 4 Input 3 Input 2 Input 1IA2 Input 2 Input 1IA2-G4 Input 2 Input 1IA1-G4-9000 Input 1OW2SOW2OW2-G4OW2SQ5IA2XOW1 Input 2 Input 1IB2XOB1 Input 2 Input 1IB2XOW Input 2 Input 1IB2XOB2S Input 2 Input 1IB2X)B2S-Q5 Input 2 Input 1

Table A.13

Data Component Name

Class Instance Number

AttributeName Number Name Number

Input1 Discrete Input Point 08hex 1 Value 3Input2 Discrete Input Point 08hex 2 Value 3Input3 Discrete Input Point 08hex 3 Value 3Input4 Discrete Input Point 08hex 4 Value 3Short Circuit Discrete Input Point 08hex 1 and 2Open Circuit Discrete Input Point 08hex 1 and 2



Byte-wise Output (Consumed) Assemblies

Instance 102

This output (consumed) assembly was included in the Series B MDSA. Its length (in bytes) is equal to the number of I/O modules on the back-plane

Instance 104

This is the default output (consumed) assembly for the Cat. No. 198-DNG module. It was included in the Series B DSA as the default consumed assembly. It is six bytes long, since there is room for six I/O modules on an MDSA gland plate. It has the following format:

Table A.14 Instance 102 — Modular Byte-wise Output Assembly

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Module 1 data1 Module 2 data2 Module 3 data: :: :n Module n data

Table A.15 Instance 104 — Default Output Assembly Instance for Cat. No. 198-DNG

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Module 1 data1 Module 2 data2 Module 3 data3 Module 4 data4 Module 5 data5 Module 6 data



Instance 106

This is the default output (consumed) assembly for the Cat. No. 198-DN. It was included in the Series B MDSA as the default consumed assembly also. It is sixteen bytes long since the back-plane of the MDSA can accommodate 16 I/O modules. It has the following format:

Instance 110

Assembly instance 110 is for use with DeviceLogix, and contains 16 consumed network bits. It is provided for gland plate systems that want to use a standard fixed size assembly and prefer to keep their I/O messages unfragmented, but still need to take advantage of some of the consumed network bits in their DeviceLogix program. Assembly instance 110 has the following format:

Table A.16 Instance 106 — Default Output Assembly Instance for Cat. No. 198-DN

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Module 1 data1 Module 2 data2 Module 3 data3 Module 4 data4 Module 5 data5 Module 6 data6 Module 7 data7 Module 8 data8 Module 9 data9 Module 10 data10 Module 11 data11 Module 12 data12 Module 13 data13 Module 14 data14 Module 15 data15 Module 16 data

Table A.17 Instance 110 — Byte-wise Unfragmented DeviceLogix Output Assembly for Cat. No. 198-DNG

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Module 1 data1 Module 2 data2 Module 3 data3 Module 4 data4 Module 5 data5 Module 6 data6 Consumed Network Bits 1…87 Consumed Network Bits 9…16



Instance 111

Assembly instance 111 is for use with DeviceLogix, and contains 32 consumed network bits. It is provided for gland plate systems that want to use a standard fixed size assembly, and need to take advantage of all of the consumed network bits in their DeviceLogix program. Assembly instance 111 has the following format:

Table A.18 Instance 111 — Byte-wise Fragmented DeviceLogix Output Assembly for Cat. No. 198-DNG

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Module 1 data1 Module 2 data2 Module 3 data3 Module 4 data4 Module 5 data5 Module 6 data6 Consumed Network Bits 1…87 Consumed Network Bits 9…168 Consumed Network Bits 17…249 Consumed Network Bits 25…32



Instance 112

Assembly instance 112 is a fixed size assembly for use with the Cat. No. 198-DN module with DeviceLogix enabled. It contains 16 bytes of I/O module data and contains all 32 consumed network bits. It has the following format:

Table A.19 Instance 112 — Byte-wise DeviceLogix Output Assembly for Cat. No. 198-DN

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Module 1 data1 Module 2 data2 Module 3 data3 Module 4 data4 Module 5 data5 Module 6 data6 Module 7 data7 Module 8 data8 Module 9 data9 Module 10 data10 Module 11 data11 Module 12 data12 Module 13 data13 Module 14 data14 Module 15 data15 Module 16 data16 Consumed Network Bits 1…817 Consumed Network Bits 9…1618 Consumed Network Bits 17…2419 Consumed Network Bits 25…32



Byte-wise Input (Produced) AssembliesThe Byte-wise produced assemblies contain status information in their first few bytes. The meanings of the status bits are given in the tables below:

Table A.20

Location Bits Description7 6 5 4 3 2 1 00 0 0 0 0 0 0 0 No Fault0 0 0 0 0 0 0 1 Module 10 0 0 0 0 0 1 0 Module 20 0 0 0 0 0 1 1 Module 30 0 0 0 0 1 0 0 Module 40 0 0 0 0 1 0 1 Module 50 0 0 0 0 1 1 0 Module 60 0 0 0 0 1 1 1 Module 70 0 0 0 1 0 0 0 Module 80 0 0 0 1 0 0 1 Module 90 0 0 0 1 0 1 0 Module 100 0 0 0 1 0 1 1 Module 110 0 0 0 1 1 0 0 Module 120 0 0 0 1 1 0 1 Module 130 0 0 0 1 1 1 0 Module 140 0 0 0 1 1 1 1 Module 150 0 0 1 0 0 0 0 Module 16Error Decoding

Error 6 Error 5 Error 4 Error 3 Error 2 Error 1 Error 0 Description0 0 0 0 0 0 0 No Error0 0 0 0 0 0 1 Module Added0 0 0 0 0 1 0 Module Removed0 0 0 0 0 1 1 Module Different0 0 0 0 1 0 0 Invalid ID0 0 0 0 1 0 1 Invalid Module

Configuration0 0 0 0 1 1 0 Too Many Modules0 0 0 0 1 1 1 Csum Error Count > 5000 0 0 1 0 0 0 Unused0 0 0 1 0 0 1 EEPROM Failure0 0 0 1 0 1 0 Unable to Power Bus0 0 0 1 0 1 1 Sensor Voltage Error0 0 0 1 1 0 0 Over Current0 0 0 1 1 0 1 Short Term

Over-temperature0 0 0 1 1 1 0 Long Term

Over-temperature



Instance 103

This input (produced) assembly was included in the Series B MDSA. Its length (in bytes) is equal to the number of I/O modules on the back-plane plus 4 bytes of status information. It has the following format:

Instance 105

This is the default input (produced) assembly for the Cat. No. 198-DNG. It was included in the Series B MDSA as the default produced assembly. It is eight bytes long (6 I/O modules on an MDSA gland plate, plus 2 bytes of status). It has the following format:

Table A.21 Instance 103 — Modular Input Assembly Instance for Cat. No. 198-DNG

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Location 1 Location 0 Status 6 Status 5 Status 4 Status 3 Status 2 Status 11 Error 6 Error 5 Error 4 Error 3 Error 2 Error 1 Error 0 Location 22 Location 7 Location 6 Location 5 Location 4 Location 3 Location 2 Location 1 Location 03 Error 7 Error 6 Error 5 Error 4 Error 3 Error 2 Error 1 Error 04 Module 1 data5 Module 2 data6 Module 3 data: :: :n Module n data

Table A.22 Instance 105 — Default Input Assembly Instance for Cat. No. 198-DNG

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Location 1 Location 0 Status 6 Status 5 Status 4 Status 3 Status 2 Status 11 Error 6 Error 5 Error 4 Error 3 Error 2 Error 1 Error 0 Location 24 Module 1 data5 Module 2 data6 Module 3 data7 Module 4 data8 Module 5 data9 Module 6 data



Instance 107

This is the default input (produced) assembly for the Cat. No. 198-DN. It was included in the Series B MDSA as the default produced assembly. It is 20 bytes long (the MDSA can accommodate 16 I/O modules, plus 4 bytes of status). It has the following format:

I/O Modules and “Nibble-wise” I/O AssembliesWhen “Nibble-wise” assemblies are chosen, each I/O Module on an MDSA back-plane will contribute 1 nibble (4 bits) of data to the assembly data. The “nibble-wise position” within the assembly is dependent upon the I/O module position on the back-plane. The I/O module that is physically closest to the DeviceNet Module appears at the lowest “nibble-wise position” within each assembly. These assemblies were originally defined for Series B MDSAs as a way to reduce the size of the assemblies, and thus reduce network traffic and conserve scanner-mapping space.

Table A.23 Instance 107 — Default Input Assembly Instance for Cat. No. 198-DN

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Status 8 Status 7 Status 6 Status 5 Status 4 Status 3 Status 2 Status 11 Status 16 Status 15 Status 14 Status 13 Status 12 Status 11 Status 10 Status 92 Location 7 Location 6 Location 5 Location 4 Location 3 Location 2 Location 1 Location 03 Error 7 Error 6 Error 5 Error 4 Error 3 Error 2 Error 1 Error 04 Module 1 data5 Module 2 data6 Module 3 data7 Module 4 data8 Module 5 data9 Module 6 data10 Module 7 data11 Module 8 data12 Module 9 data13 Module 10 data14 Module 11 data15 Module 12 data16 Module 13 data17 Module 14 data18 Module 15 data19 Module 16 data



➊ Note that the IB2XOB2S Drive Preset Speed module produces 2 nibbles of information.

The following table indicates the object mapping for the above Output Assembly components:

Table A.24 Output Data per I/O Module Type

Module Type Bit 3 Bit 2 Bit 1 Bit 0IB2SIB4IB4SIA2IA2-G4IA1-G4-9000 Out 2 Out 1OW2S Out 2 Out 1OW2 Out 2 Out 1OW2-G4 Out 2 Out 1OW2SQ5 Out 1IA2XOW1 Out 1IB2XOB1 Out 1IB2XOW Out 1IB2XOB2S ➊ Run Rev Run Fwd

Preset 3 Preset 2 Preset 1IB2X)B2S-Q5 Run Rev Run Fwd

Table A.25 Object Mapping for Output Assembly Components

Data Component Name



Out 1 Discrete Output Point 09hex X Value 3Out 2 Discrete Output Point 09hex X + 1 Value 3Run Fwd Discrete Output Point 09hex X Value 3Run Rev Discrete Output Point 09hex X + 1 Value 3Preset # Discrete Output Point 09hex X + 1 + #Preset s Value 3



The following table lists the “Input” or “Produced” nibble-wise data for each I/O Module type

The following table indicates the I/O Assembly Data Attribute mapping for Input Assemblies.

Nibble-wise Output (Consumed) Assemblies

Instance 100

This output (consumed) assembly was included in the Series B MDSA. Its length (in bytes) can be calculated as follows:

(I/O module + 1 + (no. of IB2XOB2S modules) / 2

Table A.26 Input Data per I/O Module Type

Module Type Bit 3 Bit 2 Bit 1 Bit 0IB2S Open Circuit Short Circuit Input 2 Input 1IB4 Input 4 Input 3 Input 2 Input 1IB4S Input 4 Input 3 Input 2 Input 1IA2 Input 2 Input 1IA2-G4 Input 2 Input 1IA1-G4-9000 Input 1OW2SOW2OW2-G4OW2SQ5IA2XOW1 Input 2 Input 1IB2XOB1 Input 2 Input 1IB2XOW Input 2 Input 1IB2XOB2S Input 2 Input 1IB2XOB2S-Q5 Input 2 Input 1

Table A.27 I/O Assembly Data Attribute Mapping for Input Assemblies

Data ComponentName



Input1 Discrete Input Point 08hex 1 Value 3Input2 Discrete Input Point 08hex 2 Value 3Input3 Discrete Input Point 08hex 3 Value 3Input4 Discrete Input Point 08hex 4 Value 3Short Circuit Discrete Input Point 08hex 1 and 2Open Circuit Discrete Input Point 08hex 1 and 2



Nibble-wise Input (Produced) Assemblies

Instance 101

This input (produced) assembly was included in the Series B MDSA. Its length (in bytes) can be calculated as follows:

(I/O module + 1 + (no. of IB2XOB2S modules) / 2) + 5

Unlike the “Byte-wise” output assemblies whose “location” bits operate as a binary location count, the above “Nibble-wise” assembly contains a single location bit for each possible module. The error location is simply given by setting the corresponding bit, rather than generating a binary coded module number.

Custom Parameter Based “Word-wise” I/O AssembliesThe contents of these assemblies are determined by contents of the “Assembly Word X” parameters in the EDS files.

Table A.28 Instance 100 — Nibble-wise Output Assembly Instance

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Module 2 data Module 2 data1 Module 4 data Module 4 data: : :: : :N/2

Table A.29 Instance 101 — Nibble-wise Input Assembly Instance

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Status 8 Status 7 Status 6 Status 5 Status 4 Status 3 Status 2 Status 11 Status 16 Status 15 Status 14 Status 13 Status 12 Status 11 Status 10 Status 92 Location 8 Location 7 Location 6 Location 5 Location 4 Location 3 Location 2 Location 13 Location 16 Location 15 Location 14 Location 13 Location 12 Location 11 Location 10 Location 94 Error code5 Module 2 data Module 1 data6 Module 4 data Module 3 data: : :: : :(N+5)/2



“Word-wise” Bit-Packed AssembliesAssemblies whose instance numbers are 180 or greater are all one word (16 bits) long. They can be used “stand alone”, but their main use is to assemble information for EDS file parameters. These “Word-wise” assemblies become the building blocks for the Custom Parameter Based “Word-wise” assemblies described in the previous sections. Note that these “Word-wise” assemblies are designed for use with DeviceLogix, so their contents reflect the data that can be used in a DeviceLogix program.

Table A.30 Custom Parameter Bases Word-wise (Produced) Assembly Instance 120

Word Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 0 Value of the parameter pointed to by “Produced Word 0 Param” (low byte)

1 Value of the parameter pointed to by “Produced Word 0 Param” (high byte)1 2 Value of the parameter pointed to by “Produced Word 1 Param” (low byte)







7 Value of the parameter pointed to by “Produced Word 7 Param” (high byte)

Table A.31 Custom Parameter Bases Word-wise (Consumed) Assembly Instance 121

Word Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 0 Value of the parameter pointed to by “Consumed Word 0 Param” (low byte)

1 Value of the parameter pointed to by “Consumed Word 0 Param” (high byte)1 2 Value of the parameter pointed to by “Consumed Word 1 Param” (low byte)



7 Value of the parameter pointed to by “Consumed Word 3 Param” (high byte)



Instance 180

This is a “Read Only” status assembly.

Instance 181


Instance 182


Instance 183


Instance 184

This is a “Read/Write” control assembly.

Table A.32 Instance 180 — Hardware Inputs 1…16

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Input 8 Input 7 Input 6 Input 5 Input 4 Input 3 Input 2 Input 11 Input 16 Input 15 Input 14 Input 13 Input 12 Input 11 Input 10 Input 9

Table A.33 Instance 181 — Hardware Inputs 17…24

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Input 24 Input 23 Input 22 Input 21 Input 20 Input 19 Input 18 Input 171 Input 32 Input 31 Input 30 Input 29 Input 28 Input 27 Input 26 Input 25

Table A.34 Instance 182 — Hardware Input Fault Status 1…16

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Input Flt 8 Input Flt 7 Input Flt 6 Input Flt 5 Input Flt 4 Input Flt 3 Input Flt 2 Input Flt 11 Input Flt 16 Input Flt 15 Input Flt 14 Input Flt 13 Input Flt 12 Input 11 Input Flt 10 Input Flt 9

Table A.35 Instance 182 — Hardware Input Fault Status 17…24

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Input Flt 24 Input Flt 23 Input Flt 22 Input Flt 21 Input Flt 20 Input Flt 19 Input Flt 18 Input Flt 171 Input Flt 32 Input Flt 31 Input Flt 30 Input Flt 29 Input Flt 28 Input Flt 27 Input Flt 26 Input Flt 25

Table A.36 Instance 184 — Hardware Outputs 1…16

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Output 8 Output 7 Output 6 Output 5 Output 4 Output 3 Output 2 Output 11 Output 16 Output 15 Output 14 Output 13 Output 12 Output 11 Output 10 Output 9



Instance 185


Instance 186


Instance 187


Instance 188


Table A.37 Instance 185 — Hardware Outputs 17…30

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Output 24 Output 23 Output 22 Output 21 Output 20 Output 19 Output 18 Output 171 Output 32 Output 31 Output 30 Output 29 Output 28 Output 27 Output 26 Output 25

Table A.38 Instance 186 — Consumed Network Inputs 1…16

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Net Input 8 Net Input 7 Net Input 6 Net Input 5 Net Input 4 Net Input 3 Net Input 2 Net Input 11 Net Input

16Net Input 15

Net Input 14

Net Input 13

Net Input 12

Net Input 11

Net Input 10

Net Input 9

Table A.39 Instance 187 — Consumed Network Inputs 17…32

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Net Input

24Net Input 23

Net Input 22

Net Input 21

Net Input 20

Net Input 19

Net Input 18

Net Input 17

1 Net Input 32

Net Input 31

Net Input 30

Net Input 29

Net Input 28

Net Input 27

Net Input 26

Net Input 25

Table A.40 Instance 188 — Produced Network Outputs 1…15

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Net Out 8 Net Out 7 Net Out 6 Net Out 5 Net Out 4 Net Out 3 Net Out 8 Net Out 11 Reserved Net Out 15 Net Out 14 Net Out 13 Net Out 12 Net Out 11 Net Out 10 Net Out 9



Instance 189


Instance 190


Assembly Object ServicesThe following services are implemented for the Assembly Object.

Table A.41 Instance 189 — DeviceNet Status

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 COS Idle Poll Idle COS Flt Poll Flt Exp Flt COS Cnxn Poll Cnxn Exp Cnxn1 Reserved Reserved Reserved Reserved Reserved Reserved Minor

FaultNetwork Flt

Table A.42 Instance 190 — Module Status

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Status 8 Status 7 Status 6 Status 5 Status 4 Status 3 Status 2 Status 11 Status 16 Status 15 Status 14 Status 13 Status 12 Status 11 Status 10 Status 9

Table A.43


0x0E Yes Yes Get_Attribute_Single0x10 No Yes Set_Attribute_Single



I/O Assembly Instance Summary

➊ These assemblies are intended for use when the “Motor Starter Type” attribute in the DeviceNet Interface object is set to a value greater than zero. This results in the MDSA reporting a Device Type of 22 (Motor Starter). For a complete description of these I/O assemblies and a complete description of “Motor Starter Type” operation, refer to Appendix B.

Table A.44

Instance Type Size (bytes) Description3 ➊ Consumed 1 ODVA Starter Profile output assembly52 ➊ Produced 1 ODVA Starter Profile input assembly100 Consumed (Modules+1) / 2 “Nibble-wise” output assembly101 Produced (Modules+5) / 2 “Nibble-wise” input assembly102 Consumed I/O modules Modular “Byte-wise” output assembly for 198-DNG103 Produced I/O modules + 2 Modular “Byte-wise” input assembly for 198-DNG104 Consumed 6 Default “Byte-wise” output assembly for 198-DNG105 Produced 8 Default “Byte-wise” input assembly for 198-DNG106 Consumed 16 Default “Byte-wise” output assembly for 198-DN107 Produced 20 Default “Byte-wise” input assembly for 198-DN110 Consumed 8 Un-fragmented “Byte-wise” DeviceLogix output

assembly for 198-DNG111 Consumed 10 Fragmented “Byte-wise” DeviceLogix output assembly

for 198-DNG112 Consumed 20 “Byte-wise” DeviceLogix output assembly for 198-DN120 Produced 0…16 Custom Parameter Based input assembly121 Consumed 0…8 Custom Parameter Based output assembly150 ➊ Consumed 2 Default Distributed Starter output assembly151 ➊ Produced 5 Default Distributed Starter input assembly152 ➊ Consumed 2 Default Reversing Distributed Starter output assembly153 ➊ Produced 5 Default Reversing Distributed Starter input assembly154 ➊ Consumed 2 Default Inverter Type Distributed Starter output

assembly155 ➊ Produced 5 Default Inverter Type Distributed Starter input

assembly156 ➊ Consumed 2 Default Soft Start Type Distributed Starter output

assembly157 ➊ Produced 5 Default Soft Start Type Distributed Starter input

assembly180 Produced 2 Hardware Inputs 1…16181 Produced 2 Hardware Inputs 17…32182 Produced 2 Hardware Input Fault Status 1…16183 Produced 2 Hardware Input Fault Status 17…32184 Consumed 2 Hardware Outputs 1…16185 Consumed 2 Hardware Outputs 17…32186 Consumed 2 Consumed Network Bits 1…16187 Consumed 2 Consumed Network Bits 17…32188 Produced 2 Produced Network Bits 1…15189 Produced 2 DeviceNet Status Bits190 Produced 2 Module Status Bits 1…16



Connection ObjectCLASS CODE 0x0005

No class attributes are supported for the Connection Object.

Five instances of the Connection Object are supported, instances 1, 2 and 4 from the group 2 predefined master/slave connection set, and instances 5 and 6 are available via explicit UCMM connections.

Instance 1 is the Predefined Group 2 Connection Set Explicit Message Connection. The following instance 1 attributes are supported:

Table A.45 Instance 1 Attributes

Attribute ID Access Rule Name Data Type Value1 Get State USINT 0=nonexistant

1=configuring3=established4=timed out

2 Get Instance Type USINT 0=Explicit Message3 Get Transport Class Trigger USINT 0x83 - Server, Transport

Class 34 Get Produced Connection ID UINT 10xxxxxx011

xxxxxx=node address5 Get Consumed Connection ID UINT 10xxxxxx100

xxxxxx=node address6 Get Initial Comm Characteristics USINT 0x227 Get Produced Connection Size UINT 0x618 Get Consumed Connection Size UINT 0x619 Get/Set Expected Packet Rate UINT in milliseconds12 Get Watchdog Action USINT 01 = auto delete

03 = deferred delete13 Get Produced Connection Path

LengthUINT 0

14 Get Produced Connection Path Empty15 Get Consumed Connection Path

LengthUINT 0

16 Get Consumed Connection Path Empty



Instance 2 is the Predefined Group 2 Connection Set Polled I/O Message Connection. The following instance 2 attributes are supported:




2 Get Instance Type USINT 1= I/O Connection3 Get Transport Class Trigger USINT 0x82 - Server, Transport Class 2

(If alloc_choice != polled and ack suppression is enabled then value = 0x80)

4 Get Produced Connection ID UINT 01111xxxxxxxxxxxx=node address

5 Get Consumed Connection ID UINT 10xxxxxx101xxxxxx=node address

6 Get Initial Comm Characteristics USINT 0x217 Get Produced Connection Size UINT 0…88 Get Consumed Connection Size UINT 0…89 Get/Set Expected Packet Rate UINT in milliseconds12 Get/Set Watchdog Action USINT 0=transition to timed out

1=auto delete2=auto reset

13 Get Produced Connection Path Length

UINT 6

14 Get/Set Produced Connection Path 20 04 24 (assy inst #) 30 03 15 Get Consumed Connection Path

LengthUINT 6

16 Get/Set Consumed Connection Path 20 04 24 (assy inst #) 30 03



Instance 4 is the Predefined Group 2 Connection Set Change of State/Cyclic I/O Message Connection. The following instance 4 attributes are supported:




2 Get Instance Type USINT 1=I/O Connection3 Get Transport Class Trigger USINT 0x00 (Cyclic, unacknowledged)

0x03 (Cyclic, acknowledged)0x10 (COS, unacknowledged)0x13 (COS, acknowledged)

4 Get Produced Connection ID UINT 01101xxxxxxxxxxxx=node address

5 Get Consumed Connection ID UINT 10xxxxxx101xxxxxx=node address

6 Get Initial Comm Characteristics USINT 0x01 (acknowledged)0x0F (unacknowledged)

7 Get Produced Connection Size UINT 0…88 Get Consumed Connection Size UINT 0 …89 Get/Set Expected Packet Rate UINT in milliseconds12 Get Watchdog Action USINT 0=transition to timed out

1=auto delete2=auto reset

13 Get Produced Connection Path Length

UINT 6

14 Get Produced Connection Path 20 04 24 (assy inst #) 30 0315 Get Consumed Connection Path

LengthUINT 4 (acknowledged)

0 (unacknowledged)16 Get/Set Consumed Connection Path 20 04 24 (assy inst #) 30 0317 Get/Set Production Inhibit Time UINT In milliseconds



Instances 5 and 6 are the available group 1 or group 3 explicit message connections that are allocated through the UCMM. The following attributes are supported:

The following services are implemented for the Connection Object.

Discrete Input Point ObjectCLASS CODE 0x0008

The following class attributes are supported for the Discrete Input Point Object:

Table A.48 Instances 5 and 6 Attributes



2 Get Instance Type USINT 0=Explicit Message3 Get Transport Class Trigger USINT 0x83 - Server, Transport Class 34 Get Produced Connection ID UINT Depends on message group and

Message ID5 Get Consumed Connection ID UINT Depends on message group and

Message ID6 Get Initial Comm Characteristics USINT 0x227 Get Produced Connection Size UINT 0x618 Get Consumed Connection Size UINT 0x619 Get/Set Expected Packet Rate UINT in milliseconds12 Get Watchdog Action USINT 01 = auto delete

03 = deferred delete13 Get Produced Connection Path

LengthUINT 0

14 Get Produced Connection Path Empty15 Get Consumed Connection Path

LengthUINT 0

16 Get Consumed Connection Path Empty

Table A.49


0x05 No Yes Reset0x0E No Yes Get_Attribute_Single0x10 No Yes Set_Attribute_Single

Table A.50

Attribute ID Access Rule Name Data Type Value1 Get Revision UINT 22 Get Max Instance UINT 0-64



Multiple instances of the Discrete Input Point Object are supported. All instances contain the following attributes.

The following common services are implemented for the Discrete Input Point Object.

Discrete Output Point ObjectCLASS CODE 0x0009

The following class attributes are supported for the Discrete Output Point Object:

Multiple instances of the Discrete Output Point Object will be supported. All instances will contain the following attributes.

The following common services will be implemented for the Discrete Output Point Object.

Table A.51

Attribute ID Access Rule Name Data Type Value3 Get Value BOOL 0=OFF, 1=ON

Table A.52

Service Code Implemented for: ServiceClass Instance Name

0x0E Yes Yes Get_Attribute_Single0X10 No Yes Set_Attribute_Single

Table A.53

Attribute ID Access Rule Name Data Type Value1 Get Revision UINT 12 Get Max Instance UINT 0…80

Table A.54

Attribute ID Access Rule Name Data Type Value3 Get Value BOOL 0=OFF, 1=ON5 Get/Set Fault Action BOOL 0=Fault Value attribute, 1=Hold Last State6 Get/Set Fault Value BOOL 0=OFF, 1=ON7 Get/Set Idle Action BOOL 0=Fault Value attribute, 1=Hold Last State8 Get/Set Idle Value BOOL 0=OFF, 1=ON

Table A.55


0x0E No Yes Get_Attribute_Single0x10 No Yes Set_Attribute_Single



Discrete Input Group ObjectCLASS CODE 0x001D

No class attributes are supported for the Discrete Input Group Object.

A single instance of the Discrete Input Group Object is supported. It contains the following attributes.

The following common services will be implemented for the Discrete Input Group Object.

Discrete Output Group ObjectCLASS CODE 0x001E

No class attributes are supported for the Discrete Output Group Object.

A single instance of the Discrete Output Group Object is supported. It contains the following attributes.

The following common services will be implemented for the Discrete Input Group Object.

Table A.56

Attribute ID Access Rule Name Data Type Value3 Get Number of Instances USINT 1…644 Get Binding Array of UINT List of DIP instances6 Get/Set Off_On_Delay UINT 0 μs; 2000 μs; 4000 μs,

8000 μs; 16000 μs7 Get/Set On_Off_Delay UINT 0 μs; 2000 μs; 4000 μs,

8000 μs; 16000 μs

Table A.57



Table A.58

Attribute ID Access Rule Name Data Type Value3 Get Number of Instances USINT 0…80

Table A.59





Acknowledge Handler ObjectCLASS CODE 0x002b

No class attributes will be supported for the Acknowledge Handler Object.

A single instance (instance 1) of the Acknowledge Handler Object will be supported. The following instance attributes will be supported.

The following common services will be implemented for the Acknowledge Handler Object.

DeviceNet Interface ObjectCLASS CODE 0x00B4

This “vendor-specific” object includes no class attributes.

A single instance (instance 1) of the DeviceNet Interface Object is supported:

Table A.60

Attribute ID Access Rule Name Data Type Value1 Get/Set Acknowledge Timer UINT milliseconds2 Get Retry Limit USINT 13 Get COS Producing Connection Instance UINT 4

Table A.61



Table A.62

Attribute ID

Access Rule

Name Data Type Min/Max Default Description

7 Get/Set Prod Assy Word 0 USINT 0…51 ➊0…60 ➋

1 Defines Word 0 of Assy 120







13 Get/Set COS Mask WORD 0…FFFF 0xffff 1=Module COS enabled0=Module COS disabled

16 Get/Set Consumed Assy USINT 0…187 104 ➊106 ➋

Assembly instance number that defines the consumed I/O data format.

17 Get/Set Produced Assy USINT 100…190 105 ➊107 ➋

Assembly instance number that defines the produced I/O data format.

19 Get/Set Set To Defaults BOOL 0…1 0 0=No action; 1=Reset



22 Get/Set I/O Module Status WORD 0…FFFF 0x0000 0=Data Valid at Module x1=Data Invalid at Module xBit 0 = Module 1Bit 15 = Module 16

23 Get I/O Produced Size USINT 0…20 Size (in bytes) of I/O data produced by poll, COS or Cyclic connections.

24 Get I/O Consumed Size

USINT 0…16 Size (in bytes) of I/O data Consumed by poll, COS or Cyclic connections.

25 Get I/O Error USINT 0…14 0 0 = no error1 = Module added2 = Module removed3 = Module different4 = Invalid module ID5 = Invalid module configuration6 = Too many modules7 = Csum error count > 5008 = Unused9 = EEPROM failure10 = Unable to power bus11 = Sensor or valve voltage error12 = Over-current13 = Short term over-temperature14 = Long term over-temperature

26 Get Error Location WORD 0 = Module(x) OK1 = Fault detected at module(x)Bit 0 = Module 1Bit 15 = Module 16

27 Get/Set Accept Configuration

BOOL 0…1 0 0 -> 1 Save new I/O module configuration to EEPROM

28 Get CSum Count UINT CSum errors on the module bus. Increases by 3 on error, decrements by 1 on good bus transaction.

29 Get Module Error Number

BYTE 0…16 Decimal number from 1…16 representing a module number.

30 Get DeviceNet Voltage

UINT 0… 65535 mV

31 Get Module Bus Voltage

UINT 0…65535 mV

32 Get I/O Bus Current UINT 0… 19168 mA

Coarse reading with 18 mA resolution

33 Get Number of Modules

USINT 0…17 ➌

34 Get Module ID Slot 1 USINT 0…17 ➌




Table A.62

Attribute ID

Access Rule




➊ Applies to Cat. No. 198-DNG units➋ Applies to Cat. No. 198-DN units➌

➍ Four “Motor Starter Types” can be selected via this attribute: Standard Distributed Starter, Reversing Distributed Starter, Inverter Type Distributed Starter, and Softstart Distributed Starter. For a complete description of “Motor Starter Type” operation, refer to Appendix B













50 Get/Set PNB COS Mask WORD 0…0x00FF 0 Change of state mask for PNBs1= COS enabled0= COS disabled









59 Get/Set Con Assy Word 0 USINT 0…8 5 Defines Word 0 of Assy 12160 Get/Set Con Assy Word 1 USINT 0…8 6 Defines Word 1 of Assy 12161 Get/Set Con Assy Word 2 USINT 0…8 7 Defines Word 2 of Assy 12162 Get/Set Con Assy Word 3 USINT 0…8 8 Defines Word 3 of Assy 12163 ➍ Get/Set Motor Starter

TypeUSINT 0…3 0 See notes below

Table A.62

Attribute ID

Access Rule


0 = No Module 5 = 198-IB4/IB4S 10 = Reserved 15 = Reserved

1 = 198-IB2S 6 = 198-OW1-G3 11 = 198-IB2XOB5S 16 = 198-IA1-G4-90002 = 198-IA2XOW1 7 = 198-OW2/OW2S/OW2-G4 12 = 198-OW2S-Q5 17 = 198-IB2S-Q53 = 198-IB2XOW1 8 = 198-IB2XOB1 13 = Reserved 18-255 = Invalid4 = 198-IA2/IA2-G4 9 = Reserved 14 = 198-IB2XOB2S-Q5



The following common services are implemented for the DeviceNet Interface Object.

Table A.63




Appendix B

Motor Starter Operation

The Cat. No. 198-DNG MDSA DeviceNet Module is used as a component in a line of Allen-Bradley distributed motor starters. The following Allen Bradley distributed starter catalog numbers are currently available

• 190-D – Across-the-Line Distributed Starter• 191-D – Reversing Distributed Starter• 160-D – Variable Frequency Inverter Distributed Starter.

When the Cat. No. 198-DNG DeviceNet Module is used in one of the Allen-Bradley distributed starters, it is convenient to have the starter present itself on a DeviceNet network as a distributed starter instead of as an MDSA. The Cat. No. 198-DNG MDSA DeviceNet module can be programmed so that it presents itself on a DeviceNet network as a distributed starter instead of as a communication adapter.

A “Motor Starter Type” parameter (parameter 51) is used to configure the Cat. No. 198-DNG as a Distributed Motor Starter. When the value of the Motor Starter Parameter is set to a in the table below, it identifies itself as shown in Table B.1.

B-2 Motor Starter Operation


Setting the Motor Starter Type

The following example shows how to set up the 198-DNG DeviceNet module to identify itself on the network as a Bulletin 190-D Distributed Starter.

1. From the “Device Parameters” screen for the unit being programmed, change the Motor Starter Type parameter (param 51) to the value “Distributed Str” as shown below.

Table B.1

Motor Starter Type

Description Vendor ID

Product Type

Product Code

Default Output Assembly

Default Input Assembly

0 Not a Standard Starter 1 12 98 104 1051 190-D Distributed Starter 1 22 1 150 1512 191-D Reversing Distributed Starter 1 22 2 152 1533 160-D Inverter Type Distributed

Starter1 22 3 154 155

TIPSetting the motor starter type is optional. It is convenient because it simplifies identity on the network.

Motor Starter Operation B-3


2. Click the “Download to Device” button to download the new value to the 198-DNG module

3. Cycle power to the 198-DNG DeviceNet module. (This updates the RAM.)

4. Put RSNetWorx for DeviceNet in the “off line” mode.

5. Go back online with RSNetWorx for DeviceNet. RSNetWorx will prompt you with: “Save Changes to Network File?”. Click No. This will allow the newly programmed 198-DNG module to identify itself as a distributed starter in the view of the network.

The unit will identify itself as a 190-D Distributed Starter as shown below:

Motor Starter I/O AssembliesWhen a Cat. No. 198-DNG module is programmed to present itself on the network as a Distributed Starter, its default I/O assemblies are changed. This effects the size and format of the I/O data that is produced and consumed by the unit. While all of the regular I/O assemblies described in Appendix A are still available for use, a few “Distributed Starter Specific” I/O assemblies become available, and become the defaults. The Distributed Starter Specified I/O assemblies are described in the following sections.

Standard Distributed Starter I/O AssembliesThese assemblies are available when the Motor Starter Type parameter is set to the value 1 = Distributed Str.

Standard Distributed Starter Output (Consumed) Assemblies

Instance 3 is the required output (consumed) assembly defined in the DeviceNet Motor Starter Profile.



Instance 150 is the default output (consumed) assembly for Standard Distributed Starters

Standard Distributed Starter Input (Produced) Assemblies

Instance 52 is the required input (produced) assembly defined in the DeviceNet Motor Starter Profile.

Instance 151 is the default input (produced) assembly for Standard Distributed Starters

Reversing Distributed Starter I/O Assemblies

These assemblies are available when the Motor Starter Type parameter is set to the value 2 = Reversing Starter.

Reversing Distributed Starter Output (Consumed) Assemblies


Instance 152 is the default output (consumed) assembly for Standard Distributed Starters

Reversing Distributed Starter Input (Produced) Assemblies


Instance 153 is the default input (produced) assembly for Reversing Distributed Starters

Table B.2 Instance 150 — Default Consumed Standard Distributed Starter

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Output 8 Output 7 Output 6 Output 5 Output 4 Output 3 Output 2 Run1 Output 16 Output 15 Output 14 Output 13 Output 12 Output 11 Output 10 Output 9

Table B.3 Instance 151 — Default Produced Standard Distributed Starter

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Location 1 Location 0 Status 6 Status 5 Status 4 Status 3 Status 2 Status 11 Error 6 Error 5 Error 4 Error 3 Error 2 Error 1 Error 0 Location 22 Input 8 Input 7 Input 6 Input 5 Input 4 Input 3 Input 2 Input 13 Input 16 Input 15 Input 14 Input 13 Input 12 Input 11 Input 10 Input 94 Input 24 Input 23 Input 22 Input 21 Input 20 Input 19 Input 18 Input 17

Table B.4 Instance 152 — Default Consumed Reversing Distributed Starter

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Output 8 Output 7 Output 6 Output 5 Output 4 Output 3 Run Rev Run Fwd1 Output 16 Output 15 Output 14 Output 13 Output 12 Output 11 Output 10 Output 9

Motor Starter Operation B-5


Inverter Type Distributed Starter I/O AssembliesThese assemblies are available when the Motor Starter Type parameter is set to the value 3 = Inverter Starter.

Inverter Type Distributed Starter Output (Consumed) Assemblies


Instance 154 is the default output (consumed) assembly for Inverter Type Distributed Starters

Inverter Type Distributed Starter Input (Produced) Assemblies


Instance 155 is the default input (produced) assembly for Inverter Type Distributed Starters

Distributed Starter Specific DeviceNet ObjectsWhen a Cat. No. 198-DNG is programmed to present itself as a Distributed Starter on DeviceNet, two start-specific objects become visible via DeviceNet. These two objects are

Table B.5 Instance 153 — Default Produced Reversing Distributed Starter


Table B.6 Instance 154 — Default Consumed Inverter Type Distributed Starter

Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 00 Output 8 Output 7 Output 6 Preset 2 Preset 1 Preset 0 Run Rev Run Fwd1 Output 16 Output 15 Output 14 Output 13 Output 12 Output 11 Output 10 Output 9

Table B.7 Instance 155 — Default Produced Inverter Type Distributed Starter




called out in the DeviceNet Motor Starter Profile as “Required” objects in all DeviceNet Motor Starters. Their definitions are given below.

Control Supervisor ObjectCLASS CODE 0x0029

This object only exists for units reporting a product type of 22 (Motor Starter). No class attributes will be supported.

A single instance (instance 1) of the Control Supervisor Object will be supported. The following instance attributes will be supported.

The following common services will be implemented for the Control Supervisor Object.

Overload ObjectCLASS CODE 0x002c

No class attributes will be supported for the Overload Object.

No instance attributes will be supported for the Overload Object.

No common services will be implemented for the Overload Object.

Table B.8

Attribute ID Access Rule Name Data Type Value1 Get/Set Run 1 BOOL Also maps to “Value” attribute of DOP 12 Get/Set Run 2 BOOL Also maps to “Value” attribute of DOP 23 Get Running 1 BOOL Also maps to “Value” attribute of DIP 14 Get Running 2 BOOL Also maps to “Value” attribute of DIP 3

Table B.9



Publication 198-UM002A-EN-P December 2001© 2001 Rockwell Automation. Printed in the U.S.A.

www.rockwellautomation.com

Corporate HeadquartersRockwell Automation, 777 East Wisconsin Avenue, Suite 1400, Milwaukee, WI, 53202-5302 USA, Tel: (1) 414.212.5200, Fax: (1) 414.212.5201

Headquarters for Allen-Bradley Products, Rockwell Software Products and Global Manufacturing SolutionsAmericas: Rockwell Automation, 1201 South Second Street, Milwaukee, WI 53204-2496 USA, Tel: (1) 414.382.2000, Fax: (1) 414.382.4444Europe: Rockwell Automation SA/NV, Vorstlaan/Boulevard du Souverain 36-BP 3A/B, 1170 Brussels, Belgium, Tel: (32) 2 663 0600, Fax: (32) 2 663 0640Asia Pacific: Rockwell Automation, 27/F Citicorp Centre, 18 Whitfield Road, Causeway Bay, Hong Kong, Tel: (852) 2887 4788, Fax: (852) 2508 1846

Headquarters for Dodge and Reliance Electric ProductsAmericas: Rockwell Automation, 6040 Ponders Court, Greenville, SC 29615-4617 USA, Tel: (1) 864.297.4800, Fax: (1) 864.281.2433Europe: Rockwell Automation, Brühlstraße 22, D-74834 Elztal-Dallau, Germany, Tel: (49) 6261 9410, Fax: (49) 6261 1774Asia Pacific: Rockwell Automation, 55 Newton Road, #11-01/02 Revenue House, Singapore 307987, Tel: (65) 351 6723, Fax: (65) 355 1733

Documents

Modular DeviceNet Starter Auxiliary I/O · 2014. 12. 11. · Figure 1.3 Modular DSA I/O System Mounted on DIN Rail The Modular DSA I/O System provides specially designed modules that