Siemens SINAMICS DCM - CU: Internal Error (Application Not Known); CU: Internal Error (Parameter Group Not Available); CU: Internal Error (Port Does Not Exist); CU: Internal Error (Slave Missing in Topology)

4 Faults and alarms
4.2 List of faults and alarms
SINAMICS DCM
884 List Manual (LH8), 02/2015, 6RX1800-0ED76
Fault value (r0949, interpret hexadecimal):
Method ID.
Note:
Only for internal Siemens troubleshooting.
Remedy: Contact the Hotline.
F01058 CU: Internal error (slave missing in topology)
Message value: %1
Message class: Hardware / software error (1)
Drive object: DC_CTRL, DC_CTRL_R, DC_CTRL_R_S, DC_CTRL_S, TM150
Reaction: NONE
Acknowledge: IMMEDIATELY
Cause: The requested slave component does not exist in the topology.
Fault value (r0949, interpret hexadecimal):
Method ID.
Note:
Only for internal Siemens troubleshooting.
Remedy: Contact the Hotline.
F01059 CU: Internal error (port does not exist)
Message value: %1
Message class: Hardware / software error (1)
Drive object: DC_CTRL, DC_CTRL_R, DC_CTRL_R_S, DC_CTRL_S, TM150
Reaction: NONE
Acknowledge: IMMEDIATELY
Cause: The port object assigned according to the topology of the requested slave component does not exist.
Fault value (r0949, interpret hexadecimal):
Method ID.
Note:
Only for internal Siemens troubleshooting.
Remedy: Contact the Hotline.
F01060 CU: Internal error (parameter group not available)
Message value: %1
Message class: Hardware / software error (1)
Drive object: DC_CTRL, DC_CTRL_R, DC_CTRL_R_S, DC_CTRL_S, TM150
Reaction: NONE
Acknowledge: IMMEDIATELY
Cause: The requested parameter group (IREG, NREG, ...) is not offered by this slave type.
Fault value (r0949, interpret hexadecimal):
Method ID.
Note:
Only for internal Siemens troubleshooting.
Remedy: Contact the Hotline.
F01061 CU: Internal error (application not known)
Message value: %1
Message class: Hardware / software error (1)
Drive object: DC_CTRL, DC_CTRL_R, DC_CTRL_R_S, DC_CTRL_S, TM150
Reaction: NONE
Acknowledge: IMMEDIATELY
Cause: An application that is not registered with TSM has attempted to register with registerSlaves().
The cause can be an unsuccessful TSM registration or an incorrect registration sequence. It is always necessary to
log in to the TSM before registerSlaves() can be used.