Heidenhain Troubleshooting
Connection Issues
Problem: Cannot Connect to Control
Possible causes:
- Incorrect IP address
- Network connectivity issue
- Firewall blocking communication
- No connectivity option installed (TNC 640/730 requires Option 56 or Option 18)
- Control not powered on or Ethernet disabled
Solutions:
- Verify IP address is correct and control is reachable (ping test)
- Check physical Ethernet cable connection
- Verify connectivity option is installed:
- TNC 640/730: Requires Option 56 (recommended) or Option 18
- Check SIK page to confirm option is active
- Check network settings on control (IP, subnet mask, gateway)
- Verify firewall rules allow port 19090 communication
- Restart control and Edge device
Problem: Intermittent Connection
Possible causes:
- Network instability
- DHCP IP address changing
- Control restarting during production
- High network traffic or latency
Solutions:
- Use static IP address instead of DHCP
- Check network switch/router for errors
- Verify network cable quality (replace if old/damaged)
- Monitor network latency with continuous ping
- Check for IP conflicts on network
Data Collection Issues
Problem: No Data Items Populating
Possible causes:
- Adapter configuration incorrect
- Control not exposing data
- Polling interval too high
- Data mapping not configured
Solutions:
- Review adapter configuration for typos or errors
- Verify control type matches configuration (TNC530 vs TNC640)
- Check Data Mapping settings in MachineMetrics
- Review adapter logs for specific errors
- Reduce poll_interval to 1000ms (1 second)
Problem: Specific Data Items Missing
Possible causes:
- Control does not support specific data type
- Data item not configured in adapter
- PLC data not exposed
Solutions:
- Verify control model supports requested data
- Check adapter configuration includes all desired data items
- Review Heidenhain control capabilities documentation
- Contact MachineMetrics support for control-specific limitations
Part Counting Issues
Problem: Part Count Not Incrementing
Possible causes:
- Incorrect PLC WORD address
- Part counter disabled on control
- M-code not executing
- Data mapping not configured
Solutions:
- Verify PLC WORD address is correct (check on control)
- Ensure part counter is enabled in control settings
- Check CNC program includes M53 (or appropriate M-code)
- Verify Data Mapping and Data Rules are configured
- Review adapter logs for part count events
- Test manual increment on control
Problem: Part Count Incorrect or Resetting Unexpectedly
Possible causes:
- Reading wrong PLC WORD address
- Multiple counters in use (pallet changer, etc.)
- Data Rules reset behavior misconfigured
- Control resetting counter on program start
Solutions:
- Verify correct PLC WORD address with machine documentation
- Check for multiple part counters (select appropriate one)
- Review Data Rules reset configuration
- Disable automatic reset if not desired
- Consult machine operator on expected behavior
Problem: Cannot Find Part Counter in PLC WORD Table
Possible causes:
- Part counter stored in different location
- Custom machine configuration
- No native part counter implemented
Solutions:
- Review complete PLC WORD table for any counter-like variables
- Contact machine builder for PLC WORD documentation
- Check for M-code based counting instead (M53/M54)
- Consider implementing custom macro for part counting
- Contact MachineMetrics support for alternative methods
Network Configuration Issues
Problem: Control Not Obtaining IP Address (DHCP)
Possible causes:
- DHCP server not responding
- Network cable issue
- Control Ethernet settings incorrect
Solutions:
- Check physical cable connection
- Verify DHCP server is functioning (check other devices)
- Try static IP configuration instead
- Restart control and network switch
- Check control Ethernet settings are set to DHCP/Automatic
Problem: Cannot Ping Control from Edge Device
Possible causes:
- Different subnets
- Firewall blocking ICMP
- Incorrect IP configuration
- Network routing issue
Solutions:
- Verify Edge and control are on same subnet
- Check firewall settings (disable temporarily to test)
- Verify IP address, subnet mask, and gateway settings
- Test with another device on same network
- Check network switch configuration