PanelView Plus terminals are specifically not supported in this kind of system because they cannot switch between IP address targets. You probably cannot easily solve the PanelView problem. If they work correctly and stay on when their connection is faulted, then the problem must be when they go back into RUN mode.Īlso remember that you must use a direct Module connection to each Input and Output module "Rack Optimized" connections to the FLEX adapter are not supported. Testing it is simple: set up a single-controller system with FLEX outputs configured to hold last state during a Fault, set some of them = ON, and unplug the CompactLogix. Remember that Program Mode and Fault Mode are separate settings for FLEX I/O. You are correct to be looking at the Fault Action configuration for the 1794 FLEX Output modules they should be able to be set for Hold Last State during a Fault condition. Support for those systems is only available through the local field sales office that approved you to use it. You can only get it from a Rockwell Automation sales office, and only if you are approved by them and their country manager and/or Commercial Engineering at RA.
The document and the accompanying "hot backup tool" code generation software is not publicly available. I am aware of a Application Technique document for High Availability CompactLogix that was last updated as version 4.0 about five years ago that used 1769-元0ER and 1794-AENTR products and architectures. There have been some attempts over the years to implement "hot backup" with ControlLogix and CompactLogix. However, you will also be unable to add any standard I/O modules to your project or have I/O addressed in your code and therefore you may also have to discuss this issue further with Rockwell to see if there is a better option in place.The only Studio 5000 family controllers that support real "Redundancy" are the 1756 ControlLogix, when equipped, configured, and programmed properly with the appropriate firmware, network modules, network architecture, and Redundancy Manager modules.
It has been shown that with one or more Ethernet-based drivers installed, requests return with CIP Error 0x5 Ext. NOTE: No Other Ethernet Drivers in RSLinx - For proper operation, no Ethernet-based drivers (Ethernet Devices, Remote Devices Via Gateway, etc) should be installed in RSLinx on the SoftLogix PC. The Device ID should be set to ", 1, ".įor example, if the PC's IP address is 192.168.3.4 and the SoftLogix CPU is in slot 2 of the virtual chassis, then the correct Device ID would be "192.168.3.4, 1, 2". In the General tab, locate the Device ID value. Verify that the Ethernet/IP Message Module is installed in the SoftLogix virtual chassis.
To connect the Allen-Bradley ControlLogix Ethernet Driver to a SoftLogix Soft PLC running on the same PC as the server, follow the instructions below.Įnsure that there are no Ethernet-based drivers currently running in RSLinx on the PC. Error 0x1 and CIP Error 0x8.Ĭonnecting to a SoftLogix Soft PLC on the Same PC as the OPC Server With one or more Ethernet-based drivers installed, requests will return with CIP Error 0x5 Ext. Pasted below are the Softlogix operating notes.įor proper operation, no Ethernet-based drivers (such as ethernet devices, remote devices via Gateway, and so forth) should be installed in RSLinx on the SoftLogix PC.
This is not a good option as it does not use the ControlLogix or SoftLogix driver.Ĭonsider using the SoftLogix driver instead This needs IGS to be set to Interactive mode and therefore cannot run as a service. The only way to connect with Rslogix Emulate 5000 to IGS is via a DDE client connection which means using the DDE client driver. RsLogix Emulator with the IGS driver needs a DDE client connection Request documentation on setting up the RsLogix Emulator with the IGS driver