valter.carvalho
Member
Hello, I have the following problem:
My costumer have a system configured as follows:
- Two set`s of 90-30 controller + IO's.
- Engineering and backup station running Cimplicity version 6.0
The set's of PLC's work in a cold-stanby redundancy, and follows these rules:
Each set has it's own I/O.
Each controller has access to it's own I/O only.
The process of switching is controlled by Cimplicity.
And we have the following problem: The redundancy control in the Cimplicity software uses a preferred PLC (primary PLC), which has the control unless it goes down. That means, if PLC A is the primary and PLC B the secondary, when we get PLC A down, the control is set (by Cimplicity) to the PLC B. But when we fix PLC A problem and put it on line again, the Cimplicity automatically set it to the controlling position.
This way, since the stand by is in cold mode (that means, each time it changes, we have many data to be restored from Cimplicity and from a Oracle database, prior to the start of control), when we have a shutdown in PLC A, we have to loose time while switching to PLC B, and loose time again, when PLC A is set back.
I have suggested the costumer to buy the MAX-ON sulution, but they will not.
So, there's anything to do about this in Cimplicity? Any way to configure it to have a dinamically assigned primary PLC?
Thanks in advance,
Valter Carvalho
My costumer have a system configured as follows:
- Two set`s of 90-30 controller + IO's.
- Engineering and backup station running Cimplicity version 6.0
The set's of PLC's work in a cold-stanby redundancy, and follows these rules:
Each set has it's own I/O.
Each controller has access to it's own I/O only.
The process of switching is controlled by Cimplicity.
And we have the following problem: The redundancy control in the Cimplicity software uses a preferred PLC (primary PLC), which has the control unless it goes down. That means, if PLC A is the primary and PLC B the secondary, when we get PLC A down, the control is set (by Cimplicity) to the PLC B. But when we fix PLC A problem and put it on line again, the Cimplicity automatically set it to the controlling position.
This way, since the stand by is in cold mode (that means, each time it changes, we have many data to be restored from Cimplicity and from a Oracle database, prior to the start of control), when we have a shutdown in PLC A, we have to loose time while switching to PLC B, and loose time again, when PLC A is set back.
I have suggested the costumer to buy the MAX-ON sulution, but they will not.
So, there's anything to do about this in Cimplicity? Any way to configure it to have a dinamically assigned primary PLC?
Thanks in advance,
Valter Carvalho