For machines with Heidenhain TNC and iTNC controllers CNCnetPDM enables to acquire, monitor and write machine-, process- and quality-data in near real time. Seamless integration of the data with your business information systems as well as modification of parameters at these controllers is also supported.
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:
TNC 426 430 iTNC 530
Switch to programming mode and 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 the following 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.
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 remotely. 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 DNS-Hostname of your PC to the list.
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.
Note down the PLC Password and use it in HeidenhainData.
TNC 320, 620, 640
Switch to programming mode and click [MOD], a dialog opens. Here, expand section ‘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 adding machine parameter ‘CfgAccessControl’ with ‘denyAllConnections’ = FALSE.
Note: If Access Control is active at the device access from a remote PC has to be manually granted at the controller as soon as the remote PC connects. Set permission to ‘Always’ to avoid this procedure.
If the device is protected by a PLC Password or Code Number note it down and use it in HeidenhainData.
SOFTWARE DOWNLOAD
LICENSING
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 folder on your PC you can simply copy your CNCnetPDM.ini file to this directory.
SOFTWARE SETUP & USAGE (PC)
Download HeidenhainData.zip and extract HeidenhainData.exe 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 the TCP Port your controller uses (default 19000). You can use our tool Device Port Scanner to check if your controller is reachable via this port.
CNCnetPDM HEIDENHAIN MACHINE DATA
The program enables you to connect to your machine via Ethernet and query various machine data. Double click HeidenhainData.exe and enter the IP Address or DNS Hostname of your controller (1). If required enter the PLC Password (2) needed for the device. Next, click on button [Connect] (3). If a connection can be established the button changes to [Disconnect].
After clicking button [Query] (4) the program tries to acquire data.
FIG 2: CNCnetPDM Heidenhain Machine Data
If successful, the program shows machine data in the area at the right (5).
DEFAULT OUTPUT
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:
CONTROLLER INFORMATION
TNC type, NC and PLC version.
EXECUTION MODE
iTNC 530, TNC 320, 620, 640 and TNC7: You can see the current execution mode of the machine. Possible values are:
Manual(0)
MDI(1)
Pass References(2)
Single Step(3)
Automatic(4)
Undefined(5)
For older controllers (e.g. TNC 426 or 430) HeidenhainData reads this data from the PLC, possible values (either 0 or 1):
Manual
Handweel
MDI
Auto single
Auto full
Traversing
PROGRAM STATUS
iTNC 530, TNC 320, 620, 640 and TNC7: You get information about the program state, this may be one of the following:
Started(0)
Stopped(1)
Finished(2)
Cancelled(3)
Interrupted(4)
Error(5)
Error cleared(6)
Idle(7)
Undefined(8)
For older controllers (e.g. TNC 426 or 430) HeidenhainData outputs PLC data, possible values (either 0 or 1):
Running
Interrupted
Error
Stop Ext.
Stop Int.
Emerg. A
Emerg. B
Emerg. C
Finished
PROGRAM INFORMATION
iTNC 530, TNC 320, 620, 640 and TNC7: You get information about the currently selected and active NC program and the actual block number.
OVERRIDE INFORMATION
iTNC 530, TNC 320, 620, 640 and TNC7: Override information is output in percent for Feed, Speed and Rapid.
Axis information output depends on the number of available axes on your machine. The output unit may be metric or inch according to the setup of your controller. HeidenhainData outputs the number of axes and the ID, name and actual position of each axis.
CUTTER DATA
As with axis data information about cutters and their position depends on the number of available cutters on your machine. The output unit may again be metric or inch. The program outputs the number of cutters and the name and actual position of each cutter.
TOOL TABLE DATA
iTNC 530 only: HeidenhainData outputs the name of tool no. 1 stored at the tool table of the controller. File TOOL.T and data for tool no.1 has to exist in its default layout.
Note: An error output does not necessarily mean that you cannot read table data. You can adjust this in the CNCnetPDM device driver INI file.
PLC DATA
The program automatically detects the type of your controller and reads various PLC data values from their default location. Note: As Heidenhain devices are highly configurable by the machine manufacturer the addresses may have to be adjusted in the CNCnetPDM device driver INI file.
iTNC 530 and older:
Programmed Spindle Speed
Actual Spindle Speed
Programmed Feed Rate
Actual Feed Rate
Feed Override %
TNC 320, 620 and 640:
Actual Spindle Speed
Programmed Feed Rate
Actual Feed Rate
Spindle Load
Actual Tool Number
TROUBLESHOOTING
If HeidenhainData connects to your controller but you get blank output please check if ‘EXTERNAL ACCESS’ is set to ON at the device. If access control is enabled remote access may have to be granted at the device.
If you can ping the controller but HeidenhainData outputs an error when connecting please verify that there’s an exception for TCP 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 the machine manufacturer it may be that certain areas are locked or data is stored in areas different from the standard, especially PLC data. In this case HeidenhainData outputs TNC error numbers together with an error description.
If you get all data except PLC output make sure that you use the correct PLC (OEM) Password or code number.
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.
ADAPTED CONTROLLERS
Controller
NC Software Version
Major
Service Pack
iTNC 530
>= 340494
002
0
TNC 320
>= 340554
004
1
TNC 620
>= 340564
002
1
TNC 640
>= 340594
001
0
TNC7
>= 817625
016
0
DataPilot 4110 V6.4
>= 362834
005
1
DataPilot 4290 V7.1
>= 737133
002
0
DataPilot MP 620
>= 634132
003
1
DataPilot CP 620
>= 729665
001
1
DataPilot CP 640
>= 729666
001
0
TNC 426 CA/PA
>= 280460
TNC 426 CB/PB/M
TNC 430 CA/PA/M
TNC 426 CA/CE - PA/PE
TNC 426
>= 28058x
TNC 426 CB/PB
280470/471
TNC 430 CA/PA
280470/471
TNC 426 CB/PB
280472/473
TNC 430 CA/PA
280472/473
TNC 426 CB/PB
280470/471
TNC 430 CA/PA
280470/471
TNC 426 CB/PB
280472/473
TNC 430 CA/PA
280472/473
TNC 426 CB/PB/M
280474/475
TNC 430 CA/PA/M
280474/475
TNC 426 CB/PB/M
280476/477
TNC 430 CA/PA/M
280476/477
TNC 426 CB/PB/M
280474/475
TNC 430 CA/PA/M
280474/475
TNC 426 CB/PB/M
280476/477
TNC 430 CA/PA/M
280476/477
FIG 3: Adapted Heidenhain TNC and iTNC controllers
