SINAMICS DCP
List Manual (LH21), 05/2016
389
4 Faults and alarms
4.2 List of faults and alarms
A01016 (F) Firmware changed
Drive object: All objects
Cause: At least one firmware file in the directory was illegally changed on the non-volatile memory (memory card/device
memory) with respect to the version when shipped from the factory.
Alarm value (r2124, interpret decimal):
0: Checksum of one file is incorrect.
1: File missing.
2: Too many files.
3: Incorrect firmware version.
4: Incorrect checksum of the back-up file.
Remedy: For the non-volatile memory for the firmware (memory card/device memory), restore the delivery condition.
Note:
The file involved can be read out using parameter r9925.
The status of the firmware check is displayed using r9926.
See also: r9925 (Firmware file incorrect), r9926 (Firmware check status)
A01017 Component lists changed
Drive object: All objects
Cause: On the memory card, one file in the directory /SIEMENS/SINAMICS/DATA or /ADDON/SINAMICS/DATA has been
illegally changed with respect to that supplied from the factory. No changes are permitted in this directory.
Alarm value (r2124, interpret decimal):
zyx dec: x = Problem, y = Directory, z = File name
x = 1: File does not exist.
x = 2: Firmware version of the file does not match the software version.
x = 3: File checksum is incorrect.
y = 0: Directory /SIEMENS/SINAMICS/DATA/
y = 1: Directory /ADDON/SINAMICS/DATA/
z = 0: File MOTARM.ACX
z = 1: File MOTSRM.ACX
z = 2: File MOTSLM.ACX
z = 3: File ENCDATA.ACX
z = 4: File FILTDATA.ACX
z = 5: File BRKDATA.ACX
z = 6: File DAT_BEAR.ACX
z = 7: File CFG_BEAR.ACX
z = 8: File ENC_GEAR.ACX
Remedy: For the file on the memory card involved, restore the status originally supplied from the factory.
F01018 Booting has been interrupted several times
Drive object: All objects
Cause: Module booting was interrupted several times. As a consequence, the module boots with the factory setting.
Possible reasons for booting being interrupted:
- power supply interrupted.
- CPU crashed.
- parameterization invalid.
Remedy: - carry out a POWER ON (power off/on). After switching on, the module reboots from the valid parameterization (if
available).
- restore the valid parameterization.
Examples:
a) Carry out a first commissioning, save, carry out a POWER ON (switch-off/switch-on).
b) Load another valid parameter backup (e.g. from the memory card), save, carry out a POWER ON (switch-
off/switch-on).
Note:
If the fault situation is repeated, then this fault is again output after several interrupted boots.
Siemens Parts
To Next Page
Loading...
