250-F324

Access Component Monitoring Configuration

Navigate to MOD function → Machine Parameters → CfgComponentMon → components[] to view current component limit configuration.

Use PLC parameter search function (CTRL+F) to quickly locate CfgComponentMon entries

Verify Limit Array Structure

Check that each component entry contains exactly four limit values: limits[0] (warning low), limits[1] (alarm low), limits[2] (alarm high), limits[3] (warning high).

Backup machine parameters before making changes using MOD → Data Backup function

Add Missing Limit Values

Complete the limits array by adding missing threshold values appropriate for the power supply component being monitored.

Consult power supply documentation for recommended threshold values before configuration

Validate Configuration

Save parameters and restart TNC to verify component monitoring displays correctly without alarm recurrence.

Review Current Limit Values

Access CfgComponentMon/components[] and examine the limits[] array values for the affected component to identify ordering issues.

Document current values before modification for rollback purposes

Verify Ascending Order Logic

Ensure limits are ordered: limits[0] < limits[1] < limits[2] < limits[3] representing warning_low < alarm_low < alarm_high < warning_high.

Incorrect ordering can cause false alarms or missed critical conditions

Correct Limit Sequence

Rearrange limit values in proper ascending order while maintaining logical threshold relationships for power supply monitoring.

Test Component Display

Cycle power to TNC and verify component monitoring screen shows proper limit visualization without alarm 250-F324.

Examine Configuration Syntax

Review CfgComponentMon/components[] structure for proper JSON-like syntax including correct bracket placement and parameter naming.

Use TNC's built-in parameter validation by pressing ENTER after each line modification

Validate Component Identifier

Verify component name matches exactly with power supply component identifiers recognized by the TNC system.

Case-sensitive component names must match PLC variable definitions exactly

Check Parameter Completeness

Ensure all required parameters (name, type, limits, units) are present and properly formatted in the component configuration block.

Validate and Apply Changes

Use MOD function parameter validation to check syntax before saving configuration changes to prevent system errors.

Identify Power Supply Type

Determine actual power supply model and monitoring capabilities from TNC hardware configuration and PLC program documentation.

Check PLC program comments for component type definitions and monitoring variable assignments

Verify Component Type Parameter

Access CfgComponentMon/components[]/type parameter and ensure it matches the power supply component specification (voltage, current, temperature, etc.).

Update Component Configuration

Modify component type parameter to match actual power supply monitoring requirements and supported limit types.

Incorrect component types may cause monitoring to fail silently

Restart Component Monitoring

Cycle TNC power or restart component monitoring service to apply corrected component type configuration.