Replacing ACOPOSmicro with ACOPOS P3

Hello!
We have a repetition of the machine, with same application as before. In the HW we had to change ACOPOS from micro (80VD100PS.C00X-01 - not available anymore) to P3 (8EI8X8MWS10.xxxx-1). Basic application was done on AR K4.34/5.24.1, for new one I use AR C4.90/ACP10 5.12.2. I use the same files from old project: .apt (parameter table), .ax (init parameter table). In ACP10map.ncm is changed only HW according to the new ACOPOS, the rest is the same (links to .apt and .ax files).
After downloading I receive following errors:
29294: ( Unable to determine error text)
32088: (INIT param table is specified but missing…) - but it exists in the project…
30027 as warning in the logger: (means firmware cannot be loaded - probably due to missing FW file…)

I need help to solve this… I’ve been thinking to change everything to mappMotion but I am not sure if I will have to change then also Safety and Visualization. That would be a lot of additional work…

regards, Matjaz

Hi,

29294 is likely the same cause of 32088: It does not find or can’t parse the init param table. Firmware is the ACP10 itself and sounds like it affects another module of the HW.

Using the network command trace could help, I know it shows stuff like that.

Regarding your init file: “Exists in the project” does not necessarily mean “exists on the PLC” - so I would check the software configuration.
If that’s not the case, I have another suspicion: Often enough after changing ACP10 versions, the Init and Parameter tables are not automatically adjusted / versioned. I would recommend inserting a new init parameter table and compare it with your’s - assuming there are major differences which just prevent it from being processed properly.
Either adjust yours or take the settings of yours into the new one and use that.

One of those two usually lead to success.
If not please let me/us know.

In addition: if you are on a mapp Version < 5.25 (not entirely sure, could be 5.26), all mapp components have to match version (first two groups of the number). That means you can change to mappMotion if you use still use Safety Release instead of mappSafety or use the same version for both AND if you either use VC4 OR mappView with the same version as the mappMotion you are going to use.

So working:

mappMotion 5.25.x
mappSafety 5.25.x
mappView 5.25.x

(same goes for other versions 5.24.x, 5.23.x … whatever you are using)

or

mappMotion 5.25.x
Safety Release 1.10
Visual Components 4.95.x

(disregard the versions of non mapp components above, they’re random examples)

All mapp components exist with the same versions, thus aligning them should not be an issue.

Best regards
Michael

You need to assign the errtxt, apt and the init file in your .sw file.
Regards Walde

Creating new parameter table helped. I rewrite old params to new one (which it seems is slightly different) and overcome this problem.

Hi,

thanks for the feedback.

BR