Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
How do you wish to implement redundant ERIO networks?
Would you want a double ring topology?
Protocols - HSR, DLR, RSTP
Module - dual ring connections on single module, single ring connection on two modules
See Choice A
Would you want a double network topology?
Protocol - PRP
Dual network with same information sent over both networks
More expense
See Choice B
Would you want a separate backbone topology?
Protocol - up to installer
Dual connections to ethernet backbone managed by IT
Third party protocols selected by user.
Must comply with basic requirements
See Choice C
Revised offer (2nd March 2020):
1. Single module with single connections to two separate ring / star networks using PRP.
2. Hot standby system with single connection for each CPU to two separate networks with two separate modules in each drop.
In each architecture PRP is primarily the network protocol. The network is constructed using third party switches with some requirements to be specified in the design.
In the system proposed how many drops are required?
Currently the PME PXM 0100 module supports the following 3 basic architectures:
-Standalone PLC – PXM in Local Rack
-Standalone PLC – PXM in Remote Rack
-HSBY PLC – PXMs in Local Rack
For future development our work with ProSoft will take into account the PXM additional redundancy modes enhancement listed below and we need your feedback to know the business case of these new functionalities.
Could you send me your feedback (Customer name, architecture targeted, PXM & CPU number targeted with these new functionalities)?
The table below summarizes the various configurations, (both existing and proposed)
1. M580 in a release later in 2024 or possibly 2025 schneider will have modules that support PRP. This is part of the dual redundant ethernet remote IO network. It will occur in stages but the first will provide drop modules in the rack that support PRP and at the CPU end there may be third party modules and eventually M580 PRP modules that sit in the rack.
2. The BMENOC module at this stage will not support PRP. The intent for PRP is to effectively provide zero communications down time between the M580 CPU and the remote IO X80 racks. It may be a feature in the future if there is sufficient demand but this need must be made known to your Schneider account managers and technical support people so we can try to drive the road map of development.
3. The PRP modules will allow other protocols to co-exist. Its aim is to ensure that two sets of the same ethernet packet are sent to each destination and at the destination the recipient rejects duplicated packages. To test you would need to monitor the update rate of the messages at the modules. Typically, this should be the same irrespective if both or one of the network pathways is operational. To test break a network to see if the update rate changes. I am deliberately vague at the moment as the equipment has not been released, I cannot provide exact details.
4. At the CPU end we will have the start of the PRP network. Initially this will be with a Hirschmann RED25 - which provides RSTP to PRP (Port PRP-A and port PRP-B) at the other end of the communication i.e. the drop racks there will be a new full length CRA module which will also have (Port PRP-A and port PRP-B). If the system is a hot standby CPU system, it may also be possible to have two new PRP CRA modules in one drop rack. In this case one module will be the primary module and the other will be a standby module.