Group 19, Motor Controls

1. Traction / Pump Controller T: Traction, P: Pump

Fault Fault
Fault Name Control Fault Name Control
Code Code
T1 SEAT SW OPEN T T76,P76 MC COIL SHORT T/P
T2,P2 ANALOG INPUT T/P T77 MAINTENANCE HOUR T
T3,P3 COIL SHORT HW KO T/P T78,P78 VACC NOT OK T/P
T4,P4 SAFETY OUTPUT, FAN OUTPUT T/P T79,P79 INCORRECT START T/P
T5,P5 VACC OUT RANGE T/P T80 FORW + BACK T
T7,P7 SLIP_PROFILE T/P T81,P81 SENS MOT TEMP KO T/P
T8,P8 WATCHDOG#1 T/P
T82,P82 ENCODER ERROR T/P
T9,P9 WATCHDOG# T/P
P83 OVERLOAD P
T10 WAITING DISPLAY T
P84 LOAD SENS. ERROR P
T11,P11 AUX DRIV.SHRT. T/P
T85,P85 WAITING FOR NODE T/P
T12,P12 SAFETY INPUT T/P
T86 SEQUENCE FAULT T
T13,P13 EEPROM KO T/P
P90 ACQUIRE LIFT P
T14,P14 TH. PROTECTION T/P
T15,P15 AUX COIL SHORT T/P P91 ACQUIRE TILT P
T16,P16 AUX DRIV.OPEN T/P P92 ACQUIRE S/S P
T17,P17 LOGIC FAILURE #3 T/P P93 ACQUIRE AUX1 P
T18,P18 LOGIC FAILURE #2 T/P P94 MHYRIO IN ALARM P
T19,P19 LOGIC FAILURE #1 T/P P95 LIFT OUT OF RNG. P
T30,P30 VMN LOW T/P P96 TILT OUT OF RNG. P
T31,P31 VMN HIGH T/P P97 AUX OUT OF RNG. P
T33,P33 IDLE TIME T/P P98 S/S OUT OF RNG. P
T37,P37 CONTACTOR CLOSED T/P P99 ACQUIRE REACH P
T38,P38 CONTACTOR OPEN T/P P100 REACH OUT OF RNG P
T39,P39 KEY OFF SHORT T/P T101
CAN BUS KO DISP. T/P
T40,P40 HARDWARE FAULT T/P P101
T43,P43 FLASH CHECKSUM T/P P113 STEERING HAZARD P
T44,P44 WRONG RAM MEMORY T/P P114 HEIGHT ZERO POS. P
T45,P45 SOFTWARE ERROR T/P P115 HEIGHT ENC. LOCK P
T46,P46 CURRENT GAIN T/P P116 LIFT/LOWER LIMIT P
T47,P47 WRONG 0 VOLTAGE T/P P117 REACH IN LIMIT P
T48,P48 PROG VACC NOT OK T/P
T241
T53,P53 STBY I HIGH T/P DATA ACQUISITION T/P
P241
T60,P60 CAPACITOR CHARGE T/P T243
T65,P65 MOTOR TC START T/P NO CAN MSG. T/P
P243
T66,P66 BATTERY LOW T/P T245
WRONG SET BAT. T/P
T71,P71 MOTOR SHUTDOWN T/P P245
T72,P72 MOTOR STALL T/P T249
THERMIC SENS. KO T/P
T74,P74 DRIVER SHORTED T/P P249
T75,P75 CONTACTOR DRIVER T/P

SM 931 Control Troubleshooting • 19-4-2

 Group 19, Motor Controls

2. EPS(Steering) Controller
Fault Fault
Fault Name Control Fault Name Control
Code Code
E20 EPS NOT ALIGNED EPS E149 WAITING FOR TRAC EPS
E21 MICRO SLAVE #3 EPS E150 DIR. NOT CONIFIG EPS
E22 POSITION ERROR EPS E162 SL CENTERING EPS
E23 SERIAL ERROR #1 EPS E163 MOTOR TEMPERAT EPS
E24 MICRO SLAVE #4 EPS E164 MOTOR LOCKED EPS
E25 SLAVE COM. ERROR EPS E165 STEPPER MOT. MISM EPS
E26 NO SYNC EPS E166 CLOCK PAL NOT OK EPS
E27 CURRENT GAIN EPS E167 MICRO SLAVE #8 EPS
E28 FB SENS LOCKED EPS E168 INPUT ERROR #1 EPS
E29 STEER SENSOR KO EPS E169 CAN BUS KO SL EPS
E120 HIGH CURRENT EPS E170 SL EPS NOT ALL EPS
E121 POWER FAILURE #1 EPS
E122 POWER FAILURE #2 EPS
E123 POWER FAILURE #3 EPS
E124 STBY I HIGH EPS 3. Valve Controller (MHYRIO-CB)
E125 D LINE SENSOR KO EPS
Fault
E126 Q LINE SENSOR KO EPS Fault Name Control
Code
E127 EEPROM KO EPS
M8 WATCHDOG MhyrioCB
E128 VMN NOT OK EPS
M13 EEPROM KO MhyrioCB
E129 HIGH TEMPERATURE EPS
M19 HI SIDEDRIVER KO MhyrioCB
E130 DATA ACQUISITION EPS
M20 EVPG1 DRIVER KO MhyrioCB
E131 LOGIC FAILURE #1 EPS
M21 EVPG2 DRIVER KO MhyrioCB
E132 LOGIC FAILURE #2 EPS
M22 EVPG3 DRIVER KO MhyrioCB
E133 LOGIC FAILURE #3 EPS
M23 EVPG4 DRIVER KO MhyrioCB
E134 LOGIC FAILURE #4 EPS
M24 EVP DRIVER KO MhyrioCB
E135 KS CLOSED EPS
M30 EV DRIVER KO MhyrioCB
E136 KM CLOSED EPS
M31 EVPG1 DRIV SHORT MhyrioCB
E137 KS OPEN EPS
E138 KM OPEN EPS M32 EVPG2 DRIV SHORT MhyrioCB
E139 MICRO SLAVE EPS M33 EVPG3 DRIV SHORT MhyrioCB
E140 JERKING FB EPS M34 EVPG4 DRIV SHORT MhyrioCB
E141 F.B OUT OF RANGE EPS M35 EVP DRIVER SHORT MhyrioCB
E142 MICRO SLAVE KO EPS M36 WAITING FOR PEV MhyrioCB
E143 ENCODER ERROR EPS M39 UNDER VOLTAGE MhyrioCB
E144 BAD ENCODER SIGN EPS M40 FF VALVES MhyrioCB
E145 GAIN EEPROM KO EPS M74 EV DRIVER SHORT MhyrioCB
E146 STEER HAZARD EPS M76 COIL SHORTED MhyrioCB
E147 WAITING DATA EPS M243 CAN BUS KO MhyrioCB
E148 CAN BUS KO EPS M245 WRONG SET BAT. MhyrioCB

SM 931 Control Troubleshooting • 19-4-3

 Group 19, Motor Controls

Fault Code Charts

1. Traction/ Pump Controller

Code Fault Name Fault Cause & Troubleshooting
Cause : No input from seat switch. When truck is moving, the seat sw opened.

Troubleshooting :
T1 SEAT SW OPEN - Controller detects the seat switch is open during operation.
- Check the seat switch wiring and connection.
- Check for inoperative seat switch.
Cause : This alarm occurs when the A/D conversion of the analog inputs gives
frozen value, on all of the converted signals, for more than 400msec. The goal
T2 of this diagnosis is to detect a failure of the A/D converter or a problem in the
ANALOG INPUT code flow that omits the refreshing of the analog signal conversion.
P2
Troubleshooting : If the problem occurs permanently it is necessary to substi-
tute ACE logic board.
Cause : The hardware circuits which manages short circuits protection of LC
T3 and EB/AUX coils has a problem.
COIL SHORT HW KO
P3 Troubleshooting : This type of fault is not related to external components :
replace the ACE logic board.
Cause : The safety out driver is shorted.

T4 SAFETY OUTPUT, Troubleshooting :

P4 FAN OUTPUT - Check if there is a short or a low impedance pull-down between SAFETY
OUT (CAN#19) and –BATT.
- The driver circuit is damaged in the logic board, which has to be replaced.
Cause : Accelerator CPOT voltage is lower than VACC Max, voltage while
the traction enable switch is open.

T5 Troubleshooting :
VACC OUT RANGE - This fault indicates that the accelerator voltage is 1 volt lower than the maxi-
P5
mum value programmed by PROGRAM VACC function.
- The potentiometer is not correctly calibrated.
- The potentiometer is defective.
Cause : There is an error on the choice of the parameters of the slip profile.
T7
SLIP_PROFILE Troubleshooting :
P7
Check in the hardware setting menu the value of those parameter.
Cause : At start-up the watch dog signal is already active before the software
has generated it. At stby or running condition the watch dog signal is not
T8 active. (in alarm status)
WATCHDOG#1
P8 Troubleshooting : The WD hardware circuit or microcontroller output port
are damaged. In both cases no external component are involved.
Replace the logic board.

SM 931 Control Troubleshooting • 19-4-4

 Group 19, Motor Controls

Code Fault Name Fault Cause & Troubleshooting

Cause : At start-up the watch dog signal is already active before the software
has generated it. At stby or running condition the watch dog signal is not
T9 active. (in alarm status)
WATCHDOG#
P9 Troubleshooting : The WD hardware circuit or microcontroller output port
are damaged. In both cases no external component are involved.
Replace the logic board.
Cause : The traction is waiting for the display enable.
T10 WAITING DISPLAY
Troubleshooting : Please check display wire connection.
Cause : The driver of the electro mechanic brake/ auxiliary electro valve coil
is shorted.
T11 Troubleshooting :
AUX DRIVER SHORTED
P11 - Check if there is a short or a low impedance pull-down between NEB/NAUX
(CNA#18) and –BATT.
- The driver circuit is damaged in the logic board, which has to be replaced.
Cause : The safety input is opened and accordingly the MC is opened and EB/
AUX OUT coil is driven.
T12
SAFETY INPUT
P12 Troubleshooting : Check the CAN#11 input. If it is connected to -Batt and the
alarm is generated then there is a fault in the SAFETY IN hardware circuit.
Replace the logic board.
Cause : It’s due to a HW or SW defect of the non-volatile embedded memory
supporting the controller parameters. This alarm does not inhibit the machine
operations, but the truck will work with the default values.
T13
EEPROM KO Troubleshooting : Try to execute a CLEAR EEPROM operation (refer to
P13 Console manual). Switch the key off and on to check the result.
If the alarm occurs permanently, it is necessary to replace the controller.
If the alarm disappears, the previously stored parameters will have been
replaced by the default parameters.
Cause : When the controller temperature is greater than 85°C.
T14 The maximum current decraese proportionally with the temperature increases
TH. PROTECTION from 85°C up to 105°C. At 105°C the current is 0Amps.
P14
Troubleshooting : It is necessary to improve the controller cooling.
Cause : Short circuit of EB/AUX coils connected to CNA#18 output.
T15
AUX COIL SHORT Troubleshooting : The typical root cause is in the harness or in the load coil.
P15
Check the connections between the controller output and the load.
Cause : The EB/AUX coil driver is not able to drive the load.
T16 The device itself or its driving circuit is damaged.
AUX DRIVER OPEN
P16 Troubleshooting : This type of fault is not related to external components;
replace the ACE2 logic board.

SM 931 Control Troubleshooting • 19-4-5

 Group 19, Motor Controls

Code Fault Name Fault Cause & Troubleshooting

Cause : Hardware problem in the logic card circuit for high current (overload)
T17 protection.
LOGIC FAILURE #3
P17 Troubleshooting : This type of fault is not related to external components, so,
when it is present it is necessary to replace the ACE logic board.
Cause :
Fault is in the hardware section of the logic board which manages the phase’s
T18 voltage feedback.
LOGIC FAILURE #2
P18 Troubleshooting :
This type of fault is not related to external components, so when it happens it is
necessary to replace the ACE2 logic board.
Cause : This fault is displayed when the controller detects an over voltage or
under voltage condition. In 48V controller over voltage threshold is 65V,
under voltage threshold is 11V.
Troubleshooting :
Troubleshooting of fault displayed at start-up or in standb:
in these cases it is very likely the fault is due to an under voltage, so it is sug-
gested to check:
- Key input signal down-going pulses (below under voltage threshold) due to
external loads, like DC/DC converters starting-up, relays or contactor
switching, solenoids energizing / de-energizing.
- Check the connection of power cables to the battery terminal, positive and
T19 negative, to MC and to controller +Batt and –Batt, which must be screwed
LOGIC FAILURE #1
P19 with a torque comprised in the range 13Nm÷15Nm.
- If no voltage transient is detected on the supply line and the alarm is present
every time the key is switched ON, the failure is probably in the controller
hardware, so it is necessary to replace the logic board.
Troubleshooting of fault displayed during motor driving:
in this case it can be an under voltage or an over voltage condition.
- If the alarm happens during traction acceleration or driving hydraulic func-
tions, it is very likely it is an under voltage condition; check battery charge
condition, power cable connection.
- If the alarm happens during release braking, it is very likely it is due to over
voltage condition; check line contactor contact, battery power cable connec-
tion.

SM 931 Control Troubleshooting • 19-4-6

 Group 19, Motor Controls

Code Fault Name Fault Cause & Troubleshooting

Cause :
1. Start-up test.
Before switching the LC on, the software checks the power bridge: it turns on
alternatingly the High side Power Mosfets and expects the phases voltage to
increase toward the rail capacitor value. If the phases voltage is less than 66%
of the rail capacitor voltage, this alarm occurs.
2. Motor running test.
When the motor is running, power bridge is ON, the motor voltage feedback is
tested; if it is lower than commanded value (a window of values are consid-
ered) fault status is entered.

T30 Troubleshooting :
VMN LOW If the problem occurs at start up (the LC does not close at all), check.
P30
- Motor internal connections. (ohmic continuity)
- Motor power cables connections.
- Motor leakage to truck frame.
- If the motor connections are OK, the problem is inside the controller, replace it.
If the alarm occurs during motor running, check.
- Motor connections.
- If motor phases windings/cables have leakages towards truck frame.
- That the LC power contact closer properly, with a good contact.
- If no problem are found on the motors, the problem is inside the controller,
replace it.
Cause :
1. Before switching the LC on, the software checks the power bridge: it turns
on alternatingly the Low side Power Mosfets and expects the phases voltage
to decrease down to -BATT. If the phases voltage is higher than 10% of
nominal battery voltage, this alarm occurs.
2. This alarm may occur also when the start up diagnosis is overcome, and so
the LC is closed. In this condition, the phases’ voltages are expected to be
lower than 1/2 Vbatt. If it is higher than that value, fault status is entered.

Troubleshooting :
T31
VMN HIGH If the problem occurs at start up (the LC does not close at all), check.
P31
- Motor internal connections. (ohmic continuity)
- Motor power cables connections.
- If the motor connection are OK, the problem is inside the controller, replace it.
If the problem occurs after closing the LC (the LC closed and then opens back
again), check.
- Motor connections.
- If motor phases windings/cables have leakages towards truck frame.
- If no problem are found on the motors, the problem is inside the controller,
replace it.

SM 931 Control Troubleshooting • 19-4-7

 Group 19, Motor Controls

Code Fault Name Fault Cause & Troubleshooting

T33 Cause : When truck is idle more than " IDLE TIME SEAT " parameter.
IDLE TIME
P33 Troubleshooting : The error disappears sit on the seat.
Cause :
Before driving the MC coil, the controller checks if the contactor is stuck.
The controller drives the bridge for some tens milliseconds, trying to discharge
T37 the capacitors bank. If the capacitor voltage does decrease by 20% of the key
CONTACTOR CLOSED voltage the alarm is generated.
P37
Troubleshooting :
It is suggested to verify the power contacts of LC :
to replace the LC is necessary.
Cause :
The main contactor coil has been driven by the controller, but the contactor
does not close.
T38 Troubleshooting :
CONTACTOR OPEN
P38 - It could be a problem of the contacts in the MC that are not working (does not
pull-in), try replacing the MC.
- If the contactors of MC are working correctly than the problem is in the con-
troller, replace it.
Cause : This fault is displayed when the controller detects a low logic level of
Key-Off signal during Start-Up diagnosis.

Troubleshooting :
- Key input signal down-going pulses (below under voltage threshold) due to
external loads, like DC/DC converters starting-up, relays or contactor
T39
KEY OFF SHORT switching, solenoids energizing / de-energizing.
P39 - Check the connection of power cables to the battery terminal, positive and
negative, to MC and to controller +Batt and –Batt, which must be screwed
with a torque comprised in the range 13Nm÷15Nm.
- If no voltage transient is detected on the supply line and the alarm is present
every time the key is switched ON, the failure is probably in the controller
hardware, so it is necessary to replace the logic board.
Cause :
1) Hardware problem in the logic card circuit for MC driver management.
2) Hardware problem in the logic card circuit for power section management.
T40
HARDWARE FAULT Troubleshooting :
P40 1) This type of fault is not related to external components, so, when it is pres-
ent it is necessary to replace the ACE logic board.
2) This type of fault is not related to external components, so, when it is pres-
ent it is necessary to replace the ACE logic board.

SM 931 Control Troubleshooting • 19-4-8

 Group 19, Motor Controls

Code Fault Name Fault Cause & Troubleshooting

Cause : After Key-on the software verifies the integrity of program stored in
the flash memory, if the verify has a negative result this alarm is generated.
T43
FLASH CHECKSUM Troubleshooting : The problem is in the microcontroller flash memory, which
P43 could be damaged, or in the program stored inside, which could be corrupted.
Try to program the logic again, if the alarms is still signalled the problem is in
the microcontroller. Replace the ACE logic board.
Cause :
The algorithm implemented to check the main RAM registers finds a wrong
T44
WRONG RAM MEMORY contents: the register is “dirty”. This alarm inhibit the machine operations.
P44
Troubleshooting : Try to switch the key off and then on, if the alarm is still
present replace the ACE2 logic board.
T45 Cause : Only when “DEBUG MODE” parameter is ON.
SOFTWARE ERROR
P45 Troubleshooting : Can Bus off or some can messages has been lost.
Cause :
T46 The Maximum current gain parameters are at the default values, which means
CURRENT GAIN the maximum current adjustment procedure has not been carried out yet.
P46
Troubleshooting : Ask the assistance of a Zapi technician to do the correct
adjustment procedure of the current gain parameters.
Cause :
At start-up the high resolution VMN feedback is not comprised in a permitted
window of values centred around 2,5V. The circuit is damaged in the controller.

Troubleshooting :
T47
WRONG 0 VOLTAGE It is suggested to check.
P47 - Motor internal connections. (ohmic continuity)
- Motor power cables connections.
- Motor leakage to truck frame.
- If the motor connections are OK, the problem is inside the controller, replace
the logic board.
T48
PROG VACC NOT OK Not used.
P48
Cause : The current transducer or the current feedback circuit is damaged in
T53 the controller.
STBY I HIGH
P53 Troubleshooting : This type of fault is not related to external components so,
when it is present, it is necessary to replace the controller.

SM 931 Control Troubleshooting • 19-4-9

 Group 19, Motor Controls

Code Fault Name Fault Cause & Troubleshooting

Follows the charging capacitor system :

Cause : When the key is switched ON, the inverter tries to charge the power
T60 capacitors through a series of a PTC and a power resistance, and check if the
CAPACITOR CHARGE capacitor are charged within a timeout. If the capacitor voltage measured is
P60 less than 20% of the nominal battery voltage, an alarm is signalled; the main
contactor is not closed.

Troubleshooting :
- There is an external load in parallel to capacitor bank, which sinks current
from the controller capacitors pre-charging circuit, thus preventing the caps
from charging. Check if a lamp or a dc/dc converter or an auxiliary load is
placed in parallel to capacitor bank.
- The charging resistance or PTC is opened; insert a power resistance across
line contactor power terminals; if the alarm disappears, it means the control-
ler internal charging resistance is damaged.
- The charging circuit has a failure, inside the controller.
- There is a problem in the controller power section.
Cause : When motor temperature is over than " MOTOR TC START " parameter.
T65
MOTOR TC START
P65 Troubleshooting : To reduce the heat of the motor surface if motor surface is
not heated, must be checked motor thermic sensor.
T66 Cause : When voltage battery is under minimun voltage.
BATTERY LOW
P66 Troubleshooting : Need to charging the battery.
Cause : The traction stopped because of a too high temperature on the motor.
T71
MOTOR SHUTDOWN
P71 Troubleshooting : To reduce the heat of the motor surface if motor surface is
not heated, must be checked motor thermic sensor.
Cause : The controller is trying to move the motor but the motor seems stuck.
There could be also a problem with the encoder.
T72 Troubleshooting :
MOTOR STALL
P72 - Check both electrical and mechanical encoder functionality.
- Check all connections between the controller and the encoder.
- If the problem still present try to replace the encoder.

SM 931 Control Troubleshooting • 19-4-10

 Group 19, Motor Controls

Code Fault Name Fault Cause & Troubleshooting

Cause : The driver of the main contactor coil is shorted.

T74 Troubleshooting :
DRIVER SHORTED - Check if there is a short or a low impedance pull-down between NMC
P74
(CNA#16) and –BATT.
- The driver circuit is damaged in the logic board, which has to be replaced.
Cause : The MC coil driver is not able to drive the load.
The device itself or its driving circuit is damaged.
T75
CONTACTOR DRIVER Troubleshooting :
P75
This type of fault is not related to external components:
replace the ACE2 logic board.
Cause :
This alarm occurs when there is a short circuit of the MC coils connected to
CNA#16 output. After the overload condition has been removed, the alarm
exits automatically by releasing and then enabling a travel demand.
T76 Troubleshooting :
MC COIL SHORT
P76 - The typical root cause for this error code to be displayed is in the harness or
in the load coil. So the very first check to carry out concerns connections
between controller outputs and loads.
- In case no failures/problems have been found externally, the problem is in the
controller, which has to be replaced.
Cause : The truck reached the maintenance working hours.
T77 MAINTENANCE HOUR Troubleshooting : Need to change maintenance reset value form off to on and
key off and on. It will be change on to off automatically after key on.
Cause : The test is made at key-on and immediately after that both the travel
demands have been turned off. This alarm occurs if the ACCELERATOR
reading in the TESTER menu’ is 1,0V higher than PROGRAM VACC min
T78 acquisition when the accelerator is released.
VACC NOT OK
P78 Troubleshooting : Acquire the maximum and minimum potentiometer value
through the PROGRAM VACC function. If the alarm is still present, check the
mechanical calibration and the functionality of the potentiometer. If the alarm
is not disappeared the failure is in the ACE logic board, replace it.
Cause : Wrong traction and pump request sequence.
This fault indicates an incorrect starting sequence.

Troubleshooting :
- If SRO FUNCTION is active, every time work is stopped the operator must
T79 put the truck in neutral.
INCORRECT START (SRO) - If forward, reverse or seat switch is active when key switch is turned on.
P79
- If Acce. pedal, deadman switch or HYD lever is active when key switch is
turned on.
- If Acce. pedal, deadman switch is active before FWD, RVS switch is pressed.
- If forward, reverse closed without seat switch input..
- If the fault persist after checking the wiring.

SM 931 Control Troubleshooting • 19-4-11

 Group 19, Motor Controls

Code Fault Name Fault Cause & Troubleshooting

Cause : Forward and Backward is activated at the same time.

Troubleshooting :
T80 FORW + BACK - Processor is continuously checking for a request for forward and reverse at
same time.
- Check forward and reverse switch.
T81 Cause : The output of the motor thermal sensor is out of range.
SENS MOT TEMP KO
P81 Troubleshooting : Check the sensor ohmic value and the sensor wiring.
Cause : This fault is signalled in following conditions: the frequency supplied
to the motor is higher than 40 Hz and the signal feedback from the encoder has
a jump higher than 40 Hz in few tens mSec. This condition is related to a mal-
functioning of the encoder.
Troubleshooting :
T82 - Check both the electric and the mechanical encoder functionality, the wires
ENCODER ERROR crimping.
P82
- Check the encoder mechanical installation, if the encoder slips inside its com-
partment raising this alarm condition.
- Also the electromagnetic noise on the sensor bearing can be a cause for the
alarm. In these cases try to replace the encoder.
- If the problem is still present after replacing the encoder, the failure is in the
controller.
Cause : Truck overloaded.
P83 OVERLOAD Troubleshooting :
The controller detects the load is overloaded, check the load & Sensor.
Cause : Load sensor out of range.
P84 LOAD SENS. ERROR
Troubleshooting : Check the load sensor and try to teach the sensor again.
T85 Cause : Truck waiting pump or vice versa.
WAITING FOR NODE
P85 Troubleshooting : Check the load sensor and try to teach the sensor again.
T86 SEQUENCE FAULT Not used.
Cause : MAX/MIN LIFT parameters are not correct.
P90 ACQUIRE LIFT Troubleshooting : Calibrate lift analog sensor.
If after calibration alarm persist, checkt the lift analog sensor.
Cause : MAX/MIN TILT parameters are not correct.
P91 ACQUIRE TILT Troubleshooting : Calibrate tilt analog sensor.
If after calibration alarm persist, checkt the tilt analog sensor.
Cause : MAX/MIN S/S parameters are not correct.
P92 ACQUIRE S/S Troubleshooting : Calibrate S/S analog sensor.
If after calibration alarm persist, checkt the S/S analog sensor.
Cause : MAX/MIN AUX parameters are not correct.
P93 ACQUIRE AUX Troubleshooting : Calibrate AUX analog sensor.
If after calibration alarm persist, checkt the AUX analog sensor.

SM 931 Control Troubleshooting • 19-4-12

 !"#$%&'(%)"*"!%+",*!"-.

Code Fault Name Fault Cause & Troubleshooting

Cause : Error that Mhyrio send via can when it is in alarm.
P94 MHYRIO IN ALARM
Troubleshooting : Check alarm code in Mhyrio controller.
Cause :
The voltage on A3 (PAUX) is too low, compared to the battery voltage.
P95 LIFT OUT OF RNG.
Troubleshooting : Please check the wiring.
On A3 there should be a positive voltage.
Cause : TILT out of range.
P96 TILT OUT OF RNG.
Troubleshooting : Check the Tilt sensor and try to teach again.
Cause : AUX out of range.
P97 AUX OUT OF RNG.
Troubleshooting : Check the AUX sensor and try to teach again.
Cause : S/S out of range.
P98 S/S OUT OF RNG.
Troubleshooting : Check the S/S sensor and try to teach again.
Cause : MAX/MIN REACH parameters are not correct.
P99 ACQUIRE REACH Troubleshooting : Calibrate Reach analog sensor.
If after calibration alarm persist, checkt the lift analog sensor.
Cause : REACH out of range.
P100 REACH OUT OF RNG
Troubleshooting : Check the Aux 1 sensor and try to teach again.
Cause : The traction controller does not receive the display CAN messages.
T101
CAN BUS KO DISP. Troubleshooting : Check the wiring.
P101
If it is ok, the problem is on the display, which must be replaced.
Cause : This is warning.
When drive wheel reached +90 or -90 position at the 180° steering function.
P113 STEERING HAZARD
Troubleshooting : Turn the steering wheel in the opposite direction.
It will be disappears.
Cause : When height encoder need to get zero position.
P114 HEIGHT ZERO POS. Troubleshooting :
Mast need to lowering and reset height reset switch to disappears the error.
Cause : When height encoder is lock.
P115 HEIGHT ENC. LOCK
Troubleshooting : Check height encoder wire and sensor assy.
Cause : Mast lift limit switch is detected than Mast lift is requested and can
not move more without override switch .
P116 LIFT/LOWER LIMIT Mast lower limit switch is detected than Mast lower is requested and can not
move more without override switch.
Troubleshooting : This is warning alarm.
Cause : Mast lower limit switch is detected than Mast reach in is requested
P117 REACH IN LIMIT and can not move reach in without override switch.
Troubleshooting : This is warning alarm.

/)%'0& +",*!"-%1!"#2-3.4""*5,6%7%&'898&0
 Group 19, Motor Controls

Code Fault Name Fault Cause & Troubleshooting

T241 Cause : Need current data acquisition.
DATA ACQUISITION
P241 Troubleshooting : Need to finish acquistion.
Cause : The traction controller is not receiving the CAN messages from one of
T243 the other nodes. (node number is displayed)
NO CAN MSG.
P243 Troubleshooting :
Please check the can bus wiring and the status of the missing node.
T245 Cause : The set battery selected is not correct.
WRONG SET BATTERY
P245 Troubleshooting : Check battery voltage.
Cause : The value of thermic sensor are out of range.
T249
THERMIC SENS. KO Troubleshooting :
P249
Check thermic sensor wire and connection, check thermic sensor assy.

SM 931 Control Troubleshooting • 19-4-14

 Group 19, Motor Controls

2. EPS (Steering) Controller

Code Fault Name Fault Cause & Troubleshooting
Cause : This is a real alarm that cut off the traction.
It occurs at the initial alignment if the straight-ahead condition is not matched
E20 EPS NOT ALIGNED
within 6sec. Throughout this 6 secs delay, the steer is not activated yet, the
safety relays are open and the traction is stopped.
Cause : Mismatch set-point calculation between MASTER and SLAVE.
E21 MICRO SLAVE #3
Troubleshooting : Internal fault.
Cause :
This alarm occurs for an error in the redundant test of the feedback sensors.
1) When the feedback potentiometer is used together with the feedback
encoder, the angle of the steered wheel is measured with both of them:
FEEDBACK ENC and FEEDBACK POT in the tester menu are expected to
be equal. When they are different more than 20 degrees this alarm occurs
(SET MAX FB POT–SET MIN FB POT corresponds to 180 degrees).
2) When the feedback encoder is used together with toggle switches, this alarm
occurs if the sector (toggles switches configuration) and the encoder
counting are not matched. The sector is provided via the FEEDBACK
E22 POSITION ERROR SECTOR reading in the tester menu; the encoder counting is provided via
the WHEEL ANGLE reading in the tester menu. In particular. (in case of
two toggle switches)

Troubleshooting :
Check the potentiometer connected to CNB#6 is right working.
If toggle switches are connected to CNA#2 and CNA#3, verify they are right
working and the setting AUX FUNCTION 11 is correct.
Verify also the sensor bearing in the motor (encoder) has not a slip (the sensor
bearing has two rings: one is connected to the rotor shaft; the other is
connected to the motor frame. Check these two rings are strictly connected to
their structure without slip.
Cause : Main uC and Slave uC communicate via a local serial interface.
This alarm occurs when the slave uC does not receive thecommunication from
E23 SERIAL ERROR #1 the main uC through this serial interface.

Troubleshooting : It is necessary to replace the controller.

Cause :
It occurs in one of the following conditions :
(Open loop application only) If the slave uC detects the stator voltage phasor
rotates in the opposite direction respect to the sign of the stepper motor speed,
this alarm occurs.
E24 MICRO SLAVE #4
(Closed loop application only) If the slave uC detects the stator voltage phasor
rotates in the opposite direction respect to the commanded position, this alarm
occurs.

Troubleshooting : It is necessary to replace the controller.

SM 931 Control Troubleshooting • 19-4-15

 Group 19, Motor Controls

Code Fault Name Fault Cause & Troubleshooting

Cause : Main uC and Slave uC communicate via a local serial interface.
This alarm occurs when the main uC does not receive the communication from
E25 SLAVE COM. ERROR the slave uC through this serial interface.

Troubleshooting : It is necessary to replace the controller.

Cause : Every 16msec, inside the code cycle, the main uC rises and then
lowers an input for the slave uC (SYNC). When the slave uC detects no edge
for more than 100 msec on this input, this alarm occurs. This is just a watch
E26 NO SYNC dog function: when the main uC does not execute the code cycle it does not
update the SYNC signal and the slave uC cuts off the steer and traction.

Troubleshooting : It is necessary to replace the controller.

Cause : Current gain parameters are out of range.
The Maximum current gain parameters are at the default values, which means
E27 CURRENT GAIN the maximum current adjustment procedure has not been carried out yet.
Troubleshooting : Ask the assistance of a Zapi technician to do the correct
adjustment procedure of the current gain parameters.
Cause : Alarm fb pot locked.
Encoder signal is frozen also when steering motor is demanded for moving.
E28 FB SENS LOCKED Troubleshooting : Check if the encoder is right working.
Verify "ENC SPEED" value in TESTER MENU is frozen or not meanwhile
the steering motor is running.
Cause : This alarm occurs if the command potentiometer (CPOC1 on CNA#9
or CPOC2 on CNA#8) changes with a jerk larger than MAX SP SLOPE (see
12.4.6.3). This alarm is used to catch a discontinuity in the voltages of the
E29 STEER SENSOR KO
command potentiometer.

Troubleshooting : Change the twin pot.

Cause : This alarm occurs if the circuit to limit via hardware the current in the
motor is either always active at key-on or repeatedly active when the motor is
turning.
E120 HIGH CURRENT
Troubleshooting :
Check the motor is suited to work with the eps-ac0 (not oversized).
Otherwise it is necessary to replace the controller.
Cause : This alarm occurs when the current in the phase W of the motor is
zero and the motor is commanded for moving.

E121 POWER FAILURE #1 Troubleshooting : "Check the power fuse is OK.

Check the battery positive arrives to the controller.
Check the continuity of the wire in the phase W of the motor.
Otherwise it is necessary to replace the controller.

SM 931 Control Troubleshooting • 19-4-16

 Group 19, Motor Controls

Code Fault Name Fault Cause & Troubleshooting

Cause : This alarm occurs when the current in the phase U of the motor is zero
and the motor is commanded for moving.

E122 POWER FAILURE #2 Troubleshooting : "Check the power fuse is OK.

Check the battery positive arrives to the controller.
Check the continuity of the wire in the phase U of the motor.
Otherwise it is necessary to replace the controller.
Cause : This alarm occurs when the current in the phase V of the motor is zero
and the motor is commanded for moving.

E123 POWER FAILURE #3 Troubleshooting : "Check the power fuse is OK.

Check the battery positive arrives to the controller.
Check the continuity of the wire in the phase V of the motor.
Otherwise it is necessary to replace the controller.
Cause : This alarm occurs two ways:
1) In the initial rest state after key on, if the outputs of the current amplifiers
are not comprised in the window 2.2 to 2.8 Vdc.
E124 STBY I HIGH 2) After the initial diagnosis this alarm occurs when the outputs of the current
amplifiers at rest have a drift larger than ±0.15 V.

Troubleshooting : It is necessary to replace the controller.

Cause : This alarm occurs when the mean voltage on the Direct line of the
stepper motor (connection CNA#9) is not null : the voltage on every stepper
motor line is a sine wave with null mean voltage.
E125 D LINE SENSOR KO
Troubleshooting : Check the continuity of the stepper motor connections.
In particular the resistance between CNA#9 and the minus battery (with the
stepper motor at rest) is expected being very low (close to 30 ohms).
Cause : This alarm occurs when the mean voltage on the Quadrature line of
the stepper motor (connection CNA#8) is not null: the voltage on every stepper
motor line is a sine wave with null mean voltage.
E126 Q LINE SENSOR KO
Troubleshooting : Check the continuity of the stepper motor connections.
In particular the resistance between CNA#8 and the minus battery (with the
stepper motor at rest) is expected being very low (close to 30 ohms).
Cause : It occurs if a test to write and read one location in EEPROM fails.
The SW expects to read the written value. It occurs also when the hour counter
gives different values between the three redundant locations in which it is
E127 EEPROM KO recorded. It occurs also when the busy bit of the EEPROM does not rise within
12 msec.

Troubleshooting : It is necessary to replace the controller.

Cause : This alarm occurs in the initial rest state after key on if the outputs of
the motor voltage amplifiers are not in the window from 2.2 to 2.8 Vdc.
E128 VMN NOT OK
Troubleshooting : It is necessary to replace the controller.

SM 931 Control Troubleshooting • 19-4-17

 Group 19, Motor Controls

Code Fault Name Fault Cause & Troubleshooting

Cause : This alarm occurs if the temperature of the controller base plate
overtakes 75 degrees.
E129 HIGH TEMPERATURE
Troubleshooting : Improve the cooling of the controller;
otherwise it is necessary to replace the controller.
Cause : This alarm occurs when the acquiring the motor resistance or when
adjusting the parameters to compensate for the gain of the current amplifiers
E130 DATA ACQUISITION (maximum current factory adjusted).

Troubleshooting : Recycle the key.

Cause : This alarm occurs when the real voltage between phases W and U of
the motor is different from the desired.
E131 LOGIC FAILURE #1
Troubleshooting : It is necessary to replace the controller.
Cause : This alarm occurs when the real voltage between phases W and V of
the motor is different from the desired.
E132 LOGIC FAILURE #2
Troubleshooting : It is necessary to replace the controller.
Cause : This alarm occurs in the rest state if the output of the voltage amplifier
of the phase Vu-Vw have a drift larger than ±0.25 V.
E133 LOGIC FAILURE #3
Troubleshooting : It is necessary to replace the controller.
Cause : This alarm occurs in the rest state if the output of the voltage amplifier
of the phase Vw-Vv have a drift larger than ±0.25 V.
E134 LOGIC FAILURE #4
Troubleshooting : It is necessary to replace the controller.
Cause : This alarm occurs if the main uC detects the safety contact, of the
slave uC, closed prior to be commanded.

E135 KS CLOSED Troubleshooting : This alarm occurs if the connection CNA#4 (NK1) is
around a voltage of 12 Vdc when switching on the key. In fact, when the safety
contacts are open, NK1 is expected being connected to a minus battery voltage
(not 12 V). Search for a harness problem or replace the controller.
Cause : This alarm occurs at key on if the slave uC detects the safety contact,
of the main uC, closed prior to be commanded.

E136 KM CLOSED Troubleshooting : This alarm occurs if the connection CNA#5 (K1) is around
a voltage of 12 Vdc when switching on the key. In fact, when the safety
contacts are open, K1 is expected being connected to a battery voltage (not 12
V). Search for a harness problem or replace the controller.
Cause : This alarm occurs if the main uC detects the safety contact, of the
E137 KS OPEN slave uC, open when expected being closed.

Troubleshooting : It is necessary to replace the controller.

Cause : "This alarm occurs if the slave uC detects the safety contact, of the
main uC, open when expected being closed.
E138 KM OPEN
Troubleshooting : It is necessary to replace the controller.

SM 931 Control Troubleshooting • 19-4-18

 Group 19, Motor Controls

Code Fault Name Fault Cause & Troubleshooting

Cause : It occurs when the information on the status bus between the main uC
and the slave uC is frozen to the 0xFF value (the slave uC does not update the
E139 MICRO SLAVE status bus configuration).

Troubleshooting : It is necessary to replace the controller.

Cause : This alarm occurs if the feedback potentiometer (CPOT on CNB#6)
changes with a jerk larger than 0.3 V in 16 msec.
E140 JERKING FB This alarm is used to catch a discontinuity in the voltages of the feedback
potentiometer.

Troubleshooting : Change the feedback potentiometer.

Cause : This alarm occurs for a fault on the feedback potentiometer (CPOT on
CNB#6). This alarm occurs if CPOT exits the range from 0.3 Vdc to 4.7 Vdc.
E141 F.B OUT OF RANGE Troubleshooting : Check the connections of the feedback potentiometer.
This alarm occurs when one connection of the feedback potentiometer is
broken.
Cause : In stepper motor application, this alarm occurs if the main uC is
detecting a direction of the stepper motor not matched with the one that the
slave uC is detecting.
In closed loop application, this alarm occurs if the main uC is detecting a
E142 MICRO SLAVE KO direction of the steering error not matched with the one that the slave uC is
detecting.
Furthermore, this alarm occurs also if the main uC is detecting no steering
limitation meanwhile the slave uC is detecting e steering limitation.
Troubleshooting : It is necessary to replace the controller.
Cause : It occurs when ENCODER CONTROL is set ON and the real
frequency does not pursuit the commanded frequency.
E143 ENCODER ERROR Troubleshooting : This condition is several times due to either, a mismatching
between the Encoder resolution used in the SW and the real encoder
resolution, or a wrong connection between the two encoder channels.
Cause : Encoder wire is reversed.
E144 BAD ENCODER SIGN
Troubleshooting : Swap the encoder channels.
Cause : The parameters to compensate for the gain of the current amplifiers
(ADJUSTMENT #03 and ADJUSTMENT #04) are recorded in a not volatile
memory (eeprom) with a redundant handling. In fact every adjustment is
E145 GAIN EEPROM KO recorded in three eeprom locations. If the values in these three locations are
different in between this alarm occurs.
Troubleshooting : It is necessary to send the controller to Zapi to execute the
maximum current regulation.
Cause : This is just a warning to inform that the steering controller is limiting
the angle in the steering direction.
E146 STEER HAZARD No speed reduction occurs on the traction.
Troubleshooting : you cannot continue steer in that direction.
It is only a warning.

SM 931 Control Troubleshooting • 19-4-19

 Group 19, Motor Controls

Code Fault Name Fault Cause & Troubleshooting

Cause : This warning occurs only if CAN BUS is PRESENT.
At key-on the eps-ac0 asks to the traction controller to send a list of parameters
via CAN Bus. From the request until the parameters are correctly relieved, this
E147 WAITING DATA warning occurs. The steer is not activated yet, and the safety relays remain
open when this warning is present.
Troubleshooting : Check the can bus network between Traction and EPS.
Cause : This alarm occurs only when the setting CAN BUS is PRESENT.
Then the eps-ac0 must receive the event messages from the traction controller.
E148 CAN BUS KO If these messages lack more than about 1 sec, this alarm occurs.
Troubleshooting : Check the CAN Bus communication system and analyse
the frames from the traction controller to the steer controllers.
Cause : At key-on the eps-ac0 needs an assent from the traction controller to
close the safety contacts and to turn onto operational mode. Until this assent is
not relieved, this warning occurs. The steer is not activated yet and the safety
E149 WAITING FOR TRAC relays remain open when this warning is present.
Troubleshooting : Check if Traction is in alarm.
Check the can bus network between Traction and EPS.
Cause : STEER TIRE DIR.1 and STEER TIRE DIR.2 mismatch.
E150 DIR. NOT CONIFIG Troubleshooting : Mismatch between "STEER TIRE DIR.1" and "STEER
TIRE DIR.2" parameters.
Cause : Slave autocentering is not correctly performed.
E162 SL CENTERING
Troubleshooting : Internal fault.
Cause : This alarm occurs only when DIAG MOTOR TEMP is on and the
thermal sensor inside the motor measures a temperature higher than 150
degrees. It occurs also when trying to acquire the motor resistance with a
temperature in the motor higher than 150 degree.
E163 MOTOR TEMPERAT
(still with DIAG MOTOR TEMP to ON)

Troubleshooting : Check the thermal sensor in the motor is right working.

If it is, improve the cooling of the motor.
Cause : This alarm occurs if the current in the steering motor stays close to the
maximum current longer than 1 sec.
E164 MOTOR LOCKED Troubleshooting : Search for a mechanical problem locking the motor.
To make easier the fault catching, set DEBUG OUTPUT to level 11 (see
12.4.6.4).
Cause : This alarm occurs if the frequency and the amplitude of the voltages
from the stepper motor lines are mismatched in between (i.e. the voltage from
the D and Q line of the stepper motor have high amplitude but with very low
E165 STEPPER MOT. MISM frequency). In normal condition when the amplitude of the stepper motor lines
increases, the frequency of the stepper motor lines must increase too.

Troubleshooting : It is necessary to replace the controller.

SM 931 Control Troubleshooting • 19-4-20

 Group 19, Motor Controls

Code Fault Name Fault Cause & Troubleshooting

Cause : The main uC sends an analog signal towards the slave uC to reset the
slave uC on demand. When the slave uC detects this analog signal external to a
window from 2.2 to 2.8 and not in the range to generate the reset on demand,
E166 CLOCK PAL NOT OK
the slave uC raises this alarm.

Troubleshooting : It is necessary to replace the controller.

Cause : It occurs when the encoder counting of the main uC is not matched
E167 MICRO SLAVE #8 with the encoder counting of the slave uC.

Troubleshooting : It is necessary to replace the controller.

Cause : It occurs when the voltage on CNA#4. (NK1: Lower Potential)
Terminal of the Safety Contacts (see 7.6) is higher than 12 V before to turn the
safety contacts closed.

Troubleshooting :
E168 INPUT ERROR #1 When the safety contacts are open, the voltage on CNA#4 is expected to be
close to 0 Vdc and this is independent from whether the safety contacts are
connected to a plus battery or to a minus battery (see 7.6).
In the first case (safety contacts connected to a plus battery), when the safety
contacts are open, CNA#4 is connected to a minus battery through a load.
Only a harness mistake may connect NK1 to a higher than 12 V voltage.
Cause : Alarm can bus slave.
E169 CAN BUS KO SL
Troubleshooting : Internal CAN BUS fault.
Cause : Slave not aligned.
E170 SL EPS NOT ALL
Troubleshooting : Internal fault.

SM 931 Control Troubleshooting • 19-4-21

 Group 19, Motor Controls

3. Valve Controller (MHYRIO-CB)

Code Fault Name Fault Cause & Troubleshooting
Cause : The test is made in both running and standby.
It is a self-diagnosing test within the logic.
If an alarm should occur, replace the logic.
M8 WATCHDOG
Troubleshooting :
If fault is still persist when the Key Switch is re-cycled, replace the logic.
Cause : Fault in the area of memory where the adjustment parameters are
stored. This Alarm does not inhibit machine operation but operation goes on
with default values; if fault is still present when the Key Switch is re-cycled,
replace the logic. If the fault disappears, the previously stored Parameters will
M13 EEPROM KO
have been replaced by the default parameters.

Troubleshooting : Perform a clear eeprom.

If fault is still present when the Key Switch is re-cycled, replace the logic.
Cause : The high side driver which supply the valves coils positive is shorted
or open.
M19 HI SIDEDRIVER KO
Troubleshooting : Check the wiring of positeve supply valves.
If harness is ok, replace the controller.
Cause : One of the Group1 valve driver is open.
(does not close when it is commanded by the microcontroller)
M20 EVPG1 DRIVER KO
Troubleshooting : Check the wiring of the valve Group1.
If harness is ok, replace the controller.
Cause : One of the group2 valves drivers is open.
(does not close when it is commanded by the microcontroller)
M21 EVPG2 DRIVER KO
Troubleshooting : Check the wiring of the valve Group2.
If harness is ok, replace the controller.
Cause : One of the group3 valves drivers is open.
(does not close when it is commanded by the microcontroller)
M22 EVPG3 DRIVER KO
Troubleshooting : Check the wiring of the valve Group3.
If harness is ok, replace the controller.
Cause : One of the group4 valves drivers is open.
(does not close when it is commanded by the microcontroller)
M23 EVPG4 DRIVER KO
Troubleshooting : Check the wiring of the valve Group4.
If harness is ok, replace the controller.
Cause : One of the On/Off valves drivers is open.
(does not close when it is commanded by the microcontroller)
M24 EVP DRIVER KO
Troubleshooting : Check the wiring of the digital on/off valve.
If harness is ok, replace the controller.

SM 931 Control Troubleshooting • 19-4-22

 Group 19, Motor Controls

Code Fault Name Fault Cause & Troubleshooting

Cause : One of the On/Off valves drivers is open.
(does not close when it is commanded by the microcontroller)
M30 EV DRIVER KO
Troubleshooting : Check the wiring of the epv valve.
If harness is ok, replace the controller.
Cause : One of the GROUP1 valves drivers is shorted; check the external
connection, if it is ok the driver is probably damaged.
M31 EVPG1 DRIV SHORT
Troubleshooting : Check the wiring of the valve. Check if you find shorts in
the harness that bring GND to Group1 evp output.
If harness is ok, replace the controller.
Cause : One of the GROUP2 valves drivers is shorted; check the external
connection, if it is ok the driver is probably damaged.
M32 EVPG2 DRIV SHORT Troubleshooting : Check the wiring of the valve. Check if you find shorts in
the harness that bring GND to Group2 evp output.
If harness is ok, replace the controller.
Cause : One of the GROUP3 valves drivers is shorted; check the external
connection, if it is ok the driver is probably damaged.
M33 EVPG3 DRIV SHORT
Troubleshooting : Check the wiring of the valve. Check if you find shorts in
the harness that bring GND to Group3 evp output.
If harness is ok, replace the controller.
Cause : One of the GROUP4 valves drivers is shorted; check the external
connection, if it is ok the driver is probably damaged.
M34 EVPG4 DRIV SHORT Troubleshooting : Check the wiring of the valve. Check if you find shorts in
the harness that bring GND to Group4 evp output.
If harness is ok, replace the controller.
Cause : The single proportional valve driver is shorted; check the external
connection, if it is ok the driver is probably damaged.
M35 EVP DRIVER SHORT
Troubleshooting : Check the wiring of the valve. Check if you find shorts in
the harness that bring GND to evp output.
If harness is ok, replace the controller.
Cause : There isn't the valves positive power supply.
M36 WAITING FOR PEV
Troubleshooting : Check is traction closes Main Contactor.
Cause : This fault is signalled if an undervoltage condition is detected in the
MHYRIO power supply.
M39 UNDER VOLTAGE
Troubleshooting : Check the power supply wiring of the Mhyrio.
Cause : Flip-flop circuit, that manages on/off valve drivers short-circuit
protection does not reset in the correct way.
M40 FF VALVES The problem is probably in the hardware circuit.

Troubleshooting : Check the wiring of the valve.

Check if you find shorted valve coils. If harness is ok, replace the controller.

SM 931 Control Troubleshooting • 19-4-23

 Group 19, Motor Controls

Code Fault Name Fault Cause & Troubleshooting

Cause : One of the on/off valves driver is shorted; check the external
connection, if it is ok the driver is probably damaged.
M74 EV DRIVER SHORT Troubleshooting : Check the wiring of the valve.
Check if you find shorts in the harness that bring GND to valves output.
If harness is ok, replace the controller.
Cause : ON/OFF valves drives are protected against coil short circuit;
if a short is present across the coil, the flip-flop circuit is set and the alarm is
M76 COIL SHORTED signalled.

Troubleshooting : Check the wiring of the valve.

Check if you find shorted valve coils. If harness is ok, replace the controller.
Cause : There is a problem related to the CAN-BUS line.
The error is signalled if the MHYRIO controller does not receive any message
from the CAN-BUS line. First of all, check the wiring.
M243 CAN BUS KO If it is ok, the problem is on the logic board, which must be replaced.

Troubleshooting : Check the wiring.

If it is ok, the problem is on the logic board, which must be replaced.
Cause : This fault is signalled if the battery voltage is non consistent with the
set battery programmed in the 'set option' menu.
M245 WRONG SET BAT.
Troubleshooting : Check the voltage supply of the Mhyrio.
Check the battery settings in SET OPTION MENU.

SM 931 Control Troubleshooting • 19-4-24