Compact/ControlLogix firmware upgrades

robw53

Member
Join Date
Nov 2009
Location
south yorks
Posts
515
Hi,

I'm currently putting together a schedule to bring all our compact and controllogix processors up to a standard firmware level, and then attack the PV+'s.

I currently have some new equipment that I standardised on V30 for Studio and V9.0 for FTVME, so that will be the level I will go for. I probably have around 30-40 processors or more to update the firmware on, and in some instances swap out the L32E's for L33-ER's. The current firmware varies from V19, V20.13, V20.03, a couple V21's V24 and V28.

I am seeking out advice or recommendations (even horror stories) on how this is best performed. I have been looking at the "comparability checker" on the RA site as each processor has multiple drives, HMI's, some motion, remote I/O etc and i want to make sure I don't get caught out with incompatibility issues. Many years ago I upgraded an L32E from V16 to V19 when V19 had been out a good 6 months, only to find the PV would lock up and do the strangest things. so this is something I want to avoid having happen.

Any input gratefully received.

Rob
 
If it were me and your not getting any problems, if it isn't broken, then don't try and fix it.

Yes it's lovely to have everything on the same firmware and only carry the one laptop or install the one VM, but you have to measure the risk v reward.

I speak from experience, that just leaving something alone that was working fine, would of avoided a lot of pain and downtime!
 
If you want to avoid problems, set everything up in the workshop and run a quick acceptance test before putting on the shop floor. Make it permanentish so you have a test bay ready to go in the future.

Things to look out for:
L33 is much faster to execute than a L32, so potentially timing issues.
V30 does something different with ethernet/IP from V19, so you may have to upgrade the panel at the same time. If you want to do a phased approach of processor first then hmi later, definitely test both scenarios in your test bench.

Enjoy that feeling of having the 4th S of the 5S methodology (Standardise) until next year when you buy equipment that comes with V31.

Is now a good time to point out that Windows 7 is out of extended support in 2 years time?
 

Similar Topics

Read and write the Tags direct using pycomm3 and LogixDriver. Just in case anybody wanted to know. Here's a sample: from pycomm3 import...
Replies
0
Views
776
I've recently replaced an 1756-L72 and 1756-ENBT with a 1756-L81E & 1756-ENBT2R on a ControLogix chasis. The machine ran fine for two days after...
Replies
5
Views
1,644
My new friend Ron Beaufort got me thinking about the issues with using OTL's in regards to a power cycle. While you can use a first scan bit...
Replies
10
Views
4,637
Ok guys so I'm trying to do some messaging between a 1756-L60M03Se Version 17 and a New compactlogix 1769-L36ERM Version 20. I tried to do some...
Replies
4
Views
2,681
Can someone help me understand in detail the differences and limitations between Ethernet IP on a Compact / Controllogix Controller and Ethernet...
Replies
2
Views
2,005
Back
Top Bottom