Hello,

with new firmwares you can be never in calm state in case of replace HW. Check this what I found:

Innovative CPU 319PN/DP firmw. 3.2

Check that section about compatibility with previous version 2.8...

Duris_I

Hello,

with new firmwares you can be never in calm state in case of replace HW. Check this what I found:

Innovative CPU 319PN/DP firmw. 3.2

Check that section about compatibility with previous version 2.8...

 Hello,

This is the first thing I checked.

I have this information, but thanks again ...

Yes, I agree that with such a replacement you can’t be 150% sure that everything will be super, but I want to believe it.

Have you had such cases? Maybe with your colleagues - with other PLCs.

Yeah, we faced a similar issue with S7-1511T. The program was developed and tested and running on 8 identical machines, since last two years. However this year when we commissioned four new machines they faced operational problems, specifically with the asynchronous instructions used in program, and some motion control instructions. Turned out that PLC's with FW>2.0 have them implemented in a different manner, causing the program to malfunction.

One difference is that we did not use the MMC flash transfer. We downloaded it via PG, got the warning of type mismatch, changed the CPU to current version in offline project, compiled and proceeded with download, but still ran into this problem. Later the code was optimized, to make it functional, and a separate version of project has to be stored and maintained for these four machines, even though they are all identical with exact same hardware. A job that ideally should require 1-day max of field service, expanded to 4-days of new bug fixes, code optimization and testing.

Hello,

Unreality

Yes, I agree that with such a replacement you can’t be 150% sure that everything will be super, but I want to believe it.

Have you had such cases? Maybe with your colleagues - with other PLCs. 

 eeeehm sry, I have my own rule which is due your question:

I don't want to believe to it, I strictly avoid to this. If really isn't any other way, I need reconfigure prj to new HW firmware and save more firmware copies of prj. In case of my prjs this is simple, for other manufacturer prj is horrible for most cases.