11
Programming
CONTROLLER DIAGNOSTIC TOOL (CDT)
FLD (FIELD) MISSING
If the speed controller is operating at a duty cycle of greater than 90% (almost full speed) and the field current is less
than 3 amps, a
field missing
fault is detected by the speed controller.
CAUTION
• A failed motor will ruin a controller. If a new controller is installed in a vehicle with a bad motor, the
bad motor will blow the field FET in the new controller. Always check the motor before replacing a
controller when a FLD Missing fault is shown.
What it means:
Not necessarily a controller issue.
What to do:
Check in this order: connections and continuity of orange and blue motor field wires, short in motor,
and then controller.
See External Motor Testing, Section 16, Page 16-1.
HW FAILSAFE
The armature drive FETs (field effect transistors) regulate the armature current. If the speed controller detects a failure
of the armature drive FETs or circuitry, a
hardware failsafe
fault is detected.
What it means:
A catastrophic failure internal to the controller on either the power board or the logic board.
What to do:
Check motor before replacing controller.
FAULT HISTORY
The
fault history
menu can be useful in determining the cause of a vehicle problem; however, the fault history alone
should not be the factor that determines when a component is replaced. Some faults detected by the speed controller
are not the result of a failed component, and are instead the result of vehicle operator error. If a fault appears in the
fault history
menu, the trained technician should attempt to determine when and where the fault has occurred. For
example, if the
motor stall
fault is present in the fault history, the trained technician may be able to determine the
location on the course where an operator has held the vehicle on a hill by using the accelerator pedal.
CLEAR FAULT HISTORY
After a repair has been made, the fault history should be cleared. This will enable the trained technician to properly
troubleshoot the vehicle in the future, in the event that another problem occurs. It is recommended that the fault history
be cleared in order to avoid the replacement of a component that caused a fault in the past, but has been replaced and
is now functioning correctly. For example, if the MCOR (Motor Controller Output Regulator) was disconnected and the
speed controller detected a fault code associated with the throttle, the fault history should be cleared so that any future
problem is not diagnosed incorrectly as a throttle problem.
See Fault History Folder on page 11-14.
PROGRAMMING
The
Programming
menu is accessed by using the arrow keys to highlight
Programming
and pressing the
Select
softkey to activate the menu.
The
Programming
menu selection allows the user to save and restore parameter settings files (.cpf files). These files
contain controller information and are saved to the internal memory or SD card. Once saved, they can be used for
future reference or emailed when the CDT or SD card is connected to a PC. For information on how to save and restore
these files, refer to the manual supplied with the CDT.
Page 11-22
2019 Precedent Villager 2 Maintenance and Service Manual
Summary of Contents for Precedent Villager 2
Page 2: ......
Page 395: ...ELECTRIC MAIN HARNESS Wiring Diagrams Electric Main Harness 25...
Page 396: ...Page intentionally left blank...
Page 398: ...Page intentionally left blank...
Page 399: ...GASOLINE MAIN HARNESS Wiring Diagrams Gasoline Main Harness 25...
Page 400: ...Page intentionally left blank...
Page 402: ...Page intentionally left blank...
Page 403: ...GASOLINE ENGINE HARNESS Wiring Diagrams Gasoline Engine Harness 25...
Page 404: ...Page intentionally left blank...
Page 412: ...NOTES...
Page 413: ......
Page 414: ......