Anyone used ERIO with Quantum?

The Schneider (Modicon) Quantum PLC has used an old coaxial bus system for comms between racks for nearly 20 years. The same comms cable was also used on the previous 800 series PLC, as well as many of their previous models, possibly dating back to the 70s. This is their RIO (Remote IO) system.
Recently, they have brought out a new system based on Ethernet, known as ERIO. I like the look of this, since we can get rid of the old coax, and also have a speed increase with other benifits. Unfortunately, having not used it before, I don't know if it is fully reliable or whether is still is a bit buggy.

Has anyone used this system before, and if so, how did it work out?

I haven't used it but I did consider it for a recent project. After 3 remote backplanes there may be little or no performance benefit over the S908. I don't understand why they aren't using gigabit on all their ethernet interfaces.

I have also confirmed that topological addressing eg %I3.1.4.26 can not be used with ERIO, all inputs are %I161 format and outputs %M143 type format. You also can not enter the tag names through the objects tab of the IO module properties, you have to enter them through the data editor and type in the correct address.

I believe they quote 50ms as healing time for the ethernet ring, whereas if you build the ring out of say n-tron ethernet switches I think 15ms is the spec.

That being said I like the idea of fewer points of failure (not using discrete ethernet switches).

http://www.schneider-electric.rs/documents/automation-control/tvda_small_io_system.pdf

this document has measurements of ring healing after various types of interruptions. not for quantum but m340.

V0N_hydro said:

After 3 remote backplanes there may be little or no performance benefit over the S908.

Click to expand...

It is the other way around, there is no difference for less than 3 ERIO drops, but after 3 then it is better than S908.

Just checked the manual about addressing within an ethernet rio system and it shows topological addressing is supported (see attached page 147 from http://www.global-download.schneider-electric.com/85257849002EB8CB/all/6744B89E71944255852578CB006A759A/$File/s1a48959_00.pdf)

Here was the response from support:

Hello,

How can we use topological addressing with Quantum Ethernet Remote IO? It is very convenient to be able to refer to an IO point using this bus.rack.module.channel format as it defines a physical location for the IO point within the plant, as opposed to %I201, which could be anywhere.

This was possible with the 908 remote IO, as per screen shot below;

With the newer Ethernet remote IO modules and unity 6.0 the IO Objects tab doesn’t exist. It is most convenient to be able to enter the tag names through this dialog as it ensures they are on the correct IO module.

The address for Inlet_valve_open is the same in both cases, %I\2.2\1.3.1 but the ERIO configuration gives the error “The instance is located on an address that isn’t configured”.

The help says topological addressing is allowed with Ethernet remote IO:
Thanks for your help


"[email protected]"
04/16/2012 10:56 AM <[email protected]>
cc

Subject
FW: Quantum Ethernet Remote IO Topological
Addressing and IO Variable Configuration

V0n,
The help file is incorrect and the error has been reported and submitted for correction.
Topological addressing is not supported on Ethernet Remote I/O.
____________________________________________________________

Schneider Electric | Power North America | Canada |Technical Support Specialist
Phone: +1-800-565-6699 |
Email: [email protected] | Site: www.schneider-electric.ca | Address:
5985, Mc Laughlin Rd, Mississauga, ON, L5R 1B8 CA

Quite flexible, actually

Hi there,

I was looking for some feedbacks as well as we are considering it for a new project.
I've just seen they are releasing something called "X80 drops", which basically is a M340 drop with a dedicated CRA instead of a CPU, and works as a drop behind a Quantum CPU.
Good point with this kind of drop is the "device DDT" view for each module, easier than state ram. Seems that the mapping problem solved?

Anyway, at least we have Modbus port in the drop, which was we were looking for, and was wondering about the performances vs standalone modbus port in a CPU.

Any ideas?

Yeah the m340 being used as remote io for the quantum is going to be gr8. Got documents and specs on pdf but they are a bit to big. On the schneider website you can find all these docs. If not then pm me ill mail it to you