we are developing the 9axis cnc machine with the arnco ext library and also have a license for it. since there are only maximum 5 axis block in mpCNC (MpCnc5Axis) block, we are planning to use MpCncX (MpCncXFlex) block.
while simulating 9 axis project, after enabling the MpCncXFlex block, getting the error as -1064239103 but after ErrorReset the block is running fine, but the axis interpolation is not working properly. We have tested with the below code, At N03 axis A is not ending in sync with other axis.
Questions:
Is MpCncXFlex block is the correct block to use with arnc0 ext library or some other block needs to be used (any recommendation is welcome ).
You have 9 axis, but how many of the are planned to be in a transformation and are relevant to the kinematic?
E.g. you can use the 3/4/5 axis CNC and then use the other axis as slave axis.
You can just use your 3-axis CNC and also move the slave axes from within the CNC program.
If you really want to interpolate 9 axis, you’ll have to create your own user transformation, since there is no 9-axis kinematic I know of…
Secondly: Is it a “new” project? If yes, I’d switch to mappMotion since arnc0(Ext) is not “state of the art”.
Hello,
For new Projects i would strongly recommend to use MappMotion. ARNC0 is in a Feature Freeze State and should only be used for existing projects or if there is a good reason not to use MappMotion (for example missing or incompatible features or available Licences).
For ARNC0:
About your Question whether the MpCncFlex is the right Interface to use.
The MpCncFlex introduces some Homing-Features if a Transformation is used and reduces the programming effort in comparrisson to ncactions().
The MpCncFlex has no influence to the Movement which is generated by the PathPlanner.
For a CNC with 9 Axes you can use the MpCncFlex, it should not be an issue.
I currently have no standard issue in mind which creates this error you get.
I would recommend to disable the Task with the Mapp-Functionblock and test the behaviour with the ANRC0 Test-Window if the issue with axis A is still there.
If you want to go with ARNC0 and still you have the issue. We need the whole ARNC0 CNC Init-File Declaration to have a look at.