Version 188.8.131.52: For Heidenhain TNC and iTNC controllers CNCnetPDM enables you to acquire, monitor and write machine-, process- and quality-data. Seamless integration of the data with your business information systems as well as modification of parameters at these controllers is also supported by CNCnetPDM.
This document describes setup and test of data acquisition from Heidenhain TNC 426, 430, 320, 620, 640 and iTNC 530 controllers.
To avoid that you cannot access the controller or get login errors you first have to make sure that external access is enabled in general.
To do so switch to programming mode click [MOD]. If a dialog opens, select ‘Machine settings -> External access’ and check if soft key ‘External access’ at the bottom is set to ‘Yes’. If the soft key is not shown you can make it visible by inserting or uncommenting entry in file OEM.SYS:
REMOTE.LOCKSOFTKEYVISIBLE = YES
This file can be accessed from your PC with Heidenhain TNCRemo (free). After connecting to your controller type in ‘PLC:\’ into the lower Explorer Bar. Enter the key for PLC Access (default: 807667). Then open, edit and transmit file OEM.SYS back to the device. TOP.
It also may be that external access is restricted by specific settings in file TNC.SYS in the root directory of your controller. Access it by typing in ‘TNC:\’ into the lower Explorer Bar of TNCRemo.
In this case TNC.SYS contains one or more entries like:
If there is an entry for TNCPASSWORD and none for TNCPRIVATEPATH the whole TNC drive is password protected and cannot be accessed by CNCnetPDM. Comment out all lines starting with REMOTE. or the line with TNCPASSWORD by prepending a semicolon ‘;’ to get access. If entry PERMISSION is present, you can also add the name of your PC to the list. TOP.
You have to check file TNC.SYS if you see errors like: LOGIN: Area INSPECT Unexpected response from device (TNC = Access denied (LSV 2)).
If you get output from the controller but for some items you see errors like: LOGIN: Area PLCDEBUG Unexpected response from device (TNC = Access denied (LSV 2)) then access to the controller’s PLC is locked. Open file OEM.SYS.
Comment out PLCPASSWORD by prepending a semicolon ‘;’ and set
REMOTE.PLCPASSWORDNEEDED = NO REMOTE.PLCPASSWORDFORCED = NO
Save the file and transfer it back to the controller. TOP.
Make sure that your controller is connected via Ethernet to your company network and you get a reply when you ping the controller from your PC by using it’s IP Address. (Open an elevated command prompt and type in ping IP Address of the device e.g. ping 192.168.1.100). TOP.
If you have installed CNCnetPDM on your PC with a license other than a ‘free license’ and run this program from the folder where CNCnetPDM is installed you get unlimited output. Otherwise the program outputs a restricted set of items. Please see licensing for details or contact us if you have any questions.
Note: If you like to run this program from a different location on your PC you can simply copy your CNCnetPDM.ini file to this directory.TOP
SOFTWARE SETUP & USAGE (PC)
Download HeidenhainData.zip and extract all files to a folder on your PC.
In case you use a firewall at your PC or your company network please make sure that there is an exception for TCP Port 19000. You can use our tool Device Port Scanner to check if your controller is reachable via port 19000..
CNCnetPDM HEIDENHAIN MACHINE DATA
The program enables you to connect to your controller via Ethernet and query various machine data. Double click HeidenhainData.exe and enter the IP Address or DNS Hostname of your controller (1).
After clicking button [Query] (2) the program tries to connect to your controller, you see message ‘Connecting…’ above button [Help].
FIG 1: CNCnetPDM Heidenhain Machine Data
If successful, the program shows machine data in the area at the right (3). TOP.
Initially HeidenhainData queries data that is known to be output by most adapted controllers. At the top of the output area you can see information returned by your controller:
TNC type, NC and PLC version.
iTNC 530 and newer: You get information about the currently selected program and the actual block number.
iTNC 530 and newer: You can see the current execution mode of the machine. Possible values are:
For older controllers (e.g. TNC 426 or 430) HeidenhainData reads this data from the PLC, possible values (either 0 or 1):
If you have a Heidenhein iTNC 530 controller or newer (e.g. TNC 320, 620 or 640) and activate checkbox ‘Heidenhain iTNC 530’ (4) before querying data you get additional information:
(requires NC software >= 34049x SP 04!):
TOOL TABLE DATA
Here HeidenhainData outputs data for Tool No. 1 stored at the tool table of the controller. Note: file TOOL.T and data for tool No.1 has to exist. TOP.
If you can ping the controller but still get a ‘Connection to IP Address port 19000: Failed!’ please verify that there’s an exception for port 19000 in your firewall. Use our tool Device Port Scanner to check that your controller is reachable via that port.
As Heidenhain controllers are highly customizable by your machine manufacturer it may be that certain areas are locked or data is stored on areas different from the standard, especially PLC data.
In this case HeidenhainData outputs TNC error numbers together with program error numbers.
If you get errors you can click on button [Copy], paste the output into a text file or e mail and send it to our developers for further analysis when contacting support. TOP.