Search the Community

Showing results for tags 'redundancy'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Found 6 results

  1. Hi, I have been helping a client overseas to upgrade and install some CPE330 PLCs configured as CRU320s to replace their faulty CRU320s. They had been previous controlling primarily from the Secondary (PLC B) for the last 6 years or so until PLC B finally failed due to a power surge. Having configured and downloading the previously working project to the PLCs in their respective hardware configuration, the system refuses to allow PLC A to control via the Citect SCADA, despite showing as Active and Ready on both Citect and the RMX Modules, although no outputs are read through Citect when PLC B is switched off at all. I found this forum from searching a previous post about drivers and if 90-30 and Rx3i required any changes (their previous setup before being Rx3i was 90-30), but as you confirmed in that thread, that the driver should be fine, unless you know of any issues with it working alongside newer PLCs configured as older ones? I should note we have discovered that the firmware revisions on each PLC is different and will be getting them to upgrade the later one to coincide. Each PLC has been tested in either HWC and both operate when configured as PLC B and neither operate fully as PLC A. We've had a GE technician check over the project and extracted text files from the PLCs and has confirmed the code and config looks correct. We're running out of ideas and out next step is to try and borrow 2 PLC racks and try to run them all first hand to see if PLC A runs on the SCADA in our office to try and rule out the software altogether! Any help you can provide would be much appreciated, Gene
  2. I'm using Controllogix L61 redundancy system as a slave with DCS using ethernet tcp/ip socket programming. The communication between master and slave will fail after a switchover. Kindly give solution for this. Thanks and regards, Rasu
  3. Hi, I have encountered an unexpected "PRI" LED indication of 1756-RM Series B module. When the affected redundancy module is set to primary, the status of the "PRI" LED indicator is blinking red. On the other hand, it is set to a solid red when the RM is set as secondary. I have read the manual and there are only two expected behavior for the "PRI" LED indicator, green if it is set as the primary and off if it is secondary. Does someone encountered this scenario already?   P.S. The RM does not have any minor/major faults when accessed. The status indicator indicates "PRIM" when the affected module is set as primary and "SYNC" when set as secondary. Manual switchover between controllers are done and was successful. Thanks in advance! Regards, RIValencia
  4. Redundancy causes low speed

    Hi, I'm using a 1756-l61 in a redundant chasis. The redundancy is working properly, but when I try to be online using rslogix the connection speed is too low. i did some tests, trying to removing one controller and breaking the redundancy and the speed came back to normal speed connection. some one had this problem? if yes, could help me? thanks joao 
  5. ABB AC500 HA

    hi, i'm a beginner in automation,and i want to build a project with AC 500 HA for a redundancy application. for this reason i want an example  to help to find material that i need. thank's
  6. Hi, Good day to all,   I got a situation regarding the redundancy configuration. Please refer to the image attached (Page 26, Enhanced Redundancy User Manual). Notice the 1756 ControlLogix I/O inside the green box! The chassis hasn't got a CPU but only has an Ethernet IP module for the entire chassis. Does anyone know how to add and configure this chassis to the I/O configuration tree of RSLogix5K (Logix Designer 5k)? On my configuration, I've also inserted 2 MVI56E-MNETC Modbus TCP/IP Module in addition to the standard I/O Modules. Is my configuration possible? I appreciate any help I could get, thank you very much!   Sincerely, Andrei O. Karunungan