What causes Siemens SINUMERIK alarm 61355?

Log file extension does not match the expected format specified in _PROTNAME[1] parameter. File name contains unsupported characters or incorrect syntax for the logfile naming convention. Parameter _PROTNAME[1] was modified or corrupted, pointing to an invalid file type. CYCLE106 is attempting to write to a logfile with an extension that the system does not recognize.

How do I fix Siemens SINUMERIK alarm 61355?

1. Access the parameter list and locate _PROTNAME[1] to verify the current logfile extension setting 2. Confirm that the logfile extension matches supported formats (typically .txt, .csv, or .log depending on your system configuration) 3. Reset _PROTNAME[1] to the factory default value and verify the correct syntax for your application 4. Clear the alarm and re-run CYCLE106 to confirm the logfile is now created with the correct extension 5. If the issue persists, check the HMI or diagnostics to verify the actual file being generated matches the parameter setting

Siemens SINUMERIK codes

axismd.ai

Siemens SINUMERIK Controller

Servo/Axis · Intermediate · 15-30 minutes

Alarm 61355

Siemens 840D 61355 - Channel Block: Incorrect file type for logfile

The alarm is triggerd by the following cycles: CYCLE106. The file extension for the log file is incorrect. Remedy: Check parameter _PROTNAME[1].

Siemens SINUMERIKServo/AxisIntermediate15-30 minutes

61355

Siemens 840D 61355 - Channel Block: Incorrect file type for logfile

Channel Block: Incorrect file type for logfile

The alarm is triggerd by the following cycles: CYCLE106. The file extension for the log file is incorrect. Remedy: Check parameter _PROTNAME[1].

Safety

Refer to Siemens documentation
Ensure qualified technician performs repairs

Common Causes

Log file extension does not match the expected format specified in _PROTNAME[1] parameter
File name contains unsupported characters or incorrect syntax for the logfile naming convention
Parameter _PROTNAME[1] was modified or corrupted, pointing to an invalid file type
CYCLE106 is attempting to write to a logfile with an extension that the system does not recognize

Troubleshooting Steps

1Access the parameter list and locate _PROTNAME[1] to verify the current logfile extension setting
2Confirm that the logfile extension matches supported formats (typically .txt, .csv, or .log depending on your system configuration)
3Reset _PROTNAME[1] to the factory default value and verify the correct syntax for your application
4Clear the alarm and re-run CYCLE106 to confirm the logfile is now created with the correct extension
5If the issue persists, check the HMI or diagnostics to verify the actual file being generated matches the parameter setting

Seeing Multiple Alarms?

Seeing another alarm with this one? Enter the code.

Get machine-aware diagnosis

AxisMD logs alarms against your actual machines, tracks patterns, and gives AI context your manual doesn't have.

Start free

Was this guide helpful?

Always verify with your machine manual or a certified technician before performing service procedures.