|
|
|
|
|
|
|
|
SINAMICS V20: Why did F23 fail?
|
|
SINAMICS V20: Why did F23 fail?
If the driver with firmware version less than 3.9.5 is cloned to the driver with firmware version 3.9.5, F23 failure may occur.
For firmware version 3.9.5, parameter p291 has two more bits, bit 3 and bit 4.
These two new bits were previously used for development, while the new functionality is disabled by default.
However, it was found that bit 4 was inadvertently set to "0" when cloned from previous versions, which activated an additional detection.
So for a specific motor or load, the F23 fault will be caused by the visible ripple on the DC link.
Forbid F23 malfunction
Because the access level of p291 is the protected service level, p291 can be accessed only when p3950 = 46.
If accessed through BOP, this parameter is automatically saved.
If accessed through a wireless connection module, these settings need to be saved manually.
Now there are bits 0-4 in p291.
Bits 0 and 4 need to be set to "1". Bits 1, 2 and 3 need to be set to "0".
So the binary bit mode is "10001", and p291 will display the hexadecimal "11".
So setting p291 to 11 (Hex) can prohibit F23 errors.
|
|
|
|
|
|
|
|
|
|
