VERICUT Users' Forum

Due to relentless spammers, we are no longer automatically accepting new forum registrations. If you wish to register for this forum, please send an e-mail to:

You are not logged in.

#1 2013-11-21 08:54:52

Senior Member
From: Eindhoven, Netherlands
Registered: 2005-01-17
Posts: 154

Machine specific part of a controller

With every new Vericut release, ootb controllers get updated. A good example is the Sinumerik 840D controller, through the years this has evolved into a real complete controller.
Unfortunately, all our (sin840D) machines have -besides the regular sin840D commands- also machine specific commands. Some with use of sub-programs but also different interpretations on regular/generic commands.
For this reason we cannot simply use the latest ootb controller, but we need to save -for each machine- a machine specific version of the controller.

Trying to update these existing -machine specific- versions of the controller to the latest ootb version is a nightmare, and therefore we usually don't.

It would be very useful if you could have a separate machine specific controller thing, overruling the regular/generic controller.
Vericut will use the generic controller, but only those commands specified in the machine-specific controller overrule the generic command.

Regular controller (sin840d) used for every sin840D machine

  • ...
    M6 = toolchange

Machine A specific

  • ...
    M6 = call sub program ...

Machine B specific

  • ...
    M6 = Error macro "Machine doesn't understand M6 command, For tool change use L6 instead"

This could be arranged in a separate controller file or in a new machine settings section -like the substitute section under Advanced Control Options-

Patrick Delisse
KMWE Aerospace
(Vericut V9.2.1, Siemens NX1980, Campost)


#2 2013-11-21 14:26:06

Senior Member
From: Trollhättan, Sweden
Registered: 2005-02-23
Posts: 60

Re: Machine specific part of a controller


This could have been my words.  smile

I have updated most of our milling and mill/turn-machines fitted with 840D, from 6.2.2 (with the old 840d-ctl with LOADS of home cooked solutions and control sub routines) to 7.2.1, with the latest 7.2.1 840d-ctl template + .def-file.
With the new 840d ctl-file as starting point, I have carefully added the machine specific things, one by one. This also has implied to reconsider/rebuild some old solutions since some of the actual functions are delivered ootb in the 7.2.1 ctl-file.

To sum up, the new 840d ctl (and def-file) is a great step forward!

But - now I will start with our Siemens 840d vertical lathe-machines. All with their old special solutions...

So - I think this is a great idea!

Svante Eriksson
System owner
GKN Aerospace Engine Systems Sweden
Vericut 7.2.1, 7.3.4, 7.4 - NX 9.0.3


#3 2013-11-25 00:16:29

Senior Member
From: U.S.
Registered: 2005-03-31
Posts: 351

Re: Machine specific part of a controller


Another thing CGTech is owing us is a CTL comparisson utility...

Not saying, just saying...  8)

Daniel Santos


#4 2013-11-26 13:28:43

VERICUT Specialist
From: Le Mans, France
Registered: 2004-10-14
Posts: 130

Re: Machine specific part of a controller

Just a little information which might help you guys update easier from version to version next time.
First start from library control. Then use the machine initialization file to add specific variables you will need for that machine, usually you can get those variables in GUDx.DEF files or any file under DEF.DIR folder of the machine ARC file.
Then in the same manner all specific machine subroutines, also found in machine ARC file CUS.DIR folder, can be added under machine stings in subroutines list...
This way next time you want to update the control you will keep anything specific to the machine' like tool change subroutine or any specific PROC
Note: In V73 help there will be a section in the help explaining this and how to start building a machine with a Siemens 840D control. Enjoy!



Board footer