239-0022

Access Communication Parameters

Navigate to MOD function → Machine Parameters → Communication → CC Bus Settings to check current cycle times.

Document current settings before making changes

Check CfgCcCycleTime Parameter

Verify parameter CfgCcCycleTime (typically MP7680) is not set below 2ms. Increase to 4-8ms if currently lower.

Coordinate with machine builder before changing cycle times

Monitor Communication Load

Use TNCdiag → Communication → CC Bus Load to verify telegram frequency after adjustment.

Optimal load should be below 70% for stable operation

Test System Response

Cycle power and run test program to verify alarm clearance and stable communication.

Ensure all axes are in safe position before power cycling

Review I/O Configuration

Access MOD → Machine Parameters → I/O Assignment to count active CC bus modules and their update rates.

Focus on modules with update rates faster than 10ms

Check Analog Input Sampling

Verify CfgAnalogSampleRate parameters (MP76xx series) are not set for unnecessary high-speed sampling.

Changing sample rates may affect spindle or feed control

Optimize Module Priority

Set non-critical I/O modules to lower priority or longer cycle times using CfgIoModulePriority parameters.

Safety-related I/O should maintain high priority

Validate Configuration

Use TNCdiag → I/O Status to confirm reduced telegram load and proper module response times.

Test all machine functions after I/O optimization

Inspect CC Bus Cabling

Check all CC bus cables for damage, proper shielding, and secure connections at each module.

Look for cable routing near high-power motor cables or welding equipment

Check Bus Termination

Verify proper 120-ohm termination resistors are installed at both ends of the CC bus network.

Incorrect termination can cause communication failures

Monitor Error Counters

Use TNCdiag → Communication → Error Statistics to check for CRC errors, timeouts, or retransmission counts.

Error rates above 0.1% indicate hardware issues

Test Signal Quality

Use oscilloscope to verify CC bus signal integrity - should show clean differential signals without excessive noise.

Only qualified technicians should perform signal measurements

Check System Temperature

Monitor FS controller temperature using TNCdiag → Hardware Status → Temperature readings.

FS controller should operate below 70°C for optimal performance

Verify Firmware Version

Check FS firmware version in MOD → System Info and compare against latest available updates.

Firmware updates require proper backup procedures

Test Memory Integrity

Run built-in memory test via TNCdiag → Hardware Test → Memory Check to identify potential RAM issues.

Memory tests should be run during maintenance windows

Consider Hardware Replacement

If tests indicate FS controller degradation, schedule replacement with identical part number and configuration transfer.

Backup all machine parameters before hardware replacement

Isolate Network Connections

Temporarily disconnect external Ethernet connections to determine if external traffic is causing the overload.

Test during non-production hours to avoid disrupting operations

Check Network Switch Configuration

Verify network switches have broadcast storm protection enabled and properly configured VLANs.

Network changes may affect other connected equipment

Monitor Network Traffic

Use network monitoring tools to identify sources of excessive broadcast or multicast traffic.

Look for devices with misconfigured network settings

Implement Traffic Filtering

Configure network equipment to filter unnecessary broadcast traffic from reaching the TNC system.

Ensure filtering doesn't block required communication protocols