Handicare Raptor, Service Manual, Page: 120 / 163

PG
DRIVES TECHNOLOGY
15
SP1A - D
IAGNOSTICS
SK73762/6
1 Introduction
The primary objective of this chapter is to assist service personnel in finding the likely
area of a detected fault within the whole scooter electrical system. It is important to
realize that even though the controller is signaling a fault, it may not be the controller
itself that is defective. This is because the controller is able to detect problems in
other electrical components (motors, batteries, solenoid brakes etc.) or, more
importantly, the wiring to them. When a controller has detected a fault, a system trip
is indicated.
This chapter covers diagnostics of scooters fitted with PG Drives Technology Solo, Egis
and S-Drive controllers. For a basic diagnostic capability it is not necessary to have a
programmer to use this guide, as all these controllers have a sophisticated level of
on-board diagnostics.
Using this guide, it is possible to define a trip as belonging to one of 10 types. Once
this type has been established, there are suggestions as to what the possible cause
may be.
This chapter should only be used to decide the starting point of your own diagnosis,
as it is possible for the controller to indicate a trip in another component even though
the controller itself may be defective. Nevertheless, experience has shown that
connectors and wiring are the major cause of scooter electrical problems, so it is
necessary to examine these more vulnerable areas first.
Diagnostics should only be conducted by healthcare
professionals with in-depth knowledge of PGDT electronic
controllers. An incorrect or badly effected repair could result
in an unsafe set-up of a scooter. PGDT accept no liability
for losses of any kind arising from an incorrect or badly
effected repair.
1.1 Diagnostics Process
For efficient and effective diagnosis the following basic steps should be taken.
• Establish the type of controller fitted to the scooter.
• Confirm there is a trip, or has been an intermittent trip. Refer to section 2.
• Establish the trip type. Refer to section 3.
• Refer to the trip table for the controller you are working with. Refer to Chapters
3, 4 & 5 dependant on controller type..
• Refer to the possible cause as indicated by the trip table, and carry out
recommended investigative and corrective action. Refer to Chapters 3, 4 & 5
dependant on controller type.