text: <s>[INST] CIP Motion + Drive Firmware Update = Extreme Aggravation Summary: Updating the firmware on a PF 755 drive used in CIP motion isn't worth the effort, but you HAVE to because of the bugs When you upgrade the firmware in a PF755 used in CIP motion in a Logix 5000 application, the drive definition in the IO tree also needs to be changed to match. However, when you do this, many parameters which you painstakingly set for perfect operation get wiped or reset to defaults. Your drive tuning values? Gone. The motor nameplate data that you entered? GONE. You're looking at about 15 minutes PER drive of careful parameter verification, IF you were smart enough to keep an old copy of the program with which to compare. This is not only irritating and stupid, it's the behavior of a saboteur. Rockwell, why on earth would you wipe out the motor nameplate data just because I changed the firmware revision level within the drive definition? Do any readers know of a way to simply transfer the parameters from an old program to a newer one to alleviate this problem? [/INST] It's a year later, and this is still a problem. I reused a program written last year, with drives at firmware 7.1. I had to upgrade the setting in the program, and it wiped out the same information. After going through that exercise, I discovered my shop had put encoder cards in a different slot than expected. That seems like a simple change in the software, right? Change the slot number on the pull-down? NOPE. Doing that causes Logix5000 to wipe your data. This nuclear option has to change, Rockwell. There is no good reason for this behavior. \\n </s>