320-0063

Access system configuration

Press MOD key, select 'System' → 'Configuration' → 'Machine Parameters' → 'CfgPlcLogging' to view current logging configuration.

Always backup the original configuration before making changes

Verify configuration syntax

Check CfgPlcLogging entries for proper XML syntax, valid file paths, and correct parameter formatting in the configuration display.

Invalid syntax can cause system instability

Restore default configuration

Navigate to 'System' → 'Service' → 'Configuration Reset' and select 'PLC Logging' to restore factory defaults for CfgPlcLogging parameters.

Restart PLC system

Execute PLC restart via 'PLC' → 'Operating Mode' → 'Stop/Start' to reinitialize logging with corrected configuration.

Check configured log paths

In CfgPlcLogging configuration, verify all 'LogFilePath' entries point to valid directories like 'TNC:\Log\' or accessible network paths.

Use TNC file manager to verify path existence before configuration

Create missing directories

Use TNC file manager (MOD → 'File Management') to create any missing log directories referenced in the CfgPlcLogging configuration.

Update path references

Modify CfgPlcLogging entries to use valid TNC file system paths, ensuring proper UNC format for network locations if applicable.

Test file write permissions

Verify write permissions to log directories by creating a test file in the specified path using TNC file manager.

Count active log configurations

Review CfgPlcLogging and count total number of active log file entries, comparing against TNC system limits (typically 16 concurrent logs).

Check log file size limits

Verify 'MaxFileSize' parameters in CfgPlcLogging don't exceed system memory allocation limits (usually 100MB per log file).

Smaller log files improve system performance and reduce memory usage

Disable unnecessary logging

Comment out or remove unused log file entries in CfgPlcLogging configuration to reduce system resource consumption.

Optimize log rotation settings

Configure appropriate 'MaxFiles' and 'RotationSize' parameters to prevent excessive disk usage while maintaining required logging.

Check software version compatibility

Press MOD → 'System' → 'Version Info' and compare current TNC software version against CfgPlcLogging parameter documentation.

Review deprecated parameters

Examine CfgPlcLogging for obsolete parameter names or formats that may no longer be supported in current TNC software version.

Deprecated parameters can cause system errors

Update parameter syntax

Modify CfgPlcLogging entries to use current parameter naming conventions and value formats as specified in updated TNC documentation.

Validate updated configuration

Save configuration changes and monitor system startup to ensure alarm 320-0063 is resolved with updated parameter format.