Licensing Violation 1TGACP0000.00-01 - Explicit list?

Ask Questions Mechatronics & Motion
1

Hi Community,

I’m involved in a project using a single ACOPOS P3 3-axis drive. There is a licensing violation in the logger specifying the need for 1TGACP0000.00-01 license. Is there an explicit list of all of the technologies that would trigger this?

  • The following list is on the page for the license 1TGACP0000.00-01 | B&R Industrial Automation:

    Virtual axis

  • Closed-loop control of elastic systems

  • Pitch error and backlash compensation

  • Repetitive control

  • ISQ ripple identification

  • ACOPOS reACTION

  • SafeMOTION with motors from 3rd-party vendors

  • …

Is there an explicit list with everything? Nothing on that list is currently being used in the project to the best of my knowledge.

Things in the project that may be triggering this licensing violation:

  • The project uses mappWinder through mappControl, but the project is ACP10, so the technology package is not linked directly to the drives.
  • One of the axes uses MC_CamIn to cam to another of the axes through a cam profile made in the AS cam editor.
  • The other two axes are velocity-controlled cyclically using MC_BR_MoveCyclicVelocity
  • MC_BR_CyclicWrite, MC_BR_CyclicRead FBs used

I assume it is the MC_CamIn usage since mappMotion premium references the ability to couple axes, but I cannot find it documented for ACP10.

Best,

Isaac Bean

2

small note just to update the Community,
we reviewed internally with application team the issue and Isaac found one ACOPOS Parameter table that explain the cause of licensing violation:

image

at the moment it’s not clear why we have that instance of ACOPOS FUB in the prj, Isaac is waiting feedback from the customer.
I found one document regarding ACOPOS P3 Technology Guarding from L2 with more details

image
image722×170 32.5 KB

===========================================
Few examples of licensing violation messages in the logger:

image
image1910×281 132 KB

image
image757×591 110 KB

===========================================
In general we don’t use SPT in all applications, If someone is interesting we have a training module: TM471 ACOPOS function blocks (make sure you are logged in to our website)

Ciao
Valerio

3

So am I right that this is application “issue”? so message is clear, you have to only figure out why FUB is used in the project. So from Community point of view nothing to investigate?

4

Hi Jaroslav,
the original confusion was in particular related to “reACTION” message in the logger because they don’t have reACTION technology in the prj.
When I found the document “ACOPOS P3 Technology Guarding” from L2 everything was more clear.
We are waiting a feedback from the customer to understand all pieces of the puzzle, but as you said the licensing violation message in the logger was correct.
I think there is no additional action assigned to the Community.
Thanks
Ciao
Valerio

5

Thanks for writing up the solution and your help in diagnosing the issue Valerio! The customer got back, and the SPT FUB creation was the cause of the warning. I also did not know the exact reason was specified in the logger as I was sent a screenshot of just the initial part of the warning specifying the license needed. This is also the first instance I have seen SPT referred to as reACTION, but I am no SPT pro and would not have figured this out without the L2 documentation denoting SPT and specifying PAR ID 777