This highly configurable Heidenhain device driver for CNCnetPDM enables you to monitor machine-, process- and quality data from machines with Heidenhain TNC 426, 430, 320, 620, 640 and iTNC 530 controllers, see adapted controllers. It also allows to control devices by its ability to set or change PLC data values and/or machine parameters.
You can dynamically define your own set of items (up to 30 for reading and 5 for writing) that can be enabled and disabled on a per machine basis by an INI file that is automatically created with reasonable default values for each machine configured. This INI file also allows to define individual names for every tag.
For bidirectional communication between machines with Heidenhain controllers connected to CNCnetPDM and your applications you can use our free Open Source Client (C-Sharp)
Make sure that you have an Ethernet network connection between your PC and the machine and get data, use our HeidenhainData utility to do so.
Please also add an exception for TCP port 19000 to your Firewall.
This device driver requires the most recent version of CNCnetPDM and also works with a free license. However, in this mode output is limited to the OEE machine state of your device. With a valid license you are able to output the result of up to 30 queries per reading cycle, see licensing for details.
Download the Heidenhain driver and extract heidenhain.dll into the folder where you have CNCnetPDM installed.
Edit CNCnetPDM.ini and add a new device as described in the quick start guide point 7. If you already have an entry in section [RS232] for a machine with a Heidenhain controller you can simply copy and paste this line and change its content. Change the line as follows:
FIG 2: Configure Heidenhain device driver in CNCnetPDM.ini
For machines with Heidenhain controllers the following 2 parameters are important:
Right to the IP Address of the controller (here 192.168.1.212) enter number 19000 (=port)
Change the driver name to heidenhain.dll
Start CNCnetPDM, foreground program is sufficient (Start thread)
CNCnetPDM automatically copies the original heidenhain.dll and appends the machine number as configured in the INI file, e.g. heidenhain_1000.dll for machine number 1000.
In addition an INI file with the same name is automatically created by the device driver, e.g. heidenhain_1000.ini for your first machine.
Double click CNCnetControl, if your device number is 1000 and the device name is HEIDENHAIN #1 the output should be similar to the one below:
FIG 3: CNCnetControl (Heidenhain)
Here the machine (1) shows up as connected (2) which is good. On the right side (3) you see the acquired data:
The line starting with O contains items defined in the INI file of the device that should be output to section 1. If you didn’t change the INI file you get something like the following:
Every item has a tag name followed by its tag value. All names and values are delimited by pipe ‘|’ symbols. This allows CNCnetPDM to create a database record, MTConnect or OPC UA output for every item.
With an unmodified INI file the initial configured and activated items are:
Part counter value
OEE Device state (numeric)
OEE Device state (text)
Device mode (number)
Device mode (text)
Program state (number)
Program state (text)
Name of the selected program
Name of the active program (if any)
Actual block number
Error class (iTNC 530)
Error group (iTNC 530)
Error number (iTNC 530)
Error text (iTNC 530)
Tool number (iTNC 530)
Tool index (iTNC 530)
Tool axis (iTNC 530)
Tool length (iTNC 530)
Tool radius (iTNC 530)
Override feed %
Override speed %
Override rapid %
Position of axes
Position of cutter
A marker value from the PLC
A byte value from the PLC
A word value from the PLC
A dword value from the PLC
A machine parameter value (iTNC530)
A data value from the tool table (iTNC530)
Write marker value to the PLC
Write byte value to the PLC
Write word value to the PLC
Write dword value to the PLC
Write machine parameter value
FIG 4: Ids, names, description and initial activation state of items
This device driver enables to dynamically add, group, enable or disable items and change their names. The INI file automatically created by the device driver for every machine contains sections that allow you to control its behavior.
Section [GENERAL] contains information about global parameters used by the driver on startup.
Connection Delay (new in version 188.8.131.52) allows to specify a time period in milliseconds (0 - 5000) between connection to the controller and start of communication, default =0.
Commands defines the number of all commands you’d like to use for reading and writing, maximum value = 35.
No DNC Option (new in version 184.108.40.206) enables data acquisition from newer NCK based controllers that do NOT have DNC Option 18 activated: How-to instructions.
Legacy PLC allows to automatically convert PLC Byte, Word or DWord output from older controllers like TNC426 or TNC430 to a proper format. Please set Legacy PLC = 1 in case PLC output differs from the values you see at the controller.
PLC Password can be used to enter a PLC Password or Code Number if PLC access is restricted by a password or code number.
Legacy PLC and PLC Password are only needed if you use commands that access the PLC.
Section [MARKERS] contains addresses of PLC Markers that are automatically used to identify the operation mode and program state of your machine if the controller does not support high-level language commands to acquire this information. Typically used with older TNC426 and 430 controllers.
PLC Marker Command (new in version 220.127.116.11, default plcmarker) allows you to read markers from various PLC areas. This entry only has to be adjusted for data acquisition from controllers that do NOT have DNC Option 18 activated: How-to instructions.
Items for reading and writing are organized in numeric sections e.g. . Every section contains entries where you can define names, commands and parameters for a specific item.
Section identifier, numbers from 1 to 30 are queried when reading, 31 to 35 can be used for writing
If you set this to 0 the command is not executed to read data from the device. This setting has no effect on commands for writing
A short name (max 5 characters) to describe the item e.g. STATN for status number
A comment that describes the command (optional)
Command to be executed e.g. cnc_oeestatus for the command group that contains running status. To change a command select an available command, copy it and paste it into the INI file.
Input parameter 1
For some commands input parameters can be used to set an input parameter (PLC), control output formatting e.g. program name with or without path or a divisor for an output value, see the command description.
Input parameter 2
Necessary for some commands, usually an optional divisor for PLC output (default = -1)
Some commands have sub-commands that enable you to define a specific item to be output by the driver e.g. statenumber from cnc_oeestate outputs the device state.
You can output data to 3 sections that may contain up to 256 characters. 1 goes to section ‘O’, 2 to ‘A’ and 3 to ‘F’. If data in one section exceeds the maximum length you can send items to a different section. Make sure you have entries CollectOrders, CollectFeeder and CollectQuality enabled (=1) in CNCnetPDM.ini.
FIG 5: Description of a device INI file section
Note: To change commands, switch items on or off or alter its name while CNCnetPDM is running open the device INI file with a text editor, make the desired changes and save the file. To apply the changes immediately you can click on the machine in CNCnetControl on the left side followed by clicking buttons ‘Close’ and ‘Open’ above the section ‘Devices’.
Below you can find commands and output items that can be used with this driver.
Note: Items with note ‘iTNC530’ are only supported by iTNC 530 controls. Please do not set them to active for newer controllers like TNC 320, 620 and 640.
For TNC 426 and 430 most items can be acquired by using plcmarker, plcbyte, plcword or plcdword commands. Please contact us for detailed instructions.
Numeric OEE state of the device (2 = producing, 3 = manual, 4 = interrupted, 5 = error)
State of the device as text (producing, manual, interrupted, error)
Numeric running mode of the controller (0 = Manual, 1 = MDI, 2 = Pass Reference, 3 = Single Step, 4 = Automatic, 5 = Undefined)
Reads a machine parameter e.g. 3515. ‘Input parameter 1’ defines the parameter to be read.
Output item = item to be queried (iTNC 530). In this example a value from the tool table is read
Command for writing PLC marker values (0 or 1). PLC address and value to be written have to be contained in the command from your application
Command for writing PLC byte values, PLC address and value from your application.
Command for writing PLC word values, PLC address and value from your application. PLC address has to be divisible by 2!
Command for writing PLC dword values, PLC address and value from your application. PLC address has to be divisible by 4!
Write value for a machine parameter to the device. Machine parameter name, desired value and flag have to be contained in the input command
FIG 6: Description of available command groups and output items
To quickly test and build a working INI file for your controller you can use our tool devicedrivertester. If used with this driver the program creates INI file heidenhain.ini. To use this file for a machine defined in CNCnetPDM.ini you can simply append an underscore and the machine number e.g. heidenhain_1001.ini for device number 1001.
If you want to add additional items (up to 35 in total) first adjust the number of commands in section [GENERAL]. Then, copy and paste a complete INI file section and adjust the section number and its content.
TEST WRITING OPERATIONS
It is highly recommended to test any writing operation to Heidenhain controllers before using them in a production environment with the device driver. For verification that you can access and write PLC data or machine parameters you should first use the GUI tool Heidenhain PLCRW. To test with the device driver proceed as follows:
In CNCnetControl select the device at the left side
After clicking on button [Cmd], an additional dialog opens.
Select the command number followed by 3 items delimited by pipe symbols ‘|’. If you’re using the standard device INI file you can enter:
Sets Marker value at address 1 to 1
Sets Byte value at address 1 to 1
Sets Word value at address 1 to 1
Sets Dword value at address 24 to 1
Sets parameter value of parameter 3515 to 5001
FIG 7: Format of writing commands
The first item in input is the PLC address or machine parameter followed by the desired value and a flag. Flag only has an effect on machine parameters. Possible values: 0 = persistent, 1 = temporary, 2 = persistent on reset.
To verify the result you can either define sections to read these values in your machine INI file or check with Heidenhain PLCRW.
The device driver writes a log file entry for any communication issue to the log file of the device. The file can be found in subdirectory \log of your CNCnetPDM program folder. The file format for the log file is log_ + device number + _ + date.txt. Please check this file first if you observe an issue. Deactivate commands with issues by setting them to ‘Active = 0’.
If the machine shows a red icon, state disconnected and you get just output E = 0 the machine is not reachable at all. This has nothing to do with CNCnetPDM, it’s a network issue, DNS Hostname or IP Address is wrong.
If the machine shows a green icon, state connected but you just get output E = 1 the machine is reachable but the controller does not respond to commands, check your controller setup and the parameters used in CNCnetPDM.ini (esp. port number).Please use the tool HeidenhainData to check if the machine replies to commands.
If you get numeric device states but not any of the preconfigured items please make sure that entries CollectOrders, CollectQuality and CollectFeeder are set to 1 in section [General] of CNCnetPDM.ini.
If specific items are not acquired check first with HeidenhainData that you get output. Also make sure that the numeric section of the item in the device drivers INI file is activated and has an entry for ‘Name’, inactive or items with empty names are not acquired. Also check that you didn’t misspell entries for command and output item in your device driver INI file.
In case you experience problems with other programs that interact with the controller (like tool control software) while CNCnetPDM is running please make sure that you do not use any command that accesses the machine’s PLC for reading or writing. Heidenhain does not permit simultaneous access to the PLC by more than one external program!
If you already have a previous version of the driver installed and would like to upgrade to the most recent version proceed as follows:
Stop any CNCnetPDM background service or foreground program that uses the device driver.
Extract heidenhain.dll from heidenhain_dll.zip into the folder where you have CNCnetPDM installed, overwrite the existing file.
Delete ALL heidenhain_NNNN.dll (NNNN = machine number) files.
If you already have created adapted INI files for specific devices do NOT delete the heidenhain_NNNN.ini files.
After restarting CNCnetPDM upgraded device driver versions for all machines are automatically created.