Connecting Distributed I/O Devices to a Quantum EIO System

Original instructions

Distributed I/O Devices

Distributed I/O devices can be connected to a Quantum EIO system in the following 2 ways:

Distributed I/O devices in a sub-ring have 2 Ethernet ports (to maintain the ring), and they support . An example of devices on a distributed I/O sub-ring would be several STB islands that use STB NIP 2311 NIMs.

Ethernet distributed I/O devices that can be put on distributed I/O clouds include 2 families of devices:

I/O Scanned Devices	Devices that Cannot be I/O Scanned
variable speed drives — Altivar ATV 32, 61, 71	Magelis HMI controllers
main protection and control functions — TeSys T	Pelco cameras
ETB (I/O modules), OTB (distributed I/O modules), and STB (modules connected on a single island)
remote masters — Profibus master interface, ETG1000 master interface, Hart master interface
Modbus TCP and EtherNet/IP distributed I/O devices
third-party distributed I/O devices compatible with the Quantum EIO system

Topology Choices

Your Ethernet remote I/O network will comprise of one of the following topologies:

These 2 topologies, which are discussed later in this guide, are comprised of the devices in the following table. These devices and their Ethernet port types define how you will choose and build your topology.

To Insert in the Network...	Use...	Topology Type
distributed I/O devices with a single Ethernet port	a distributed I/O cloud (with devices in a star topology)	You can connect a distributed I/O cloud to a high-capacity daisy chain loop. A distributed I/O cloud participates in the remote I/O network only if it is connected to a DRS that resides on the main ring in a high-capacity daisy chain loop. In this case, interlink a 140CRP31200 head module with a 140NOC78000 head module on the local rack, since the 140NOC78000 module supports the distributed I/O cloud. NOTE: A distributed I/O cloud that is connected to a 140 NO• 780 •• module on the local rack within a simple daisy chain loop is isolated. The cloud is not physically part of the remote I/O network.
distributed I/O devices with dual Ethernet ports	a distributed I/O cloud (with devices in a star topology) — or — a distributed I/O sub-ring (with devices in a daisy chain loop, if they support RSTP).	You can only connect a distributed I/O cloud or distributed I/O sub-ring via a DRS that resides on the main ring in a high-capacity daisy chain loop.

A network communication protocol for industrial automation applications that combines the standard internet transmission protocols of TCP/IP and UDP with the application layer common industrial protocol (CIP) to support both high speed data exchange and industrial control. EtherNet/IP employs electronic data sheets (EDS) to classify each network device and its functionality.

A daisy chain loop, often referred to as SDCL, that contains remote I/O devices only (no switches or distributed I/O devices). This topology consists of a local rack (containing a remote I/O head module), and 1 or more remote I/O drops (each drop containing a remote I/O adapter module).

Often referred to as HCDCL, a high-capacity daisy chain loop uses DRSs to extend the distance between remote I/O drops or connect sub-rings (containing remote I/O drops or distributed I/O devices) and/or distributed I/O clouds to the Ethernet remote I/O network.

Any Ethernet device (Schneider Electric device, PC, servers, or third-party devices) that supports I/O exchange with a PLC or other Ethernet communication service.

A group of distributed I/O devices connected either to a non-ring port on a DRS or to a distributed I/O communications module in the local rack. Distributed I/O clouds are single-point connections to the Ethernet I/O network and are not required to support RSTP.

(rapid spanning tree protocol) A protocol that allows a network design to include spare (redundant) links to provide automatic backup paths if an active link stops working, without the need for loops or manual enabling/disabling of backup links.