I'm just starting to use Machine Configurator, and I need to create my own MCF and CCF files for Heidenhain iTNC 530, it is impossible to use files from the samples, as my machine differences from the default ones. But I don't have enough information how to do it. Is there any literature about Machine Configurator, ini-files, DLL-files?
I think these movies are best place to start with:
Probably you can find also more up to date materials, but those from NX7.5 cover most informations.
What exactly is the problem?
Why do you need to create your own CCF? I find CCF for iTNC very reliable.
Which NX version do you use?
For what kind of machine you are developing ISV?
You cannot create your own CCF files, since they are provided as is by Siemens exclusively.
You can add changes to the MCF file to suite your needs.
The MCF file inherits the CCF file and you can overwrite nearly everything in the MCF file.
Production: NX10.0.3, VERICUT 8.1, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 10.1
Development: VB.NET, Tcl/Tk Testing: NX12.0 Preparing: NX12.0
Employees of the customers, together we are strong
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide
I can't agree with your first sentence. I made my own CCFs several times.
Obviously we can discuss which approach is better, but technically it is possible.
I'm so glad that you determined to help me. So there is the problem:
I'm developing 5 axis mill machine, kinematic type is "P",
rotational axis are "A" and "B".
I'm using NX 188.8.131.52. There is no
machine in the library, that has the same kinematic as my does. So I have
made my own MCF, copied HeidenhainTNC.CCF and Basic.CCF from sim08_mill_5ax
and added them to my MCF.
And when I try to simulate my NC code I get the next
In spite of the errors, it works.
but when the next NC code: "5 CYCL DEF 7.3 Z-523.0" is executed, I get error
Here simulation stops.
That why I made a decision to create my own CCF. And I just copy methods
I think I need and delete commands that cause errors. But I'm not sure that
this is the correct way.
And I have question about transformations. For example GMe_ActivateToolCorrection
uses "$TOOL" transformation. But it is not included in the transformations list.
Is there any list of default transformations or I should creat my own transformation
and describe them in the body of the methods?
Thanks for participating!
It has to be working. I made ISV kit for Grob machine (AB rotary axes) with iTNC controller. Also for NX9.
I don't have Machine Configurator up and running at this moment, but all you have to is:
- fill correctly all parameters in "Internal Variables" tab - especially rotary axis versors and names.
- make sure if axes are configured correctly in Machine Tool Builder in NX, also in "Channel Configuration"
And with NX9 I think I had this "getJointNumber" error. I usually solved it the brute way:
- by editing "CSEInitializeChannel". There were some conditions for each rotary axis (A, B, C) and I simply removed one which is not needed for my machine. It usually fixed problems, so I was not looking for any nicer solution.
I think $TOOL is the only one "invisible" transformation. It is always on first place on transformations list.
I may be wrong in some of this points, because it is what I remember. I didn't checked it.
Instead of doing things this way:
"That why I made a decision to create my own CCF. And I just copy methods
I think I need and delete commands that cause errors."
I use to do it this way:
- if I need to override some command or method, I simply copy it to my MCF (if it is allowed) and modify. If it is not allowed (marked with red icon), I create command/method with the same name in my MCF - it replaces it's implementation in CCF.