Heidenhain TNC monitoring in Scout MES reads data from the iTNC 530, TNC 620 and TNC 640 controls over your factory LAN.
iTNC 530
- mode
- program status
- program name
- feed rate
- feed and spindle override
- spindle speed
- tool
- alarms with number and text
- PLC memory
Other data (e.g. part count) is determined during deployment.
TNC 620 and TNC 640
- mode
- status
- feed rate
- override
- spindle speed
- tool number
- PLC memory
Other data (e.g. part count) is determined during deployment.
How the connection works
Scout reads the data over your factory LAN, directly from the control, with no electrical modifications. The machine does not need internet access: SCT (Scout Configuration Tool) runs as Windows services on a computer in your network and sends the data to the Scout server over HTTPS, so you do not need to open any inbound ports. We install and configure SCT remotely. You prepare a Windows computer in the LAN and send us the list of machines (control type and IP address). Scout only reads data. It does not control machine motion.
Frequently asked questions
iTNC 530, TNC 620 and TNC 640.
iTNC 530: mode, program status and name, feed rate, feed and spindle override, spindle speed, tool, alarms with number and text, and PLC memory. TNC 620 and TNC 640: mode, status, feed rate, override, spindle speed, tool number and PLC memory. Part count is determined during deployment.
We do, remotely. You prepare a Windows computer in your LAN and send us the list of machines; we install and configure SCT and connect the machines. To add a machine later, you write to us and we change the configuration remotely.
Talk to us
Not sure which data Scout can read from your Heidenhain machines? Talk to our expert during a free consultation.