
© by SEMIKRON / 2019-07-23 / Technical Explanation / SKYPER
®
42 LJ R
PROMGT.1026/ Rev.7/ Template Technical Explanation
Page 21/35
5.
Protection features
5.1
Failure management
The SKYPER
42 LJ R driver core detects several error events on primary and secondary side. The driver’s
reaction on those events depends on the selected error mode, as described in chapter 4.8. The following
table covers all possible error routine scenarios.
Table 7: SKYPER
®
42 LJ R | Failure management
Conditions
Reaction
Error event
Occurrence
CFG_ERR
nERR_OUT
Outputs
Turn-off path
Undervoltage of
power supply
primary side
HIGH/LOW
LOW
immediately
OFF and locked,
immediately, until reset
Standard
nERR_IN at
low-level
primary side
HIGH
LOW
immediately
OFF,
with next turn-off signal at
the corresponding input
Locked
immediately
OFF & locked until reset
Standard
LOW
LOW
immediately
OFF and locked,
immediately, until reset
Standard
Undervoltage of
power supply
secondary side
HIGH
LOW
immediately
OFF,
with next turn-off signal at
the corresponding input
Locked
immediately
OFF & locked until reset
Soft Off
affected channel
Standard
not affected
channel
LOW
LOW
immediately
OFF and locked,
immediately, until reset
Short circuit
detection
(DSCP)
secondary side
HIGH
LOW
immediately
OFF,
with next turn-off signal at
the corresponding input
Locked
immediately
OFF & locked until reset
Soft Off
affected channel
Standard
not affected
channel
LOW
LOW
immediately
OFF and locked,
immediately, until reset
nERR_IN at
low-level
secondary side
HIGH
LOW
immediately
OFF,
with next turn-off signal at
the corresponding input
Locked
immediately
OFF & locked until reset
Soft Off
affected channel
Standard
not affected
channel
LOW
LOW
immediately
OFF and locked,
immediately, until reset
If the SKYPER
42 LJ R driver has entered the error state, it must be reset before it can resume operation
again. The driver could be reset under the following conditions:
•
>30µs non-error condition (Reaction on customer side has to be done within that time)
•
>9µs no input signals at TOP_IN/BOT_IN (Customer confirms error)
After completing the reset sequence the driver returns ‘ready for operation’ by setting the nERR_OUT
output to high-level.