MDLU3 Alarms

m December 16th, 2008
MDLU3 alarms Sw up to 3.43, 4.43
Alarm number Description
2 BUS overvoltage
3 Motor overtemperature
4 Module overtemperature
5 Braking Resistor overtemperature
6 Short-circuit to earth
7 Auxiliary Power Supply alarm
8 Local Link Alarm
9 S1 Sensor alarm
10 Timeout
11 Overspeed
12 Drive overcurrent
14 Flash checksum error
15 Data memory checksum error
16 Incompatible parameters
18 Self-calibration Alarm
36 Boot revision incompatible
37 Following error
38 S2 Sensor alarm
49 I2T-alarm
51 Check congruence position S1-S2 KO
52 Tandem function KO
53 Self-test Hardware
54 Brake failure
55 Incompatible sensors
56 V/f regulation
60 Safety failure class 0
MDLU3_Alarms.doc Page 1 of 58
MDLL3 alarms Sw up to 1.00
Alarm number Description
902 DC Bus pre-charging fault
905 Module overload
907 Mains overvoltage
908 DC Bus overvoltage
909 Unbalanced mains
910 Timeout
912 PWS Overcurrent
913 Auxiliary Power Supply fault
917 Dip-switch configuration changed
top
2 BUS overvoltage
DC BUS voltage higher than the allowed value.
Possible cause:
wrong operation of internal or external braking resistance
mains voltage too high
peak of power braking not enough
Possible remedy:
check connection and functioning of the internal/external braking resistance
check the mains voltage
check the dimensioning time.
Allowable extensions for this alarm:

• ext. 0: Overvoltage from PWS signal SRT. This alarm signal is issued by Power Supply MDLLx or MBLD (flat
cable level).
• ext. 1: Overvoltage bus voltage image UBC.
top
3 Motor overtemperature
The motor temperature is higher than the maximum allowed.
Possible cause:
the motor has worked in overcharge status for too long time and the thermal switch has operated
the thermal switch wiring is not connected present or is incorrect
Possible remedy:
check the working thermal cycle of the motor
check the connector thermal switch wiring and the continuity of the thermal switch connections cable

• ext. 0: Motor over temperature
The allowable max value is putted into the V270 parameter that contain the value, in Ohm, of the resistance of
the thermal probe after that the alarm will go out.
Check the technical data sheets of the thermal probe for to find the relation between ohmic resistance and motor
temperature.
This extension is applicable to both PTC and NTC thermal probes. The resistance of the thermal probe PTC is
bigger then V270 value. The resistance of the thermal probe NTC is lower then V270 value.
• ext. 1: NTC thermal probe not wired

This alarm is issued when an NTC thermal probe is used and it is not wired or it is wrong wired. The resistance of
the thermal probe NTC is bigger then 100kOhm.
top
The temperature of the heat-sink power module is higher than the maximum allowed (about 90
degrees centigrade).
Possible cause:
The internal temperature of the electrical cabinet or the environment temperature is too high (higher than 45
degrees centigrade).
Incorrect system dimensioning.
The force ventilation fan does not run.
Possible remedy:
Address to the machine manufacturer to check the correct thermal exchange.
Check the dimensioning of the drives + electrical cabinet system.
Inform the NUM technical assistance.
This alarm doesn’t have extensions.
top

The temperature of the braking resistance or of the heatsink’s power supply module is higher than the
maximum allowed. This alarm signal is issued by Power Supply MDLLx or MBLD (flat cable level).
Possible cause:
The working cycle is characterized with very closed accelerations/decelerations and the external braking
resistance has reached a too high temperature.
With MBLD drives with regenerative power supply, if the regenerative function doesn’t work in the right way we
can find this alarm.
The heatsink of the MDLLx or MBLDx has reached a temperature > 90 °C
Possible remedy:
Use a less heavy working cycle by increasing the time between the accelerations or by increasing the breaking
resistance power.
Check the correct thermal heat exchange inside the enclosure the electrical cabinet.
top
Short circuit to the ground of the power section. This alarm signal is issued by Power Supply MDLLx
or MBLD (flat cable level).
Possible cause:
DC BUS ground leakage.

Drive Power Supply.
Possible remedy:
Check the motor cable / cables and drive ground leakage.

Change Drive Power Supply (MDLLx) that could be damaged.
top
7 Auxiliary Power Supply alarm

The auxiliary voltage is not available.
Possible cause:
One or more of the auxiliary voltage inside the drive is not available.
Possible remedy:
Inform NUM technical assistance.

• ext. 0: +/-15V auxiliary power supply missing
This alarm is issued whenever +/-15V power supply is missing. Such power supply is used to power the AD
conversion circuitry of sensors and BUS voltage; furthermore it is used to supply power to the sensor itself.
• ext. 1: 3.3V auxiliary power supply overvoltage

This alarm is issued when 3.3V power supply exhibits an overvoltage condition. Such power supply is used to
power the DSP, the FPGA and all computation circuitry on Kernel board. In case of 3.3V overvoltage condition is
safer to turn-off the drive and subsitute it as soon as possible.
top
8 Local Link Alarm

This alarm is due to fault on the serial link between MDLU2/MBLD2 drives used for to create the
Tandem function.
Allowable extensions for this alarm are:
• ext. 0: The slave drive doesn't answer. This alarm is issued only by the master drive.
If bits 1,2,3 in V170 are resetted =0, but in V169 drives are declared like master or slave, drives become
independently but the Link is still active. Alarms of one drive are not transferred to the other one but the Link
alarms are active. E.g.: If the Link is physically interrupted, alarm A08.0 issues from master and A08.42 from
slave like Tandem function was active.
• ext.42: Local communication link interrupted.

The master drive started the communication but failed to continue.
This alarm is issued only by the slave drive.
If bits 1,2,3 in V170 are resetted =0, but in V169 drives are declared like master or slave, drives become
independently but the Link is still active. Alarms of one drive are not transferred to the other one but the Link
alarms are active. E.g.: If the Link is physically interrupted, alarm A08.0 issues from master and A08.42 from
slave like Tandem function was active.
• ext.51: No slave drive answered on the local communication link.

This alarm is issued only by the Master drive.
• ext.52: The master drive sends consecutive bad data packets.

The master drive, after the start of the communication, sends consecutive data packets with errors inside. The
timeout amount is related to the status of the drive torque enable: yes or no.
• ext.53: The master drive has never started the communication with the slave drive.
• ext.61: The drive configuration has changed from master to slave and viceversa without passing through power-
up.
• ext.63: Both the axes are declared as masters.

This alarm is issued only by NUMDRIVE C bi-axis
• ext.64: Both the axes are declared as slaves.

This alarm is issued only by NUMDRIVE C bi-axis.
top
9 S1 Sensor Alarm
These alarms are related to the S1 sensor.
Possible cause:
Wrong connection of one or more sensor connections or fault sensor.
Possible remedy:
Check sensor connections on the connector.
Stegmann sensor
• ext. 1: Stegmann alarm: Analogue signal out of specification
• ext. 2: Stegmann alarm: Wrong internal angle offset
• ext. 3: Stegmann alarm: Data field partition destroyed
• ext. 4: Stegmann alarm: Analogue limit not available
• ext. 5: Stegmann alarm: Internal I2C bus not working
• ext. 6: Stegmann alarm: Internal checksum error
• ext. 7: Stegmann alarm: Encoder reset by program monitoring
• ext. 8: Stegmann alarm: Counter overflow
• ext. 9: Stegmann alarm: Parity error
• ext. 10: Stegmann alarm: Wrong checksum of transmitted data
• ext. 11: Stegmann alarm: Command unknown
• ext. 12: Stegmann alarm: Number of transmitted data wrong
• ext. 13: Stegmann alarm: Transmitted command not allowed
• ext. 14: Stegmann alarm: Data can't be written to selected data field
• ext. 15: Stegmann alarm: Wrong access code
• ext. 16: Stegmann alarm: Size of data fields can't be changed
• ext. 17: Stegmann alarm: Specified address is outside data field
• ext. 18: Stegmann alarm: Access to non-existent data field
• ext. 28: Stegmann alarm: Monitoring the magnitude of analogue signals
• ext. 29: Stegmann alarm: Critical encoder current
• ext. 30: Stegmann alarm: Critical encoder temperature
• ext. 31: Stegmann alarm: Speed too high, position acquisition impossible
• ext. 32: Stegmann alarm: Position of single-turn not allowed
• ext. 33: Stegmann alarm: Position error multi-turn, 1
• ext. 40: Stegmann alarm: Error building absolute position (linear system)
Endat sensor
• ext. 0: Endat Alarm: Absolute position error
• ext. 1: Endat Alarm: Lighting
• ext. 2: Endat Alarm: Signal amplitude
• ext. 3: Endat Alarm: Position error
• ext. 4: Endat Alarm: Supply voltage too high
• ext. 5: Endat Alarm: Supply voltage too low
• ext. 6: Endat Alarm: Current too high
• ext. 7: Endat Alarm: Battery failure
Stegmann / Endat sensor

• ext.200: POM with coded references:
The distance measured between two references is higher than the value present in the V368 parameter.
• ext.201: POM:
The first zero reference position was detected in a wrong position (not multiple of 4).

The second zero reference position was detected in a wrong position (not multiple of 4).
• ext.230: Sensor: repeated pulse counter UGA misalignments
• ext.231: Sensor: excess of movement detected while waiting for UGA alignment. The axis has done an
uncontrolled movement during the analogue & encoder position components alignement phase.
• ext.232: Sensor: movement exceeded 30 electr. Degree while waiting for UGA alignment. This alarm can be
issued only if the alarm ext.231 is excluded. The axis has done an uncontrolled movement during the analogue &
encoder position components alignment phase bigger then the equivalent 30° electrical. In this case not only the
position is wrong but there is a high risk of loss motor phase.
• ext.238: It is issued by a wrong set up of MODE_SINCOS RS485 encoder
• ext.239: It is issued by a wrong set up Baud Rate RS485 encoder.
• ext.240: It is issued by a wrong data field format Stegmann sensor: No data fields defined ! No data fileld
necessary to manage an Hiperface NUM o SER sensor.
• ext.241: It is issued by a wrong initialisation Timeout sensore position. No digital communication with the sensor
Possible special cause:
Wrong power supply connection.
Possible remedy:

Verify the amplitude of sine and cosine signals using MP202 amd MP203, if they are both simultaneusly around
zero could be a power supply problem. MP238 must be around 100% if power supply is good.
• ext.242: It is issued by a wrong data field format for NUM Stegmann sensor.
• ext.243: It is issued by a wrong data field format for SER Stegmann sensor.
• ext.244: It's not possible to find a correct value for the resolver carrier gain.
• ext.245: Resolver signals saturation while searching best carrier phase.
• ext.246: The resolver cable requires the High-Voltage power supply enable connection.
• ext.247: Timeout while searching best carrier phase for resolver.
• ext.248: Encoder signals sine or cosine saturated. It is possible to exclude the alarm setting V348.10 = 1
• ext.249: Either the resolution bit number of the absolute position or the number of turns uploaded from encoder
memory do not match with ones declared.
• ext.250: Only for synchronous and linear motor with Hiperface sensors: phase offset not present in the encoder
• ext.251: Checksum error in the EEPROM memory of the encoder
• ext.252: Motor poles pairs / Sensor poles pairs can't match for Permanent Magnet Synchronous Motor+resolver.
• ext.253: Stegmann encoder type unknown.

This alarm extension is issued when a Stegmann encoder has the sensor code ID declared in the V344
parameter not coherent.
• ext.254: Sensor no connected or sine or cosine signal too low.

Check the sensor wiring and if it will be ok, set the right value in the V314 parameter
• ext.255: Fault in the encoder communication.

The drive cannot communicate with the encoder through the digital interface during the initialization phase.
It is possible that the encoder is badly connected or the wiring is wrong.
Possible remedy:

• ext.256: The absolute position displacement in the middle of the travel is not allowed for EnDAt linear encoder.
Check the bit 18 in the V348 parameter.
• ext.257: Sensor error signal (connector pin 21 state = low).

• ext.258: Fast serial sensor missing data.

The drive does not communicate correctly with the sensor through the digital interface.
It is possible that the sensor is badly connected or the wiring is wrong.
• ext.259: EnDat 2.2 sensor CRC error.

It is possible that the encoder or the wiring electromagnetic shield is badly connected.
• ext.260: SSI sensor not connected.

Check sensor connections on the connector. It is possible that the encoder is not correctly connected.
• ext.261: High-speed communication (5MHz) with EnDat2.2 not possible.

top
10 Timeout
Time out expired.
• ext. 1: Timeout on Braking (config. V30.1 / V32), the speed motor has not been gone down speed V41 / V42
within the time V43
• ext. 4: PWM timing error: missing PWM refresh.
top
11 Overspeed
The motor exceeded the maximum speed permitted for the motor
or the motor didn’t stay at 0 speed during the initialization phase of the drive.
• ext. 0: Motor overspeed
Possible cause:
o The motor speed exceeded the maximum speed threshold.

(parameters V96, V99, V1096, V1099)
o Wrong set up of the speed loop parameters.
o It has been requested to enable the drive while the motor is moving at speed above its flux-weakening
starting speed (V417, V457, V496, V497).
Possible remedy:
o Check the values present in the parameters managing the maximum speed
(parameters V96, V99, V1096 and V1099)
o Check the values present in the parameter managing the speed loop control.
o Check enabling condition: wait for motor speed has reached a value below its flux-weakening starting
speed (V417, V457, V496, V497) before enabling it.
• ext. 1: the motor didn’t stay at 0 speed during the initialization phase of the drive: a drive re-initialization was
tried while the motor was moving; wait for motor stop before retry a drive reset/re-initialization.
• ext. 2: speed > flux-weakening starting speed : the drive was requested to enable while the motor was running at
speed higher than the flux-weakening starting speed (V417, V457, V496, V497). Other possibilities: for
synchronous motor V42 > V497, for linear motor V41 > V496, for asynchronous motor V42 > V417 (low range)
or V457 (high range)
top
12 Drive overcurrent
The current exceeded the maximum value allowable for the drive
Possible cause:
Error on the power connection motor side
Error in the transducer wiring connection used for feedback in the current loop management
Error in motor / drive association; used a wrong ST (Technical specification).
EPS function started with a wrong set up of the parameters (parameters V180, V181, V182, V183)
Possible remedy:
Check the motor power wiring U, V, W.
Check the wiring of the transducer used as feedback in the current loop management.
Load the right ST.
Make a new and right set up of the EPS function
top

Alarm due to SW checksum incompatibility in Flash memory (managed by BOOT program)
This alarm is issued during the initialization phase of the drive.
• ext. 0: Error in the SW DSP checksum (SW missing)
• ext. 1: Error in the KFPGA programming (possible HW error)
• ext. 2: Error in the KFPGA checksum (SW missing)
• ext. 3: DSP software version incompatible
top

The checksum of the E2PROM memory of the drive is wrong.
• ext. 0: Error in the parameters table checksum
• ext. 1: Error in the alarm table checksum
• ext. 2: Error in the mechanical ratio checksum (it is correlated to the AP02 special application).
This alarm is issued if the Checksum of AP02 informations stored in Flash memory is wrong. The first time the
function is enabled on a new drive this alarm is issued (not resettable alarm). It needs to switch off and restart the
drive
top
Alarm for parameter incompatibility.
Possible cause:
Motor / drive association incompatibility.
Parameters not available. (For example: parameter memory formatted)
Possible remedy:
Load the correct parameters configuration for the motor / drive association and verify the parameter value.
Load the correct ST.
• ext. 0: Speed/Position regulator parameters exchanges set 0,1 not correct
• ext. 4: HW / SW incompatibility
• ext. 6: Inom dereating not correct. The alarm issues if the Inom value defined into V108 /V115 doesn’t take into
account the dereating owing to the PWM frequency value (5khz -> 10khz) (only for NUMDRIVE C).
• ext. 7: Oversampling configuration modified: it requires OFF->ON of the drive to be effective.
• ext. 8: Sensor - FPGAsensors not compatible: it requires OFF->ON of the drive. The alarm issues when
Resolver is declared or undeclared modifying V348. This modifie requires always the OFF-> ON of the drive.
• ext. 20: this alarm can issue (only for NUMDRIVE C) for two reasons:
1) Wrong configuration coherence of V020 (axis#0) with V252. If bit 0 of V020 (axis#0) is set (Sensor connectors
X3, X4 plugged-in) V252 has to be equal to “G”: that means NUMDRIVE C bi-axis HP. If bit 0 of V020 (axis#0) is
reset (Sensor connectors X3, X4 absent) V252 has to be equal to “H”: that means NUMDRIVE C bi-axis BP.
2) Wrong configuration coherence of V020 (axis#0) with V350,V351 or V352. If bit 0 of V020 (axis#0) is reset
(Sensor connectors X3, X4 absent) V350,V351,V352 have to be equal to 0: that means position, speed or current
sensor loop configurated on the connectors X1, X2.
• ext. 35: SW functions not available. The alarm issues if e.g.: AP01 is enabled in V160 but V35.0=0, AP02 is
enabled in V160 but V35.1=0, Tandem function AP03 is enabled in V170 but V35.2=0, AP06 is enabled in V160
but V35.3=0, AP08 is enabled in V160 but V35.5=0, AP10 is enabled in V160 but V35.7=0, AP12 is enabled in
V160 but V35.9=0, AP13 is enabled in V160 but V35.10=0.
With V35.11=0 it is possible to manage two sensors only if all loops are linked to only one sensor,
V350=V351=V352=0 or V350=V351=V352=1.
If the motor is a linear motor and V35.12=0 the alarm issues.
If the drive is NUMDRIVE C bi-axis BP the only one SW function available is AP02.
• ext. 160: Incompatibility between special application and others drive parameters.
E.g.
AP01: bit V348/V349.6 of the sensor that doesn’t close the position loop has to set =1 otherwise the alarm
issues.
AP02:this alarm can issue for many reasons:
1) The motor is a linear motor
2) The sensor selected for AP02 is not present
3) The sensor selected for AP02 is not an absolute sensor V348/V349 Bit3=Bit4=Bit5=0.
4) The sensor selected for AP02 is coded reference
AP06: in parameters V348/V349 only one sensor is declared (AP06 needs two sensors).
AP08: this alarm can issue for many reasons:
1) It is not possible activates AP08 if all loops are closed by the same sensor
2) V160.7=1. It is not possible to activate contemporaneously AP08 and AP10
1) It is not possible activates AP12 if all loops are closed by the same sensor
2) The axis is Slave in Tandem function V169.1=1 e V170.1=1. If the axis is Slave V169.1=1 but
Tandem function is not active V170.1=0 the alarm doesn’t issue
1) AP12 is not active, V160.9=0
2) Notch filter is not active, V500.5=0
• ext. 170: The torque duplication is no longer available but older SetTools can try to configure it e.g.: if bit
V170.1=0 and bit V170.2=1 (Torque duplication function declaration not implemented in MDLU3) the alarm
A16.170 issues.
• ext. 220: V220.7 = 1 with V271 = 100. V220.7 = 1 only with V271 = 50
• ext. 251: ST Parameters incompatibility
• ext. 252: Drive type not correct
• ext. 253: Drive size not correct
• ext. 255: Motor type not supported (only NUMDRIVE C bi-axis BP version)
• ext. 257: Motor poles pairs number not correct (only NUMDRIVE C bi-axis BP version)
• ext. 267: ST Peak current not correct
• ext. 271: FPGA re-synchronisation after sampling time current loop change
• ext. 305: AP02 requires the setting of V305 “Measure module for rot. axis/spindle abs[0]”. V305 has not to be
equal to 0
• ext. 307: S1 overflow error on multi-divi
• ext. 310: S1 overflow error on multi-divi + offset
• ext. 312: S2 overflow error on multi-divi
• ext. 313: S2 overflow error on multi-divi + offset
• ext. 317: V317 power supply > 5.5V but S1 sensor not available for high power supply (otherwise Stegmann
sensor not connected).The jumper between pin 5 and 6 of S1 that enables the sensor power supply > 5.5V is not
present
• ext. 318: V318 power supply > 5.5V but S2 sensor not available for high power supply (otherwise Stegmann
sensor not connected). The jumper between pin 5 and 6 of S2 that enables the sensor power supply > 5.5V is not
present
• ext. 348: S1 configuration error.

This alarm can issue for many reasons:
1) S1 is configurated like current loop sensor and V348.9=1
2) Hall sensor on S1 is not allowed
3) Linear sensor V348.8=1 is declared like corrent loop sensor of a rotative motor.
4) Sensorless encoders declared on Linear and Synchronous motors
5) Sensorless on current AND speed loop ONLY (...both !!!)
6) Sinusoidal signal compensation (CSS) on Sensorless encoders
• ext. 349: S2 configuration error.

This alarm can issue for many reasons:
1) S2 is configurated like current loop sensor and V349.9=1
2) Resolver-Sensor on S2 not allowed
3) Linear sensor V349.8=1 is declared like corrent loop sensor of a rotative motor.
4) Sensorless encoders declared on Linear and Synchronous motors
5) Sensorless on current AND speed loop ONLY (...both !!!)
6) Sinusoidal signal compensation (CSS) on Sensorless encoders
• ext. 350: P-loop not allow with non-configured sensor or Hall sensor
• ext. 351: V-loop not allow with non-configured sensor or Hall sensor
• ext. 352: C-loop not allow with non-configured sensor
• ext. 355: The parameters V355=0 and V356≠1
• ext. 1305: AP02 requires the setting of V1305 “Measure module for rot. axis/spindle abs[1]” . V1305 has not to
be equal to 0
• ext. 1307: Overflow error on multi-divi
• ext. 1310: Overflow error on multi-divi + offset
• ext. 1312: Overflow error on multi-divi
• ext. 1313: Overflow error on multi-divi + offset
• ext. #parameter: #parameter identifies the missing parameter number in flash table
top
18 Self-calibration alarm
Alarm related to the self-calibration phases of the EPS and EPSM functions.
• ext. 2: Error during EPS self-phasing phase:

The EPS procedure was not able to find the electrical phase of the motor. E.g. the electric current used during
EPS function is too low.
It is necessary to tune well the V180, V182, V183 parameters.
• ext. 3: Incoherency between the acceleration sign and torque current sign.
This alarm condition is monitored from the start of the EPS procedure till 1 second after the POM end, this
motoring is performed for security motivation. E.g. acceleration versus not coerent with current versus owing to
phase offset error.
If this alarm is issued it is necessary a new tuning of the EPS procedure.
To enable this new tuning it is necessary to disable the monitoring, setting V273.3 = 1.
• ext. 4: It was requested a POM after an EPS procedure V273.0 = 0 with the parameter V269 = 0
It is necessary input the correct value in the V269 parameter as described in the Procedure manual
AMOMAN004E for the EPS / EPSM functions
• ext. 5: Timeout during the EPSM function.

This alarm is issued about 6 seconds after the start of the EPSM command, in case one or more conditions
needed for to enable the EPSM command are not satisfied. The conditions to satisfy for enable the EPSM are:
o Drive in Run or Alarm status
o DC BUS energized: voltage present.
o Drive with torque and speed disabled.
o Safety relays enabled.
• ext. 6: Timeout during the EPSM function

Timeout on EPSM state machine: background NOT running.
• ext. 7: Timeout during the EPSM function

Timeout on EPSM offset writing on encoder.
• ext. 8: Timeout during the EPS function

Conditions for EPS not satisfied.
top

Alarm due to boot revision incompatibility.
top
37 Following error
The motor exceeded the allowable maximum following error.
Possible cause:
No good tuning of the control speed loop
No good tuning of the control position loop
No good working of the transducer used for the feedback of the control speed loop
No good working of the sensor used for the feedback of the control position loop
It is possible to exclude this alarm setting to 1 the bit 5 of the V30 parameter.
• ext. 0: CNC parameter P23 threshold exceeded
• ext. 1: Speed dynamic check threshold exceeded. See values parameters V45, V1045 for linear motor set [0]
and set[1], and V46, V1046 for sync/async motor set[0] and set [1].
• ext. 2: Return from NC control suspend procedure. This alarm is always issued (for safety reasons) when WPM
leaves again the drive control to the NC.
top
38 S2 Sensor alarm
These alarms are related to the S2 sensor.
Possible cause:
Wrong connection of one or more sensor connections or fault sensor.
Possible remedy:
Stegmann sensor
• ext. 1: Stegmann alarm: Analogue signal out of specification
• ext. 2: Stegmann alarm: Wrong internal angle offset
• ext. 3: Stegmann alarm: Data field partition destroyed
• ext. 4: Stegmann alarm: Analogue limit not available
• ext. 5: Stegmann alarm: Internal I2C bus not working
• ext. 6: Stegmann alarm: Internal checksum error
• ext. 7: Stegmann alarm: Encoder reset by program monitoring
• ext. 8: Stegmann alarm: Counter overflow
• ext. 9: Stegmann alarm: Parity error
• ext. 10: Stegmann alarm: Wrong checksum of transmitted data
• ext. 11: Stegmann alarm: Command unknown
• ext. 12: Stegmann alarm: Number of transmitted data wrong
• ext. 13: Stegmann alarm: Transmitted command not allowed
• ext. 14: Stegmann alarm: Data can't be written to selected data field
• ext. 15: Stegmann alarm: Wrong access code
• ext. 16: Stegmann alarm: Size of data fields can't be changed
• ext. 17: Stegmann alarm: Specified address is outside data field
• ext. 18: Stegmann alarm: Access to non-existent data field
• ext. 28: Stegmann alarm: Monitoring the magnitude of analogue signals
• ext. 29: Stegmann alarm: Critical encoder current
• ext. 30: Stegmann alarm: Critical encoder temperature
• ext. 31: Stegmann alarm: Speed too high, position acquisition impossible
• ext. 32: Stegmann alarm: Position of single-turn not allowed
• ext. 40: Stegmann alarm: Error building absolute position (linear system)
Endat sensor
• ext. 0: Endat Alarm: Absolute position error
• ext. 1: Endat Alarm: Lighting
• ext. 2: Endat Alarm: Signal amplitude
• ext. 3: Endat Alarm: Position error
• ext. 4: Endat Alarm: Supply voltage too high
• ext. 5: Endat Alarm: Supply voltage too low
• ext. 6: Endat Alarm: Current too high
• ext. 7: Endat Alarm: Battery failure
Stegmann / Endat sensor

The distance measured between two references is higher than the value present in the V378 parameter.
• ext.201: POM:
The zero reference position was detected in a wrong position.

The second zero reference position was detected in a wrong position.

The distance measured between two references is not equal to an integer number of sinusoid periods.
• ext.230: Sensor: repeated pulse counter misalignments
• ext.231: Sensor: overspeed detected while waiting for UGA alignment. The axis has done an uncontrolled
movement during the analogue & encoder position components alignement phase.
• ext.232: Sensor: movement exceeded 30 electr. Degree while waiting for UGA alignment. This alarm can be
issued only if the alarm ext.231 is excluded. The axis has done an uncontrolled movement during the analogue &
encoder position components alignment phase bigger then the equivalent 30° electrical. In this case not only the
position is wrong but there is a high risk of loss motor phase.
• ext.238: It is issued by a wrong set up of MODE_SINCOS RS485 encoder
• ext.239: It is issued by a wrong set up Baud Rate RS485 encoder.
• ext.240: It is issued by a wrong data field format stegmann sensor: NO data fields defined ! NO data fileld
necessary to manage an Hiperface NUM o SER sensor.
• ext.241: It is issued by a wrong initialisation Timeout sensore position. No digital communication with the sensor
Possible remedy:

• ext.242: It is issued by a wrong data field format for NUM Stegmann sensor.
• ext.243: It is issued by a wrong data field format for SER Stegmann sensor.
• ext.248: Encoder signals sine or cosine saturated. It is possible to exclude the alarm setting V348.10 = 1
• ext.249: Either the resolution bit number of the absolute position or the number of turns uploaded from encoder
memory do not match with ones declared.
• ext.250: Only for synchronous and linear motor with Hiperface sensors: phase offset not present in the encoder
• ext.251: Checksum error in the EEPROM memory of the encoder
• ext.252: Motor poles pairs / Sensor poles pairs can't match for Permanent Magnet Synchronous Motor+resolver.
• ext.253: Stegmann encoder type unknown.

This alarm extension is issued when a Stegmann encoder has the sensor code ID declared in the V345
parameter not coherent.
• ext.254: Sensor no connected or sine or cosine signal too low.

Check the sensor wiring and if it will be ok, set the right value in the V315 parameter
• ext.255: Fault in the encoder communication.

The drive cannot communicate with the encoder through the digital interface.
It is possible that the encoder is badly connected or the wiring is wrong.
Possible remedy:

• ext.256: The absolute position displacement in the middle of the travel is not allowed for EnDAt linear encoder.
Check the bit 18 in the V349 parameter.
• ext.257: Sensor error signal (connector pin 21 state = low).

• ext.258: Fast serial sensor missing data.

It is possible that the sensor is badly connected or the wiring is wrong.
• ext.259: EnDat 2.2 sensor CRC error.

It is possible that the encoder or the wiring electromagnetic shield is badly connected.
• ext.260: SSI sensor not connected.

Check sensor connections on the connector. It is possible that the encoder is not correctly connected.
• ext.261: High-speed communication (5MHz) with EnDat2.2 not possible.

top
49 I2T alarm
This alarm is issued whenever the I2T condition has been reached and the drive is configured to
handle such situation as an alarm instead of a warning (V30)
Possible cause:
The working cycle of the machine-tool involves a phase where the drive current delivered to the motor is too high
for a too long time.
Some damage/defect has caused friction to increase, so requiring more current to be delivered to the motor in
order to follow CNC acceleration commands.
Some parameters on CNC require very high accelerations that can’t be respected by the drive and motor which
the machine-tool is equipped with.
Possible remedy:
Check the working cycle of the machine-tool

Check the machine-tool mechanics for any cause of increased friction.
Check CNC accelerations parameter and, possibly, relax them to reduce required working speed.
NOTE:
It is always possible to eliminate such alarm by configuring parameter V30 of the drive in order to handle the I2T
condition as a simple warning.
But be careful! In case of I2T handled as a simple warning, the CNC is NEVER informed that such condition has
occurred and may continue to requires so high working speed as to generate “following error” due to the fact that the
drive has limited its torque current in order not to burn the motor and/or itself.
• ext. 0: Threshold exceeded
• ext. 108: Wrong value for V108 rated motor current l.r.
• ext. 115: Wrong value for V115 rated motor current h.r.
• ext. 128: Wrong value for V128 stall motor current l.r.
• ext. 129: Wrong value for V129 stall motor current h.r.
top
51 Check congruence position S1-S2 KO

This alarm is related to the AP06 special application:
The difference between the measures, in physical units, coming from the S1 and S2 sensors
exceedes the value stored in V190 parameter and this condition stays active for a time longer than the
value stored in V191 parameter.
Possible cause:
• Broken of the kinematical chain motor / load.
• Broken of one or botch sensors.
• Wrong set up of the AP06 special application
Possible remedy:
• Check the kinematical chain motor / load.
• Check the connections of the sensors, their mechanical fit, check if the sensors are good or not.
• Make a new tuning of the AP06 special application.

(V190, V191 parameters)
top
52 Tandem function KO
This alarm is related to the tandem function: AP03 special applications
This alarm summarizes all the fault conditions emerging from mechanical problems and/or electronic
problems in the master and slave drives.

• ext. 0: The slave drive is in fault status.
• ext. 41: Torque equalizer saturation timeout.

The timeout value is stored in the V176 parameter.
The alarm has been created with the scope to detect electrical and/or mechanical problems of the anti-backlash
system: this means that the two motors, mechanically coupled to realize the anti-backlash function, don’t supply
the same torque to move the machine.
Check the kinematical chain, the sensors fitting, the mechanical joints, etc.
This alarm is issued only by the master drive.
• ext. 42: AB balancer timeout: Partner not enabled due to unknown reasons.
E.g.: master enables current, flux and speed loops, then it waits 500 msec the slave communication of current,
flux and speed loops enabled.
If the answer is o.k., the master activates torque balancer and position loop: axis is completely operative.
If the answer is not o.k. owing to e.g. 1) Slave SAM board is not in status 6 and the slave hasn’t completed the
own loops enable phase 2) Slave Safety Light is open and then the slave hasn’t completed the own loops enable
phase, the alarm issues.
• ext. 50: The slave is in Halt state while the master is torque enabled.
The master drive goes immediately in the alarm status if the system is torque enabled and the slave drive has
been put in Halt status using CNC/SetTool or WPM.
To go out from this alarm condition, it is imperative to put in the same status all the drives involved in the Tandem
function, master and all the slaves:
1. Put in alarm status the master drive and all the slave drives
2. Send an Alarm Reset command, at same time, to the master and to all the slaves
This alarm is issued only by the master drive.
• ext. 60: The master is in Halt state while the slave is torque enabled.
The Slave drive will go immediately in alarm status if the system is torque enabled and the Master has been put
in Halt status using CNC/SetTool or WPM.
To go out from this alarm condition, it is imperative to put in the same state all the drives involved in the Tandem
function, master and all the slaves:
1. Put in alarm status the master drive and all the slave drives
2. Send an Alarm Reset command, at same time, to the master and to all the slaves
• ext. 62: This alarm has been created only in the slave drive to show that master drive is, for any cause, in the
alarm status.
top
Alarm due to bad hardware functionality.
• ext. 0: Current sensing A/D converter not properly initialized.
• ext. 1: An error has occurred in the FPGAs reset procedure.
• ext. 2: Checksum error on control FPGA program in flash memory.
• ext. 3: The DONE pin hasn't gone high after the configuration of the control FPGA
• ext. 4: Checksum error of the FPGA sensor board 1 program in flash memory.
• ext. 5: Checksum error of the FPGA sensor board 2 program in flash memory (only for NUMDRIVE C bi-axis).
• ext. 6: The DONE pin hasn't gone high after the configuration of FPGA sensor board 1 or 2.
• ext. 7: The control board PLL isn't working.
• ext. 8: The sensor board 1 PLL isn't working.
• ext. 9: The sensor board 2 PLL isn't working (only for NUMDRIVE C bi-axis).
• ext. 10: The control board address and data buses aren't working properly.
• ext. 11: The sensor board 1 address and data buses aren't working properly.
• ext. 12: The sensor board 2 address and data buses aren't working properly (only for NUMDRIVE C bi-axis).
• ext. 13: The control board programming code is missing.
• ext. 14: The sensor board 1 programming code is missing.
• ext. 15: The sensor board 2 programming code is missing (only for NUMDRIVE C bi-axis).
• ext. 16: PWR EEprom I2C not detected (only for NUMDRIVE C).
• ext. 17: PWR EEprom I2C: Checksum error (only for NUMDRIVE C).
• ext. 18: PWR EEprom I2C: Missing Imax data (only for NUMDRIVE C).
• ext. 19: PWR EEprom I2C: Missing Inom data (only for NUMDRIVE C).
• ext. 20: Wrong sensor connectors X3, X4 configuration (see V0020 axis#0 only) (only for NUMDRIVE C bi-axis).
• ext. 21: Sensor connectors X3, X4 configuration modified (Changements not allowed) (see V0020 axis#0 only):
this alarm disappears after RESET and POWER UP (only for NUMDRIVE C bi-axis).
• ext. 22: Wrong Power board: Power board not coherent with drive type (only for NUMDRIVE C).
• ext. 23: Reading/writting information in Flash memory failed.

This alarm is issued if the Flash memory is not accessible for more then 2 sec. It needs to switch off and restart.
• ext. 24: Drives addresses are equal.
• ext. 25: Tandem link deactivation needs power-up.
• ext. 26: SAM board presence not coherent with drive type.
• ext. 27: Hardware incompatiblity between control and power boards (only for NUMDRIVE C bi-axis).
• ext. 28: NUM-STO safety function not allowed for hardware incompatibility.
top
54 Brake failure (for NUMDrive C only)

This alarm is related to the Brake internal functionalities

• ext. 0: 24 Volt for brake not connected or open fuse.
• ext. 1: Brake not connected or Overcurrent or Short Circuit on the output.
top
55 Incompatible sensors
This alarm is related to the incompatible sensors declaration (see V0348, V0349)

• ext. 0: TTL sensor on S1 and S2 not allowed.
• ext. 1: Sensorless on S1 and S2 not allowed.
• ext. 2: Sensor error signal test on both sensors not available.
• ext. 3: Fast Serial sensor on S1 and S2 not allowed.
• ext. 4: Fast Serial sensor with oversampling not allowed.
• ext. 5: Fast serial sensor - Endat sensor on S1,S2 not allowed.
• ext. 6: TTL sensor on both connectors X1,X2 (X3,X4) not allowed.
• ext. 7: Sensor error signal test on both connectors X1,X2 (X3,X4) not available.
• ext. 8: Fast Serial sensor on both connectors X1,X2 (X3,X4) not allowed.
• ext. 9: Fast serial sensor - Endat sensor on connectors X1,X2 (X3,X4) not allowed.
• ext. 10: SSI sensor on S1 and S2 not allowed.
top
56 V/f regulation
This alarm is related to the V/f regulation motor control

• ext. 0: Config: motor type not allowed (V255).
• ext. 1: Config: electrical gear switch not allowed (V256).
• ext. 2: Config: set parameters 1 not allowed (V260, V261)
• ext. 3: Config: i2t must be configured as alarm (V30.6).
• ext. 4: Config: no vertical payloads allowed (V109).
• ext. 5: Config: special applications not allowed (V160.0/3/5/7/9/10).
• ext. 6: Config: anti-backlash not allowed (V169, V170).
• ext. 7: Config: acceleration deceleration ramps mandatory (V30.14/15).
• ext. 8: Config: encoder type for current loop not allowed.
• ext. 9: Config: encoder type for speed loop not allowed.
• ext. 10: Config: encoder type for position loop not allowed.
• ext. 11: Math err: wrong [V/Hz] slope: check V601, V602, V603.
• ext. 12: Math err: wrong gain of current limiter: check V91, V600, V605.
top
60 SAFETY failure class 0

This alarm is related to the SAM Safety board
This alarm summarizes all the fault conditions monitorated by SAM Safety board.

• ext. 51: SAM EEPROM wrong checksum (default values loaded).
• ext. 52: SAM module exchanged (default values loaded).
• ext. 259: SAM requested (V30.8 = 1) but not detected.
• ext. 260: SAM detected but not requested (V30.8 = 0).
• ext. 261: SAM or NUM-STO detected: Stop Function (V30.9 = 1) not allowed
• ext. 262: SAM parameter ResEnc not defined.

This alarm is issued if the parameter ResEnc is equal to 0 or it is a negative value.
• ext. 263: [Encoder resolution / SAM parameter ResEnc] ratio wrong.

This alarm is issued if the ratio is not an integer number, that means if there is a remainder.
• ext. 264: SAM parameter ResEnc not compatible with drive parameters.
• ext. 265: NUM-STO requested (V30.18 = 1) but not detected.
• ext. 266: NUM-STO detected but not requested (V30.18 = 0).
top


• ext. 0: Class 1 error forced.
• ext. 5: Safe operational stop violated.
• ext. 6: Safely reduced setup speed exceeded.
• ext. 56: Safely reduced operating speed exceeded.
• ext. 115: Error at Safe Deceleration Process: Insufficent brake ramp (PLC).
top


• ext. 10: Emergency stop triggered.
• ext. 23: 24Vdc overvoltage.
• ext. 25: Short circuit at outputs of channel A to GND.
• ext. 28: SAM24Vdc overvoltage (SW).
• ext. 29: SAMSTART max. admissible pulse lenght exceeded.
• ext. 36: System error: Input.
• ext. 39: Parameter block checksum error.
• ext. 40: System error: SPI framing error.
• ext. 41: Unequal input states.
• ext. 42: Cross circuit at output (unequal states).
• ext. 45: Error in I/O current monitoring.
• ext. 46: System error: Error in SAM24Vdc monitoring (unequal value).
• ext. 47: System error: Drive release / SAM jumper.
• ext. 49: System error: SPI short circuit.
• ext. 50: System error: UART short circuit.
• ext. 54: Parameters: unequal checksum.
• ext. 57: Input SAMSTART low instead of high (Auto Start).
• ext. 58: Input SAMSTART high instead of low (Safe Start).
• ext. 59: Guard confirmation : Max. admissible pulse lenght exceeded.
• ext. 62: Wrong voltage at inputs.
• ext. 63: Output AUX_OUT_A (cross circuit to other output).
• ext. 64: Output INTERLOCK_OUT_A (cross circuit to other output).
• ext. 65: Output RELAY_A (cross circuit to other output).
• ext. 66: Output SAFETY24V_A (cross circuit to other output).
• ext. 67: Output AUX_OUT_A (cross circuit to 24V).
• ext. 68: Output INTERLOCK_OUT_A (cross circuit to 24V).
• ext. 69: Output RELAY_A (cross circuit to 24V).
• ext. 70: Output SAFETY24V_A (cross circuit to 24V).
• ext. 71: System error: Output drive of channel A defective.
• ext. 72: System error: Input ESTOP_A.
• ext. 73: System error: Input GUARD1_A.
• ext. 74: System error: Input SETUPENABLE_A.
• ext. 75: System error: Input SETUPMODE_A.
• ext. 76: System error :Input SAFETY_REF_A.
• ext. 77: System error :Input GUARD2_A.
• ext. 78: System error: Input INTERLOCK_IN_A.
• ext. 79: System error: Input GUARD1CONF_A.
• ext. 80: Short circuit at output of channel B to GND.
• ext. 82: ResEnc (resolution of encoder) is set to 0.
• ext. 83: System error: CPU synchronization.
• ext. 84: No motor movement for 36h.
• ext. 85: System error:Time out high-priority tests (5sec).
• ext. 86: System error:Time out low-priority tests.
• ext. 87: dec_Qstop (max. admissible brake ramp) is set to 0.
• ext. 88: Output AUX_OUT_B (cross circuit to other output ).
• ext. 89: Output INTERLOCK_OUT_B (cross circuit to other output).
• ext. 90: Output RELAY_B (cross circuit to other output).
• ext. 91: Output SAFETY24V_B (cross circuit to other output).
• ext. 92: Output AUX_OUT_B (cross circuit to 24V ).
• ext. 93: Output INTERLOCK_OUT_B (cross circuit to 24V).
• ext. 94: Output RELAY_B (cross circuit to 24V).
• ext. 95: Output SAFETY24V_B (cross circuit to 24V).
• ext. 96: System error: Output drive of channel B defect.
• ext. 97: System error: Input ESTOP_B.
• ext. 98: System error: Input GUARD1_B.
• ext. 99: System error: Input SETUPENABLE_B.
• ext. 100: System error: Input SETUPMODE_B.
• ext. 101: System error :Input SAFEFUNCIN_B.
• ext. 102: System error: Input GUARD2_B.
• ext. 103: System error: Input INTERLOCK_IN_B.
• ext. 104: System error: Input GUARD1CONF_B.
• ext. 105: SAM24VGND not connected.
• ext. 107: Difference 24Vdc - SAM24Vdc to big.
• ext. 108: Difference 24Vdc – SAM24Vdc Overvoltage (HW) - Not resettable alarm
• ext. 111: System error: AD converter.
• ext. 116: Safe operational stop repeatedly violated.
• ext. 119: Input INTERLOCK_IN is high even it is to ignore by konfiguration.
• ext. 120: Setup speed (n_maxRed) is higher than Automatic speed (n_maxAuto).
• ext. 122: SAM24VDC undervoltage.
• ext. 127: SAM24VGND not connected.
top


• ext. 4: Error at Safe Stopping Process; Insufficient brake ramp (Quick Stop).
• ext. 13: Safe Operational Stop in fault state violated.
• ext. 43: Error in position acquisition (unequal values).
• ext. 44: Error in speed acquisition (unequal values).
• ext. 113: Safe Operational Stop in fault state disabled.
• ext. 118: INTERLOCK_IN isn't turning to high (time out if t_Relay=2).
top


• ext. 0: Simultaneous errors.
• ext. 24: 24Vdc undervoltage.
• ext. 26: System error: 5V supply voltage.
• ext. 27: System error: 5V undervoltage.
• ext. 30: System error: RAM self test failed.
• ext. 31: System error: Stack overrun.
• ext. 32: System error: Program sequence control Communication.
• ext. 33: System error: Program sequence check (idle Task).
• ext. 34: System error: Program sequence check (MS Task).
• ext. 37: System error: PROM checksum error.
• ext. 48: System error: SAM24Vdc overvoltage cut off unit.
• ext. 53: System error: Position acquisition (commutating position).
• ext. 60: System error : Unequal states of SAM state machines.
• ext. 81: System error: UART Overrun/Framing error.
• ext. 106: System error: Temperature sensor.
• ext. 109: Switch off temperature (HW).
• ext. 110: System error: Unequal SamOpMode.
• ext. 112: Unequal software revisions.
• ext. 114: System error: Software is not compatible with current hardware version.
• ext. 117: Error accumulation at Safe Stopping Process :Insufficient brake ramp (Quick stop).
• ext. 121: System error: Unknown state of SAM State machine.
• ext. 123: System error: ENABLE_ALL 5VGate cut off unit.
• ext. 124: System error: ENABLE_ALL Temp cut off unit.
• ext. 125: System error: Asynchronous communication (UART/SPI).
• ext. 126: System error: RAM (Bit).
• ext. 255: The Togglebit FrameRF does not toggle once per data block.
• ext. 256: Timeout receiving SAM_ID exceeded. DSP does not communicate with the SAM module on the
synchronous serial interface (SPI). Once DSP has recognized the module ( by reading its no-volatile memory
through I2C bus, at power on ), it sends an own identifier via serial bus. If DSP does not receive any response
from SAM within time-out interval, it generates this alarm .
• ext. 257: SAM SPI Protocol version is higher than DSP version.
• ext. 258: SAM SPI Protocol version is lower than DSP version ( SAM update required ).
top
902 DC Bus pre-charging fault

This alarm is related to the

• ext. 0: Possible hardware failure of the pre-charging circuit.
top

The temperature of the Power Supply module is higher than the maximum allowed (about 90 degrees
centigrade).

• ext. 0: Module overtemperature.
top

The temperature of the braking resistance of the Power Supply module is higher than the maximum
allowed.

• ext. 0: Disconnected resistor or wrong value.
top
905 Module overload


• ext. 0: Alarm threshold exceeded.
top


• ext. 0: Short-circuit to earth.
top
907 Mains overvoltage


• ext. 0: Voltage amplitude too high.
top
908 DC Bus overvoltage


• ext. 0: DC Bus overvoltage.
top
909 Unbalanced mains


• ext. 0: Missing phase.
• ext. 1: Unbalanced voltage.
top
910 Timeout

• ext. 0: PWM timing error: PWM not refreshed.
top

Alarm due to bad hardware functionality.

• ext. 0: Current sensing A/D converter not properly initialized.
• ext. 1: An error has occurred in the FPGAs reset procedure.
• ext. 2: Checksum error on control FPGA program in flash memory.
• ext. 3: The DONE pin hasn't gone high after the configuration of the control FPGA .
• ext. 4: Checksum error of the PWS interface board FPGA program in flash memory.
• ext. 6: The DONE pin hasn't gone high after configuration of PWS interface board FPGA.
• ext. 7: The control board PLL isn't working.
• ext. 8: The PWS interface board PLL isn't working.
• ext. 10: The control board address and data buses aren't working properly.
• ext. 11: The PWS interface board address and data buses aren't working properly.
• ext. 13: The control board programming code is missing.
• ext. 14: The PWS interface board programming code is missing.
• ext. 16: PWR EEprom I2C not detected.
• ext. 17: PWR EEprom I2C: checksum error.
• ext. 18: PWR EEprom I2C: missing Imax data.
• ext. 19: PWR EEprom I2C: missing Inom data.
• ext. 23: Reading / writing information in flash memory failed.
• ext. 24: Erroneous AD conversion on PWS interface board.
top
912 PWS Overcurrent


• ext. 0: Overcurrent alarm from control board FPGA.
top
913 Auxiliary Power Supply fault

The auxiliary voltage is not available.
Possible cause:
One or more of the auxiliary voltage inside the Power Supply module is not available.
Possible remedy:
Inform NUM technical assistance.

• ext. 0: +/-15V auxiliary power supply missing
This alarm is issued whenever +/-15V power supply is missing. Such power supply is used to power the AD
conversion circuitry of sensors and BUS voltage.
• ext. 1: 3.3V auxiliary power supply overvoltage

This alarm is issued when 3.3V power supply exhibits an overvoltage condition. Such power supply is used to
power the DSP, the FPGA and all computation circuitry on Kernel board. In case of 3.3V overvoltage condition is
safer to turn-off the module and subsitute it as soon as possible.
top

Alarm due to SW checksum incompatibility in Flash memory (managed by BOOT program)

• ext. 0: Error in the SW DSP checksum (SW missing).
• ext. 1: Error in the KFPGA programming (possible HW error)
• ext. 2: Error in the KFPGA checksum (SW missing)
• ext. 3: DSP software version incompatible
top

The checksum of the E2PROM memory of the drive is wrong.

• ext. 0: Error in the parameters table checksum.
• ext. 1: Error in the alarm table checksum.
top

Alarm for parameter incompatibility.

• ext. 0: HW / SW incompatibility.
• ext. 9108: Inom derating incorrect.
• ext. 9251: ST Parameters incompatibility.
• ext. 9252: Power supply type incorrect.
• ext. 9253: Power supply size incorrect.
• ext. 9267: ST Peak current incorrect.
• ext. 9271: FPGA re-synchronization after sampling time current loop change.
top
917 Dip-switch configuration changed


• ext. 0: Changing of dip-switch layout.
top

MDLU3 Alarms

Uploaded by

Copyright:

Available Formats

MDLU3 Alarms

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MDLU3 Alarms

Uploaded by

Copyright:

Available Formats

m December 16th, 2008

MDLU3 alarms Sw up to 3.43, 4.43

Alarm number Description

5 Braking Resistor overtemperature

7 Auxiliary Power Supply alarm

8 Local Link Alarm

14 Flash checksum error

15 Data memory checksum error

36 Boot revision incompatible

51 Check congruence position S1-S2 KO

60 Safety failure class 0

61 Safety failure class 1

62 Safety failure class 2

63 Safety failure class 3

64 Safety failure class 4

MDLL3 alarms Sw up to 1.00

Alarm number Description

36 Boot revision incompatible

902 DC Bus pre-charging fault

903 Module overtemperature

904 Braking Resistor overtemperature

905 Module overload

906 Short-circuit to earth

907 Mains overvoltage

908 DC Bus overvoltage

909 Unbalanced mains

911 Self-test Hardware

912 PWS Overcurrent

913 Auxiliary Power Supply fault

914 Flash checksum error

915 Data memory checksum error

916 Incompatible parameters

917 Dip-switch configuration changed

wrong operation of internal or external braking resistance

mains voltage too high

peak of power braking not enough

check connection and functioning of the internal/external braking resistance

check the mains voltage

check the dimensioning time.

Allowable extensions for this alarm:

• ext. 1: Overvoltage bus voltage image UBC.

the thermal switch wiring is not connected present or is incorrect

check the working thermal cycle of the motor

Allowable extensions for this alarm:

• ext. 1: NTC thermal probe not wired

Incorrect system dimensioning.

The force ventilation fan does not run.

Address to the machine manufacturer to check the correct thermal exchange.

Check the dimensioning of the drives + electrical cabinet system.

Inform the NUM technical assistance.

This alarm doesn’t have extensions.

5 Braking Resistor overtemperature

The heatsink of the MDLLx or MBLDx has reached a temperature > 90 °C

This alarm doesn’t have extensions.

DC BUS ground leakage.

Check the motor cable / cables and drive ground leakage.

This alarm doesn’t have extensions.

7 Auxiliary Power Supply alarm

Inform NUM technical assistance.

Allowable extensions for this alarm: