ACOPOS and AC112 firmwares

Hi,

I’m not familiar this equipment and have a couple of questions

In a system with a X20 PLC + ACOPOS P3 for example as far as I know PLC sends the correct firmware version to the ACOPOS and modules and if I connect a different ACOPOS P3 the system doesn’t work, is this the same on a old ACOPOS system? I’ve seen old ACOPOS systems where let’s say a ACOPOS 1022 is replaced with a ACOPOS 1045 and the system works fine, is this the way it is supposed to work? does the PLC sends the correct firmware version to the AC112 module or the module needs to be updated in a different way? in a old ACOPOS system is there a difference if the PLC is a X20 or a 2005 PLC (CP360)?

Sorry if there are too many questions, thanks

Hi @Jose_Veliz,
Please Login on our website and download our training module TM400 Introduction to motion control (just search TM400 and you will find a link to that)

In a system with a X20 PLC + ACOPOS P3 for example as far as I know PLC sends the correct firmware version to the ACOPOS and modules and if I connect a different ACOPOS P3 the system doesn’t work, is this the same on a old ACOPOS system?

The same

I’ve seen old ACOPOS systems where let’s say a ACOPOS 1022 is replaced with a ACOPOS 1045 and the system works fine, is this the way it is supposed to work?

I have seen that too

does the PLC sends the correct firmware version to the AC112 module or the module needs to be updated in a different way?

in a old ACOPOS system is there a difference if the PLC is a X20 or a 2005 PLC (CP360)?

No
—————————————————————–
Example 1: Look at this prj (X20 CPU and ACOPOS P3) with mapp Motion:

Example 2: APC + ACOPOSmulti and mapp Motion:

Example 3: Standard ACOPOS with old ACP10

In all of them you see the operating system of the ACOPOS drives inside the prj, the PLC sends that to the drives via powerlink (CAN is no more supported, but in the past CAN was an alternative option for the communication with the drives).

Ciao
Valerio

2 Likes

Hi @Jose_Veliz, if the question is answered, please mark Valerio’s reply as a solution.

Hello,

i just wannt to add…

Powerlink
Please be aware that the AC112 is operating on Powerlink V1.
Whilst AC114 Classic ACOPOS; ACOPOS P3 and ACOPOSmulti operate on Powerlink V2.
Powerlink V1 and V2 can not be mixed. But both Version supported Firmware Download to the ACOPOS.

Replacing ACOPOS Moduls
It is still possible to exchange ACOPOS moduls from different Powerclasses and it will work. We have in the Hardware Tree so called Wild-Card Hardware Files with these xxx in Ordernumbers. These Wild-Cards can be used so see which Modules can be exchanged via each other and would work. Mainly it must be of same Type SingleAxis/MultiAxis, Safe/Nonsafe …



image

Even if you use a spezial Ordernumber Module in Hardware Tree these Module is same as its Wild-Card one. It improves only the Documentation of the Installed Module having the full Ordercode.

For ACOPOS classic there were no wild-cards but basicaly each Modul is as far as i know a wild-card for all other Modules. They were all SingleAxis, NonSafety - only different Powerclass.

The ACOPOS do all have a centralised Firmware on the PLC since the erly days.
Behavior of ACP10 was the same Independent of PLC-Type X20, 2005, 2003 (SG3/SG4)

Greetings
Michael

3 Likes

Thanks so much Michael for your clarification on the limitation of old AC112 powerlink card, it supports only V1 mode:
We upgraded a big machine last year and a last minute surprise was the powerlink card mounted on the panel didn’t support the old powerlink mode V1.
After that in our check list o the top we have “check Powerlink mode compatibility“

Second limitation of AC112: you can’t installed latest ACP10 version on that:
Few details I got from Support last year:
”when the customer has a machine which is using a combination of AC112 and AC114 then they need to use PLK V1 and need to stay on ACP10 V2.xx.x versions otherwise AC112 won’t work anymore. The latest version in the ACP10 V2.xx.x family is V2.52.8 indeed. This is “so far” away from V3.xx.x because we simply made a version jump with ACOPOS P3 to V3.xx.x Similar to the jump we made from ACP10 V3.18.2 to V5.xx.x and the jump we are going to make from V5.27.x to V6.xx.x”
Thanks
Ciao
Valerio

3 Likes