Hello everyone,
I have the following problem with a machine. When the machine is started for the first time (main switch on), the axes do not initialise.
After rebooting the CPU everything works normally. Does anyone have any idea what the problem might be? An Apc10 Config and MpAxisbasic Init files are used. (Unfortunately I don’t quite understand why both are used). CPU: 5PPC2100-BY22-000 + AcoposMulti
Kind regards, Michael
Hello @Michael_Pilgrim,
MpAxisBasic in ACP10 is likely an add-on. The ACP10cfg.ncc is necessary for the ACP10 manager, where the Powerlink interface of the axis is defined and also the start-up behaviour of the axis and mostly the setting of “Network initialisation” causes the described behaviour, which is described in the Online Help at https://help.br-automation.com/#/de/4/ncsoftware/acp10/nc_config.html
If the axis has an error and the network initialisation is not done automatically, you would have to do a reset the axis as first by the application.
I would recommend that you set the "Automatic reset” to true.
If this is still not working, could you please check the logger (probably the ACP10 manager reported an error during initialisation) and share it?
In the MpAxisConfiguration you are able to select, if the init parameter module is used or directly the MpAxisBasicConfiguration, which is a little bit easier to configure (e.g. the scaling of the axis).
If the MpAxisBasicConfiguration is used this is transferred to the axis after enabling the MpAxiBasic function block, before the init parameter module would be used.
br Christoph
Thank you for your reply.
Unfortunately, I cannot find the values to be set for the following errors.
These errors only occur when the machine is started for the first time.
Hi @Michael_Pilgrim ,
you have the same issue on multi axes, so just focus on one.
In the configuration view you set those limits:
Open mapp Cockpit and check which value you have for positive and negative acc/dec limits:
Open drive log and filter the entries only for that axis and pos/neg acc/dec limits:
You should have the same limits configured inside Automation Studio in the configuration view, if not you are using function block/s to change them at runtime.
ops you are using ACP10 and not mapp Motion, but the issue is the same.
In the configuration view you configure the axis limits (you have 2 options for the Axis Configuration: “Enabled“ or “Init Table“):
In your case I see you use mpAxisBasic; Do you use MpAxisBasicConfig too?
If yes check the structure:
Check in the network command trace the entries for ax acc/dec limits and see when you set the value to zero
I made a small prj with no mapp (just an example where ax limits are defined in the init parameter table, the case when in the configuration view for your Axis Configuration you select “Init table“):
When you open ax test window, you see acc/dec limits in the acp10axis structure:
regarding network command trace:
Thanks
Ciao
Valerio
