As you can deduct from my questions, I’m pretty new to B&R world.
One of our servo drive’s (part # 80VD100PD.C000-14) power supplies (part # 80PS080X3.10-01) went bad. The replacement part is the same part # but different revision. Do I need to update the rev # or other parameters anywhere or it’s a plug and play replacement? Is it a difference if the replacement has an earlier rev# than the replaced part vs. a later rev#?
Same questions if the servo drive would go bad and needs to be replaced.
as long as the product code is identical and only the revision number is different, the hardware can be replaced without the need to change software.
In extremely rare cases, it could be that a automatic firmware downgrade (if the firmware on the replacement module is higher than the firmware used in the project) cannot be processed by the PLC, but I’m not aware about that with the named modules (and normally it’s even no problem if a firmware downgrade cannot be executed, the modules are still working).
If you want to see what are the differences between revisions, you need a customer login to the B&R website. With this login, you can check the revision history of a hardware module to get some more information about the changes.
Thank you for the answer! In these rare cases, how can you manually downgrade/change the firmware? Can you connect directly to the device and do it or you need to change the firmware version in the physical view tab of the project file (Automation Studio) and then transferring to the target?
yes, firmware version are setup in the projects physical view - this firmware files are transferred to the PLC via project transfer, and the PLC checks at every bootup the consistency between the project and the module firmware and automatically up- or downgrade them if needed.
In those very rare cases I meant, a downgrade to versions lower than a minimum version isn’t allowed and possible at all, the module itself prohibits the download to avoid issues because of hardware incompatibilities with too old firmware (that means, that you even don’t need to change the project in such a case).
I personally can only remember that many years ago it was needed to avoid a downgrade of a very old firmware version to one or two IO slices, but even the newer firmware functions were kept compatible to the older ones.
Thank you for the clarification. One more question came up - if the replacement module has different firmware, what’s the right way to handle it - let the PLC up/ downgrade the new device at bootup or update the project file with the new device’s firmware and transfer to the PLC?