All libraries and configurations are present (checked several times against AS 4.12 projects), but McAcpDrv does not recognize the axis as configured.
MpAxisBasic reports no error until the PowerOn command is executed, at which point a timeout error occurs.
Do you have any hints or experience with what the issue might be?
Thank you
Best regards
Michal Malek
Since the logger says no modules are configured, either this is missing or you didn’t even add any hardware modules at all?
Also, side note: With the config system you can create several axis objects in the same file, no need to have a separate one for each axis (unlike with ACP10, where you had one axis init and parameter table for each axis)
Hi Michael,
I forgot to mention that the axis is referenced to a pure virtual axis
and therefore, in my understanding, it should not be recognized by McAcpDrv as not configured.
Moreover, once the axis is configured, it should not have an empty structure—especially since the other axes do not have empty structures.
Michal Malek
Yes, you are right. The original concept is based on a single virtual axis. There are two other configurations (.axis, .purevaxcfg, and .limitset files) that contain no axes but can be used in the main axis configuration (by using MC_BR_ProcessConfig).
So the application starts with the initial configuration, and there is no reason for any McAcpDrv issues.
At the same time, it doesn’t matter whether the other two configurations have an empty axis element, but they must both be empty—one cannot be empty while the other is not.
At this point please reduce your project by anything not related to this issue and provide it here since it’s pure guesswork going by the info provided (code >> some human trying to describe an issue) and the provided info is sometimes contradictory (having an empty element mpAxis01b but showing the config for mpAxis01, etc…)
Hi @Michal_Malek, have you solved your issue? If not, you will probably need to contact local support and provide them with the project, so they can drill deeper into it and investigate what is wrong there.
Hi Michael,
Sorry for the confusion caused by including information that is not fully related to this issue. Nevertheless, reducing the configuration to a single axis leads to the same behavior.
Once again, I am using a purely virtual axis:
This setup is the same as I was familiar with in AS 4.12.
Even though the axis initialization completes, the warning -2134830183 still occurs at the end.
Best regards
Michal Malek
And once more I am asking for a project where this is happening (reduced by everything irrelevant to the issue, so basically nothing top secret should be left anyway).
I have created a new project with one PurVAx package myself and can’t reproduce it.
I do not want to operate purely on screenshots when the missing bit could be anywhere not shown…
The Project was i think correctly exported. But then the Logical-Folder of the Project was removed. (Possibly due to the point that community is puplic and it was not intended to share)
Anyway, the reconstruction of the logical view and the removal of all related stuff in configuration view is not a nice challange, if this is not stated by the sender.
The repaired project is to large to share due to the library folder in logical view, so i will currently not share it again.
Axis-Object
The Thread was started to discuss a situation with accessing Axes Elements via the Axis-Objects given in the Program.
The Provided Project now only contains 1 axis , in opsite to the first discussed 3 axis.
Additionaly the Task was also deletet as it was obviously in the Logical View.
I created a new one to have the nessesary Variables.
The only points i have to point out is, that there are Variables double used (red), Acp/Axis Structure mixed in unexpected way (green) and “::” missing ahed of Variable (blue)
If there are still questions about the usage and initialisation of Axis-Objekts in Variables, please provide a better description of your issue. We can only help if we understand the issue occuring.
This Warning is not related to motion. It has its source in mapp View and is telling you that there was used a special kind of Certificated “SelfSigned”
As it is only a Warning it does not mean that a function is not working. It is more about
the security topic of how another could accept this certificate or not.
If you have more questions about the Certificates it might be goot to have a new Thread as the Headline of this one is more about motion.
Sorry Michael, I was asked to reduce the project to only the relevant (single) components, so I narrowed it down to an axis configuration issue. As I mentioned, there is a warning -2140330224 (-2134830183 was copied by mistake) at the very beginning of the configuration process that states: “No ACOPOS axis is configured.”
This warning is the only clue I have regarding the non-functional mappMotion behavior (the Power command results in a timeout). Therefore, I need to eliminate this warning.
In my view, the remaining parts (I/O configuration, tasks, axis configurations without a referenced axis, etc.) are irrelevant, because they come into play long after this warning is generated. Moreover, in this reduced form, the project works fully in AS 4.12.
Reagrads
Michal Malek
I think the reduction of the software was ment to a state were the issue is still in the project occuring. If you strap it down to much it does not help in explanation of issue.
Just consider next time, not an issue for this time.
ok, so if it was a copy error we continue with the warning -2140330224
This warning states that no ACOPOS-Servo Drive and no ACOPOStrak Segment is in use, and the McAcpDrv-Library does not continue operation.
This is completly fine because you do not have a ACOPOS-Servo or Track-Segment in your Hardware Tree.
There are various ACP-Inverter Modules which would be operated by a different Library
P66 uses as far as i know the McDS402Ax
P77 will get a new Library and full software support with mappMotion 6.6 and a new Library (you local B&R office can be a contact to discuss if there are preRelease Versions available)
But this inverters are all Disabled or not connected in the current Project.
Was the inital issue related to a situation were different axis types were used or were all Axis-Objects of the same kind?
If you have a logging of the inital issue you can also upload a Motion-Logger so we can have a look in whole Data and not only a Picture.
Just another side question, after looking a bit more in detail to the Project, you already have a X20SLX806-1 which is for Safety+ in you hardware Tree. So you must have a good contact to you local B&R just to support this. Can’t they help you with Motion eighter, just thinking a local contact would be easyer to explan, not replacing community as a whole?
Agree with @michael.bertsch, we have reached the limit of how the Community can help you. This problem needs investigation by the local support team. Please provide them with the complete project as well as a link to this discussion. Would be great if you update us with your findings, please.
