Schneider Electric Quantum EIO - Remote I/O Modules Configuration Guide

External Features

140CRP31200:

Remote I/O Modules

1 LED display

2 SERVICE port (ETH 1)

3 INTERLINK port (ETH 2)

4 DEVICE NETWORK port (ETH 3)

5 DEVICE NETWORK port (ETH 4)

NOTE: To help prevent dust from entering the unused Ethernet ports on this module, cover the port with the stopper:

External Ports

The 140CRP31200 module monitors the functionality of network links depending on which links are connected to the network. The module has 4 external ports (but a single IP address):

S1A48978.14

Remote I/O Modules

Service Port Configuration topic , page 41

Port

SERVICE

INTERLINK

DEVICE

NETWORK

Quantity

Description

The SERVICE port allows the diagnosis of Ethernet ports and provides access to external tools and devices (Control Expert,

ConneXium Network Manager, HMI, etc.). The port supports these modes:

• access port (default): This mode supports Ethernet communications.

• port mirroring: In this mode, data traffic from one or more of the other 3 ports is copied to this port. This allows a connected tool to monitor and analyze the port traffic.

• disabled

NOTE:

• You can configure the SERVICE port either on line or off line.

• In port mirroring mode, the SERVICE port acts like a read-only port. That is, you cannot access devices (ping, connection to Control Expert, etc.) through the SERVICE port.

NOTE: The maximum load the network can process from distributed I/O devices is:

• 5 Mbps per dual-ring switch (DRS) port or service port

• 20 Mbps for distributed I/O traffic on the main ring

Refer to the

The INTERLINK port provides connectivity to other Quantum EIO modules.

These 2 copper ports provide:

• connections for remote I/O communications

• cable redundancy via the daisy chain loop architecture

NOTE: Do not connect a device with a speed in excess of 100 Mbps to any port. If the device is configured for a speed that exceeds 100 Mbps, the

Ethernet link may not be established between the device and the module through the port.

Quantum EIO Adapter Module Descriptions

Introduction

These adapter modules are used on Ethernet remote I/O drops in 31 Quantum

EIO installations:

• 140CRA31200

• BMXCRA312•0

A remote I/O drop can be connected directly to either the main ring or a remote I/O sub-ring.

NOTE: If you use a low-end CPU (140 CPU 6• 1••) (2 Mb or less), you can only install a maximum of 31 remote I/O drops. Of those 31 drops, you can only install a maximum of sixteen BMXCRA312•0 remote I/O drops. If you use a high-end CPU (140 CPU 6•• ••) (4 Mb or more), you can install a maximum of thirty-one BMXCRA312•0 or 140CRA31200 remote I/O drops.

Functionality

Adapter modules exchange data with the 140CRP31200 remote I/O head module on the local rack:

• The 140CRA31200 module is an adapter module on a Quantum remote I/O drop.

• The BMXCRA31200 and BMXCRA31210 modules are adapter modules on

Modicon X80 remote I/O drops.

Features:

14 S1A48978.14

Remote I/O Modules

• The input data from the Ethernet remote I/O drop is collected and published to the remote I/O scanner.

• The output modules are updated with the data received from the remote I/O scanner.

• The protocol used for exchange is EtherNet/IP.

• The remote I/O scanner views the 140CRA31200 or BMXCRA312•0 module as a remote I/O adapter.

• The exchanges are deterministic, which means that the time it takes to resolve a remote I/O logic scan is predictable.

CAUTION

UNEXPECTED BEHAVIOR OF THE APPLICATION.

If you use your BMXCRA in a Quantum Ethernet IO architecture, take care to update the Quantum CPU and the 140CRP31200 to the following minimum versions:

• CPU: V3.1

• CRP: V1.56

Failure to follow these instructions can result in injury or equipment damage.

External Features

These adapter modules have the same dimensions and installation constraints as other modules in their respective product lines (Quantum or Modicon X80):

S1A48978.14

1 LED display

2 rotary switches

3 SERVICE port (ETH 1)

4 DEVICE NETWORK port (ETH 2)

5 DEVICE NETWORK port (ETH 3)

Remote I/O Modules

Service Port Configuration , page 41

NOTE: To help prevent dust from entering the unused Ethernet ports on these adapter modules, cover the ports with the stopper:

External Ports

Two of the Ethernet ports allow implicit I/O exchanges with a remote I/O scanner adapter. (An implicit I/O exchange has a maximum frame size of 1400 bytes.) The ports can be implemented alone or in redundant mode.

You can use a maximum of 31 adapters in a single Ethernet remote I/O network.

For network topology planning, refer to the Quantum Ethernet I/O System

Planning Guide .

These modules have up to three 10/100 Base-T Ethernet ports:

Port

SERVICE

DEVICE

NETWORK

Description

The SERVICE port allows the diagnosis of Ethernet ports and provides access to external tools and devices (Control Expert, ConneXium Network Manager, HMI, etc.). The port supports these modes:

• access port (default): This mode supports Ethernet communications.

• port mirroring: In this mode, data traffic from one of the other 3 ports is copied to this port. This allows a connected management tool to monitor and analyze the port traffic.

• disabled

NOTE:

• You can configure the SERVICE port either on line or off line.

• In port mirroring mode, the SERVICE port acts like a read-only port. That is, you cannot access devices (ping, connection to Control Expert, etc.) through the SERVICE port.

• There is no SERVICE port on the BMXCRA31200 adapter module.

Refer to

The DEVICE NETWORK copper port provides:

• connections for remote I/O communications

• cable redundancy

NOTE: Do not connect a device with a speed in excess of 100 Mbps to any port. If the device is configured for a speed that exceeds 100 Mbps, the

Ethernet link may not be established between the device and the module through the port.

Cable Redundancy

Use a daisy chain network configuration that implements the RSTP service to establish redundant communications between the adapter module and a remote I/

O scanner. The adapter operates normally when at least one of the 2 physical paths to the 140CRP31200 is valid. (For network topology planning, refer to the

Quantum Ethernet I/O System Planning Guide .)

Module Specifications

Product Certification

The Quantum EIO head/adapter modules meet these standards:

16 S1A48978.14

Remote I/O Modules

Environmental Requirements

Parameter protection protection class over voltage class operating temperature storage temperature sinusoidal vibration

Reference

EN 61131-2

IEC 60527

EN 61131-2

IEC 60068-2-1

Ab&Ad (cold)

IEC 60068-2-2

Bb&Bd (cold)

IEC 60068-2-1

Ab&Ad (cold)

IEC 60068-2-2

Bb&Bd (cold)

IEC 60068-2-6fC

EN 61131-2

IEC 60068-2-27Ea operating shock altitude free fall, random

(packaged)

UL (UL508)

CSA (CSA22.2 no. 142)

C-tick

Hazardous locations (Cl1 div 2)

IEC61000-4-16

EMI EN 55011

EN 61131-1

IEC 61131-2 (zone B and zone C, except surges on AC: zone B only)

Quantum EIO modules conform to these product certification and marine classification authorities:

Key

ABS

DNV

GOST

RINA

Certification Body

American Bureau of Shipping

Bureau Veritas

Det Norske Veritas

Gosudarstvennyy Standart

Germanischer Lloyd

Lloyd's Register

Registro Italiano Navale

Country

United States

France

Norway

Russia

Germany

United Kingdom

Italy

The electrical isolation within a Quantum EIO system modules complies with the

1500 Vac/2250 Vdc 60s from IEEE 802.3 2008.

EN 61131-2

IEC 60068-2-32

Specification

IP20 protection class 1 category II

0 ... 60° C

-40 ... 85° C

• .5 ... 8.4 Hz at 3.5 mm constant amplitude

• 8.4 ... 150 Hz at 1g constant acceleration

• 10 cycles at sweep rate of 1 oct/min

30 g peak, 11 ms, half-sine wave, 3 shocks in each direction (+ and -) for each of the 3 principle axes

0 ... 5000 m maximum during operation. For altitudes > 2000 m, reduce the operating temperature by 6° C for each additional 1000 m.

5 random drops from 1 m onto flat surfaces

S1A48978.14

Remote I/O Modules

Parameter free fall, flat drop

(unpackaged) free fall, angled

(unpackaged) relative humidity

(operating) relative humidity

(nonoperating)

Reference test ed., method 1

EN 61131-2

IEC 60068-2-32 test ed., method 1

EN 61131-2

IEC 60068-2-31

IEC 60068-2-78Ca

IEC 60068

Specification

• 2 random drops from 1 m onto flat surfaces

• 5 drops from 0.1 m onto flat surfaces

5 drops from 0.1 m onto each corner

93% (+/- 2%, noncondensing) at 60° C for conformally coated modules 140CRA31200C and 140CRP31200C

NOTE: The BMXCRA31210 is also available in a coated version.

I/O Devices

Introduction

This topic lists the Quantum and Modicon X80 I/O devices that can be connected to an Ethernet remote I/O network.

To add I/O modules to an Ethernet remote I/O drop in Control Expert offline mode, click and drag the modules from the Hardware Catalog to the remote I/O drop in the bus editor. You can also double-click the rack slot in which you want to insert the I/O module and select from the New Device dialog box. The available I/O modules are listed in the following tables.

Quantum Analog and Digital Modules

These analog and digital I/O modules are supported in Quantum Ethernet remote

I/O drops:

Input

Analog I/O Modules :

140 ACI 030 00

140 ACI 040 00

140 AII 330 00

140 AII 330 10

140 ARI 030 10

140 ATI 030 00

140 AVI 030 00

Digital I/O Modules :

140 DDI 153 10

140 DDI 353 00

140 DDI 353 10

140 DDI 364 00

140 DDI 673 00

140 DDI 841 00

140 DDI 853 00

140 DAI 340 00

140 DAI 353 00

140 DAI 440 00

Output

140 ACO 020 00

140 ACO 130 00

140 AIO 330 00

140 AVO 020 00

140 DDO 153 10

140 DDO 353 00

140 DDO 353 01

140 DDO 353 10

140 DDO 364 00

140 DDO 843 00

140 DDO 885 00

140 DAO 840 00

140 DAO 840 10

140 DAO 842 10

Input/Output

140 AMM 090 00

140 DDM 390 00

140 DDM 690 00

140 DAM 590 00

18 S1A48978.14

Input

140 DAI 453 00

140 DAI 540 00

140 DAI 543 00

140 DAI 553 00

140 DAI 740 00

140 DAI 753 00

140 DII 330 00

140 DSI 353 00

Output

140 DAO 842 20

140 DAO 853 00

140 DRA 840 00

140 DRC 830 00

140 DVO 853 00

140 DIO 330 00

Remote I/O Modules

Input/Output

Modicon X80 Analog and Digital Modules

These analog and digital I/O modules are supported in Modicon X80 Ethernet remote I/O drops:

Input

Analog I/O Modules :

BMX ART 0414

BMX ART 0814

BMX AMI 0410

BMX AMI 0800

BMX AMI 0810

Digital I/O Modules :

BMX DDI 1602

BMX DDI 1603

BMX DDI 1604

BMX DAI 0805

BMX DAI 0814

BMX DAI 1602

BMX DAI 1603

BMX DAI 1604

BMX DAI 1614

BMX DAI 1615

BMX DDI 3202K

BMX DDI 6402K

Output

BMX AMO 0210

BMX AMO 0410

BMX AMO 0802

BMX DDO 3202K

BMX DDO 6402K

BMX DDO 1602

BMX DDO 1612

BMX DAO 1605

BMX DAO 1615

BMX DRA 0804

BMX DRA 0805

BMX DRA 0815

BMX DRA 1605

BMX DRC 0805

Input/Output

BMX AMM 0600

BMX DDM 16022

BMX DDM 16025

BMX DDM 3202K

NOTE: Schneider Electric recommends that you upgrade the module with the latest available software version. However, a BMX ART 0414 module, V2.1 or later, can work properly behind a Modicon X80 remote I/O adapter module.

Intelligent and Special Purpose Modules

These intelligent/special purpose modules are supported in Quantum and

Modicon X80 Ethernet remote I/O drops:

Type expert

Quantum Module Modicon X80 Module

BMX CRA 312 00

—

BMX CRA 312 10

BMX ERT 1604T 140 ERT 854 10

140 ERT 854 20

140 ESI 062 10

S1A48978.14

Remote I/O Modules

Type counting communication

Quantum Module

140 EHC 105 00

140 EHC 202 00

140 XBE 100 00

140 NRP 312 00/01

Modicon X80 Module

BMX CRA 312 00

—

BMX CRA 312 10

BMX EHC 0200

BMX EHC 0800

BMX NOM 0200.

Restrictions are described in chapter BMXNOM0200

Limitation and

Implementation Rules (see

Modicon X80,

BMXNOM0200 Serial Link

Module, User Manual).

BMX EIA 100 (max of 1 per drop; may be combined with one BMX NOM 0200 module)

BMX NRP 0200/01 fiber cable conversion

NOTE: Schneider Electric recommends that you upgrade the module with the latest available software version. However, a BMX NOM 0200 module, V1.4 or later, can work properly behind a Modicon X80 remote I/O adapter module.

Modicon X80 Analog and Digital Module Versions

When the following modules are used in an EIO drop with a BMX CRA 312 10 adapter module, they require these versions (or later):

Module

BMX AMI 0410

BMX AMM 0600

BMX AMO 0210

BMX ART 0414

BMX ART 0814

BMX EHC 0200

BMX EHC 0800

Product Version

PV5

PV5 (PV6)

PV7 (PV8)

PV5 (PV6)

PV7

PV3 (PV4)

PV5 (PV6)

PV3

Hardware Release Level

RL5

RL5 (RL6)

RL7 (RL8)

RL5 (RL6)

RL7

RL3 (RL4)

RL5 (RL6)

RL3

Software Version

SV1.1

SV1.2

SV1.1

SV2.0

SV2.1

SV2.0

SV2.1

SV1.1

20 S1A48978.14

Overview

Remote I/O Modules

This chapter describes the hardware installation of a Quantum EIO system. It includes the installation of modules in the local rack and the Ethernet remote I/O drop to which it is connected. Other discussions include the interconnections between rack-mounted modules and the hardware considerations for different

PLC platforms.

Installing Quantum EIO Modules

Introduction

This section describes the installation of these Quantum EIO modules:

• 140CRP31200 remote I/O head module (on the local rack)

• 140CRA31200 remote I/O adapter module (on a Quantum remote I/O drop)

• 140CRA31908 remote I/O adapter module (for S908 applications)

• BMXCRA312•0 remote I/O adapter module (on a Modicon X80 remote I/O drop)

Installing the Quantum Controller

Introduction

For any Quantum EIO system, install a Quantum controller on the local rack. Only processors with firmware version 3.0 or later (version 3.10 for BMXCRA312•0 support) are compatible with Quantum EIO installations.

Compatible Processors

Compatible processors:

Processor Type standalone

Hot Standby

Part

140 CPU 651 50

140 CPU 651 60

140 CPU 652 60

140 CPU 658 60

140 CPU 671 60

140 CPU 672 60

140 CPU 672 61

140 CPU 678 61

NOTE: Low-end Quantum processors (140 CPU 434 12U, 140 CPU 534 14U,

140 CPU 311 10) and Quantum safety processors (140 CPU 651 60S, 140

CPU 671 60S) are not compatible with Quantum EIO systems.

Selecting a Power Supply

When installing a Quantum controller, add a power supply module that is capable of supplying power to all modules on the rack.

S1A48978.14

Remote I/O Modules

Mounting a Quantum EIO-Compatible Module on the Backplane

Introduction

Use these instructions to install Quantum and Modicon X80 modules that operate in a Quantum EIO system:

• 140CRP31200 remote I/O head module (on the local rack)

• remote I/O adapter module:

◦ 140CRA31200 remote I/O adapter module (on a Quantum remote I/O drop)

◦ BMXCRA312•0 adapter module (on a Modicon X80 remote I/O drop)

◦ 140CRA31908 adapter module facilitates the use of S908 hardware and applications in M580 Ethernet I/O architectures.

• 140NOC78000 distributed I/O head module (on the local rack)

• 140NOC78100 control head module (on the local rack)

Grounding Considerations

Do not apply power to a Quantum rack until connections are made at both ends of the Ethernet cable. For example, connect the cable to both the 140CRP31200 and another device (adapter module) or ConneXium dual-ring switch DRS before you turn on the power.

Refer to the Quantum EIO System Planning Guide for details on dual-ring switches (DRSs).

DANGER

ELECTRICAL SHOCK HAZARD

• Switch off the power supply to the automation controller stations at both ends of the connection before inserting or removing an Ethernet cable.

• Use suitable insulation equipment when inserting or removing all or part of this equipment.

Failure to follow these instructions will result in death or serious injury.

Use fiber-optic cable to establish a communications link when it is not possible to master potential between distant grounds.

22 S1A48978.14

Remote I/O Modules

Mounting a Module

Step Action

Hold the module at an angle and mount it on the 2 hooks near the top of the backplane.

The figure shows the correct way to hold the module:

Swing the module down so the connector engages the backplane connector.

Use a Phillips-head screw driver to tighten the screw at the bottom of the module from 2 to

4 in-lbs or from .22 through .45 N•m of torque.

NOTE: The figure above shows a Quantum module being mounted from top to bottom. Modicon X80 modules mount from bottom to top.

Replacing a Module

You can replace a Quantum EIO module at any time using another module with compatible firmware. The replacement module obtains its operating parameters over the backplane connection from the CPU. The transfer occurs immediately at the next cycle to the device.

The operating parameters that the CPU sends to a replacement module do not include any parameter values that were edited in the original module using explicit messaging SET commands.

Quantum EIO-Compatible Module Installation Considerations

Introduction

Observe the following guidelines when you install these Quantum and Modicon

X80 modules in a Quantum EIO system:

• 140CRP31200 remote I/O head module (on the local rack)

• remote I/O adapter module (on the remote I/O drop)

◦ 140CRA31200 module on a Quantum drop

◦ 140CRA31908 adapter module on a Quantum drop

◦ BMXCRA312•0 module on a Modicon X80 drop

• 140NOC78000 distributed I/O head module (on the local rack)

• 140NOC78100 control network head module (on the local rack)

S1A48978.14

Remote I/O Modules

are clearly labeled, page 12

Grounding Considerations

DANGER

ELECTRICAL SHOCK HAZARD

• Switch off the power supply to the automation controller stations at both ends of the connection before inserting or removing an Ethernet cable.

• Use suitable insulation equipment when inserting or removing all or part of this equipment.

Failure to follow these instructions will result in death or serious injury.

Use fiber-optic cable to establish a communications link when it is not possible to master potential between distant grounds.

NOTE: Refer to the ground connections information in Electrical installation guide .

Installation

You can apply power to the Quantum EIO controller rack after the 140CRP31200 head module or adapter module is inserted:

• Successful installation:

◦ Initialization is finished.

◦ Interconnections to other modules are validated (drop adapter module only).

• Unsuccessful installation:

◦ Initialization does not finish.

◦ Interconnections to other modules are not validated (adapter modules only).

You can see the status of the installation on the LED display.

NOTE: Because all modules on the local rack are initialized when power is applied, the 140CRP31200 remote I/O head module can only validate the interconnections with 140NOC78000 and 140NOC78100 head modules after these modules have been initialized. Therefore, the adapter module waits until its queries about the interconnected port information are answered.

NOTE: These guidelines pertain to the installation of a single head module or adapter module, not the entire network. For network power-up guidelines, refer to Quantum EIO, System Planning Guide .

Remote I/O Network Cable Installation

Introduction

Your application can include:

• communications with a simple remote I/O daisy chain loop

• communications with a mix of remote I/O and distributed I/O networks

The cable connections to the 140CRP31200 remote I/O head module on the local rack are different in these scenarios. They are discussed below.

Each device network port on the 140CRP31200 module is connected to the main ring of the daisy chain. Likewise, each device network port on a 140CRA31200 or

BMXCRA312•0 adapter module is connected to an Ethernet I/O device. The

140CRP31200 module and the •••CRA312•0 adapter modules do not have fiber optic ports.

The Ethernet ports

on the 140CRP31200 module and the •••CRA312•0 adapter modules.

24 S1A48978.14

Remote I/O Modules

Remote I/O Simple Daisy Chain Loop

The 140CRP31200 module supports communications with Ethernet remote I/O drops in daisy chain loops:

1 local rack with a 140CRP31200 remote I/O head module

2 Modicon X80 remote I/O drop with a BMXCRA312•0 adapter module

3 Quantum remote I/O drop with a 140CRA31200 adapter module

When you support only remote I/O, you do not have to link the 140CRP31200 module to other communication modules on the local rack.

Mix of Remote I/O Drops, Distributed I/O Devices, and Clouds

The Quantum EIO architecture allows distributed I/O devices to participate directly on the remote I/O network. This can be useful if, for example, you want to integrate a SCADA or HMI panel or other non-Quantum device into the remote I/O network.

S1A48978.14

Remote I/O Modules

installing a module on the backplane, page 22

Distributed I/O devices cannot be connected directly to the main ring of the remote

I/O network, but they can be connected via a DRS. Most DRS preconfigurations enable some switch ports to support distributed I/O clouds:

1 main ring

2 140CRP31200 interlinked to 140 NO• 7•• module on the local rack

3 dual-ring switch (DRS)

4 dual-ring switch (DRS) connection to distributed I/O sub-ring

5 dual-ring switch (DRS) connection to distributed I/O cloud

Some dual-ring switch (DRS) preconfigurations support the connection of distributed I/O devices connected directly to a sub-ring. In these configurations, the distributed I/O devices have the advantage of cable redundancy provided by the sub-ring loop. In order for a distributed I/O device to operate on a sub-ring, use a device with 2 Ethernet ports that support RSTP.

The above figure shows two STB islands used as distributed I/O devices on a subring. The network interface module installed in each island is an STB NIP 2311

NIM, which has dual Ethernet ports and the RSTP service.

Installing the Communications Adapter on the Remote Drop

Introduction

This section describes the installation of the 140CRA31200 or BMXCRA312•0 adapter module in an Ethernet remote I/O drop.

Installing a Quantum EIO Adapter Module

Locate a Backplane Slot

Install the 140CRA31200 adapter module in any slot in the remote I/O drop. Insert the BMXCRA312•0 adapter module in slot 0 only in the remote I/O drop.

Refer to the directions for

26 S1A48978.14

Remote I/O Modules

Power Consumption

Power consumption is 1.2 A on a 5 Vdc power rail on the backplane (6 W). The adapter module supports modules on 2 racks. (Power consumption has no relation to the number of installed rack modules.)

Select a Power Supply

When configuring the PLC station, use a power supply module that can supply power to all rack modules.

NOTE: You can place a power supply module in any slot on Quantum

Ethernet remote I/O drop. In Modicon X80 Ethernet remote I/O drops, you can insert the power supply only in the double-wide slot to the left of slot 0.

Select a power module that suits your unique system requirements. These modules (and their conformally coated versions) are supported:

Power Supply Type standalone summable

Quantum Module

• 140 CPS 21 00 (C)

• 140 CPS 511 00 (C)

• 140 CPS 111 00 (C)

Modicon X80 Module

–

• BMX CPS 2010

• BMX CPS 3020

• BMX CPS 2000

• BMX CPS 3500

• BMX CPS 3540

• BMX CPS 4002 redundant

• 140 CPS 214 00 (C)

• 140 CPS 414 00 (C)

• 140 CPS 114 20 (C)

• 140 CPS 224 00 (C)

• 140 CPS 424 00 (C)

• 140 CPS 524 00 (C)

• 140 CPS 124 20 (C)

• ABL 8RED 24400

• ABL 8REM 24030

• ABL 8RPS 24030

Installing Ethernet Remote I/O Drops on a Remote Rack

Introduction

These guidelines apply to Ethernet remote I/O drops on remote racks.

Racks and Extensions

An Ethernet remote I/O drop can include 2 racks. In a 2-rack drop, the racks are linked with these bus extender modules and cables:

Remote Drop Type

Quantum

Modicon X80

Bus Extender Module

140 XBE 100 00

BMX XBE 1000

Cable

140 XCA 717 0• (1 to 3 m)

BMX XBC •••K (0.8 to 12 m)

Maximum Configuration

Quantum remote I/O drops can include two 16-slot racks for a maxiumum of 32 slots. Modicon X80 remote I/O drops with a BMXCRA312•0 adapter module can support two racks for a maximum of 24 slots.

S1A48978.14

Remote I/O Modules

list of modules that remote I/O installations support, page 18

The table shows the maximum number of modules of each type in remote drops:

Module Type Quantum 140CRA31200 remote I/O adapter (note 1) power supply (note 2) bus extension (note 3)

I/O

Modicon X80

BMXCRA312•0

• NOTE 1:

◦ 140CRA31200: This adapter module consumes 1 slot in the main (first) rack in Quantum remote drops. The extended (second) rack in a Quantum remote I/O drop does not require an adapter.

◦ BMXCRA312•0: This adapter module supports a Modicon X80 remote I/O drop with 2 racks when a bus extender module is in both the main and extended racks.

• NOTE 2: A power supply consumes 1 dedicated slot in each rack in Quantum and Modicon X80 remote I/O drops.

• NOTE 3: A bus extender module is required for each rack in remote I/O drops. In Quantum remote I/O drops, the bus extender consumes 1 rack slot.

In Modicon X80 remote I/O drops, the bus extender attaches to the end of the rack and does not consume a rack slot.

Refer to the

Setting the Location of the Ethernet Remote I/O Drop

Setting Rotary Switches

Set the location of the Ethernet remote I/O drop on the network with the rotary switches on the front of the 140CRA31200 or BMXCRA312•0 adapter module before you apply power to the module and before you download the application:

The values you set are applied during a power cycle. If you change the switch settings after the module has powered up, the Mod Status LED is activated and a mismatch message is logged in the module diagnostic.

Because new values on the rotary switches are implemented only at the next power cycle, we recommend that you set the value before starting the module.

(Valid values: 00 ... 159)

The values on the rotary switches combine with the device prefix (for example,

140CRA_ xxx or BMXCRA_ xxx ) to create the device name (where xxx represents the value of the rotary switches). The preceding figure shows the Tens switch set to 0 and the Ones switch set to 01, for a device name of 140CRA_001.

NOTE:

• The rotary switches can be manipulated with a small flat-tipped screwdriver.

• No software is required to configure or enable the rotary switches.

• Do not use the Stored and Clear IP settings on the Ones rotary switch. (The functionality of these settings does not apply to remote I/O installations.)

S1A48978.14

Remote I/O Infrastructure Cables

Cable Installation

Remote I/O Modules

Introduction

Observe these guidelines when making cable connections between remote I/O devices on a Quantum EIO installation. (Remote I/O devices include local racks, remote I/O drops, or DRSs.)

A copper cable connection between 2 consecutive remote I/O devices cannot exceed 100 m. A fiber cable connection between 2 consecutive remote I/O devices cannot exceed 15 km (single mode) or 2.5 km (multi-mode).

Connections Between Devices

This figure shows the distances between remote I/O devices in Quantum EIO installations:

1 140CRP31200 remote I/O head module

2 140NOC78000 distributed I/O head module

3 140NOC78100 control head module

4 DRS (with copper and fiber ports): This DRS extends the distance between devices using fiber cable (up to 15 km).

5 distributed I/O sub-ring connected to the main ring via (4)

6 fiber cable portion of the main ring used to separate the DRSs beyond 15 km

7 copper cable (twisted pair) portion of the main ring

8 remote I/O drop

9 DRS (with copper ports only): This DRS extends the distance between devices.

10 control network

NOTE: It is required to use shielded twisted pair CAT5e (10/100 Mbps) cables, ideally ConneXium 490NTC•000•• cables.

S1A48978.14

Remote I/O Modules

NOTICE

COMMUNICATION FAULTS

Use shielded twisted pair CAT5e (10/100 Mbps) cables to prevent communication faults.

Failure to follow these instructions can result in equipment damage.

Interlink

To support distributed I/O sub-rings in Quantum EIO installations, establish an interlink between an Ethernet communication module on the local rack and the

140CRP31200 remote I/O head module:

1 local rack, including a 140 NOC 780 00 distributed I/O head module that is interlinked with a 140CRP31200 remote I/O head module

2 DRS connected to the main ring and a distributed I/O sub-ring

3 distributed I/O sub-ring

NOTE: For the interlink connection, it is required to use shielded twisted pair

CAT5e (10/100 Mbps) cables.

NOTICE

COMMUNICATION FAULTS

For the interlink connection, use shielded twisted pair CAT5e (10/100 Mbps) cables to prevent communication faults.

Failure to follow these instructions can result in equipment damage.

Duplicate IP Address Checking

Introduction

Each Quantum EIO module has a single IP address. Therefore, the address conflict detection algorithm (also called duplicate IP checking) is performed based on the status (link up, link down) of the ports.

Link Down

These conditions apply when links are lost:

30 S1A48978.14

Control Expert Parameter tab, page

Remote I/O Modules

Link Status

A transition has occurred from 1 connected link to all links down.

There is 1 link down and at least 1 connected link.

Description

When no module ports are connected to a cable (all links are down), all services are reset. For example, I/O connections, Modbus connections, and explicit EtherNet/IP connections close, but low-level network services (like RSTP or switches) are not affected. The updated Net Status LED indicates the status.

There is no impact on services that are running in the module.

Link Up

These conditions apply when links are added:

Link Status

A transition has occurred from no connected links to

1 connected link.

A transition has occurred from at least 1 connected link to an additional connected link.

Description

A duplicate IP check is performed:

• no duplicate : All services start.

• duplicate : I/O services stop. The 140CRA31200 or

BMXCRA312•0 adapter module gets new configuration and downloads the IP configuration again. The system goes to default IP and I/O modules are set to fallback mode.

A duplicate IP check is performed:

• no duplicated: All services continue.

• duplicate: All services stop.

NOTE: The updated Net Status LED indicates the status.

Loss of I/O Connection

Conditions

An I/O connection can be lost under these conditions:

Condition CPU 140CRP31200

Adapter Module

(140CRA31200 or

BMXCRA312•0)

• Perform a hot swap.

• Replace a module of the same type.

X X

There is no remote I/O cable connection.

The I/O connection is closed.*

*Hot swap of the CPU results in an explicit close (lost I/O connection).

Remote Adapter Fallback

In some instances, the 140CRA31200 or BMXCRA312•0 adapter module on the remote I/O drop can lose I/O connections for a period longer than the configured hold up time. During the hold up, the adapter tries to get IP and configuration parameters from the 140CRP31200. If the adapter does not obtain those parameters, it gets these results:

• inputs : retain last known values

• outputs : set to fallback

NOTE: Configure the hold up time on the

S1A48978.14

Remote I/O Modules

Introduction

Use Control Expert to configure your local rack and remote drops for Ethernet communications.

Creating a Control Expert Project

Introduction

Use the instructions in this section to create a Control Expert project that allows communication between a local rack and an Ethernet remote I/O drop. Here are the basic stages of the Control Expert configuration:

1. Select a high-end Quantum processor to create a new Control Expert configuration.

2. Add a power supply to the local rack.

3. Add an Ethernet remote I/O head module (140 CRP 312 00) to the local rack.

4. Configure a rack assembly for the Ethernet remote I/O drop.

NOTE: These instructions assume that you have a working knowledge of

Control Expert.

Configuring the Local Rack

Assemble a Local Rack

In Control Expert, assemble a Quantum rack:

Step

Action

In Control Expert, create a project.

Add a PLC from the New Project window.

In the Project Browser , doubleclick Local Bus .

Add a power supply to the Local

Bus .

Add a 140 CRP 312 00 remote I/O head module to an available slot in the local rack.

Use the same method to add a 140

NOC 780 00 distributed I/O head module to the Local Bus .

Double-click any empty slot to add modules to the Local Bus .

Save the file.

Comment

Click File > New .

Result : The New Project window appears.)

For this example, double-click the 140 CPU

651 50 module. ( New Project > Quantum >

140 CPU 651 50 ).

Click Tools

Project Browser

Configuration > Local Bus .

Result : The Local Bus window opens, and the rack includes the processor you selected.)

Drag the module to slot 1. ( Tools catalog

> Hardware

> Local Quantum Drop > Supply >

140 CPS 114 X0 )

Drag the module to slot 4. ( Tools catalog

> Hardware

> Local Quantum Drop >

Communication > 140 CRP 312 00 )

Drag the module to slot 5. ( Tools catalog

> Hardware

> Local Quantum Drop >

Communication > 140 NOC 780 00 )

This step is optional, but you can provide

Ethernet transparency between the device network and the control network by adding a

140 NOC 781 00 control head module to the local rack.

Click File > Save .

32 S1A48978.14

Remote I/O Modules

The local rack in your Control Expert configuration should look like this:

S1A48978.14

Note that the Local Bus contains these modules:

• power supply (140 CPS 114 •0)

• CPU (140 CPU 651 50)

• remote I/O head module (140 CRP 312 00)

• distributed I/O head module (140 NOC 780 00)

• control head module (140 NOC 781 00)

Rack Parameters

Double-click the 140 CRP 312 00 module in the Local Bus window to access these configuration parameters for the local rack:

•

•

•

•

•

Service port, page 41

•

Device DDT, page 46

NOTE: You can accept the automatically assigned IP address or change the

IP address in the Control Expert IP Config tab.

Rack Considerations

Remember:

• The copy/cut/paste commands are not available for the 140CRP31200 module.

• You can cut or copy other devices in the local rack or the drop and paste them in any rack of the same type. You can perform these actions (cut, copy, paste) only in the same device editor. You cannot move objects from the local rack to the drop or vice-versa.

• The number of the first slot in a rack is 1. Therefore, a 4-slot rack has slot numbers 1, 2, 3, 4.

Remote I/O Modules

added a 140CRP31200 module to the local rack in a

Configuring the Ethernet Remote I/O Drop

Instructions

In the previous topic, you

Control Expert project, page 32

. The 140CRP31200 remote I/O head module supports communication with an Ethernet remote I/O rack.

When you insert a 140CRP31200 module in the local rack, Control Expert automatically creates an EIO Bus , which has the same capabilities as an existing

S908 legacy remote I/O bus.

In the EIO Bus , you can select a Quantum drop or an Modicon X80 drop.

Within an Modicon X80 drop, the BMXCRA31200 adapter module is inserted by default. This module supports only standard digital and analog modules. Insert a

BMXCRA31210 module from the Drop end communicator field if you require more functionality, such as the following:

•

service port, page 16

• expert modules

•

time stamping, page 36

• CCOTF

Use these instructions to configure a remote rack ( EIO Bus ) that includes a

140CRA31200 or BMXCRA312•0 adapter module in slot 1:

Step

Action

In the Project Browser , double-click EIO

Bus to see the (empty) drop.

Comment

( Tools view

> Project Browser > Structural

Project

Configuration

EIO

Bus )

In the EIO Bus window, double-click the square link connector to access the available racks.

Select a rack for a Quantum Ethernet I/O drop or a Modicon X80 Ethernet I/O drop.

NOTE: If you select a Modicon X80 drop, also choose a BMXCRA31200 or BMXCRA31210 adapter module in the Drop end communicator field of the New Device window.

Double-click any empty slot to add modules to the EIO Bus .

Save the file.

The New Device window appears.

This example uses the 4-slot 140 XBP

004 00 rack: New Device

Number

Click File > Save .

> Part

> EIO Quantum Drop > Rack

> 140 XBP 004 00 . Select the device and press OK .

For this example, this step is optional.

34 S1A48978.14

local rack (including a 140CRP31200 remote I/O head module), page 32

Remote I/O Modules

The Control Expert configuration now includes the remote rack window ( EIO Bus ). Because the Ethernet remote

I/O drop requires a module for communication with the local rack, Control Expert automatically adds an adapter module in slot 1.

Rack Parameters

The adapter module is now installed as the communications adapter module of your Ethernet remote I/O drop. Double-click the adapter to see its configuration tabs:

•

RSTP, page 39

•

SNMP, page 39

•

Service port, page 41

Rack Considerations

Remember these points:

• You can insert 2 racks on a Modicon X80 Ethernet remote I/O drop with a

BMXCRA31210. You can only insert 1 rack with a 140CRA31200 module.

• Control Expert automatically inserts BMXCRA312•0 adapter modules in slot

0. You cannot delete or move these modules.

• The number of the first slot in a Quantum rack is 1. The number of the first slot in a Modicon X80 rack is 0. Therefore, a 4-slot Quantum rack includes slot numbers 1, 2, 3, 4, and a 4-slot Modicon X80 rack includes slot numbers

0, 1, 2, 3.

• You can cut or copy other devices in the remote drop and paste them in any rack of the same type. You can perform these actions (cut, copy, paste) only in the same device editor. You cannot move objects from the local rack to the drop or vice-versa.

Available Control Expert Configuration Tabs

About the Parameters

The Control Expert configuration tabs are available after you have configured these:

•

•

Ethernet remote I/O drop (including a 140CRA31200 or BMXCRA312•0 remote I/O adapter module), page 34

S1A48978.14

Remote I/O Modules

double-click the communication module in the local rack, page 32 .

Control Expert Configuration Tabs

This table indicates the available Control Expert configuration tabs for the local rack’s 140 CRP 312 00 head module and the remote I/O drop’s adapter module:

Control Expert Tab 140CRP31200 Head Module

(Local Rack)

Time Stamping, page 36

•••CRA312•0 Adapter Module

(Remote I/O Drop)

(See note.)

X (BMXCRA31210 only)

NOTE: The adapter module (140CRA31200 or BMXCRA312•0) automatically receives an IP address. To maintain unique addressing on the network, keeping and using the auto-assigned

IP addresses is generally considered a good practice.

NTP Configuration in Control Expert

Introduction

This topic describes the Control Expert NTP (time stamp) parameters for the

BMXCRA31210 module. To access these parameters on the Control Expert NTP tab,

Access the NTP Tab

To access the NTP tab, open the Bus Editor , double click on the CRP module and then select the NTP tab:

Field

NTP server configuration for adapter modules

Parameter

IP address of Primary NTP Server

IP address of Secondary NTP Server

Polling period

—

Value a.b.c.d (0.0.0.0)

1, 120 (5)

—

Comment entered value online behavior disabled in connected mode

NOTE: For time zones that support daylight saving time (DST), the default value is enabled (checked). It is disabled (unchecked) for all time zones that don't support DST.

Valid IP addresses for NTP servers:

• 1.0.0.0 ... 126.255.255.255

• 128.0.0.0 ... 223.255.255.255

For any other IP address, a detected error is reported. Addresses 224.0.0.0 and higher are experimental multicast addresses. Addresses starting at 127 are loopback addresses.

36 S1A48978.14

Setting the Time Zone

Set the time zone in the Project Settings window:

Remote I/O Modules

Set the time zone:

Step

Action

In Control Expert, select Tools > Project Settings .

Expand the General menu in the Projects Settings window, and select the Time setting.

Select the appropriate values for each time zone property.

Click Apply to save changes, or click OK to save changes and close window.

Control Expert Configuration for Remote I/O Ethernet Modules

Overview

This section describes the module configuration tabs in Control Expert. Use the parameters on these tabs to configure services for the 140CRP31200 module in the local rack and the adapter module (140CRA31200 or BMXCRA312•0) in

Ethernet remote I/O drops.

S1A48978.14

Remote I/O Modules

IP Configuration

140CRP31200 module, page 32

Access the IP Config Tab

The Control Expert IP configuration parameters apply to the 140CRP31200 head module in the local rack. To access the IP Config tab,

double-click on the

IP Config Parameters

Configure the IP parameters for the 140CRP31200 head module in the IP address configuration field on the IP Config tab:

Parameter

IP address A

IP address B

Subnetwork mask

Gateway address

Description

The address corresponds to the 140CRP31200 module.

This address is used for Hot Standby configurations.

NOTE: If you change IP address A, the system may recalculate all IP addresses (including those of the drops) to keep all devices in the same subnet.

This bit mask identifies or determines the IP address bits that correspond to the network address and the subnet portion of the address. (The value can be changed to any valid value in the subnetwork.)

This is the IP address of the default gateway to which messages for other networks are transmitted.

Default Value

192.168.10.1

IP address A + 1

255.255.0.0

0.0.0.0 (when not used)

Configure the IP parameters for the adapter module (in the remote drop) in the

CRA IP address configuration field on the IP Config tab:

Parameter

Drop No.

Device Name

IP Address

Description drop number device name (140CRA31200 or BMXCRA312•0 adapter)

When an Ethernet remote I/O drop is added, the adapter module is automatically assigned an IP address. (You can change this IP address in the IP Address column, but we recommend that you accept the automatically assigned IP address.)

Default Value

—

S1A48978.14

Remote I/O Modules

RSTP Bridge Configuration

About RSTP

Use RSTP to design a network with redundant cabling so that remote I/O communications automatically find an alternate path if a communication disruption occurs (for example, a cable breaks or a device becomes inoperable). This method does not require you to manually enable or disable communication paths.

Changing these parameters can affect sub-ring diagnostics, I/O determinism, and network recovery times.

Access the RSTP Tab

You can access the RSTP parameters in Control Expert by double-clicking these modules in the Control Expert rack view:

• head module on the local rack (140CRP31200)

• adapter module on the remote drop (140CRA31200 or BMXCRA312•0)

The RSTP tab appears:

Parameters

This table shows the Bridge priority parameters for the RSTP Operational State on the Control Expert RSTP tab:

Bridge Priority

Root

Backup Root

Value

4096

140CRP31200 default for Hot Standby

(automatic)

Adapter Module

—

Participant 32768 — default

NOTE: In Hot Standby systems, the RSTP bridge priority is applied to the 140CRP31200 module in rack A.

SNMP Agent Configuration

About SNMP

Use the SNMP tab in Control Expert to configure SNMP parameters for these

Quantum Ethernet I/O modules:

• head module on the local rack (140CRP31200)

• adapter module on the remote drop (140CRA31200 or BMXCRA312•0)

An SNMP v1 agent is a software component of the SNMP service that runs on these modules to allow access to diagnostic and management information for the modules. You can use SNMP browsers, network management software, and other tools to access this data. In addition, the SNMP agent can be configured with the

IP addresses of 1 or 2 devices (typically PCs that run network management

S1A48978.14

Remote I/O Modules

software) to be the targets of event-driven trap messages. Such messages inform the management device of events like cold starts and the inability of the software to authenticate a device.

Access the SNMP Tab

Double-click these modules in the Control Expert configuration to access their

SNMP tabs:

• 140CRP31200 head module (local rack)

• 140CRA31200 or BMXCRA312•0 adapter module (remote drop)

The SNMP tab appears:

Field

IP Address managers

Agent

Use the SNMP tab to configure the SNMP agents for the communication modules in the local rack and remote drop. The SNMP agent can connect to and communicate with 1 or 2 SNMP managers as part of an SNMP service. The

SNMP service includes:

• authentication checking, by the Ethernet communication module, of any

SNMP manager that sends SNMP requests

• management of events or traps

SNMP Parameters

These parameters are found on the Control Expert SNMP tab:

Parameter

IP Address manager 1

IP Address manager 2

Location (SysLocation)

Contact (SysContact)

Enable SNMP manager

Description

The address of the first SNMP manager to which the SNMP agent sends notices of traps.

The address of the second SNMP manager to which the SNMP agent sends notices of traps.

device location description of the person to contact for device maintenance unchecked (default): You can edit the

Location and Contact parameters.

checked: You cannot edit the Location and Contact parameters.

Value

0.0.0.0 ... 255.255.255.255

31 characters (maximum) checked/unchecked

40 S1A48978.14

Remote I/O Modules

Field

Community names

Security

Parameter

Set

Get

Trap

Enable “Authentication failure” trap

Description password that the SNMP agent requires to read commands from an SNMP manager

(default = Public ) unchecked (default): not enabled.

checked (enabled): The SNMP agent sends a trap notice to the SNMP manager if an unauthorized manager sends a Get or Set command to the agent.

Value

15 characters (maximum) checked/unchecked

Online Behavior

Tests are done to verify that the IP addresses of the managers are not:

• multicast

• loopback

• broadcast

Service Port Configuration

Access the Service Port Tab

Double-click these modules in the Control Expert rack view to access the Control

Expert Service Port tab:

• head module on the local rack (140CRP31200)

• adapter module on the remote drop (140CRA31200 or BMXCRA31210)

The Service Port tab appears:

Field

Service Port

Parameter

Enabled

Disabled

Service Port Parameters

These parameters are on the Control Expert Service Port tab:

Value

—

Comment

Enable port and edit port parameters.

Disable port parameters.

S1A48978.14

Remote I/O Modules

Field

Service Port

Mode

Parameter

Access (default)

Mirroring

Value

—

Access Port

Configuration

Port Mirroring

Configuration

Service Port

Number

Source Port(s)

ETH1

Internal Port

ETH2

ETH3

ETH4

added a remote I/O drop to your Control Expert project, page 27

Comment

This mode supports Ethernet communications.

In port mirroring mode, data traffic from one or more of the other ports is copied to this port. A connected tool can monitor and analyze port traffic.

NOTE: In this mode, the SERVICE port acts like a read-only port.

That is, you cannot access devices (ping, connection to Control

Expert, etc.) through the SERVICE port.

You cannot edit the value in the Service Port Number field.

all Ethernet traffic for the module

140CRP31200: all INTERLINK port traffic adapter modules: Ethernet traffic through the first remote I/O port

140CRP31200: Ethernet traffic through the first remote I/O port adapter modules: Ethernet traffic through the second remote I/O port adapter modules: Ethernet traffic through the second remote I/O port

(140CRP31200 only)

On Line Behavior

140CRP31200 head module in explicit messages. (The changed values are not stored, so a mismatch can exist between the parameters that are being used and those that are in the stored application.) If the module does not respond to the explicit messages, a message appears.

Limitations

The SERVICE port on the 140CRP31200 head module and the adapter modules have the same limitations as the cloud port of the dual-ring switch (DRS).

Therefore, the module's cloud port and the DRS's cloud port can be connected to the same equipment.

The maximum load the module can process from distributed I/O devices:

• 5 Mbps: per SERVICE port

• 20 Mbps: total distributed I/O traffic on the main ring

For more information about considerations that apply to the use of the distributed

I/O cloud port and the service port on the DRS, refer to the Predefined

Configuration Files topic in the Quantum Ethernet I/O System Planning Guide .

Control Expert Configuration for Ethernet Remote I/O Drops

Introduction

This section discusses the use of Control Expert to configure the Ethernet remote

I/O drop and its adapter module. It includes descriptions of the parameters on the

Configuration , Parameter , and Device DDT tabs in Control Expert.

NOTE: These instructions assume that you have already

42 S1A48978.14

Remote I/O Modules

Configuring the Size and Location of Data

Introduction

Use the Control Expert Configuration tab to configure the size and location of data for an Ethernet remote I/O drop that includes a 140CRA31200 or

BMXCRA312•0 remote I/O adapter module.

NOTE: These instructions assume that you have already

Control Expert project, page 34 .

Access the Configuration Tab

Access the Configuration parameters in Control Expert:

Step

Action

Expand (+) the EIO Bus in the Control

Expert Project Browser .

Double-click the Quantum EIO drop.

Select the Configuration tab.

Comment

( Project Browser > EIO Bus > EIO

Quantum Drop / EIO Modicon X80 Drop )

The EIO drop window appears. It contains the parameter tabs from the Ethernet remote I/O drop.

The Configuration tab is available for the

Quantum EIO drop only.

The Configuration tab shows the Parameter Name and the corresponding

Value :

Configuration Parameters

On the Control Expert Configuration tab, configure these parameters for the

Ethernet remote I/O Quantum drop:

Parameter Name

Starting address status table

Ending address status table

In Bytes

Out Bytes

Value the first register in the status table (configured) the starting address + the maximum number of addresses for the configured rack size the total number of bytes for input modules in the remote I/O drop the total number of bytes for output modules in the remote I/O drop

NOTE: These parameters do not apply to Modicon X80 drops.

Configuring the Parameters

Parameter Tab (Remote I/O Drop)

This topic describes the Control Expert Parameter tab for an Ethernet remote I/O drop that includes a 140CRA31200 or BMXCRA312•0 adapter module.

NOTE: These instructions assume that you have already

Control Expert project, page 34 .

S1A48978.14

Remote I/O Modules

The Parameter tab appears:

IP Configuration tab, page 38

Access the Parameter Tab

Access the Parameter tab in Control Expert:

Step

Action

Expand (+) EIO Bus in the Control

Expert Project Browser .

Double-click the EIO drop

(Quantum or Modicon X80.

Select the Parameter tab.

Comment

Path: Project Browser > EIO Bus > EIO

Quantum Drop / EIO Modicon X80 Drop

The EIO drop window appears. It contains the parameter tabs for the remote I/O drop.

Parameter Descriptions

Use the Control Expert Parameter tab to configure the following parameters for the Ethernet remote I/O drop.

Address information parameters:

Parameter Comment

Device Name The device name of the device includes a fixed device prefix and a number provided by the rotary switch. Valid device names conform to this structure:

• 140CRA_ xxx

• BMXCRA_ xxx

Remember that xxx equals the 3-digit value selected on the rotary switches, so the device name includes the device prefix ( 140CRA or BMXCRA ) plus that value.

When the device is placed on the Ethernet remote I/O drop, the number is set to the device number. The device number does not change when the device moves to a new location.

Valid device numbers are unique within the application. A message like this appears when analysis reveals redundant device numbers:

IP Address

Sub Network

{EIO Bus (2) 140 CRA 312 00}: Device name is not unique

NOTE: The device number does not change if you move the drop, but you can modify the number. However, if you modify the number, the link breaks between the device name and the drop number. Schneider Electric recommends that you allow the drop number to equal the device name, even if it can be modified.

You cannot edit the IP address and Sub network (mask) fields. The IP address is editable only in the

of the 140CRP31200 module.

The value for Sub network is deduced from the 140CRP31200 sub network mask.

Hold up time parameter:

S1A48978.14

IU_ERIO function block, page 63

Remote I/O Modules

Parameter

Hold up time

Comment

The hold up time represents the time (ms) that device outputs are maintained in their current states after a communication disruption and before taking their fallback values:

• default value : 1000 ms

• valid value range : 50...65,530 ms

The minimum holdup time differs for standalone and Hot Standby systems. If you assign a holdup time value that is less than the recommended minimum value, you can send an I/O module to the fallback state. When communications are restored, the I/O module restarts and may not operate as anticipated.

WARNING

UNINTENDED EQUIPMENT OPERATION

Do not configure a holdup time value that is less than the recommended minimum value for standalone or Hot Standby systems:

REQUIRES CLEANUP standalone systems:

• periodic application: 4.4 x PLC scan time

• cyclic application: configured watchdog value

REQUIRES CLEANUP

Hot Standby systems: configured watchdog value + PLC scan time

Failure to follow these instructions can result in death, serious injury, or equipment damage.

Connection parameters :

Parameter

Custom RPI

CRA->CRP

RPI

CRP->CRA

RPI

Comment

Check this box to configure the CRA->CRP RPI value.

NOTE: The minimum CRA->CRP RPI value is 5 ms.

NOTE: Only change the CRA->CRP RPI value if you are using the

Inputs: The RPI is the input refresh rate at which the adapter module sends inputs to the 140CRP31200 module. The RPI is set in the subscribe field for the adapter on the remote I/O drop.

• periodic mode : default value = 1/2 MAST period

• cyclic mode : default value = 1/4 MAST watchdog timeout period

• valid values : 5...1500 (ms)

You can configure this value when Custom RPI is checked.

Outputs: Outputs are passed from the 140CRP31200 module to the adapter. Set the output refresh rate with the Application Trigger value ( CRP->CRA RPI ) at the end of the CPU MAST task:

• periodic mode : default value = 1.1 * MAST period. The value output is sent at the end of the actual MAST period.

• cyclic mode : default value = 1/4 * watchdog timeout period. The value output is sent at the end of the actual MAST period.

NOTE: The default value for the watchdog timer is 250 ms. If the MAST task does not finish within the watchdog period, the process times out. If the watchdog is greater than 4 times the MAST period, the drops could switch to fallback while the CPU is running. For example, MAST period = 20 ms, logic execution = 90 ms, watchdog time = 100 ms.

You cannot edit this value. All outputs are published synchronously or at the execution of the MAST task:

• synchronously: immediately at the end of the MAST task

• execution of IU_ERIO: You can only generate outputs when you

use the IU_

ERIO function block, page 63 . (See the note below.)

S1A48978.14

Remote I/O Modules

NOTE:

• When the Periodic mode is selected for the MAST task, the Period value allows the complete execution of the logic. (The MAST can overrun when its execution time exceeds this value.) Valid values: 1...255 ms

(increment: 1 ms).

• When Cyclic mode is selected for the MAST task, the outputs are sent upon the completion of the task. The Watch Dog value (10 ... 1500 ms, default = 250) should be greater than the execution time. Valid values:

10...1500 ms (increment: 10 ms, default = 250 ms).

Device DDT Parameters

Device DDT Parameters (Remote I/O Drop)

This topic describes the Control Expert Device DDT tab for an Ethernet remote I/

O drop that includes a 140CRA31200 or BMXCRA312•0 adapter module. A derived data type (DDT) is a set of elements with the same type ( ARRAY ) or with different types (structure).

The device DDT instance name can be defined manually but, when adding a module, a default device DDT instance name (see EcoStruxure ™ Control Expert,

Program Languages and Structure, Reference Manual) is defined by Control

Expert

NOTE:

• These instructions assume that you have already

Control Expert project, page 34

• Refer to the

Derived Data Types chapter, page 48

to create, update, and view derived data types.

Access the Device DDT Tab

Access the Device DDT parameters in Control Expert:

Step

Action

Expand (+) EIO Bus in the Control

Expert Project Browser

Double-click on the EIO drop (Quantum or Modicon X80.

Comment

Path: Project Browser

EIO Bus

EIO

Quantum Drop / EIO Modicon X80 Drop

The EIO drop window appears. It contains the parameter tabs for the remote I/O drop.

Example of the Implicit device DDT area which contains a name and a type.

Parameters

Use the Control Expert Device DDT tab to configure these parameters for the adapter on the remote I/O rack:

S1A48978.14

Parameter

Implicit device DDT Name

Goto details

Type

Remote I/O Modules

Description

A default device DDT instance name (see EcoStruxure ™

Control Expert, Program Languages and Structure,

Reference Manual) is defined by Control Expert.

NOTE:

• There are 2 device DDT types for Ethernet remote

I/O drops in a Quantum system:

◦ 140CRA31200 adapter: T_U_DROP_STD_IN

◦ BMXCRA312•0 adapter: T_M_DROP_EXT_IN

• There is 1 device DDT type for a Quantum

Ethernet remote I/O drop in an M580 system:

◦ 140CRA31200 adapter: T_Q_DROP_EXT_IN module type (uneditable) link to the DDT data editor screen

Time Stamping

Time Stamp Module

Use these modules on an Ethernet remote I/O drop:

• Modicon X80 BMXCRA31210 adapter module with a BMX ERT 1604 time stamp module

• Quantum 140CRA31200 adapter module with a 140 ERT 1604 module

This sample rack configuration in Control Expert shows an X80 EIO drop with the required BMX ERT 1604 module:

Configuration

Double-click the BMX ERT 1604 in the remote rack to see the time stamp Configuration tab.

S1A48978.14

Remote I/O Modules

NOTE: For more information about time stamping with the BMXCRA31210 modules, refer to the Modicon X80, BMXERT0604T Time Stamp Module,

User Guide .

Derived Data Types

Overview

This chapter describes how to complete your Control Expert project by creating, updating, and viewing derived data type (DDT) variables.

Device DDT Names for the Quantum EIO Remote I/O Head Module

Introduction

This topic describes the Control Expert Device DDT tab for a Quantum local rack that includes a 140CRP31200 remote I/O head module. A derived data type

(DDT) is a set of elements with the same type ( ARRAY ) or with different types

(structure).

The device DDT instance name can be defined manually but, when adding a module, a default device DDT instance name (see EcoStruxure ™ Control Expert,

Program Languages and Structure, Reference Manual) is defined by Control

Expert

Modifying a Device DDT name

In Control Expert a Device DDT name can be easily modified:

Step

Action

Open Data Editor in the Control

Expert Project Browser .

Right click on the device DDT and use the Copy/Paste .

Expand Local Bus in the Control

Expert Project Browser .

Double-click the 140CRP31200 module.

Select the Device DDT tab.

Comment

Path: Tools > Data Editor

A new default name is proposed by default.

Path: Tools > Project Browser > Project >

Configuration > Local Bus

The parameter tabs appear.

select the new DDT name (eg : My_CRP312) as the name of Device DDT.

The Implicit device DDT field contains a default name and type.

Access the Device DDT Tab

In Control Expert:

Step

Action

Expand Local Bus in the Control Expert

Project Browser .

Double-click the 140CRP31200 module.

Select the Device DDT tab.

Comment

Path: Tools > Project Browser > Project

Configuration

Local Bus

The parameter tabs appear.

48 S1A48978.14

Remote I/O Modules

Example of the Implicit device DDT area which contains a name and a type.

S1A48978.14

Parameters

Use the Control Expert Device DDT tab to configure parameters for the

140CRP31200 module on the local rack:

Parameter

Implicit device

DDT

Goto details

Name

Type

Description a default device DDT instance name (see EcoStruxure ™ Control

Expert, Program Languages and Structure, Reference Manual) is defined by Control Expert.

module type (uneditable) link to the DDT data editor screen

Implicit Device DDT Types

The 140CRP31200 module implements the implicit device DDT type in accordance with the CPU configuration:

• T_U_CRP_HSBY_IN: Hot Standby configurations

• T_U_CRP_STD_IN: standalone configurations

Hot Standby Configurations

This table describes the fields in the T_U_CRP_HSBY_IN implicit device DDT type that is used with the 140CRP31200 module in Hot Standby configurations:

Field

LOCAL_PLC

REMOTE_PLC

Type

T_U_CRP_STD_IN

Access

Description

140CRP31200 status (local PLC)

140CRP31200 status (remote/peer PLC)

Standalone and Hot Standby Configurations

This table describes the fields in the T_U_CRP_STD_IN implicit device DDT type that is used with the 140CRP31200 module in standalone and Hot Standby configurations.

ETH_STATUS (BYTE):

Name

PORT1_LINK

Type

BOOL

Rank

Bit

Description

PORT2_LINK BOOL 1 1

0 = Port 1 link is down.

1 = Port 1 link is up.

0 = Port 2 link is down.

1 = Port 2 link is up.

Remote I/O Modules

Name

PORT3_LINK

PORT4_LINK

CRP_LINK

REDUNDANCY_

STATUS

SCANNER_OK

GLOBAL_STATUS

Type Rank

Bit

Description

BOOL

0 = Port 3 link is down.

1 = Port 3 link is up.

0 = Port 4 link is down.

1 = Port 4 link is up.

0 = CRP link is down.

1 = CRP link is up.

0 = Redundant owner is not present.

1 = Redundant owner is present.

NOTE: In Hot Standby systems, if this bit is set to 1 either in the local or remote 140CRP31200 DDT then the main physical ring is OK. If this bit is set to 0 in both the local and remote 140CRP31200 DDTs, the main physical ring is broken.

BOOL 6 6

BOOL 7 7

0 = Scanner is not present.

1 = Scanner is present.

0 = At least 1 service is not operating normally.

1 = All services are operating normally.

NOTE: You can monitor breaks in the remote I/O main ring by diagnosing the

REDUNDANCY_STATUS bits in the 140CRP31200 module DDT. The system detects and reports in this bit a main ring cable break that persists for at least

5 seconds.

Within the REDUNDANCY_STATUS bit:

• 0: The cable is broken or the device is stopped.

• 1: The loop is present and healthy.

In a Hot Standby system, perform a BITWISE OR operation of the

REDUNDANCY_STATUS bit in the DDTs for both the primary and standby

140CRP31200 modules to determine whether a cable break has occurred. As indicated above, a value of 0 indicates a cable break; a value of 1 indicates no cable break.

SERVICE_STATUS (BYTE):

Name Type

RSTP_SERVICE

PORT502_SERVICE

SNMP_SERVICE

IP_ADDRESS_

STATUS

(reserved bits)

BOOL

—

Rank

Bit

Description

5...7

0 = RSTP service is not operating normally.

1 = RSTP service is operating normally or disabled.

0 = Port 502 service is not operating normally.

1 = Port 502 service is operating normally or disabled.

0 = SNMP service is not operating normally.

1 = SNMP service is operating normally or disabled.

0 = IP address is a duplicate or unassigned.

1 = Assigned IP address is not a duplicate.

—

ETH_PORT_STATUS:

50 S1A48978.14

Name

These combined 2-bit values indicate the conditions (WORD) port function

RSTP role

Remote I/O Modules

—

Rank

—

14/15

Bit

1/0

3/2

5/4

7/6

9/8

11/10

12/13

Description

Ethernet port 1 function

Ethernet port 1 RSTP role

Ethernet port 2 function

Ethernet port 2 RSTP role

Ethernet port 3 function

Ethernet port 3 RSTP role

Ethernet port 4 function

Ethernet port 4 RSTP role disabled access port port mirror remote I/O network port unknown alternate/backup root designated

IN_BYTES:

Type

UINT

Rank

4/5

Bit

—

IN_ERRORS:

Type

UINT

Rank

6/7

Bit

—

OUT_BYTES:

Type

UINT

Rank

8/9

Bit

—

OUT_ERRORS:

Type

UINT

Rank

10/11

Bit

—

Description number of bytes (octets) received on interface

Description number of inbound packets that contain detected errors

Description number of bytes (octets) sent on interface

Description number of outbound packets that contain detected errors

Device DDT Names for Quantum EIO Remote I/O Adapter Modules

Introduction

This topic describes the Control Expert Device DDT tab for an Ethernet remote I/

O drop that includes a •••CRA312•0 adapter module.

The I/O structure type for the Quantum remote I/O drop is T_U_DROP_STD_IN.

The I/O structure type for the Modicon X80 remote I/O drop is T_M_DROP_EXT_

IN. In addition, when a remote I/O drop with a Quantum 140CRA31200 module is placed into an M580 system, the I/O structure type is T_Q_DROP_EXT_IN.

The device DDT instance name can be defined manually but, when adding a module, a default device DDT instance name (see EcoStruxure ™ Control Expert,

S1A48978.14

Remote I/O Modules

Program Languages and Structure, Reference Manual) is defined by Control

Expert

NOTE: These instructions assume that you have already

Control Expert project, page 27 .

Access the Device DDT Tab

In Control Expert:

Step

Action

Expand EIO Bus in the Control Expert

Project Browser to display the EIO drop (Quantum

Double-click the EIO drop.

Select the Device DDT tab.

Example of the Implicit device DDT area which contains a name and a type.

Comment

Path: Tools

Project

> Project Browser >

> Configuration > EIO Bus >

EIO Quantum Drop

The EIO drop window appears.

Name

IO_HEALTH_RACK1 only for T_Q_DROP_EXT_IN

IO_HEALTH_RACK2 only for T_Q_DROP_EXT_IN

Drop Parameters

Use the Control Expert Device DDT tab to configure these parameters for the

Ethernet remote I/O drop:

Parameter

Implicit device DDT

Goto details

Name

Type

Description

A default device DDT instance name (see EcoStruxure ™

Control Expert, Program Languages and Structure,

Reference Manual) is defined by Control Expert.

module type (uneditable) link to the DDT data editor screen

Diagnostic Parameters

This table contains the DROP diagnostic parameters for the Ethernet remote I/O drop module:

Type

WORD

Bit

—

Description

Health bits of rack 1: slots 1 to 16

WORD — Health bits of rack 2: slots 1 to 16

52 S1A48978.14

device name of the remote I/O drop, page 44

Name

DEVICE_NAME

VERSION

ROTARY_SWITCHES

CRA_STATE

CRA_DIAGNOSTIC [WORD] GLOBAL_IO_HEALTH

CCOTF_IN_PROGRESS

CCOTF_INVALID_CONF

IOPL_MISMATCH

SWITCH_CHANGE

DROP_COM_HEALTH

CYCLE_CURR_TIME

CYCLE_MAX_TIME

CYCLE_MIN_TIME

TIME_STAMP_RECORDS

(Not used for 140CRA31200 applications.)

TS_DIAGNOSTIC_FLAGS

(WORD)

(BMXCRA312•0 only)

TIME_VALID

CLOCK_FAILURE

CLOCK_NOT_SYNC

BUFF_FULL

SOE_UNCERTAIN

TS_BUF_FILLED_PCTAGE

(BMXCRA312•0 only)

TS_EVENTS_STATE

(BMXCRA312•0 only)

ETH_STATUS (BYTE) PORT1_LINK

S1A48978.14

UINT

BOOL

—

BYTE

BOOL

—

Type string[16]

Bit

—

WORD —

BYTE

—

BOOL

UINT

—

UINT

—

Remote I/O Modules

Description

firmware version (Maj, Min) (4 digits coded in BCD) rotary switch value at power up

1: CRA module is idle.

2: CRA module is stopped.

3: CRA module is running.

0: At least one I/O module in the drop reports bad health.

CCOTF is in progress.

CCOTF configuration is not valid.

There is an output data mismatch. The modules in the rack are not the same as the modules configured in the PLC.

The rotary switches settings have changed since the last power up.

This bit shows the drop communication health (set to 1 in remote I/O drop).

This word indicates the execution time of the last CRA cycle.

It has values between [0,65535] with a resolution of 0.01 ms, therefore, the last cycle time is between [0,655] ms.

This word indicates the longest CRA cycle execution time since the last start.

It has values between [0,65535] with a resolution of 0.01 ms, therefore, the longest cycle time is between [0,655] ms.

This word indicates the shortest CRA cycle execution time since the last start.

It has values between [0,65535] with a resolution of 0.01 ms, therefore, the shortest cycle time is between [0,655] ms.

This word contains the number of Time

Stamp records available in the drop local buffer.

The time is valid and synchronized.

The time source of the sending device is not validated. The time stamp value is ignored.

The time source of the sending device is not synchronized with the external UTC time.

The buffer is full.

The SOE (sequence of events) in the buffer is not known. The SOE is reset when the sequence of events is OK.

This byte reports the percentage of the buffer filled (0...100).

The byte reports the main state of TS events.

0 = Port 1 link is down.

1 = Port 1 link is up.

Remote I/O Modules

Name

PORT2_LINK

PORT3_LINK

(reserved bit)

RPI_CHANGE

REDUNDANCY_OWNER

GLOBAL_STATUS

SERVICE_STATUS (BYTE) RSTP_SERVICE

NTP_UPDATE (reserved)

MAX_PACKET_INTERVAL

SNTP_SERVICE (reserved)

PORT502_SERVICE

SNMP_SERVICE

ETH_PORT_STATUS (BYTE)

(reserved bits)

These combined 2-bit values indicate the conditions port function

RSTP role

Type

BOOL

—

BOOL

—

WORD

—

UINT

Bit

4...7

1/0

3/2

5/4

7/6

9/8

11/10

12/13

14/15

—

Description

0 = Port 2 link is down.

1 = Port 2 link is up.

0 = Port 3 link is down.

1 = Port 3 link is up.

—

RPI change: EtherNet/IP RPI change is in progress (during CCOTF).

0 = Redundant owner is not present.

1 = Redundant owner is present.

0 = At least 1 service is not operating normally.

1 = All services are operating normally.

0 = RSTP service is not operating normally.

1 = RSTP service is operating normally or disabled.

0 = SNTP service is not operating normally.

1 = SNTP service is operating normally or disabled.

0 = Port 502 service is not operating normally.

1 = Port 502 service is operating normally or disabled.

0 = SNMP service is not operating normally.

1 = SNMP service is operating normally or disabled.

—

Ethernet port 1 function

Ethernet port 1 RSTP role

Ethernet port 2 function

Ethernet port 2 RSTP role

Ethernet port 3 function

Ethernet port 3 RSTP role

Ethernet port 4 function

Ethernet port 4 RSTP role disabled access port port mirror remote I/O network port alternate backup designated root elapsed time (100 ms) since last update from NTP server maximum packet interval (ms) for output packets

S1A48978.14

Name

IN_BYTES

IN_ERRORS

OUT_BYTES

OUT_ERRORS

SOE_UNCERTAIN

Type

UINT

BOOL

—

Bit

—

Remote I/O Modules

Description number of bytes (octets) received on interface number of inbound packets that contain detected errors (In Errors) number of bytes (octets) sent on interface number of outbound packets that contain detected errors (In Errors)

The SOE (sequence of events) in the buffer is not known. The SOE is reset when the sequence of events is OK.

Device DDT Types for I/O Modules

Refer to the following user guides for specific I/O module device DDT types:

I/O Module

Modicon X80 discrete input/output

Modicon X80 analog input/output

BMX EHC 0800

BMX EHC 0200

BMX NOM 0200

BMX ERT 1604T

User Guide Reference

Modicon M340 Using EcoStruxure ™ Control Expert Discrete Input/

Output Modules User Manual

Modicon M340 with EcoStruxure ™ Control Expert Analog Input/Output

Modules User Manual

Modicon M340 with EcoStruxure ™ Control Expert Counting Module

BMX EHC 0800 User Manual

Modicon M340 with EcoStruxure ™ Control Expert Counting Module

BMX EHC 0200 User Manual

Modicon M340 with EcoStruxure ™ Control Expert Serial Link User

Manual

BMX ERT 1604T M340 ERT Module User Manual

Elementary Functions (EFs) and Function Blocks (EFBs)

Introduction

Use the elementary functions (EFs) and elementary function blocks (EFBs) in the following table when you use Quantum RIO drops in M580 systems.

Using Quantum Function Blocks in M580 Systems

Supporting Quantum Configurations

M580 PLCs use these elementary functions (EFs) and elementary function blocks

(EFBs) to support Quantum I/O configurations:

Function Block

ACI030

ACI040

ACO020

ACO130

AII330

AII33010

AIO330

AMM090

Quantum Family

I/O management

Description

EFBs: Manage the I/O for Quantum ERIO modules.

S1A48978.14

Remote I/O Modules

Function Block

ARI030

ATI030

AVI030

AVO020

ERT_854_10

ERT_854_20

ERT_854_30

I_NORM_WARN

I_PHYS_WARN

I_SCALE_WARN

I_SET

I_RAW

I_RAWSIM

I_NORM

I_PHYS

I_SCALE

I_FILTER

O_NORM_WARN

O_PHYS_WARN

O_SCALE_WARN

O_SET

O_RAW

O_NORM

O_PHYS

O_SCALE

O_FILTER

DROP

XDROP

Quantum Family

I/O management

I/O management analog I/O scaling analog I/O scaling analog I/O scaling analog I/O scaling analog I/O scaling analog I/O scaling analog I/O scaling analog I/O scaling analog I/O scaling analog I/O scaling analog I/O scaling analog I/O scaling analog I/O scaling analog I/O scaling analog I/O scaling analog I/O scaling analog I/O scaling analog I/O scaling analog I/O scaling

I/O configuration

Description

EFBs: Scale analog values from Quantum analog modules.

EFs: Scale analog values from Quantum analog modules.

EFBs: Scale analog values from Quantum analog modules.

EFs: Scale analog values from Quantum analog modules.

EFBs: I/O configuration blocks for building data blocks for analog or ERT modules.

Application Download

Downloading the Application to the PLC

Download the Control Expert application to the PLC through one of its ports or through a connection to an Ethernet communication module:

Method

USB port

Modbus Plus port

Connection

If the PLC and the PC that is running Control Expert both have USB ports, you can download the application to the PLC directly through the

USB ports.

If the PLC and the PC that is running Control Expert both have Modbus

Plus ports, you can download the application to the PLC directly through the Modbus Plus ports.

56 S1A48978.14

Remote I/O Modules

Method serial port

Connection

If the PLC and the PC that is running Control Expert both have serial ports, you can download the application to the PLC directly through the serial ports.

Ethernet port If the PLC and the PC that is running Control Expert both have Ethernet ports, you can download the application to the PLC directly through the

Ethernet ports.

communication module You can download the application to the PLC by connecting Control

Expert to the IP address of the communication module.

NOTE: You cannot download the application to the PLC with the 140CRP31200 module.

S1A48978.14

Remote I/O Modules

Explicit Messaging

Overview

EtherNet/IP uses the TCP/IP and UDP/IP protocols to implement both explicit and implicit messaging.

This chapter explains the 140CRP31200 remote I/O head module and its use of explicit messaging for request-and-reply communications for non-real-time information (like configuration and diagnostic data). A network node that receives a TCP/IP-encapsulated explicit message processes the message and generates a response.

NOTE: The 140CRP31200 module can process 16 MBP_MSTR blocks per

MAST cycle.

NOTE: If you receive a detected error message — stating that the

140CRP31200 module does not have a link (has no cable), MSTR functionality may not be available. If this happens, check that your cables are connected properly.

This chapter describes how to use both Control Expert function block logic and the

Control Expert interface to send explicit messages.

EtherNet/IP Explicit Messaging Using MBP_MSTR

Introduction

This section shows you how to configure the MBP_MSTR function block for explicit messages.

NOTE: Use the 140CRP31200 module to send MBP_MSTR commands to diagnose the status of sub-rings. For other operations (get remote statistics, read data, etc.), we recommend that you send an MBP_MSTR command from a 140 NO• 7•• •• module.

Supported MBP_MSTR Function Codes

Function Codes

We recommend using these MBP_MSTR function codes with the 140 CRP 312 00 module to diagnose sub-rings:

MBP_MSTR Control

Code

0x00 0x0E

Description

EIP explicit message (connected)

0x01 0x0E EIP explicit message (unconnected)

140 CRP 312 00

Support

X, page 58

NOTE: The 140 CRP 312 00 module supports only 16 MBP_MSTR codes per

CPU cycle.

EtherNet/IP Explicit Messaging Services

Overview

Communication protocols:

• EtherNet/IP : The 140 CRP 312 00 module uses the EtherNet/IP protocol for all exchanges of I/O data.

• Modbus : The 140 CRP 312 00 module uses the Modbus/TCP protocol for reading diagnostics and for MBP_MSTR.

58 S1A48978.14

Explicit Messaging via the

Remote I/O Modules

Every EtherNet/IP explicit message performs a service. Each service is associated with a service code (or number). You will need to identify the explicit messaging service by its name, decimal number, or hexadecimal number.

You can execute EtherNet/IP explicit messages using either a Control Expert

MBP_MSTR function block or the Control Expert Ethernet Configuration Tool’s

EtherNet/IP Explicit Message Window . (Refer to

Control Expert GUI, page 61 .)

NOTE: Configuration edits made to an Ethernet communication module from the Control Expert Ethernet Configuration Tool’s EtherNet/IP Explicit Message

Window are not saved to the operating parameters stored in the CPU and, therefore, are not sent by the CPU to the module on startup.

You can use Control Expert to construct a request that executes any service supported by the target device that is compliant with the EtherNet/IP protocol.

Services

The services supported by Control Expert include these standard explicit messaging services:

Service Code

Hex Dec

Description

Get_Attributes_All

Set_Attributes_All

Get_Attribute_List

Set_Attribute_List

Reset

Start

Stop

Create

Delete

Multiple_Service_Packet

Apply_Attributes

Get_Attribute_Single

Set_Attribute_Single

Find_Next_Object_Instance

Error Response (DeviceNet only)

Restore

Save

No Operation (NOP)

Get_Member

Set_Member

Insert_Member

Remove_Member

GroupSync x (available service)

— (service not available)

—

Available in...

MBP_MSTR block

—

Control Expert

GUI

—

S1A48978.14

Remote I/O Modules

Configuring the CONTROL and DATABUF Parameters

Overview

The CONTROL and DATABUF output parameters define the operations of the

MBP_MSTR function block. For the EtherNet/IP protocol, the structure of the

CONTROL and DATABUF output parameters remains the same for all explicit messaging services.

Configuring the Control Parameter

Use MSTR operation 14 or 270 to send generic Modbus requests on the network.

(These operation codes are not available on the Modbus Plus port or embedded

Ethernet port on the CPU.)

The CONTROL parameter register contains these consecutive words:

Register

CONTROL[0]

CONTROL[1]

CONTROL[2]

CONTROL[3]

CONTROL[4]

CONTROL [5]

CONTROL [6]

CONTROL[7]

CONTROL[8]

Function operation detected error status data buffer length response offset routing register

IP address request length response length

Description

• 14 = unconnected

• 270 = connected

Holds the event code (read-only).

Data buffer length, in words

Offset for the beginning of the response in the data buffer, in 16-bit words

Note: To avoid overwriting the request, make the response offset value greater than the request length CONTROL[10] .

Specify a network destination node during data transfer:

• MSB: The most significant byte contains the source node address (for example, the slot number of the 140 NOE 771 •• or 140CRP31200 module).

Exception:

The value of the integrated Ethernet port on the CPU is 254 (FE h) regardless of the CPU slot number.

Note: Only 1 Ethernet 140CRP31200 module can be used.

• LSB: The least significant byte contains the destination node address (for example, MBP on the Ethernet Transporter (MET) mapping index for the 140

NOE 771 •• or the drop number for the 140CRP31200).

Each address contains 1 byte of the 32-bit IP address:

• high byte = byte 4 of the IP address (MSB)

• low byte = byte 3 of the IP address

• high byte = byte 2 of the IP address

• low byte = byte 1 of the IP address (LSB) length of the CIP request, in bytes length of the response received, in bytes read only—set after completion

1. For example, the Control parameter handles the IP address 192.168.1.6 in the following order: Byte 4 = 192, Byte 3 = 168, Byte 2 = 1,

Byte 1 = 6.

Configuring the Data Buffer

The DATABUF varies in size. It consists of contiguous registers that include—in sequence—both the CIP request and the CIP response. To avoid overwriting the request, confirm that the data buffer is large enough to contain both the request and response data.

Data Buffer:

Variable size: set in CONTROL[2]

CIP Request:

Request size: set in CONTROL[7]

60 S1A48978.14

Devices Services tab, page

Remote I/O Modules

CIP Response:

Starting position: set in CONTROL[3]

Response size: reported in CONTROL[8]

NOTE: If the response offset is smaller than the request size, response data overwrites part of the request.

The formats of the data buffer’s CIP request and CIP response are described in this table. (Both the request and response are structured in little endian order.)

Request

Byte offset

...

Response

Byte offset

Field

Service

Request_Path_Size

Request_Path

Request_Data

Data Type

Byte

Padded EPATH

Byte array

Field

Reply Service

Reserved

General Status

Data Type

Byte

Size of Additional Status Byte

Additional Status Word array

Response Data Byte array

Description

Service of the explicit message

The number of words in the Request_Path field

This byte array describes the path of the request (including class ID, instance ID, etc.) for this transaction.

Service-specific data in the explicit message request delivery (if none, this field is empty)

Description

Service of the explicit message + 16#80

EtherNet/IP General Status

Additional Status array size—in words

Additional status

Response data from request, or additional detected error data if

General Status indicates a detected error

Explicit Messaging via the Control Expert GUI

Sending Explicit Messages to EtherNet/IP Devices

Introduction

The 140 CRP 312 00 module uses explicit messages from Control Expert to obtain diagnostics information from an EtherNet/IP module or device on the network.

Access the EtherNet/IP Explicit Message Window

Step

Action

Access the 140 CRP 312 00 module for

Online Action.

Double-click the 140 CRP 312 00 module in the Control Expert rack view.

Comment

Refer to the

102

The EtherNet/IP Explicit Message tab appears.

S1A48978.14

Remote I/O Modules

The EtherNet/IP Explicit Message Tab

The EtherNet/IP Explicit Message window shows an example of the configuration of an EtherNet/IP explicit message and the response to the message. The explicit message is addressed to a DRS to obtain diagnostic information:

Field

Address

NOTE: Refer to your

EtherNet/IP device user manual for the values in the

Address field.

Service

Data (hex)

Messaging

Send to Device (button)

Parameters

Features of the EtherNet/IP Explicit Message screen:

Parameter (Value)

IP Address

( x.x.x.x

)

Class

(1...65535)

Instance

(0...65535)

Attribute

(0...65535)

Number

(1...127)

Name

Enter Path (hex)

—

Connected

Unconnected

—

Description

The IP address of the target device, used to identify the target of the explicit message. (The IP address in the example above is 192.168.1.6.)

The class identifier of the target device is an integer that is used to construct the message path. (The class in the example above is 4.)

The class instance of the target device is an integer that is used to construct the message path. (The class instance in the above example is

100.)

The specific device attribute (or property) is the target of the explicit message. This integer is used to construct the message path. (The attribute in the above example is 3.)

NOTE: Check this box to enable this optional field.

Number is an integer that is associated with the service that the explicit message performs.

NOTE: If you select Custom Service , type in a service number. This field is read-only for all other services.

Scroll to the name of the service that you want the explicit message to perform. In the example above, Get_Attribute_Single is selected.

Check this box to enable the message path field where you can manually enter the entire path to the target device. (In the example above, the box is not checked.)

The Data field contains the data to be sent to the target device for services that send data. (The field is blank in the example above.)

Select the type of explicit message to send:

• unconnected : An unconnected message requires path information

(addressing) that identifies the destination device and (optionally) device attributes.

• connected : A connected explicit message contains path information and a connection identifier to the target device.

NOTE: The example uses an Unconnected message.

After the explicit message is configured, press Send to Device .

62 S1A48978.14

adapter’s publishing frequency (subscribe field CRA-> RPI ), page

Field

Response (hex)

Status

Repeat (500ms)

Remote I/O Modules

Parameter (Value)

—

Description

Response contains the (hexadecimal) data sent to the configuration by the target device when you press Send to Device .

After you press Send to Device , the messages in the Status field indicate the status of the explicit message.

Check this box to send the explicit message every 500 ms. (In this example, leave this blank.)

NOTE: You can use explicit messaging to perform many different services, but every EtherNet/IP device does not support every service.

Immediate I/O Access (IU_ERIO)

Description

Function Description

WARNING

UNINTENDED EQUIPMENT OPERATION

Do not use the IU_ERIO function block in Quantum Hot Standby installations.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

An IU_ERIO function block updates Ethernet remote I/O drop input and output modules with an optimal response time. The Ethernet remote I/O drop inputs and outputs are updated during the MAST task.

Call this function block in a MAST task. It can be called more than once in a task.

NOTE: To maintain system performance, we recommend that you use no more than 10 executions of the IU_ERIO block during a single MAST task.

The input and output modules are physically located on an Ethernet remote I/O drop and declared in the Ethernet configuration.

EN and ENO can be configured as additional parameters.

NOTE: Refer to the Quantum EIO System Planning Guide for calculating the

ART when your application does not use an IU_ERIO function block.

IU_ERIO Mechanism

The Ethernet remote I/O drop input values are read in the 140CRP31200 module with an optimal response time.

The input values read in the 140CRP31200 module represent the latest values sent in an asynchronous way by the adapter module in each drop. The maximum time shift between values read in the 140CRP31200 and actual input values depends on the

S1A48978.14

Remote I/O Modules

The following diagram represents the I/O exchanges between a CPU and the

Ethernet remote I/O drops:

Representation in FBD

Representation:

Representation in LD

Representation:

Representation in IL

CAL IU_ERIO(DROP:=>Drop_Number, DIR:=>Input_Output, STATUS=

>Status_Report);

Representation in ST

IU_ERIO(DROP:=>Drop_Number, DIR:=>Input_Output, STATUS=

>Status_Report);

S1A48978.14

description of the connection parameters, page 44 .

Remote I/O Modules

Parameter Description

Input parameters:

Parameter

Drop

Dir

Data type

INT

BOOL

Meaning

Drop number (1...31)

Drop number:

• 1: Drop 1

• 2: Drop 2

• ...

• 31: Drop 31

Data direction:

• 0 = Outputs. The output values are sent immediately to the 140CRP31200 module.

• 1 = Inputs. The input values are read immediately from the 140CRP31200 module.

Output parameter:

Parameter

Status

Data type

WORD

Meaning

Status report from the 140CRP31200 module:

• 0002 hex: Invalid drop number

• 0003 hex: Ethernet remote I/O drop is not configured

• 0004 hex: Ethernet remote I/O drop is not connected

• 0005 hex: Retry number is exceeded

• 0007 hex: An error is detected on the

140CRP31200 module

• 0008 hex: Operation was not completed before time out

• 0009 hex: 140CRP31200 module is not present on the local drop

• 000B hex: Operation OK

NOTE: If no connection is opened with the Ethernet remote I/O drop, a detected communication error (system words %SW172 to %SW173) is returned.

S1A48978.14

Remote I/O Modules

Implicit Messaging

The MAST Task in Implicit Exchanges

Task Management

This topic explains implicit messaging and the relationship between the MAST task configuration and the remote I/O implicit exchanges.

Implicit messaging maintains open connections for real-time communications of a predefined nature between consumers and producers. Implicit messages contain control data and a connection identifier.

EtherNet/IP uses the TCP/IP and UDP/IP protocols to implement both explicit and implicit messaging.

Access the MAST Configuration

View the Properties of MAST :

Step

Action

Go to the Properties of MAST dialog box in Control Expert ( Tools

Browser

Project

Program

Tasks

MAST ).

Project

Right-click Properties .

Configure the parameters.

CIP Definitions

Inputs: The MAST period should be 2 times the RPI of the 140CRA31200 or

BMXCRA312•0 adapter on the remote I/O drop. This provides new input values for every MAST cycle. (For example, an RPI of 25 ms provides data for a MAST period of 50 ms.)

Outputs: The CPU in the local rack of a Quantum Ethernet I/O system produces outputs to Ethernet remote I/O drops and consumes inputs from those drops

(based on the producer/consumer model). A consumer (the remote drop) detects the lack of updated data through a time-out. (Possible time-out values are N x RPI, where N = 4, 8, 16 ....) When a time-out is triggered, the consumer assumes that the producer is absent.

Periodic and Cyclic Modes

The effect that periodic and cyclic modes have on implicit messages is explained in the

Quantum I/O Management for Implicit I/O Exchanges

Assign state RAM addresses:

Drop type

Quantum Ethernet remote

I/O

Modicon X80 Ethernet remote I/O

Instruction

The direct state RAM address manages the Quantum I/O data.

Assign the state RAM addresses for each module. (Default values are proposed by Control Expert in the module configuration windows.)

You can also define symbols on the I/O variables allocated in the state

RAM.

To assign state RAM addresses for Modicon X80 I/O data, refer to the topic

Device DDT Names for Quantum EIO adapters, page 51

66 S1A48978.14

Overview

Remote I/O Modules

This chapter describes the diagnostics for the Quantum EIO modules. For details on diagnostics at the system level, refer to the systems diagnostics topic in the

Quantum Ethernet I/O System Planning Guide .

LED Indicators

LED Indicators on the 140 CRP 312 00 Module

Display

These LEDs are on the front of the 140CRP31200 module:

Description general power-up sequence

FDR client

EIP scanner

S1A48978.14

Indications

ODVA standard

LED conditions: component not operating invalid configuration not configured configured no/default module MAC no/default port MAC sequence non-ODVA standard no Ethernet connections duplicate IP waiting for IP default IP receive or assign IP invalid configuration no EIP connection or all EIP connections closed

—

Active green

—

— on

—

5 blink (.25

sec on; .25

sec off)

—

Ready green

Mod Status red on green off off off flash off off blink blink 2 blink 2

6 blink (.25

sec on; .25

sec off)

—

— blink 3 blink 4 off flash flash blink (.25

sec on; .25

sec off)

— off off flash on off off

— blink (.25

sec on; .25

sec off)

— on blink 5 blink 6 on blink 7 on off off off off flash on on on on off

Net Status red

—

— off off off

— blink (.25

sec on; .25

sec off)

— on off off off off off green

—

— on/flash off off

— blink (.25

sec on; .25

sec off)

— off off off flash off flash

Remote I/O Modules

Description

one or more connections established one connection timeout

Active green

—

Ready green on

Mod Status red off green on off on

Net Status red off green on

— on flash off

NOTE: In Hot Standby systems, the Net Status LEDs on the 140 CRP 312 00 modules are solid green during normal operations. When power to the 140

CRP 312 00 module in either rack A or B is lost, the Net Status LED on the

140 CRP 312 00 module in the partner rack is unchanged (solid green).

Ethernet Port Indications

These LEDs report the status of the Ethernet port:

Name

LINK

ACT

Color green yellow

— green

—

Status on on off blinking off

Description

100 Mbps link detected

10 Mbps link detected no detected link active Ethernet link (transmit or receive) inactive Ethernet link

LED Indicators on the Quantum EIO Adapter Module

Display

The LEDs are on the front of the adapter module:

140CRA31200:

68 S1A48978.14

BMXCRA312•0:

Remote I/O Modules

Indications

LED conditions:

Description power-up sequence not configured blink (.25 sec on; .25 sec off)

IP address not valid

Run green

—

IO red

—

Mod Status green red

Green/Red/Green flashing flashing off off

Net Status green red

Green/Red/Off off flashing off off

• valid IP address

• invalid configuration off off configured

I/O data communication established detected error states no external error detected external error detected

STOP

RUN recoverable error nonrecoverable error duplicate IP address flashing flashing flashing on

— off on

(note 1)

(note 2)

— on

—

— on on off off

— off

—

— off off flashing on on

—

— flashing flashing on off off off off

—

OS firmware update flashing

— flashing

— off

— on off off on on

NOTE 1 (STOP state):

• on: An input or output is a detected error that originates in a module, or a channel configuration or a channel configuration error has been detected.

• off: Operations are normal.

NOTE 2 (RUN state):

• on: External error is detected.

• off: External error is not detected.

Ethernet Port Indications

S1A48978.14

These LEDs report the status of the Ethernet port:

Name

LINK

Color green yellow

—

Status on on off

Description

100 Mbps link detected

10 Mbps link detected no detected link

Remote I/O Modules

Name

ACT

Color green

—

Status blinking off

Description active Ethernet link (transmit or receive) inactive Ethernet link

diagnostics through Control Expert, page 103

Service Port Management

Service Port Configuration

Introduction

The 140CRP31200 remote I/O head module and the remote I/O adapter modules

(140CRA31200 and BMXCRA31210) support the configuration of the SERVICE port without requiring you to re-build or download your application.

140CRP31200

The online configuration of the SERVICE port on the 140CRP31200 module is discussed in the section about

Adapter Modules

You can send explicit messages with an EtherNet/IP tool for the configuration of the SERVICE port on the 140CRA31200 or BMXCRA31210 modules. For details, refer to the discussions of

EtherNet/IP CIP objects, page 100

and

SERVICE port configuration for adapter modules, page 70

Cycling Power

The online configuration of the SERVICE port is volatile. The following situations can arise when power is cycled to the module while the application is being applied:

• The configuration can be lost.

• The configuration in the application can be applied to the SERVICE port.

Service Port Configuration for Adapter Modules

Configuration

Follow these steps to modify the Service Port configuration of an online

140CRA31200 or BMXCRA312•0 adapter module:

Step

Action

Launch the EtherNet/IP Explicit Message window, page 61

Assign these Device Services parameters:

• Address :

◦ IP Address: Enter the IP address of the adapter with the SERVICE port you want to configure.

◦ Class: 0x400

◦ Instance: 1

• Service :

◦ Name: Set_Attribute_Single

Set the Port Control value:

• Attribute : Check this box.

• Attribute (field): Enter 1 (access port).

• Data (hex) (field): Enter a value that is based on the

Port Control attribute definition, page 101 .

70 S1A48978.14

Port Control attribute definition, page 101

Remote I/O Modules

Step

Action

NOTE:

• To set the UINT value of 2, set the data field to 02 00 (low byte/high byte).

• If you enter 2 (port mirroring) in Attribute , refer to the next table.

• In port mirroring mode, the SERVICE port acts like a read-only port. That is, you cannot access devices (ping, connection to Control Expert, etc.) through the SERVICE port.

Leave the default values for these parameters:

• Enter Path(hex) : Leave this check box unselected.

• Repeat(500ms) : Leave this check this check box unselected.

• Messaging : Select Unconnected .

Press Send to Device .

Port Mirroring: Use these steps only if you chose 2 (port mirroring) for the Port

Control value (above):

Step

Action

Set the Port Control value:

• Attribute : Check this box.

• Attribute : Enter 2 (port mirroring).

• Data(hex) : Enter a value that is based on the

Accept the default values for other parameters (as before).

Press Send to Device .

Diagnostics Available through the CPU

System Diagnostics

Introduction

System diagnostics are performed locally on the CPU with system bits (%S) and system words (%SW).

Local Rack Diagnostics

Local rack diagnostics are accessible for the 140CRP31200, 140 NOC 771 ••, and

140 NOE 771 •• modules within the standard system bits (%SW180 to %SW339).

Ethernet Remote I/O Drop Diagnostics

Ethernet remote I/O drop diagnostics are accessible for the entire drop within system bits and words in the PLC (%S, %SW). Each drop is animated with a health bit display of the health bit status for:

• a drop node

• a module in a remote drop

The Quantum PLC on the local rack monitors remote I/O drops and module health. The 140CRA31200 or BMXCRA312•0 adapter module on the remote I/O drop transmits detected errors in drop modules to the Quantum PLC via

implicit exchanges, page 81 . The detected errors are stored in the global diagnostic

buffers of the PLC and in the diagnostic buffer of the individual drop module.

The Quantum PLC or the 140CRP31200 module on the local rack updates the detected error buffers. Health bits are updated in the PLC only if the adapter of the concerned drop communicates with the 140CRP31200 module on the local rack.

If these modules cannot communicate, the concerned health bits are set to 0.

S1A48978.14

Remote I/O Modules

System Bits/Words

%S117

%SW101

%SW108

%SW109

%SW152 ... %SW153

%SW172 ... %SW175

%SW176 ... %SW179

%SW180 ... %SW181

%SW182 ... %SW183

%SW641 ... %SW702

System Bits and Words

This table describes new or modified system bits and words that represent detected errors:

Symbol

EIOERR

EIO_CCOTF_COUNT

FORCED_DISCRETE_COUNT

FORCED_ANALOG_COUNT

EIO_DROP_ERROR

EIO_CONNECT_STATUS

SDBY_EIO_CONNECT_STATUS

IOHEALTHij

(i = 1 ... 32, j = 1 ... 5)

EIO_MOD_HEALTH

Description detected remote I/O error on the Ethernet I/O network

EIO CCOTF counting status register forced bit counting status register forced bit counting status register detected Ethernet remote I/O drop status

The bit is set to 0 if at least one I/O module in the drop as a detected error.

The bit is set to 1 if all modules are operating properly.

• %SW152.0: drop #1

• %SW152.1: drop #2

• ........

• %SW153.14: drop #31

Ethernet I/O communication health status for drops in standalone and primary systems

Ethernet I/O communication health status for drops in standby systems health bits of the PLC modules (including Hot Standby and

Safety Hot Standby systems)

Ethernet remote I/O module health bit status

NOTE: Refer to Quantum-Specific System Words section (see EcoStruxure ™

Control Expert, System Bits and Words, Reference Manual) for a detailed explanation.

Viewing Diagnostics in Control Expert

The bus editor in Control Expert uses color animation to display the status of each drop, rack, or module on the EIO Bus . The slot number of the drop/rack/module appears in red when a detected error is associated with that slot. For a module, the red display indicates the module is missing, inoperable, or improperly configured.

Drop

140 CRA

Status drop (d) rack (r), drop (d)

Language

Object

%SWi.j

%SWi i j

BMX CRA module (m), rack

(r), drop (d) rack (r), drop (d) module (m), rack

(r), drop (d)

%SWi.j

%SWi

%SWi.j

152 + [(d-1)/16]

641 + [(d-1)*2] +

(r-1)

641 + [(d-1)*2] +

(r-1)

641 + [(d-1)*2] + r

(d-1)/16

16-m

15-m

NOTE: Remember that the 16 slots have different numbering schemes:

• 140CRA31200 drop: slots 1...16

• BMXCRA312•0 drop: slots 0...15

NOTE: Remember that the rack numbering scheme is also different:

• 140CRA31200 drop: 1 or 2

• BMXCRA312•0 drop: 0 or 1

S1A48978.14

Derived Data Types section, page 48 .

Remote I/O Modules

Device Data Types for the Remote I/O Modules

Device Data Types

The DDT structures for these remote I/O modules are described elsewhere:

• 140CRP31200 head module (local rack)

• 140CRA31200 or BMXCRA312•0 adapter (remote drop)

These DDTs are available in the application. Refer to the

The DDT diagnostics data is mapped to default local variables. The data is updated every MAST cycle.

Diagnostics Available through Modbus/TCP

Modbus Diagnostic Codes

Supported Diagnostic Codes

Modbus function code 3 provides access to a variety of diagnostic functions, including basic network diagnostics, Ethernet port diagnostics, and Modbus port

502 diagnostics.

To access the function code 3 diagnostics from the local device, set the unit ID to

100.

The following modules support these Modbus diagnostic codes.

• Quantum remote I/O head module (140CRP31200)

• Quantum distributed I/O head module (140NOC78000)

• Quantum control head module (140NOC78100)

• Quantum remote I/O adapter module (140CRA31200)

• M340 distributed I/O head module (BMXNOC0401)

• M340 remote I/O adapter module (BMXCRA31200)

• Quantum IEC 61850 module (140NOP85000)

• M580 communications module (BMENOC03•1)

• M580 communications module (BMENOP0300)

Modbus Function Code 3: Basic Network Diagnostics

Basic network diagnostics start at address 40001(decimal) as described in the following table.

Starting

Address

(Decimal)

40001

Length

(Words)

40003 1

Register Byte Order

MS BYTE LS BYTE

MS Byte

Byte 02

MS Byte

Byte 01

40004

40005

40006

40008

MS Byte

IP 1

IP 3

SM 1

LS Byte

IP 2

IP 4

SM 2

Comments

Basic network diagnostic validity

Communication global status

Supported communication services

Status of communication services

IP address (IP1.IP2.IP3.IP4)

Subnet mask (SM1.SM2.SM3.SM4)

S1A48978.14

Remote I/O Modules

Starting

Address

(Decimal)

Length

(Words)

Register Byte Order

MS BYTE LS BYTE

40010

40012

40015

SM 3

GW 1

GW 3

MAC 1

MAC 3

MAC 5

MS Byte

SM 4

GW 2

GW 4

MAC 2

MAC 4

MAC 6

40018

40020

40022

40023

40024

40026

40028

40030

40038

LS Byte

C01

C03

C01

C03

LS Byte

C01

C03

C01

C03

C01

C03

Char 2

Char 4

Char 6

Char 8

Char 10

Char 12

Char 14

Char 16

Byte 01

C00

C02

C00

C02

MS Byte

C00

C02

C00

C02

C00

C02

Char 1

Char 3

Char 5

Char 7

Char 9

Char 11

Char 13

Char 15

MS Byte

Byte 02 LS Byte

Comments

Default gateway (GW1.GW2.GW3.GW4)

MAC address (MAC1:MAC2:MAC3:MAC4:MAC5:

MAC6.

Ether frame format capability / configuration / operational

Ethernet receive frames OK

Ethernet transmit frames OK

Number of open client connections

Number of open server connections

Number of Modbus detected error messages sent

Number of Modbus messages sent

Number of Modbus messages received

Device name

IP assignment mode capability / operational

Example: Reading Basic Network Diagnostics with Modbus Function Code 3

Here is an example of how to read registers 40018 and 40019, the Ethernet receive frames OK count registers. The request contains 7 bytes. The starting address, shown as a hex value in byte 2 below, is calculated as follows:

40018 – 40001 = 17 dec = (11 hex)

The number of registers to be diagnosed (2 hex) is shown in byte 4:

Byte

Number

Value

Function code = 03 (hex)

Starting Address Hi = 00 (hex)

S1A48978.14

S1A48978.14

Remote I/O Modules

Byte

Number

Value

Starting Address Low = 11 (hex)

No. of Registers Hi = 00 (hex)

No. of Registers Low = 2 (hex)

CRC high byte (inserted by the Modbus sending application)

CRC low byte (inserted by the Modbus sending application)

The normal response is returned in 8 bytes. In this example, the expected response is 14229 hex; this value is shown in bytes 2 through 5 of the response:

Byte Number

Value

Function code = 03 (hex)

Byte count = 4 (hex)

1 st register data, high byte = 00 (hex)

1 st register data, low byte = 01 (01 hex)

2 nd register data, high byte = 42 (hex)

2 nd register data, low byte = 29 (hex)

CRC high byte

CRC low byte

Byte Number

Value

Original function code + 80 hex (= 83 hex)

Detected error code

CRC high byte

CRC low byte

For more information on Modbus function code 3 and other function codes, refer to the Modicon Modbus Protocol Reference Guide (PI-MBUS-300).

Modbus Function Code 3: Ethernet Internal Port Diagnostic

Data

Internal port diagnostics start at address 40040 (decimal) as described in the following table.

40043

40044

40045

40046

40047

40048

Starting

Address

(Decimal)

40040

40041

40042

Length

(Words)

Register Byte Order Comments

BYTE

MS Byte LS Byte

Internal port Diagnostics Data Validity

Internal port Logical/Physical Port Number

Internal port Ethernet Control Capability

MS Byte LS Byte

MAC 1

MAC 3

MAC 2

MAC 4

Internal port Link Speed Capability

Internal port Ethernet Control Configuration

Internal port Link Speed Configuration

Internal port Ethernet Control Operational

Internal port Link Speed Operational

MAC Address (MAC1:MAC2:MAC3:MAC4:MAC5:

MAC6)

Remote I/O Modules

Starting

Address

(Decimal)

40051

40053

40055

40057

40059

40061

40063

40065

40067

40069

40071

40073

40075

40077

40079

40081

40083

Length

(Words)

Register Byte Order Comments

BYTE

MSB

C00

C02

MSB

C00

C02

MSB

C00

C02

MSB

C00

C02

MSB

C00

C02

MSB

C00

C02

MSB

C00

C02

MSB

C00

C02

MSB

C00

C02

MSB

C00

C02

MSB

C00

C02

MSB

C00

MSB

C00

C02

MSB

C00

C02

MAC 5

MSB

C00

C02

MSB

C00

C02

MSB

C00

C02

MAC 6

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

Internal port Media Counters Data Validity

Internal port Num Frames Transmitted OK

Internal port Num Frames Received OK

Internal port Num Ether Collisions

Internal port Carrier Sense Errors detected

Internal port Num Ether Excessive Collisions

Internal port CRC Errors detected

Internal port FCS Errors detected

Internal port Alignment Errors detected

Internal port Num Internal MAC Tx Errors detected

Internal port Late Collisions

Internal port Num Internal MAC Rx Errors detected

Internal port Multiple Collisions

Internal port Single Collisions

Internal port Deferred Transmissions

Internal port Frames Too Long

Internal port Frames Too Short

S1A48978.14

Remote I/O Modules

Starting

Address

(Decimal)

40085

40087

40088

40089

...

40118

40119

40120

40121

40123

40125

40127

40129

401331

40133

40135

40137

40139

40141

Length

(Words)

Register Byte Order Comments

BYTE

2 Internal port SQE Test Error detected

MSB

C00

C02

MSB

C00

C02

MSB

C00

C02

MSB

C00

C02

MSB

C00

C02

MSB

C00

C02

MSB

C00

C02

MSB

C00

C02

MSB

C00

C02

MSB

C00

C02

MSB

C00

C02

MSB

C00

C01

C02 LSB C03

MS Byte LS Byte

IL char64 IL char63

IL char62 IL char61

...

IL char04 IL char03

IL char02 IL char01

MS Byte LS Byte

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

C01

LSB C03

Internal port Interface Label Length

Internal port Interface Label characters

Internal port Interface Counters Diagnostic Validity

Internal port Num Octets Received

Internal port Num Unicast Packets Received

Internal port Num Non Unicast Packets Received

Internal port Num Inbound Packets Discarded

Internal port Num Inbound Packets Error detected

Internal port Num Inbound Packets Unknown

Internal port Num Octets Sent

Internal port Num Unicast Packets Sent

Internal port Num Non Unicast Packets Sent

Internal port Num Outbound Packets Discarded

Internal port Num Outbound Packets Error detected

S1A48978.14

Remote I/O Modules

Modbus Function Code 3: Ethernet Port 1 Diagnostic Data

Port 1 diagnostics start at address 40143 (decimal). As described in the following table, port 1 diagnostic data fields are the same as for the internal port, with the appropriate starting address offset.

Starting

Address

Length Register Byte Order

40143

...

40244

...

MS BYTE LS BYTE

MS Byte LS Byte

...

MSB C00 C01

C02 LSB C02

Comments

Port 1 Port Diagnostics Data Validity

...

Port 1 Num Outbound Packets Error detected

Modbus Function Code 3: Ethernet Backplane Port Diagnostic

Data

Backplane port diagnostics start at address 40246 (decimal). As described in the following table, backplane port diagnostic data fields are the same as for the internal port and port 1, with the appropriate starting address offset.

Starting

Address

Length Register Byte Order

40246

...

40347

...

MS BYTE LS BYTE

MS Byte LS Byte

...

MSB C00 C01

C02 LSB C02

Comments

Backplane Port Diagnostics Data Validity

...

Backplane Port Num Outbound Packets Error detected

Modbus Function Code 3: Ethernet Port 3 Diagnostic Data

Port 3 diagnostics start at address 40349 (decimal). As described in the following table, port 3 diagnostic data fields are the same as for the internal port and ports 1 and 2, with the appropriate starting address offset.

Starting

Address

Length Register Byte Order

40349 1

MS BYTE LS BYTE

MS Byte LS Byte

...

40450

...

MSB C00 C01

C02 LSB C03

Comments

Port 3 Port Diagnostics Data Validity

...

Port 3 Num Outbound Packets Error detected

Modbus Function Code 3: Ethernet Port 4 Diagnostic Data

Port 4 diagnostics start at address 40452 (decimal).As described in the following table, port 4 diagnostic data fields are the same as for the internal port and ports

1-3, with the appropriate starting address offset.

Starting

Address

Length Register Byte Order

40452

...

40553

...

MS BYTE LS BYTE

MS Byte LS Byte

...

MSB C00 C01

C02 LSB C03

Comments

Port 4 Port Diagnostics Data Validity

...

Port 4 Num Outbound Packets Error detected

S1A48978.14

S1A48978.14

Remote I/O Modules

Ethernet Port Not Present

If an Ethernet port is not physically present on the device, the relevant Modbus registers will return data = 0.

Modbus Function Code 3: Modbus TCP Port 502 Diagnostic

Data

Modbus TCP port 502 diagnostics start at address 40555 (decimal) as described in the following table.

Starting

Address

40555

40557

40558

40559

40561

40563

Length

Register Byte Order

MS BYTE LS BYTE

MS Byte

Byte 01

Byte 02

MS Byte

LS Byte

MS Byte

MSB C00

C02

MSB C00

C02

MS Byte

LS Byte

C01

LSB C03

C01

LSB C03

LS Byte

40564

40565

40566

40567

40568

40570

40571

40572

40573

40575

40576

40578

...

40663

40665

40666

40668

...

Comments

Modbus TCP/Port 502

Diagnostic Data Validity

Port 502 Status

Num Open Connections

Num MB Messages Sent

Num MB Messages Received

MS Byte

MSB C00

C02

MS Byte

LS Byte

C01

LSB C03

LS Byte

Num MB Open Client

Connections

Num MB Open Server

Connections

Max Num Connections

Max Num Client Connections

Max Num Server Connections

Num MB Detected Error

Messages Sent

MSB - IP1 IP2

IP3 LSB - IP4

MS Byte LS Byte

MSB - IP1 IP2

IP3

MS Byte

LSB - IP4

LS Byte

...

MSB - IP1

IP3

MS Byte

...

IP2

LSB - IP4

LS Byte

Num Attempts to Open

Unauthorized Connection 1

Remote IP Address 2

Num Attempts to Open

Unauthorized Connection 2

...

Remote IP Address 31

MSB - IP1 IP2

IP3 LSB - IP4

MS Byte LS Byte

Num Open Priority Connections

Max Num Priority Connections

Num Entries in Unauthorized

Table

Remote IP Address 1 Connection 1

Num Attempts to Open

Unauthorized Connection 31

Remote IP Address 32

Num Attempts to Open

Unauthorized Connection 32

Connection 2

Connection 31

Connection 32

Remote I/O Modules

Modbus Function Code 3: Modbus TCP Port 502 Connection

Table Data

Modbus TCP port 502 connection table data starts at address 40669 (decimal) as described in the following table.

Starting

Address

40669

40670

Length

Register Byte Order

MS BYTE LS BYTE

MS Byte LS Byte

40671

40672

40673

40675

MS Byte

IP1

IP3

MS Byte

LS Byte

IP2

IP4

LS Byte

Comments

Connection Table Validity

Number of Entries

Starting Entry Index

Connection 1 Index

Connection 1 Remote IP

Address

40676

40677

40678

40679

40680

40681

40683

MS Byte

IP1

IP3

MS Byte

LS Byte

IP2

IP4

LS Byte

Connection 1

Connection 1 Remote Port

Number

Connection 1 Local Port

Number

Num MB Messages Sent on

Connection 1

Num MB Messages Received on Connection 1

Num MB Detected Error

Messages Sent on Connection

Connection 2 Index

Connection 2 Remote IP

Address

Connection 2

40684

40685

40686

40687

...

41168

41169

41171

...

MS Byte

...

MS Byte

IP1

IP3

MS Byte

LS Byte

...

LS Byte

IP2

IP4

LS Byte

Connection 2 Remote Port

Number

Connection 2 Local Port

Number

Num MB Messages Sent on

Connection 2

Num MB Messages Received on Connection 2

Num MB Detected Error

Messages Sent on Connection

...

Connection 63 Index

Connection 63 Remote IP

Address

Connection 63*

41172

41173

41174

41175

41176

41177

MS Byte

IP1

LS Byte

IP2

Connection 63 Remote Port

Number

Connection 63 Local Port

Number

Num MB Messages Sent on

Connection 63

Num MB Messages Received on Connection 63

Num MB Detected Error

Messages Sent on Connection

Connection 64 Index

Connection 64 Remote IP

Address

Connection 64*

S1A48978.14

Remote I/O Modules

Starting

Address

Length

Register Byte Order Comments

MS BYTE LS BYTE

IP3 IP4

MS Byte LS Byte 415179

41180

41181

41182

MS Byte

LS Byte

Connection 64 Remote Port

Number

Connection 64 Local Port

Number

Num MB Messages Sent on

Connection 64

Num MB Messages Received on Connection 64

41183 1 MS Byte LS Byte Num MB Detected Error

Messages Sent on Connection

*140 CRA 312 10 and BMX CRA 312 •0 RIO adapter modules support a maximum of 8 connections.

Diagnostics Available through EtherNet/IP CIP Objects

Introduction

Quantum Ethernet I/O applications use CIP within a producer/consumer model to provide communication services in an industrial environment. This section describes the available CIP objects for Quantum EIO modules.

About CIP Objects

Overview

The Ethernet communication module can access CIP data and services located in connected devices. The CIP objects and their content depend on the design of each device.

CIP object data and content are exposed—and accessed—hierarchically in the following nested levels:

Identity Object

NOTE: You can use explicit messaging to access these items:

• Access a collection of instance attributes by including only the class and instance values for the object in the explicit message.

• Access a single attribute by adding a specific attribute value to the explicit message with the class and instance values for the object.

This chapter describes the CIP objects that the Ethernet communication module exposes to remote devices.

Overview

The Identity object presents the instances, attributes and services described below.

S1A48978.14

Remote I/O Modules

Class ID

Instance IDs

The Identity object presents two instances:

• 0: class

• 1: instance

Attributes

Identity object attributes are associated with each instance, as follows:

Instance ID = 0 (class attributes):

Attribute ID Description

X = supported

— = not supported

Revision

Max Instance

GET

SET

—

Instance ID = 1 (instance attributes):

Description Attribute ID hex dec

05 05

X = supported

— = not supported

Vendor ID

Device Type

Product Code

Revision

Major

Minor

Status bit 2:

0x01=the module is configured bits 4-7:

0x03=no I/O connections established

0x06=at least 1 I/O connection in run mode

0x07=at least 1 I/O connection established, all in IDLE mode

Serial Number

Product Name

Modbus Identity

Type GET

UINT

STRUCT

USINT

Word

UDINT

STRING

STRUCT

SET

—

Services

The Identity object performs the following services upon the listed object types:

S1A48978.14

Service ID hex dec

01 01

Description

Get_Attributes_All

Class Instance

X X

Remote I/O Modules

Notes

Returns:

• all class attributes (instance = 0)

• instance attributes 1 to 7 (instance = 1)

Returns the value of the specified attribute.

0E 14

X = supported

— = not supported

Get_Attribute_Single

Assembly Object

Overview

The Assembly object consists of the attributes and services described below.

NOTE: You can send an explicit message to the Assembly object only when no other connections have been established that read from or write to this object. For example, you can send an explicit message to the Assembly object if a local slave instance is enabled, but no other module is scanning that local slave.

Class ID

Instance IDs

The Assembly object presents the following instance identifiers:

• 0: class

• 101, 102, 111, 112, 121, 122: instance

Attributes

The Assembly object consists of the following attributes:

Instance ID = 0 (class attributes):

Attribute ID

X = supported

— = not supported

Description

Revision

Max Instance

Number of Instances

Instance attributes:

GET

SET

—

S1A48978.14

Remote I/O Modules

Instance ID

101

102

111

112

121

122

X = supported

— = not supported

Attribute ID

Description

Local slave 1: T->O input data

Local slave 1: O>T

Local slave 2: T->O input data

Local slave 2: O>T

Local slave 3: T->O input data

Local slave 3: O>T

Type

Array of BYTE

GET

SET

—

Services

The CIP Assembly object performs these services upon the listed object types:

Service ID hex

0E dec

10 16

Description

Get_Attribute_Single

Set_Attribute_Single 1

Class

—

Instance

Notes

Returns the value of the specified attribute

Returns these values:

0E=attribute not settable: assembly is not o->T type

0F=permission denied: assembly is being used by an active connection

13=config too small: the Set_Attribute_Single command contains partial data

15=data too big: the Set_Attribute_Single command contains too much data

X = supported

— = not supported

1. When valid, the size of the data written to the Assembly object using the Set_Attribute_Single service equals the size of the Assembly object as configured in the target module.

Connection Manager Object

Overview

The Connection Manager object presents the instances, attributes and services described below.

Class ID

Instance IDs

The Connection Manager object presents two instance values:

• 0: class

• 1: instance

Attributes

Connection Manager object attributes are associated with each instance, as follows:

84 S1A48978.14

S1A48978.14

Remote I/O Modules

Instance ID = 0 (class attributes):

Attribute ID Description

X = supported

— = not supported

Revision

Max Instance

Instance ID = 1 (instance attributes):

Attribute ID hex dec

01 01

Description

Open Requests

Open Format

Rejects

Open Resource

Rejects

Open Other Rejects

Close Requests

Close Format

Requests

Close Other

Requests

Connection

Timeouts

Type

UINT

X = supported

— = not supported

Connection Entry

List

CPU_Utilization

STRUCT

UINT

UDINT MaxBuffSize

BufSize Remaining UDINT

GET

SET

—

GET SET Value

—

Number of Forward Open service requests received

Number of Forward Open service requests that were rejected due to bad format

Number of Forward Open service requests that were rejected due to lack of resources

Number of Forward Open service requests that were rejected for reasons other than bad format or lack of resources

Number of Forward

Close service requests received

Number of Forward

Close service requests that were rejected due to bad format

Number of Forward

Close service requests that were rejected for reasons other than bad format

Total number of connection timeouts that occurred in connections controlled by this connections manager

0 (Unsupported optional item

Services

The Connection Manager object performs the following services on the listed object types:

Remote I/O Modules

Service ID hex dec

01 01

0E 14

X = supported

— = not supported

Description

Get_Attributes_All

Get_Attribute_Single

Class Instance Notes

Returns the value of all attributes.

Returns the value of the specified attribute.

Quality Of Service (QoS) Object

Overview

The QoS object implements Differentiated Services Code Point (DSCP or

DiffServe ) values for the purpose of providing a method of prioritizing Ethernet messages. The QoS object presents the instances, attributes and services described below.

Class ID

48 (hex), 72 (decimal)

Instance IDs

The QoS object presents two instance values:

• 0: class

• 1: instance

Attributes

The QoS object consists of the following attributes:

Instance ID = 0 (class attributes):

Attribute ID

X = supported

— = not supported

Description

Revision

Max Instance

Instance ID = 1 (instance attributes):

Attribute ID

Description

DSCP Urgent

Type

USINT

GET

SET

DSCP Scheduled

DSCP High

DSCP Low

USINT

GET

SET

—

Value

For CIP transport class

0/1 Urgent priority messages, default value

= 55.

For CIP transport class

0/1 Urgent priority messages, default value

= 47.

For CIP transport class

0/1 Urgent priority messages, default value

= 43.

For CIP transport class

0/1 Urgent priority messages, default value

= 31.

86 S1A48978.14

Remote I/O Modules

Attribute ID

Description

DSCP Explicit

Type

USINT

GET

SET

Value

For CIP explicit messages (transport class 2/3 and UCMM), default value = 27.

X = supported

— = not supported

NOTE: A change in the instance attribute value takes effect on device re-start, for configurations made from flash memory.

Services

The QoS object performs the following services upon the listed object types:

Service ID hex dec

0E 14

10 16

X = supported

— = not supported

Description

Get_Attribute_Single

Set_Attribute_Single

Class

—

Instance

TCP/IP Interface Object

Overview

The TCP/IP interface object presents the instances (per network), attributes and services described below.

Class ID

F5 (hex), 245 (decimal)

Instance IDs

The TCP/IP interface object presents 2 instance values:

• 0: class

• 1: instance

Attributes

TCP/IP interface object attributes are associated with each instance, as follows:

Instance ID = 0 (class attributes):

Attribute ID Description

X = supported

— = not supported

Revision

Max Instance

GET

SET

—

Instance ID = 1 (instance attributes):

S1A48978.14

Remote I/O Modules

Attribute ID

Description

Status

Configuration

Capability

Type

DWORD

Configuration Control DWORD

Physical Link Object STRUCT

Path Size

Path

UINT

Padded

EPATH

Interface Configuration STRUCT 05

IP Address

Network Mask

Gateway Address

X = supported

— = not supported

Name Server

Name Server 2

Domain Name

Host Name

UDINT

STRING

GET

SET

—

X X

Value

0x01

0x01 = from BootP

0x11 = from flash

0x00 = other

0x01 = out-of-box default

X —

—

0x00 = out-of-box default

Services

The TCP/IP interface object performs the following services upon the listed object types:

Service ID hex dec

01 01

Description Class Instance Notes

Get_Attributes_All

Get_Attribute_Single

Set_Attribute_Single 1

—

Returns the value of all attributes.

Returns the value of the specified attribute.

Sets the value of the specified attribute.

X = supported

— = not supported

1. The Set_Attribute_Single service can execute only when these preconditions are satisfied:

• Configure the Ethernet communication module to obtain its IP address from flash memory.

• Confirm that the PLC is in stop mode.

Ethernet Link Object

Overview

The Ethernet Link object consists of the instances, attributes and services described below.

Class ID

F6 (hex), 246 (decimal)

S1A48978.14

Instance IDs

The Ethernet Link object presents the following instance values:

• 0: class

• 1: port 1

• 2: port 2

• 3: port 3

• 4: port 4

Remote I/O Modules

Attributes

The Ethernet Link object presents the following attributes:

Instance ID = 0 (class attributes):

Attribute ID Description

X = supported

— = not supported

Revision

Max Instance

Number of Instances

Description

Instance ID = 1 (instance attributes):

Type GET SET Value

GET

SET

—

Attribute ID hex

01 dec

01 Interface Speed UDINT X —

02 02 Interface Flags DWORD X —

Valid values include:

0, 10000000, 100000000

Bit 0: link status

0 = Inactive

1 = Active

Bit 1: duplex mode

0 = half duplex

1 = full duplex

Bits 2—4: negotiation status

3 = successfully negotiated speed and duplex

4 = forced speed and link

Bit 5: manual setting requires reset

0 = automatic

1 = device need reset

Bit 6: local hardware detected error

0 = no event

1 = event detected module MAC address 03

Physical Address

Interface Counters

In octets

In Ucast Packets

In NUcast Packets

ARRAY of 6

USINT

STRUCT

UDINT

—

— octets received on the interface unicast packets received on the interface non-unicast packets received on the interface

S1A48978.14

Remote I/O Modules

Description Attribute ID hex dec

05 05

In Discards

In Errors

In Unknown Protos

Out Octets

Out Ucast Packets

Out NUcast Packets

Out Discards

Out Errors

Media Counters

Alignment Errors

FCS Errors

Single Collisions

Multiple Collisions

SQE Test Errors

Deferred Transmissions

Late Collisions

06 06

Excessive Collisions

MAC Transmit Errors

Carrier Sense Errors

Frame Too Long

MAC Receive Errors

Interface Control

Control Bits

Forced Interface Speed

Type GET SET Value

UDINT

STRUCT

UDINT

X —

UDINT

STRUCT

WORD

UINT

X X inbound packets received on the interface, but discarded inbound packets with detected errors (does not include in discards) inbound packets with unknown protocol octets sent on the interface unicast packets sent on the interface non-unicast packets sent on the interface outbound packets discarded outbound packets with detected errors frames that are not an integral number of octets in length bad CRC — frames received do not pass the

FCS check successfully transmitted frames that experienced exactly 1 collision successfully transmitted frames that experienced more than 1 collision number of times the detected SQE test error is generated frames for which first transmission attempt is delayed because the medium is busy number of times a collision is detected later than 512 bit times into the transmission of a packet frames that do not transmit due to excessive collisions frames that do not transmit due to a detected internal MAC sublayer transmit error times that the carrier sense condition was lost or not asserted when attempting to transmit a frame frames received that exceed the maximum permitted frame size frames not received on an interface due to a detected internal MAC sublayer receive error

API of the connection

Bit 0: Auto-negotiation

0 = disabled

1 = enabled

Note: When auto-negotiation is enabled,

0x0C (object state conflict) is returned when attempting to set either:

• forced interface speed or

• forced duplex mode

Bit 1: forced duplex mode (if auto-negotiation bit = 0)

0 = half duplex

1 = full duplex

Valid values include:

S1A48978.14

Attribute ID hex dec

Description Type GET SET Value

Remote I/O Modules

10 16 Interface Label SHORT_

STRING

X —

10000000, 100000000

Note: Attempting to set any other value returns the detected error 0x09 (invalid attribute value)

A fixed textual string identifying the interface, that should include ‘internal’ for internal interfaces. Maximum number of characters is

64.

X = supported

— = not supported

Services

The Ethernet Link object performs the following services upon the listed object types:

Service ID hex

X = supported

— = not supported dec

Description

Get_Attributes_All

Set_Attribute_Single

Get_Attribute_Single

Get_and_Clear

Class

—

Instance

EtherNet/IP Interface Diagnostics Object

Overview

The EtherNet/IP Interface Diagnostics object presents the instances, attributes and services described below.

Class ID

350 (hex), 848 (decimal)

Instance IDs

The EtherNet/IP Interface object presents two instance values:

• 0: class

• 1: instance

Attributes

EtherNet/IP Interface Diagnostics object attributes are associated with each instance, as follows:

Instance ID = 0 (class attributes):

S1A48978.14

Remote I/O Modules

Attribute ID Description

X = supported

— = not supported

Revision

Max Instance

GET

SET

—

Attribute ID

Instance ID = 1 (instance attributes):

Description

Protocols Supported

Connection Diagnostics

Max CIP IO Connections opened

Type

UINT

STRUCT

UINT

Current CIP IO Connections UINT

Max CIP Explicit

Connections opened

UINT

Current CIP Explicit

Connections

CIP Connections Opening

Errors

UINT

CIP Connections Timeout

Errors

Max EIP TCP Connections opened

UINT

UINT Current EIP TCP

Connections

IO Messaging Diagnostics

IO Production Counter

IO Consumption Counter

STRUCT

UDINT

GET

SET

—

IO Production Send Errors

Counter

IO Consumption Receive

Errors Counter

Explicit Messaging

Diagnostics

Class 3 Msg Send Counter

UINT

STRUCT

UDINT

X X

Value

Number of Class 1 connections opened since the last reset

Number of Class 1 connections currently opened

Number of Class 3 connections opened since the last reset

Number of Class 3 connections currently opened

Increments each time a Forward Open is not successful (Originator and Target)

Increments when a connection times out (Originator and Target)

Number of TCP connections (used for EIP, as client or server) opened since the last reset

Number of TCP connections (used for EIP, as client or server) currently open

Increments each time a Class 0/1 message is sent

Increments each time a Class 0/1 message is received

Increments each time a Class 0/1 message is not sent

Increments each time a consumption is received with a detected error

X = supported

— = not supported

Class 3 Msg Receive

Counter

UCMM Msg Receive

Counter

UCMM Msg Receive

Counter

UDINT

Increments each time a Class 3 message is sent

(client and server)

Increments each time a Class 3 message is received

(client and server)

Increments each time a UCMM message is sent

(client and server)

Increments each time a UCMM message is received

(client and server)

Services

The EtherNet/IP Interface Diagnostics object performs the following services upon the listed object types:

92 S1A48978.14

Service ID hex dec

01 01

X = supported

— = not supported

Description

Get_Attributes_All

Get_Attribute_Single

Get_and_Clear

Class Instance

—

Remote I/O Modules

Notes

Returns the value of all attributes.

Returns the value of the specified attribute.

Returns and clears the values of all instance attributes.

EtherNet/IP IO Scanner Diagnostics Object

Overview

The EtherNet/IP IO Scanner Diagnostics object presents the instances, attributes and services described below.

Class ID

351 (hex), 849 (decimal)

Instance IDs

The EtherNet/IP IO Scanner Diagnostics object presents two instances:

• 0: class

• 1: instance

Attributes

EtherNet/IP IO Scanner Diagnostics object attributes are associated with each instance, as follows:

Instance ID = 0 (class attributes):

Attribute ID

X = supported

— = not supported

Description

Revision

Max Instance

GET

SET

—

Instance ID = 1 (instance attributes):

Attribute ID

Description

IO Status Table

Size

Status

X = supported

— = not supported

Type

STRUCT

UINT

ARRAY of

UNINT

GET

SET

—

Services

The EtherNet/IP IO Scanner Diagnostics object performs the following services upon the listed object types:

S1A48978.14

Remote I/O Modules

Service ID hex dec

01 01

0E 14

X = supported

— = not supported

Description

Get_Attributes_All

Get_Attribute_Single

Class Instance

Notes

Returns the value of all attributes.

Returns the value of the specified attribute.

IO Connection Diagnostics Object

Overview

The IO Connection Diagnostics object presents the instances, attributes and services described below.

Class ID

352 (hex), 850 (decimal)

Instance IDs

The IO Connection Diagnostics object presents two instance values:

• 0: class

• 1...256: instance (The instance number is the connection number in the configuration.)

Attribute ID

Attributes

IO Connection Diagnostics object attributes are associated with each instance, as follows:

Instance ID = 0 (class attributes):

Attribute ID

X = supported

— = not supported

Description

Revision

Max Instance

GET

SET

—

Instance ID = 1 to 256 (instance attributes):

Description

IO Communication Diagnostics

IO Production Counter

IO Consumption Counter

Type

STRUCT

UDINT

IO Production Send Errors Counter UINT

UINT IO Consumption Receive Errors

Counter

CIP Connection Timeout Errors

CIP Connection Opening Errors

UINT

GET

SET

CIP Connection State

CIP Last Error General Status

UINT

Value

Increments at each production

Increments at each consumption

Increments each time a production is not sent

Increments each time a consumption is received with a detected error

Increments when a connection times out

Increments each time a connection is unable to open

State of the Connection Bit

General status of the last error detected on the connection

94 S1A48978.14

Attribute ID

Description

CIP Last Error Extended Status

Input Communication Status

Type

UINT

Output Communication Status UINT

Connection Diagnostics

Production Connection ID

Consumption Connection ID

Production RPI

STRUCT

UDINT

Production API

Consumption RPI

Consumption Connection

Parameters

Local IP

Local UDP Port

Remote IP

Remote UDP Port

Production Multicast IP

UDINT

Consumption API UDINT

Production Connection Parameters UDINT

UDINT

UINT

UDINT

UINT

UDINT

Consumption Multicast IP

Protocols Supported

UDINT

Remote I/O Modules

GET SET Value

Extended status of the last error detected on the connection

Communication status of the inputs (see table, below)

Communication status of the outputs (see table, below)

X X

Connection ID for production

Connection ID for consumption

RPI for production

API for production

RPI for consumption

API for consumption

Connection parameters for production

Connection parameters for consumption

—

Multicast IP used for production (or 0)

Multicast IP used for consumption (or 0)

Protocol supported on the connection:

1 = EtherNet/IP

X = supported

— = not supported

The following values describe the structure of the instance attributes: CIP

Connection State , Input Communication Status , and Output Communication

Status :

Bit Number

15...3

Description

Reserved

Idle

Consumption inhibited

Production inhibited

Values

0 = no idle notification

1 = idle notification

0 = consumption started

1 = no consumption

0 = production started

1 = no production

Service ID hex dec

01 01

0E 14

S1A48978.14

Description

Services

The EtherNet/IP Interface Diagnostics object performs the following services upon the listed object types:

Class Instance Notes

Get_Attributes_All

Get_Attribute_Single

—

Returns the value of all attributes.

Returns the value of the specified attribute.

Remote I/O Modules

Service ID hex dec

4C 76

X = supported

— = not supported

Description

Get_and_Clear

Class Instance

— X

Notes

Returns and clears the values of all instance attributes.

EtherNet/IP Explicit Connection Diagnostics Object

Overview

The EtherNet/IP Explicit Connection Diagnostics object presents the instances, attributes and services described below.

Class ID

353 (hex), 851 (decimal)

Instance IDs

The EtherNet/IP Explicit Connection Diagnostics object presents two instance values:

• 0: class

• 1...

N : instance ( N = maximum concurrent number of explicit connections)

Attributes

EtherNet/IP Explicit Connection Diagnostics object attributes are associated with each instance, as follows:

Instance ID = 0 (class attributes):

Attribute ID hex

X = supported

— = not supported

Description

Revision

Max Instance

Value

0...N

GET

SET

—

Instance ID = 1 to N (instance attributes):

Description Type Attribute

ID hex

GET SET Value

Originator connection ID UDINT X — Originator to target connection

Originator IP

Originator TCP Port

Target connection ID

UINT X

UDINT X

—

— Target to originator connection

Target IP

Target TCP Port

Msg Send Counter

UDINT X

—

— Incremented each time a Class

3 CIP message is sent on the connection

96 S1A48978.14

Attribute

ID hex

Description

Msg Receive counter

Remote I/O Modules

Type GET SET Value

UDINT X — Increments each time a Class 3

CIP message is received on the connection

X = supported

— = not supported

Services

The EtherNet/IP Explicit Connection Diagnostics object performs the following services upon the listed object type:

Service ID hex dec

01 01

Description

Get_Attributes_

All

X = supported

— = not supported

Class Instance Notes

X X Returns the value of all attributes.

EtherNet/IP Explicit Connection Diagnostics List Object

Overview

The EtherNet/IP Explicit Connection Diagnostics List object presents the instances, attributes and services described below.

Class ID

354 (hex), 852 (decimal)

Instance IDs

The EtherNet/IP Explicit Connection Diagnostics List object presents two instance values:

• 0: class

• 1...

N : instance

Attributes

EtherNet/IP Explicit Connection Diagnostics List object attributes are associated with each instance, as follows:

Instance ID = 0 (class attributes):

Attribute ID Description

X = supported

— = not supported

Revision

Max Instance

GET

SET

—

Instance ID = 1 to N (instance attributes):

S1A48978.14

Remote I/O Modules

Attribute ID

X = supported

— = not supported

Description

Number of connections

Explicit Messaging

Connections Diagnostic List

Originator connection ID

Originator IP

Originator TCP port

Target connection ID

Target IP

Target TCP port

Msg Send counter

Type

UINT

ARRAY of

STRUCT

UDINT

UINT

UDINT

Msg Receive counter UDINT

GET

SET

—

Value

Total number of opened explicit connections

O->T connection ID

—

T->O connection ID

—

Increments each time a Class 3 CIP message is sent on the connection

Increments each time a Class 3 CIP message is received on the connection

Description

Services

The EtherNet/IP Explicit Connection Diagnostics object performs the following services upon the listed object types:

Class Instance Notes

Service ID hex dec

01 01

X = supported

— = not supported

Get_Attributes_All

Create

Delete

Explicit_Connections_

Diagnostic_Read

—

Returns the value of all attributes.

—

RSTP Diagnostics Object

Overview

The RSTP Diagnostics object presents the instances, attributes and services described below.

Class ID

355 (hex), 853 (decimal)

Instance IDs

The RSTP Diagnostics object presents these instance values:

• 0: class

• 1: instance

98 S1A48978.14

Attribute ID

Remote I/O Modules

Attributes

RSTP Diagnostics object attributes are associated with each instance.

Instance ID = 0 (class attributes):

Description

Revision: This attribute specifies the current revision of the RSTP Diagnostic

Object. The revision is increased by 1 at each new update of the object.

Max Instance: This attribute specifies the maximum number of instances that may be created for this object on a per device basis (for example, an RSTP

Bridge). There is 1 instance for each RSTP port on a device.

Type

UINT

GET

SET

—

X = supported

— = not supported

Attribute ID

Instance ID = 1 to N (instance attributes):

Description

Switch Status

Protocol Specification

Bridge Priority

Time Since Topology

Change

Topology Change Count

Type

STRUCT

UINT

UDINT

GET

CLEAR

—

Value

—

Refer to RFC-4188 for attribute definitions and value range. In addition, the following value is defined: [4]: the protocol is IEEE 802.1D-2004 and IEEE 802.1W

Refer to RFC-4188 for attribute definitions and value range.

Designated Root

Root Cost

Root Port

Max Age

Hello Time

Hold Time

Forward Delay

Bridge Max Age

Bridge Hello Time

Bridge Forward Delay

Port Status

Port

Priority

State

Enable

Path Cost

Designated Root

Designated Cost

Designated Bridge

Designated Port

Forward Transitions Count

—

String

UINT

STRUCT

UDINT

UINT

UDINT

String

UDINT

String

UDINT

UINT

UDINT

UINT

UDINT

—

Refer to RFC-4188 for attribute definitions and value range.

Services:

S1A48978.14

Remote I/O Modules

Attribute ID Description

03 Port Mode

Port Number

Admin Edge Port

Oper Edge Port

Auto Edge Port

Type

STRUCT

UINT

GET

CLEAR

—

Value

• Get_and_Clear: The current value of this parameter is returned with the response message.

• other services: The current value of this parameter is returned without being cleared.

—

This attribute indicates the port number for a data query. The value range is configuration dependent. For a 4-port Ethernet device, as an instance, the valid range is 1...4.

This attribute indicates if this is a user-configured edge port:

• 1: true

• 2: false

Other values are not valid.

This attribute indicates if this port is currently an edge port:

• 1: true

• 2: false

Other values are not valid.

This attribute indicates if this port is a dynamically determined edge port:

• 1: true

• 2: false

Other values are not valid.

X = supported

— = not supported

Service ID hex

01 dec

Description

Services

The RSTP Diagnostics object performs these services:

Class Instance Notes

Get_Attributes_All

Get_Attribute_Single

Get_and_Clear

—

This service returns:

• all attributes of the class

• all attributes of the instance of the object

This service returns:

• the contents of a single attribute of the class

• the contents of the instance of the object as specified

Specify the attribute ID in the request for this service.

This service returns the contents of a single attribute of the instance of the object as specified. Then the relevant counter-like parameter(s) within the specified attribute are cleared. (Specify the attribute ID in the request for this service.)

X = supported

— = not supported

Service Port Control Object

Overview

The Service Port Control object is defined for port control purposes.

100 S1A48978.14

Class ID

400 (hex), 1024 (decimal)

Instance IDs

The Service Port Control object presents these instance Values:

• 0: class

• 1: instance

Remote I/O Modules

Attributes

Service Port Control object attributes are associated with each instance.

Required class attributes (instance 0):

Attribute ID

X = supported

— = not supported

Description

Revision

Max Instance

Type

UINT

Get

Set

—

Required instance attributes (instance 1):

Description Type Get Attribute ID hex

01 dec

01 Port Control UINT X

Set

Value

02 02 Mirror UINT X X

0 (default): disabled

1: access port

2: port mirroring

3: extended port bit 0 (default): ETH2 port bit 1: ETH3 port bit 2: ETH4 port bit 3: internal port

X = supported

— = not supported

NOTE:

• If the SERVICE/EXTEND port is not configured for port mirroring, the mirror attribute is ignored. If the value of a parameter request is outside the valid range, the service request is ignored.

• In port mirroring mode, the SERVICE/EXTEND port acts like a read-only port. That is, you cannot access devices (ping, connection to Control

Expert, etc.) through the SERVICE/EXTEND port.

Services

The Service Port Control object performs these services for these object types:

S1A48978.14

101

Remote I/O Modules

double-click on the 140 CRP 312 00 module, page 32

Service ID hex dec

01 01

Name

Get_Attributes_All

Class

02 02 Set_Attributes_All

—

Get_Attribute_

Single

Set_Attribute_

Single

X = supported

— = not supported

—

Instance

Description

Get all attributes in a single message.

Set all attributes in a single message.

Get a single specified attribute.

X Set a single specified attribute.

Diagnostics Available through Control Expert

Introduction

The Quantum EIO modules support online actions. Use the online actions to perform these tasks:

• Display EtherNet/IP objects for the head module or a remote EtherNet/IP device.

• View and edit the service/extend port configuration parameters for the head module/

• Ping the head module or a remote EtherNet/IP or Modbus TCP device to confirm it is active on the Ethernet network.

• Connect to a remote device to perform these actions:

◦ View the remote device’s default parameter settings.

◦ View the remote device’s current parameter settings.

◦ Edit and download to the remote device its editable parameter settings.

Device Services

Access the Device Services Tab

The Control Expert IP configuration parameters apply to the 140 CRP 312 00 head module in the local rack. To access the Device Services tab,

Device Services Parameters

These parameters are found on the Control Expert Device Services tab:

Field

Network Card

CRP Diagnostics

(See below.)

Parameter

Card

• Connect

• Disconnect

• Online Action

• EtherNet/IP Explicit Message

Apply

Description

IP address of the PC connection to the 140 CRP

312 00 apply configuration

102 S1A48978.14

EtherNet/IP Objects, page 103

Remote I/O Modules

Access Online Action

In the CRP Diagnostics field, select Connect to connect to the PLC and press

Apply to access the configuration tabs for Online Action or EtherNet/IP Explicit

Message :

• Online Action configuration tabs:

◦

◦

Service Port, page 103

◦

Ping, page 104

•

EtherNet/IP Explicit Message, page 61

EtherNet/IP Objects

View Parameters

Use the EtherNet/IP Objects tab to view available EtherNet/IP parameters:

Step

Action

In Control Expert, access the module for

Online Action.

Double-click on the 140 CRP 312 00 module in the Control Expert rack view.

Select the EtherNet/IP Objects tab.

Press Refresh .

Comment

Refer to Online Action, page 103

View these parameters:

• Group/Parameters

• Value

• Unit

This action updates the screen with current parameters.

Service Port Management (Online Action)

Introduction

Configure the SERVICE port for the 140CRP31200 module on the Control Expert

Service Port tab.

Access the Service Port Tab

Step

Action

In Control Expert, access the module for Online Action.

Refer to Online Action, page

103

Double-click the 140CRP31200 module in the Control Expert rack view.

Select the Service Port tab.

Field

Service Port Mode

Access Port

Configuration

Port Mirroring

Configuration

Service Port Parameters

Parameter

Access (default)

Value

ETH1

Mirroring ETH1

Service Port Number ETH1

Source Port(s)

ETH1

Internal Port Yes

Comment

You cannot edit the value in the Service Port Number field.

Service Port Mode = Mirroring (see note)

Service Port Mode = any available source port

Ethernet traffic destined for the module

S1A48978.14

103

Remote I/O Modules

Field Parameter Value

ETH2

ETH3

ETH4

Yes

—

Comment traffic through the 140CRP31200 INTERLINK port

Ethernet traffic through the first remote I/O port

Ethernet traffic through the second remote I/O port

Description — — description of the source port

NOTE: In port mirroring mode, the SERVICE port acts like a read-only port. That is, you cannot access devices (ping, connection to

Control Expert, etc.) through the SERVICE port.

Buttons on the Service Port tab:

Button

Update

Refresh

Description

After you change Service Port parameters, press this button so that the module can use the new configuration.

This button reads the latest Service Port configuration from the module.

On Line Behavior

The Service Port parameters are stored in the application, but you can reconfigure (change) the parameters in connected mode. Values that you reconfigure in connected mode are sent to the 140CRP31200 module through explicit messages. (The changed values are not stored, so a mismatch can exist between the parameters that are being used and those in the stored application.)

If the module does not respond to the explicit messages, a message appears.

Limitations

The SERVICE port on the 140CRP31200 module has the same limitations as the cloud port of the dual-ring switch (DRS). Therefore, the cloud port on the module and the cloud port on the DRS can be connected to the same equipment.

For more information about considerations that apply to the use of the distributed

I/O cloud port on the DRS, refer to the topic Predefined Configuration Files topic in the Quantum Ethernet I/O System Planning Guide .

Pinging the 140CRP31200 Module

Introduction

Use the Control Expert ping function to send an ICMP echo request to the

140CRP31200 head module. The request determines if the target device is present. If the target device is present, the request determines the time elapsed until an echo response from the target device is received.

Access the Ping Tab

Open the Control Expert Ping tab:

Step

Action

In Control Expert, access the 140CRP31200 head module for

Online Action, page

103

Double-click on the 140CRP31200 head module in the Control Expert rack view.

Select the Ping tab.

104 S1A48978.14

Ping Tab

This illustration shows the Ping tab and its parameters:

Remote I/O Modules

Ping parameters:

Field

Address

Ping

Parameter

IP Address

Repeat (100ms)

Stop on Error

Ping (button)

Ping Result

Clear (button)

Value

— checked unchecked checked unchecked

—

Comment

IP address of the target module.

Ping once.

Ping every 100 ms.

Stop pinging when a detected communication error is displayed.

Continue pinging when a detected communication error is displayed.

Start pinging. (Click again to stop repeated pinging when no detected error is displayed.)

This box reports the response to the ping.

Click this button to clear (empty) Ping Result .

Displaying I/O Memory Consumption

Displaying Memory Consumption

In Control Expert you can monitor the I/O memory consumption by viewing the bus properties. Use one of these methods:

• In the Project Browser , right-click Project > Configuration > EIO Bus >

Properties

• In the Project Browser , right-click Project > Configuration > EIO

[Quantum or Modicon X80] Drop > Properties

• In background of the EIO Bus window, right-click Bus properties .

• In the Edit menu, scroll to Bus properties .

S1A48978.14

105

Remote I/O Modules

The IO-Memory screen looks like this:

Exceeding EIO Limitations

Control Expert displays a detected error in the log window if one of these events occurs:

• The size of the EIO memory exceeds 1400 input bytes or 1400 output bytes.

• The size of the EIO network exceeds 32768 input bytes or 24576 output bytes.

• The size of the EIO network exceeds 80% of the 32768 input bytes or 80% of the 24576 output bytes.

Logging DTM Events to a Control Expert Logging Screen

Description

Control Expert maintains a log of events for:

• the Control Expert embedded FDT container

• each Ethernet communication module DTM

• each EtherNet/IP remote device DTM

Events relating to the Control Expert FDT container are displayed in the FDT log event page of the Output Window .

Events relating to a communication module or remote EtherNet/IP device are displayed:

• in configuration mode: in the Device Editor , by selecting the Logging node in the left pane

• in diagnostic mode: in the Diagnostics window, by selecting the Logging node in the left pane

Logging Attributes

The Logging window displays the result of an operation or function performed by

Control Expert. Each log entry includes the following attributes:

Attribute

Date/Time

Log Level

Description

The time the event occurred, displayed in the format: yyyy-mm–dd hh:mm:ss

The level of event importance. Values include:

Information A successfully completed operation.

Warning An operation that Control Expert completed, but which may lead to a subsequent error.

106 S1A48978.14

Remote I/O Modules

Attribute Description

Error An operation that Control Expert was unable to complete.

Message A brief description of the core meaning of the event.

Detail Message A more detailed description of the event, which may include parameter names, location paths, etc.

Accessing the Logging Screen

In Control Expert:

Step

Action

Open a project that includes a BME NOC 03•1 Ethernet communication module.

Clock Tools > DTM Browser to open the DTM Browser .

In the DTM Browser , double-click the BME NOC 03•1 (or right-click Open ) to open the configuration window.

Select Logging in the navigation tree in the left pane of the window.

S1A48978.14

107

Remote I/O Modules

Firmware Upgrade

Introduction

This chapter describes the steps for upgrading the firmware for your

140CRP31200 head module and the 140CRA31200 or BMXCRA312•0 adapter module.

Firmware Update with Automation Device Maintenance

Overview

The EcoStruxure ™ Automation Device Maintenance is a standalone tool that allows and simplifies the firmware update of devices in a plant (single or multiple).

The tool supports the following features:

• Automatic device discovery

• Manual device identification

• Certificate management

• Firmware update for multiple devices simultaneously

NOTE: For a description of the download procedure, refer to the

EcoStruxure ™ Automation Device Maintenance, User Guide .

140CRP31200 Firmware Upgrade with OS Loader

OS

Use the Control Expert OS Loader to upgrade the firmware on the 140CRP31200 module. OS Loader was installed on your PC when you installed Control Expert.

(The minimum required version of OS Loader is V6.0. The compatible version is included with your copy of Control Expert.)

A complete firmware upgrade includes the installation of these discrete files:

• kernel

• exec

The kernel and exec files are installed independently. Therefore, perform the firmware upgrade process two times (once for each file).

The name of the firmware file indicates the upgrade type (kernel or exec).

Examples:

• kernel file name: CCS1_Noc_Kerl_OSLoader.bin

• exec file name: CCS1_Noc_Exec_OSLoader.bin

NOTE: These instructions assume that you are familiar with Control Expert.

For more information about the OS Loader, refer to the chapter OSLoader

Screens (see EcoStruxure ™ Control Expert, OS Loader, User Manual).

Upgrade Procedure

Follow these steps to upgrade either the firmware kernel or the firmware exec.

108 S1A48978.14

Step

Remote I/O Modules

NOTE:

• We recommend that you update the kernel before you upgrade the exec.

Both firmware upgrade files are installed in the same manner. The only difference is the name of the file you select.

• Confirm that there is no interruption to power or communications during the firmware upgrade process. Otherwise, the 140CRP31200 module can be damaged.

• During the firmware upgrade, the I/O communications with the adapter on the remote drop are interrupted. After the

Hold up time, page 44

expires, the I/O modules return to their fallback state.

Action

Connect the PC that is running the Control Expert OS

Loader directly to one of the module ports.

Launch OS Loader.

Click Next to continue.

Select the FTP communication driver and press Next to continue.

In the Target Address area, type in the FTP Address of the

140CRP31200 module that is the target of the upgrade.

Click Next to continue. Perform these tasks at the next installation screen:

—

Comment

Available ports:

• SERVICE port:

◦ 140CRP31200 head module

◦ 140CRA31200 adapter (Quantum remote drop)

◦ BMXCRA31210 adapter (Modicon X80 remote drop)

• INTERLINK port (140CRP31200)

• DRS port that is configured for a distributed I/O cloud

Start > Programs > EcoStruxure Control Expert > OS

Loader .

Go directly to the first installation step.

The next screen displays a list of devices discovered by OS

Loader. It also displays the FTP address for each discovered device.

— a b

Select Download OS to device .

Click the Browse button to navigate to and select the desired firmware upgrade file.

— Click Next . Perform these tasks at the next installation screen: a b

Compare the selected firmware File against the firmware already loaded in the

Device .

Confirm that the Hardware ID for both the file and the device are the same

Click Next . On the summary page, click Download .

Click Close .

The OS Loader displays the progress of the FTP session.

The download is complete when it displays the word

SUCCESS .

The firmware download is finished.

The upgrade process takes approximately 2 minutes:

• 1 minute for firmware upgrade

• 1 minute to reboot and reestablish I/O connections

Hot Standby

Use these steps to upgrade the 140CRP31200 firmware in Hot Standby configurations:

S1A48978.14

109

Remote I/O Modules

Step

Action

Use the preceding instructions to upgrade the firmware for the 140CRP31200 in the standby rack.

NOTE: During the firmware upgrade, the I/O communications with the remote drop’s adapter and the 140CRP31200 module in the primary rack are not interrupted. However, the standby I/O communications with the adapter are interrupted.

When the firmware on the 140CRP31200 in the standby rack is upgraded, perform a manual switch-over that gives the newly upgraded standby rack the role of primary rack.

Upgrade the firmware for the adapter in the (new) standby rack to facilitate future Hot

Standby switch-overs.

Adapter Firmware Upgrade with Unity Loader

Overview

Use these procedures to upgrade the firmware for the 140CRA31200 or

BMXCRA312•0 remote I/O adapter:

Stage

Description

Download and install Unity Loader software.

Configure and store IP parameters (optional).

Connect your configuration PC to the remote I/O adapter.

Transfer the firmware upgrade to the remote I/O adapter.

The minimum required version of Unity Loader is V2.2. (V2.3 is required for the

BMXCRA312•0 adapter module and I/O modules in a Modicon X80 Ethernet remote I/O drop.)

Downloading and Installing Unity Loader

Download the Unity Loader software to your PC:

Step

Action

Enter the web address for Schneider Electric (www.se.com) in an Internet browser.

In the Search from input field , enter the phrase Unity Loader and press Enter .

Examine the search results and select the appropriate entry for the Unity Loader software.

NOTE: You can select the Download results.

> Softwares menu command to filter the

Follow the on-screen instructions to download both the Unity Loader installation software and any necessary installation instructions.

Run the Unity Loader setup file and follow the instructions (on the screen and in the downloaded documentation) to install Unity Loader.

Default Address Configurations

If you wish, you can configure and store IP parameters for the remote drop’s communications adapter when these conditions are met:

• The rotary switch setting is Stored .

• You have not configured and stored valid IP parameters

The adapter uses these default address configurations:

110 S1A48978.14

EtherNet/IP explicit message, page 58

Remote I/O Modules

Parameter

Default IP Address

Description

The default IP address starts with 10.10 and uses the last 2 bytes of the

MAC address. As an example, a device with the MAC address of

00:00:54:10:8A:05 has a default IP address of 10.10.138.5 (0x8A=138,

0x05=5).

The default mask is 255.0.0.0 (a class A mask).

Default Sub-Network

Mask

Default Gateway

Address

The default gateway address is identical to the default IP address.

The default address is based on the adapter’s MAC address. This makes it possible for several Schneider Electric devices to use their default network configurations on the same network.

To use a specific set of IP parameters, store them in the adapter module. Set the rotary switches to the Stored position.

You can send an

to the

TCP/IP interface object, page 87

of the module to store the configured IP parameters.

NOTE: The adapter uses the stored IP parameters only after a power cycle.

Connect the Configuration PC to the Remote I/O Adapter

Connect your configuration PC (that is running Unity Loader) directly to the

140CRA31200 or BMXCRA31210 adapter module. These ports are available:

• SERVICE port

• DRS port that is configured for a distributed I/O cloud

NOTE: There is no SERVICE port on the BMXCRA31200 adapter.

Verify that communications are established between the PC and the adapter by issuing a Ping command from the PC:

Step

Action

Open a command window on the PC.

In the Run dialog, type in cmd .

Click OK .

At the command prompt, type in the ping command and the device IP address.

Comment

Start > Run .

Example: C:\>ping 192.168.21.38

The command window verifies that a connection is established:

Upgrade Procedure

Do not interrupt the firmware download process:

S1A48978.14

111

Remote I/O Modules

Step

configured in the application, page 38

• Do not allow an interruption to the power or the communications during the firmware upgrade process.

• Do not shut down the Unity Loader software during the upgrade.

If the firmware download process is interrupted, the new firmware is not installed and the adapter continues to use the old firmware. If an interruption occurs, restart the process.

Open Unity Loader on your PC and update the firmware for the remote I/O adapter:

Action

Open Unity Loader on your PC. ( Start > Programs > Schneider Electric > Unity Loader )

Unity Loader opens and displays the Project tabM

112

In the Connection area of the Project page, connect to the module:

• In the Media list, select Ethernet .

• In the Address field, type in the IP address of the adapter, which is either:

◦ configured : The adapter is already communicating on the network and the IP address for the module is

◦ default : The adapter’s rotary switch position is Stored and you did not already store valid IP parameters.

• Click Connect .

After Unity Loader has connected to the module, click the Firmware tab:

In the PC area, click the ellipsis ( ...

) button to open a dialog where you can navigate to and select the firmware file for the network connectivity module. The firmware is contained in a Unity Loader file (.ldx extension).

S1A48978.14

Step

Remote I/O Modules

Action

After you select the firmware file and close the dialog, the selected revision of this firmware is displayed in the list on the left, and the current version of the firmware is displayed in the list on the right.

When the arrow in the middle of the screen (above) is green, click Transfer .

NOTE: Only click Transfer if the arrow is green. A yellow arrow indicates that the firmware file on your computer is the same version or newer than the file selected for transfer; a red arrow indicates that the firmware on the computer is not compatible with the remote I/O adapter.

Click yes on the 2 dialogs that appear. A third dialog appears (below), which indicates the transfer status with the blue bars at the bottom of the screen. After the transfer is complete, click Close .

NOTE: If you are upgrading firmware for more than one remote I/O adapter, additional dialogs will appear. Click yes to close each dialog.

In the Unity Loader software, click Disconnect and close the window.

Reboot the module to finalize the firmware update.

The upgrade process takes approximately 2 minutes:

• firmware upgrade (1 minute)

• reboot, reestablish I/O connections (1 minute)

S1A48978.14

113

Remote I/O Modules