Software Versions and Firmware Revisions - Revisited...
OK, here we go again...
What is so special about RSLogix v8.52?
Not only is it a Redundancy Release, but it was the first...
RSLogix 5000 version 8.x was released at:
v8.52.00 (Redundancy v8 Support Added)
v8.02.00 (Minor UDT Bug Fix)
v8.00.00 (Mainly Tag Handing Enhancements)
RSLogix 5000 v8.00.00 & v8.02.00 were released before ControlLogix Redundancy was first introduced. So they did not support Redundancy. ControlLogix Redundancy v8 was introduced for the Redundant 1756-L55Mxx controllers and version 8 was the first Redundancy release for these controllers.
Software versions and firmware revisions must be at v8.5x/r8.5x or higher to support ControlLogix Redundancy v8.
RSLogix 5000 v8.52.00 was the first software version to support Redundancy and was released in tandem with ControlLogix Redundancy v8.
Controller firmware revisions released at r8 included...
8.021
8.014
8.051red (First Redundancy Release)
8.009red (Redundancy Release - made available after r8.051)
8.009std (Standard Release)
8.002
At the time of its release, the minimum controller firmware revision required to use ControlLogix Redundancy v8 was "r8.051red" and this was also released in tandem with RSLogix 5000 v8.52.00. A later redundancy release was made available at the same revision number as the already in use standard firmware revision r8.009.
Note: When a controller is using "r8.009red" or "r8.051red" it is displayed as "8.90" or "8.51" in RSLogix 5000, dropping the one "0" or two "00". So "8.90" was actually released before "8.51" making it older, even though the number reads as if it is higher and newer. When viewing them in RSLogix 5000, this syntax makes it very difficult for users to decipher what the actual revision number is and which revisions are newer than which.
Software Versions v Firmware Revisions...
Byron said:
...I have a client with a Control Logic 5000 system from 2001 written in RSLOGIX5000 V.8.20...the software tells me because the firmware is old: v.8.2...it wants 8.20...
There is no RSLogix 5000 "V8.20". There is RSLogix 5000 "v8.02.00", but that is not the same.
There is controller firmware revision "r8.002", which is displayed as "8.20" in RSLogix 5000 Controller Properties, or any other dialog in RSLogix 5000 which refers to the controller firmware revision. So this controller appears to be using firmware revision r8.002 (8.20).
Any one of the three versions of RSLogix 5000 at v8 should be able to open and download a v8 project, or upload from a r8.20 controller.
Back to the installation issue...
7045 - Installation: Error 1393 Unknown Internal Error Filesystem was deactivated
Access Level: TechConnect
If you cannot access that Technote - it basically says there is a problem with installing the "RSLogix 5000 Documentation". Try reinstalling only this time deselect the documentation installation option before proceeding.
But...now the whole installation query...
Byron said:
...I'd love to have the older versions on the same laptop as v10-20, but I'm not sure it is do-able, so I am trying to install to another laptop.
On one computer, you can install one major revision each of RSLogix 5000 Enterprise Series v10-v20 and one pre v10 copy of RSLogix 5000.
Example:
RSLogix 5000 Enterprise Series v10 through v20 + RSLogix 5000 v8
Note: Pre v10 releases are referred to as "RSLogix 5000". v10-v20 releases are referred to as "RSLogix 5000 Enterprise Series".
The reason you can only install one copy of pre v10 software is that they were built as an updatable product. So if you had RSLogix 5000 v7 installed and you installed v8 it would upgrade v7 to v8. Both versions could not co-exist on the same computer.
That all changed at v10, and the "fun" began!
So how come v8 cannot co-exist with v7, but it can co-exist with v10-v20?
Because the old and new products are different software builds, an old copy can co-exist with one or more newer copies i.e. installing v10-v20 will not attempt to upgrade an existing pre v10 installation. They are not the same products at the build level.
Also, the pre v10 software opens differently to the v10-v20 software...
v10-v20 - Multiple versions installed:
If you open a v10-v20 copy of RSLogix 5000 Enterprise Series, using its main executable file, it will open at the version last used. If you then open an *.ACD project file of a different installed version, it will automatically load the correct RSLogix 5000 Enterprise Series version.
Pre v10 - One copy installed along with v10-v20:
If you have an installation such as the example above and you have a v10-v20 copy of RSLogix 5000 Enterprise Series open, again, it will load at whatever version was last used. If you then attempt to open a pre v10 *.ACD project file, such as v8, it will not open. You must open the specific "RSLogix 5000" executable file for the v8 installation. This can be found under the "Rockwell Software/RSLogix 5000" folder. You can then open the *.ACD file from within there. Likewise, if you attempt to open a v10-v20 *.ACD file from within v8, it will not open. You must use the RSLogix 5000 Enterprise Series executable.
Alternatively, for all versions, open projects by double-clicking on the *.ACD file itself and it should open the correct software version if it is installed.
You should not have to go another laptop to install RSLogix 5000 v8.52 separate to your newer versions. They can co-exist.
But having said all that...
While the above is possible, they are referring more to the software versions being allowed to exist on the same computer for offline programming. It does not take into account the potential differences in software dependency for communications and security features, etc.
Because RSLogix 5000 v8.52 is so old, it may not be compatible with the software environment you currently have your v10-v20 installations under. While it is supported under Windows XP Pro x86 (32-bit) SP1 or SP2,
NOT SP3, there are other considerations to be made...
RSLogix 5000 v8.52 is at Coordinated Product Release 6 (CPR6), so it does not support the newer FactoryTalk Services Platform (FTSP), which was introduced at FTSP v2.10 CPR9. It only supports FTSP's predecessor, FactoryTalk Automation Platform (FTAP), and only FTAP v1.8 CPR6 at the latest.
Also, RSLogix 5000 v8.52 CPR6 will only work with RSLinx Classic v2.43 CPR6 at the latest.
So it is possible that the current software environment is not conducive to a successful installation of v8.52. I would recommend you look at installing and running v8.52 and its compatible friends in a
VMware session running under Windows XP Pro SP2.
Then you have the already mentioned Activations to consider. Both RSLogix 5000 v8.52 and RSLinx Classic v2.43 use the older Master Disk Activation method. I would also recommend you contact Rockwell for assistance with that.
Regards
George
P.s. I've attached the splash screen for RSLogix 5000 v8.52, just for nostalgic reasons...