Академический Документы
Профессиональный Документы
Культура Документы
Remote
Remote I/O
I/O
<Trainer>
2/12/20
Remote I/O
Local I/O
● Backplane communication
● Very high performances
● Low distance
Distributed I/O
● Proprietary communication
● High performances
● Greater distance than Local I/O
● Low size of data exchanges
Ethernet I/O
The M580 system uses Modicon X80 I/O modules, many of which are used in
an M340 system.
The system also supports several Ethernet-based eX80 I/O modules, which
can be installed on both the main local rack and Ethernet remote racks.
The local rack can also support an Extension rack of Premium I/O modules.
A: Distributed
B: Local
C: Remote
Remote I/O
Out of the nine standalone M580 CPUs, five support RIO (Remote I/O):
• BME P58 2040
• BME P58 3040
• BME P58 4040
• BME P58 5040
• BME P58 6040
These CPUs have the Remote I/O Scanner Service embedded within them
allow deterministic I/O exchanges, and are able to communicate with
Modicon X80 RIO drops on an Ethernet network.
To support the new Ethernet backplane and to allow Ethernet based I/O
modules to be located in the Remote I/O drops, there is a new Remote I/O
drop adaptor module, the BME CRA 312 10.
The BME CRA 312 10 is also known as the eX80 Performance EIO
adapter within an M580 Remote I/O architecture.
Devices other than the CRA modules can utilise the RIO Scanner.
The existing X80 drop adaptors BMX CRA 312 00 & BMX CRA 312 10
are also supported.
Performance CRA
In standard and coated version
• Top features, including system Time Stamping at 10ms
• Ethernet BME CRA supports “Ethernet only” module: HART module, Weighing module and future
embedded communication module
Standard CRA
• Cost optimized for small drops
• Basic functions
CRA Ethernet port
• Act as Modbus/TCP server
• Act as server for CIP explicit messaging
Confidential Property of Schneider Electric | Page 14
Remote I/O Offer
Remote Drop Adapter
Remote I/O
On the M580 and each CRA module, 2 Ethernet ports are used for linking the head and the drops
together.
These ports are labelled DEVICE NETWORK (ports ETH2 and ETH3).
• In a simple architecture, an M580 DEVICE NETWORK port is linked to a CRA drop modules
using one port.
• Additional drops can then be "daisy chained" from this point: .
To ensure a high reliability system, cable redundancy can be achieved by looping back to the second
DEVICE NETWORK port of the M580 CPU.
• This kind of architecture is deterministic and ensures high availability of the system, with
recovery times less than 50ms.
Remote I/O
100m
Up to 31 CRA modules can be inserted to extend the distance, dependant upon the chosen M580 CPU:
100m 100m
One option to extend the architecture beyond the 100m segments is to use BMX NRP 0200 / 0201 - Fibre-
optic repeater modules.
Using NRP modules allows for a fibre optic connection between consecutive X80 I/O drops. This allows for
distances up to 15km (single mode).
100m 100m
Interlinked to CRA
Fault monitoring through CRA
Another option to extend the architecture beyond the 100m segments is to use Dual Ring Switches (DRS)
• Using Dual Ring Switches (DRS) can extend the distance between consecutive Ethernet remote I/O
drops
• Distance extension (add 100m segments)
• Create sub-rings for high availability
• Allow integration of other Ethernet devices in the same network
• Using fibre optic DRS, extension up to 2 or 15 km
100m 100m
Remote I/O
The final step is to populate the drop with Power Supply, and
any additional I/O modules.
The Network Manager allows the IP Address to be configured for the CRA.
Identifier is given as BMECRA_0xx where xx corresponds to the number set by the switches
on the front of the CRA
The following questions will help to check understanding of the topics covered in
this chapter:
• What are the three different types of I/O?
Distributed I/O, Remote I/O and Local I/O
• What is the distance limitation using a normal Ethernet cable to a REMOTE drop?
100m