Design and Implementation of An Expert Management System For Automobile Fault Detection and Diagnosis

DESIGN AND IMPLEMENTATION OF
AN EXPERT MANAGEMENT SYSTEM FOR

AUTOMOBILE FAULT DETECTION.
By
-----------
---------------
SUPERVISED BY
------------------
A PROJECT RESEARCH SUBMITTED TO THE

DEPARTMENT OF COMPUTERSCIENCE, ANAMBRA STATE
UNIVERSITY ULI IN PARTIAL FULFILMENT TO THE
AWARD OF BSc IN COMPUTER SCIENCE
MARCH, 2012
APPROVAL PAGE
This is to certify that this project written by ---------- with

Registration Number ------ has been approved by the
Department of Computer Science, Anambra State University
Uli, in partial fulfillment for the award of BSc in Computer
Science.
……………………………. ……………….
Date
(Project Supervisor).
……………………………. ……………….
Date
Head of Department
……………………………. ……………….
Dean Date
Faculty of Natural Science
……………………………. ……………….
External Supervisor Date
NOTE: These materials are meant to assist and guide you during your
project. Study it carefully and use the information in them to develop
your own new copy.
For more project topics and materials visit: http://www.classgist.com
Enquiries: http://www.classgist.com/contactus.aspx
DEDICATION
I dedicate this work to Almighty God.

ACKNOWLEDGEMENT
Very sincerely, my first greeting goes --------------------

your own new copy.
ABSTRACT
This project deals with the design and implementation of an
expert system for car faults diagnosis. The project is motivated
by the need to guide car owners and learners motor mechanics
in the maintenance and trouble shooting of motor problems
without having to resort to presumptions and conjectures.
Particularly, it is expected that the proposed design would
ensure that car owners have proper assistance in times of
crisis and what’s more will save them from the clutches of
exploitative roadside mechanics. For this purpose a rule- base
artificial intelligence (AI) technique was utilized to obtain
theoretical and practical expert system parameters, and then a
conceptual expert system was designed. The expert system
functioning is based on the database of car faults, symptoms
and their correction, which make up its knowledge base. The
new system was developed using visual basic 6.0 programming
language and access database. This language was chosen
because of its easy syntax and features for developing
windows based application.
TABLE OF CONTENTS
Title page i
Approval page ii
Dedication iii
Acknowledgement iv
Abstract v
Table of contents vi
CHAPTER ONE
1.0 Introduction 1
1.1 Background of the study 1
1.2 Problem statement 2
1.3 Objectives 3
1.4 Significance of the study 4
1.5 Scope of the study 5
1.6 Limitations 5
1.7 Methodology 5
CHAPTER TWO
2.1 Literature review 7
2.2 The Conceptual Structure of an Expert System 14
2.2.1 Problem Assessment 14
2.2.2 Knowledge Acquisition 15
2.2.3 Knowledge Representation 17
2.2.4 Verification 18
2.2.5 Validation 18
your own new copy.
2.3 Testing Expert System 19

2.4 MYCIN 21
CHAPTER THREE
System analysis and design 27
3.0 Introduction 26
3.1 Weakness of the Present System 28
3.2 Methodology 28
3.3 Knowledge acquisition 28
3.3.1 Domain Expert 29
3.3.2 Interview 29
3.3.3 Consultation 29
3.3.4 Diagnosis 32
3.3.5 Correction/ explanation 32
3.4 System Design 33
3.4.1 Rule based development method 34
3.4.2 Inference technique 36
3.4.3 Flowchart of the proposed program 38
3.5 Program design 39
3.5.1 High level model of the proposed system 40
CHAPTER FOUR
4.0 System implementation 41
4.1 Introduction 41
4.2 System requirement 42
4.3 Testing 42
4.4 Maintenance 43
4.5 Program Documentation 44
4.5.1 Sample input/output data formats 45
4.5.2 Loading the package 46
4.5.3 Exiting 47
CHAPTER FIVE
5.0 Summary, Recommendation and conclusion 48
5.1 Summary 48
5.2 Recommendation 49
5.3 Conclusion 49
References 66
Appendix I 75
Appendix II 58
your own new copy.
CHAPTER ONE
1.0 INTRODUCTION
In present time most households own at least one car.
This figure shows that a car is very important to people’s lives
as it completes the cycle of living.
This computer expert system is hoped to help those who
are in need of guides to deal with their cars problems. Although
it might not give a complete guide and help as a human expert,
namely mechanics, at least the expert system can give
temporary assistance to those who are in need of instant help,
as a result of the limitation of time and distance.
1.1 BACKGROUND OF THE STUDY

With the help of a car, movement from one place to
another has been made easy especially for those who are
always mobile in their jobs. Cars simplify our lives and make
time to be more valuable as we can save more time using the
car. But at the same time, people who own cars definitely don’t
want to have a problem with their cars as the troubleshooting
of a car can be a nightmare to them, especially women. Some
of those own a car individually don’t know how to deal with
their cars whenever it has a problem. All they know is to start
the engine, drag the clutch if it is not automatic, press the
paddy and break when they need to. An even the worse
situation is that they don’t even know how to fill the fuel tank,
and that is not good. They won’t know what to do when
something happens to their cars. All they can do at best is, call
the mechanic for help.
So, this computer expert system is hoped to help those
who are in need of guides to deal with their cars problems.
Although it might not give a complete guide and help as a
human expert, namely mechanics, at least the expert system
can give temporary assistance to those who are in need of
instant help, as a result of the limitation of time and distance.
1.2 STATEMENT OF THE PROBLEM

your own new copy.
In dealing with problems of a car and troubleshooting,

mechanics are those who can help to solve them. The use of a
computer expert system is beneficial in different ways. It gives
a temporary and instant guide to car owners in different
situations like:
 When mechanic support is unavailable
 When we are in a hurry
 When distance to mechanics location is far
 When mechanics diagnosis wrongly, etc.
1.3 OBJECTIVES OF THE STUDY

To develop an expert system on car maintenance and
troubleshooting that is capable of assisting car owners in
dealing with their cars problems and troubleshooting them
whenever time is limited and the human experts, also known
as mechanics is not available at that very time. The
development of the system surely has some significance to
humans especially those who own a car and to the system
developer as well. Among others, the system will perform the
following functions:
 It will conclude its diagnosis based on answers of the users
to specific question posed by the system to the user.
 It provides facility in order to take the user opinion on the
following: does the use agree with the system’s diagnosis?
Does the user disagree with the system’s diagnosis?
 It provides explanation, picture, why and fact facility.
 It stores the facts and the conclusion of the inference of the
system and the facts and the conclusion of the inference of
the user, for each case in data base.
 It processes the data base in order to extract rules, which
complete the knowledge base.
1.4 SIGNIFICANCE OF THE STUDY

The proposed system can help inexperienced mechanics
or drivers in diagnosing the fault of the car.
In addition, the system has the following benefits:
 Expert systems help in the improvement of productivity:
Having this system will enable mechanics to do more work in
less time.
 Expert system reduces the need for skilled mechanics: The
repairs of a car require a high level of expertise. With this
system, inexperienced mechanics can be guided to find the
fault.
 Expert systems capture the knowledge of company experts
who someday will retire, resign or die.
 Expert systems train newly lived employees to solve problem
the way experienced professionals do.
your own new copy.
 Expert system are not vulnerable to problems such as

fatigue, emotion and overwork, all of which plaque human
experts.
 Expert systems place expert knowledge into machine
readable form, where it can be summoned at any time.
 Expert systems give consistent result.
 Expert systems can complete some tasks quicker them a
human.
1.5 SCOPE OF THE STUDY

The expert system may contain certain limits and flaws,
as it is only a prototype. We commonly know that a car has
many parts on its body and even in the body itself. However,
the system will only deal with problems that are normally or
commonly found in the engine part of the car as the system is
just a prototype, which means the function will be expanded
through time. The system will also deal with only cars produced
from the year 2000 till date.
1.6 LIMITATION OF THE STUDY

TIME: Time frame for this work is short
 Finance as a student
 Limited literature in computer to assist the researcher
 Not much work has been done in this area of computer
science/ engineering.
1.8 DEFINITION OF TERMS

 Actuator: This is a device in a car that uses electricity to
do sort of automated mechanical movement such as
power door locks or a remote trunk opener.
 Car Sensor: This is a technological device that dictates
or senses a signal or a physical condition in a car.
 Car Diagnosis: Is the identification of the nature and
causes of problem in a car.
 Car Brain Box: This is an electronic device that
incorporates micro processors for the monitoring and
control of various functions in a vehicle.

your own new copy.
CHAPTER TWO
REVIEW OF RELATED LITERATURE
2.1 INTRODUCTION
The purpose of writing this literature review is to pass on
to the reader what knowledge and ideas have been established
on the topic and what their strengths and weaknesses are.
Literature review lets the researcher gain and demonstrates
skills like the ability to seek information and to scan the
literature efficiently using manual or computerized methods
and to identity useful articles and books. Before coming out
with the idea of developing this expert system for car faults
diagnosis which is an implementation of experts system, some
research had been done regarding the previous and current
technology of expert systems itself.
The research would go into reviewing the literature of
underlying concepts behind the development of several
applications of expert systems. This phase is quite important as
we got to know on how well expert system performs in their
ability of assisting and replacing the human expert as well as
the user, the result of researchers and reviews that have been
conducted help much in giving the idea and insight to the
development on the existing application of expert system to be
implemented in this system.
An automobile like any other machines is created to make
things easier for man as it serves his purpose for his
convenience. A car when purchased is usually in near perfect
working condition. However over time, due to continuous use,
neglect or wear or environmental influence the vehicle begins
to experience some fault. This can be the most stressful period
for most vehicle owners, especially those who don’t have any
idea on what to do.
There are also situation in which auto technicians are
either unavailable or costly to hire. A motorist with a broken
down vehicle on a long, empty stretch of road in the middle of
the night is unlikely to get any help from a mechanic. It would
also save a lot of money if vehicle owners could carry out
minor repairs on their cars themselves, and even if the
situation arises that the vehicle be taken to the repair shop,
the car owner could avoid being bamboozled if he or she has
an idea of the internet fault.
We have some testing equipment and procedures which
are necessary to any effective diagnosis of automobiles faults
example are;
 Digital Multi-Meter: It is use to test foro basic voltage
(alternate current and direct current) resistance,
frequency duty cycle, temperature etc. it is also
adequate for detecting electrical faults.
 Exhaust Gas Analyzer: It measure the types of gases
presented in the exhaust pipe (oxygen, carbon dioxide
and hydrocarbons). It is used to diagnose fault in
your own new copy.
ignition, fuelling and various mechanical engine

problems.
 Jump Lead: It provides emergency power to the
battery.
 Fuel Pressure Test Kit: IT measures fuel pressure up
to 7.0 bars.
 Vacum Gauge: It takes the pulse of the engine from a
connection to the inlet manifold and is useful for
diagnosing timing and mechanical faults.
 Spark Jumper: It use to checks for a spark from plugs
whilst cranking the engine.
Other tools are like spanners and pliers. Apart from
having all this testing equipments, there still some necessary
basic inspection, required by the car owners to undergo daily.
Such inspections are;
 To check the engine oil, level and condition
 To check coolant level and coolant system condition
 To check the automatic transmission fluid level and
condition.
 Check battery condition
 Check battery electrolyte level
 Check battery cables and connections
 Check fan belt condition and tension
 Remove spark plays and check the condition renew if
necessary.
 Look for cracks and sign of tracking
 Check the rotor condition and measure the resistance
where appropriate.
 Checks for freedom from vacuum leaks from the vacuum
hoses, inlet manifold, oil dipstick.
 Clean away accumulated sludge, and assure that the
hoses are clean.
 Check air filter condition renew if it is slight dirty
 Check exhaust system condition
 Check fuel system condition check for fuel leaks worn or
broker components.
 Visually inspect all connections, multi plugs and terminals.
Check for corrosion and loose or displayed terminals.
 Check the throttle body for a carbon build-up usually as a
result of fumes from the breathing system. The carbon
can cause of fumes from the breathing open throttle
which can cause idle, cursing and other running problems
carburetor clearing fluid usually cleans away the carbon
nicely.
Using a rule based approach a component expert system
can be developed to carry out a through diagnosis of
automobile engine faults, diagnosing the possible faults
associated with each symptom and a correctional procedure for
each of them. When we are talking of an expert system
technology we are referring to a “computer software system
your own new copy.
that emulates the decision making ability of a human expert”.

It diagnosis problems and gives advice on what the cause of
those problem are and can also give solution.
Townsend (2009) noted that an expert system is a
computer program that uses knowledge and reference
procedures to solve problems that are difficult enough to
require significant human expertise for their solution. Simply
stated expert systems are computer programs designed to
mimic the though and reasoning processes of a human expert.
Expert system can be developed for many kinds of applications
involving diagnosis prediction, interpretation and instruction
(Edmunds,2010 ). According to Townsend (2009) diagnosis still
remain the primary application computers. They are used in
application where the procedures or algorithms for the
problems do not exist or are poorly defined.
Today, better development tools are available and closer
interdisciplinary cooperation is resulting in agricultural
researchers gaining more insight into the theory and concepts
necessary to build effectives systems (crass Weller, 2011).
Several notable expert systems have developed in recent
years. For example, CALEX is an expert system which was
developed for the diagnosis of peach and nectarine disorder by
the University of California, (plant 2006) like most experts
systems, CALEX is rule based and uses certainty factors so that
the knowledge base consists of production rules in the form of
if, then statements. The inference engine pieces together
chains of rules in an attempt to reach a conclusion.
The knowledge base of the CALEX peaches and
nectarines, representing most of the disorders in California
(plant 2006) CITPATH, a computerized diagnostic key and
information system was developed to identity five major fungal
diseases of citrus foliage and fruit in Florida (Ferguson, 2005).
CITPATH also utilizes rule based approaches which provide
heretics- linked description and graphics displays of symptoms
with reference to chemical control methods. (Ferguson 2005).
The Penn state apple orchard consultant (PSAOC) is an
example of another type of expert system which has
demonstrated the advantage of using specialist from different
areas to develop large integrated modules.
Crass Weller (2009) observed that horticultural
applications presently developed include modules for weed
control, folia analysis interpretation and trickle irrigation
scheduling and visual diagnosis of nutrient deficiencies. VITIS,
a grape disease management expert system has also been
developed similarly in cooperation with specialist from
Pennsylvania, new York Ohio and Michigan. The VITIS model
was also used as a model for Austvit, an Australian viticulture
management expert system.
Travis (2002) observed that Austvit use the same logic in
the approach to decision and integrates viticulture
entomological and plant pathological decision making to arrive
your own new copy.
at an integrated recommendation (Edmunels, 2008, Liebowitz,

2008 plant 2009, sell 2009). The participation of a knowledge
expert one who bus received specialized training or gained
knowledge through years of experiences is required (Townsend
2007, Jones 2009). The knowledge must be captured and
stored in a manner that can be used to make decision. It
should require a human expert a limited…of time to solve. A
well developed system should be able to read world problems
and be able to communicate information to non- expert users
(plant,2009). Possibly the largest obstacles in developing
experts system is extracting knowledge from the human
experts and transferring into computer code. For this reason
the process of constructing an expert system is known as
knowledge engineering and the system builder is referred to as
knowledge engineer (Feigenbewin 2007). Expert system
development includes three phases: knowledge acquisition
knowledge representational and testing (liebowitz 2009) in the
following sections, these procedures are discussed in more
details.
2.2 THE CONCEPTUAL STRUCTURE OF AN EXPERT

SYSTEM
After reviewing the outcomes of the research the
fundamental and basic concept of expert system was then
identified in order to guide the brainstorming for determination
of problems domain. Once the problems domain is determined
it was used and set to be the title of the system development.
Beside that, through the researcher and reviews done all the
underlying concept of the expert system development was
recognized which includes the critical elements involved in the
development, the technology needed compatible software and
hardware as well as the issues of humans’ social life and
systems reliability.
2.2.1 Problem Assessment

Based on the concept of expert system acquired in the
conceptualization phase, the problem domain for the
development of the system was then determined. In this phase
the appropriateness of the problem was taken into
consideration as to make sure that it is suitable to be solved by
expert system.
Studies were conducted to determined the feasibility and
justification of the problem which include defining the overall
goals of the project. Other then that during this assessment
phase all the sources needed for the development was
identified as well as the principles requirements. It is structural
according to the following task
Task 1: Determined motivation of organization
Task 2: Identify candidate problems
Task 3: Perform feasibility study
Task 4: Perform cost/benefit analysis
your own new copy.
Task 5: Select the best project

Task 6: Write project proposal
2.2.2 Knowledge Acquisition

Expert system is all about applying human expertise into
computer verse, which is based grandly on the integration of
human knowledge with the system. Thus knowledge acquisition
is the heart of expert system. After the problem domain was
determine in the previous phase, the knowledge and
information based on the problem was then acquired.
Therefore the knowledge sources have also to be ascertained
which could be the experts in the domain itself. But in the
development of this expert system for car faults diagnosis
most of the information and knowledge gathered was acquired
from the internet, the sites that contain quite lots of
information on car or automotive maintenance and
troubleshooting by various experts namely mechanism.
At the early stage, the information gathered was general
and they key concept of car troubleshooting was unearned.
Later, information was gained from system testing to explore
more detailed information knowledge acquisition is a time
consuming process in which the knowledge engineer works
alongside the participating expert and extracts, structures and
organizes the information to be presented in the expert system
(Bergsma, 2003).
Knowledge acquisition requires no standard methodology
for extracting knowledge. However, it usually involves a
progressive number of personal interviews of the experts to
record information pertinent to the knowledge-based
occasionally, the role of the knowledge engineer can be
significantly reduced if the understanding of the development
processes by the participating experts are substantial and they
are willing able to organize and express all the necessary
information to develop facts or rules based on their personal
heuristics. Consistency in the naming conventions of facts or
rules in vital and the ability to develop a language which is
familiar to the end users is also important. Acquired knowledge
should be played back to experts perhaps using a different
medium them the one used to acquire it (Townsend,2007),
during the knowledge acquisition phase, the knowledge
engineer should identify the conclusions that the experts
system should render and verify this knowledge as it is
acquired. Knowledge acquisition should also be supplemented
with a thorough review of current literature to provide the most
available up-to-date information (sell, 2005).
2.2.3 Knowledge Representation

After the domain has been identify and knowledge
acquired from a participating expert a model for representing
the knowledge must be developed. Numerous techniques for
handlings information in the knowledge-based are available;
however, most expert systems utilize rule based approaches
your own new copy.
(Townsend, 2007). The knowledge engineer, working with the

expert, must try to define the best structure (Jones, 2009).
Other commonly used approaches include decision tress,
blackboard system and object oriented programming.
2.2.4 Verification
Prior to testing of an expert system with outside experts,
every query response which should lead to a correct conclusion
or diagnosis should be systematically verified with the
knowledge-based. This procedures can be accomplished
without the assistance of the participating expert is essential to
ensure that the expert system provides credible based should
be adjusted to eliminate any identified conflicted or problems.
Experts systems which utilized visual images to supports text
should also be verified to ensure each image correctly
corresponds to the specific symptoms described.
2.2.5 Validation
This should be done by the primary expert who was
involved in the systems knowledge based development and
knowledge representation its phase provides the experts with
the opportunity to explore the functioning expert system and
make suggestions for changes in the interface design, image
database or knowledge base. Generally, the system should be
challenged by the expert by presenting contrived problems or
queries based on past field experience. Again, the system
should be adjusted to eliminate any conflicts or design
problems.
Validation provides the final opportunity to evaluate an expert
system prior to testing by additional experts concede to the
development of a credible prototype which provides a
reasonably accurate ability. Although validation is an essential
phase to expert system development problems of access to
expert assistance, time and resources constraints can often
make validation procedure impractical or limited.
2.3 TESTING EXPERT SYSTEM

When the knowledge engineer and the expert are satisfied
that the expert system is complete, the system should be
tested against and agreed upon performance criteria. At this
time other experts can be invited to evaluate and use the
system for testing purpose. Either real world case scenarios or
stimulated case can be used for testing purpose. Once the
system has been adequately tested and found to meet a
defined level of accuracy, efficiency and reliability, a final
version can be prepared for distribution and use.
However, in the event, if the system does not perform
adequately, further verification or validation and field testing
your own new copy.
may be necessary before making a final version of the system

available to the intended audience.
A typical component of a rule- based expert system integrates.
 Knowledge Base: This is a problem domain that specific
knowledge base that stores the encoded knowledge to
support one problem domain such as diagnosing why a
car won’t start. In a rule based expert system, the
knowledge base includes if then rules and additional
specifications that control the course of the interview (sell,
2005).
 Inference Engine: A set of rules of making dedications
from the data and that implements the reasoning
mechanism and controls the interview process (Townsend
2007). The inference engine might be generalized so that
the same software is able to process many different
knowledge bases.
 Users Interface: This request information the users and
output intermediate and final results (Edmurals 2009). In
some expert systems, inputs are acquired from additional
sources such as data based and sensors. An expert
system shell consists of a generalized inference engine
and user interface designed to work with a knowledge
base provided in a specific format (Liebowitz, 2008). A
shell often includes tools that help with the design
development and testing of knowledge base with the shell
approach expert system representing many different
problem domains may be developed and delivered with
the same software environment (Basri H, 2008).
The use interacts with the system through a user interface
which may use means natural language or nay other style of
interaction. Then an interface engine is used to reason with
both the expert knowledge (extracted from our friendly expert)
and data specific to the particular problems being solved. The
expert knowledge will typically be in the form of a set of if –
then rules.
The case specific data includes both data provided by the users
and partial conclusions (along with certain measures) based on
this data. In simple forward chaining rule based system the
case specific data will be the elements in working memory.
2.4 MYCIN
No discourse on expert system is complete without a
discussion of mycin. As mentioned above, Mycin was one of the
earliest expert systems and its design has strongly influenced
the design of commercial experts system and expert system
shells.
Mycin was an expert system developed to diagnose and
recommend treatment for certain blood infections. To do the
diagnosis “properly” involves growing cultures of the infecting
organism.
Unfortunately this takes around 48 hours and if doctors
waited until this was complete, their patients might be dead.
your own new copy.
So, doctors have to come up with quick guesses about likely

problems from the available data, and use these guesses to
provide a “covering” treatment where drugs are given which
should deal with any possible problems.
Mycin was developed partially in order to explore how
human experts make these rough (but important) guesses
based on partial information, however, the problem is also a
potential important one in practical terms, there are lots of
junior or non- specialized doctors who sometime have to make
such a rough diagnosis, and it there is an expert tool available
to help them, then this might allow more effective treatment to
be given. In fact, mycin was never actually used in practice.
This wasn’t because of any weakness in its performance in
tests it outperformed members of the Stanford medical school.
It was as much because of ethical and legal issues related to
the use of computers in medicine. If it gives the wrong
diagnosis, who do you use?
Anyway mycin represented its knowledge as a set of if then
rules with certain factors. The following is an English version of
one of mycin’s rules.
If the infection is primary bactericidal and the site of the
culture is one of the strike sites and the suspected portal of
entry is the gastrointestinal treat. Then there is suggestive
evidence (0.7) that infection is bacterial. The 0.7 is roughly the
certainty that conclusion will be true given the evidence. If the
evidence is uncertain, the certainties of the bits of evidence will
be combined with the certainty of the rule to give the certainty
of the conclusion.
Mycin was written in LISP (LIST processing), and its rule
is formally represented as LISP expressions. The action part of
the rule could just be an conclusion about the problem being
solved or it could be an arbitrary lisp expression. This allowed
great flexibility, but removed some of the modularity and
clarity of rule based systems, so using the facility had to be
used with care. Anyway mycin is a (primarily) goal- directed
system using the basic backward chining reasoning strategy
that we described above.
However, mycin sued various leviratic to control the
search for a solution (or proof of some hypothesis). These were
needed both to make the reasoning efficient and to prevent the
users being asked to many unnecessary questions. One
strategy is to first ask the user a number of more or les preset
questions that are always required and which allow the system
to rule out totally unlikely diagnosis. Once these questions
have been asked the system can then focus on particular, more
specific possible blood disorders, and go into full backward
chaining mode to try and prove each one.
This rules out a lot of unnecessary search, and also
follows the pattern of human patient doctor interviews.
The other strategies related to the way in which rules are
involved. The first one is simple gives a possible rule to use,
your own new copy.
mycin first checks all the previses of the rule to see if any are
known to be false. If so, there’s not much point using the rule.
The other strategy related more to the certainty factors. Mycin
will first look at rules that have more certain conclusions. And
will abandon a search once the certainties involved get below
0.2.
A dialogue with mycin is somewhat like a mini- dialogue
but of course longer and somewhat more complex. There are
three main stages to the dialogues. The first stage, initial data
about the case is gathered so the system can come up with a
very broad diagnosis.
In the second more directed questions are asked to test
specific hypothesis. At the end of this section a diagnosis is
proposed. In the third section, questions are asked to
determine an appropriate treatment given the diagnosis and
facts about the patient.
This obviously concludes with a treatment
recommendation. At any stages the uses can ask why a
question was asked or how a conclusion was reached, and
when treatment is recommended. The users can ask for
alternative treatments if the first is not viewed as satisfactory.
Mycin, though pioneering much expert system research, also
had a number of problems which were remedied in later more
sophisticated architecture. One of these was that the rules
often domain knowledge problems solving knowledge and
“screening conditions” (conditions to avoid asking the user silly
or awkward questions. E.g. checking patient is not child before
asking about alcoholism). A later version called NEOMYCIN
attempted to deal with these by having an explicit disease
taxonomy (represented as a frame system) to represents facts
about different kinds of disease tree from general classes of
diseases to every specific ones gathering information to
differentiate between two disease subclasses (i.e. if disease 1
has subtypes disease 2 and disease 3 and you know that the
patient has the disease 1, and subtype disease 2 has symptom
1 but not disease 3 the ask about symptom1).
There were many other developments from the MYCIN
project. For EMYCIN was really the first experts shell
development from MYCIN.
A new expert system called PUFF was developing using EMYCIN
in the new domain of heart disorders. And a system called
NEOMYCIN was developed for training doctors, which would
take them through various example cases, checking their
Research and Conceptualization Problem assessment
review
conclusion and explaining where they went wrong.
We should make it clear at this point that not all expert
system are MYCIN like. Many use different approaches to both
problems
Testingsolving and knowledge
Design and representation. A full course
Knowledge
implementation acquisition & analysis
on expert systems would consider the different approaches
used, and when each is appropriate.
Knowledge refinement
Documentation Management
your own new copy.
CHAPTER THREE
SYSTEM ANALYSIS AND DESIGN
3.0 INTRODUCTION
Systems analysis is a vital aspect of project development
because it others the researcher opportunities to understudy
the existing system in order to eliminate problem or constraints
militating against the smooth functions of the existing systems.
With this in hand, the design of the new system will be efficient
and effective as applied in this project.
The process of developing the expert system is not really
an easy job to do as it requires much effort in the skills of
problems solving, instead of using the energy and time. An
expert system is a computer program which simulates the
human problems solving and reasoning and so it must be
integrated properly with the right knowledge as human beings
have knowledge acquisition is believed to be the critical and
most difficult task in the development of expert system, but
the implementation and integration process is seen as an
equally important and tough job to be done. That is why
designing is very important as to make sure that the step in
the development process is right and always meets the
requirement.
3.1 WEAKNESS OF THE PRESENT SYSTEM
1. Inability to represent accurately time varying and spatially
varying phenomena.
2. Inability of the program to dictate specific gaps in the
knowledge base.
3. Difficulty for knowledge engineers to acquire knowledge
from expert reliability.
4. Difficulty for knowledge to ensure consistency in the
knowledge base.
5. Inability of the program to learn from its errors
3.2 METHODOLOGY
The methodology adopted here is an improvement from
the previous methodologies in the field of computer science,
software engineering, knowledge engineering and multi-media
since this expert system will be an integration of these
technologies.
3.3 KNOWLEDGE ACQUSITION

To develop viable system adequate information on the
working of the particular system being developed must be
obtained and represented in a format in which rules can be
applied. Acquisition of this knowledge could be from a human
expert and is coded into a form that a compute may apply to
similar problems.
3.3.1 DOMAIN EXPERT

your own new copy.
The domain expert is the individual who is a professional

in the field of the system being developed. In this instance the
domain is an automobile technician, who is highly skilled in the
diagnosis and correction of automobile faults.
3.3.2 INTERVIEW
An interview must be carried out with the domain expert
in order to obtain a knowledge base for the expert system. This
may be an oral interview or by use of a questionnaire.
The interviewer must be careful to ensure that the actual
thoughts of the domain experts are captured in order to ensure
an expert system that would run effectively.
3.3.3 CONSULTATION
This is the point at which the user makes contact with the
expert system by means of user interface. The users guided by
the expert systems make a number of inputs, which the
systems through a number of rules determine, the adequate
diagnosis.
Note: rating (certainty value) is on scale of 0-5
SYMPTOM FAULT RATING CORRECTION
Squeaky engine noise Loose reams, rod 5.0 Tighten meets of
bearings reams and /or bearings
blocked fuel filter 4.0 Replace fuel filter

Loose clutch Weak clutch plates 4.0 Replace clutch plate
Clutch not responding Leaking dance sleeve 4.5 Close leak
Black exhaust emissions Bad rings 3.5 Adjust pistons
Faulty links and metals 4.0 Adjust/ replace links
Thin white exhaust emissions Fouled injector 4.0 Changes fuel injector
exhaust system leak 2.5 Fix leak
Thick white exhaust Fuel mixture too rich 4.0 Adjust/replace
emissions carburetor
Bluish exhaust emissions Greasy engine oil 4.5 Changes lubrication
oil
Non- started cold engine Flat battery 4.0 Changes/ replace
battery
Broken timing chain 2.0 Replace timing chain
Clogged air filter 3.0 Flush air filter
Faulty spark plugs 3.5 Replace spark plugs
Non start (hot engine) Clogged air filter 3.5 Flush air filter
Leaking fuel injector 2.0 Replace/ fix injector
fuel mixture too rich 3.0 Adjust/ replace
carburetor
Lack of power Bad inhibition timing 2.5 Adjust timing belt
low
Low fuel pressure 3.5 Replace pressure
regulator
Blocked fuel filter 4.0 Replace fuel filter
Incorrect grade of oil 2.5 Changes lubrication
oil
Hesitation or uneven running Fuel injection system 4.0 Replace injector
fault pointless
Low fuel pressure 2.5 Adjust pressure
regulator
Engine stalling or cutting out Inductor vacuum leak 2.0 Seal leak
at
Idle speed Injector mechanical 4.0 Seal injector leak
your own new copy.
leak
Engine knock Worn spark plugs 3.5 Change spark plugs
Cooling fault 3.0 Check cooling fans
Build- up of carbon 4.5 Clean out cylinders
deposit in cylinders
Fuel of low octane 4.0 Flush tank, change
fuel
Engine backfires through Injector mechanical 3.0 Clean injector/seal
exhaust value fault injector leaks
Leaking or burnt 4.5 Replace exhaust value
exhaust value
Engine backfire through inlet Induction vacuum leak 3.0 Seal vacuum leak
value
Burnt inlet value 4.0 Replace inlet value
Carbon build –up on 4.0 Clean inlet value
the back of inlet value
Overheating Burnt gasket 4.5 Replace gasket
leaking radiator 4.0 Sea; leak with seal out
Radiator choked up 3.0 Flush radiator/ change
coolant
Alternator belt not 2.0 Adjust alternator belt
well tensioned
Screeching sound from engine Bad adjustment of fan 5.0 Adjust/ change fan belt
belt
Car jerking Bad plug adjustment 4.0 Change spark plugs
Choked fuel filter 4.0 Flush/ replace filter
Water in fuel tank 3.0 Flush fuel tank
FIGURE 3.1 CONSULTATION TABLE
3.3.4 DIAGNOSIS
Based on the input of the user, the expert system used
the inherent rules to come up with a diagnosis of the particular
fault associated with the selected symptoms with a certainty
value attached to it. If the user is not satisfied with the output,
the expert system can give possible alternative faults with their
associated certainties.
3.3.5 CORRECTION/ EXPLANATION

With each diagnosis comes a lined correction procedure,
which tells the user what actions to take to handle the
problemss) encountered. Also an explanation mechanism to
enlighten the user on the nature of the problem and its
implication is also included.
3.4 SYSTEM DESIGN

The analysis of the knowledge acquired in the knowledge
acquisition phase had lead to the design of the system which
includes the overall structure of the system’s knowledge, the
programming parts as well as the interfaces which is equally
important.
It was designed after the insight gained from the previous
phase on the best approach for representing the expert’s
knowledge and problem solving strategies in the expert system
beside that, the method that has been used to process the
system’s knowledge was also defined in this phase, where
forward chaining rule based expert system was selected as the
inference engine.
This decision was made after taking into consideration of the
organization or architecture of the knowledge and the problem.
Solving strategies determined earlier. After all of the elements
your own new copy.
have been designed, the development phase was started for

both programming and the construction of the user interfaces.
Design phase was also considered as the phase of
prototype development. In this project case, the final product
itself is actually a prototype.
That means in the design phase, the partial prototype was
built which represented the initial part of the full prototype
expert system. The partial prototype was built for the purpose
of providing a deeper insight and better understanding of the
problem and system’s requirements. In fact system’s design is
inherently an interactive process where finding from system
testing are used to refine the system’s knowledge and
structure.
3.4.1 RULE BASED DEVELOPMENT MODEL

The development of this expert system for car faults
diagnosis was based on the current most popular choice of
knowledge engineers for building an expert system that is rule
– based expert system.
The popularity of this kind of system’s development has
grown due to the large numbers of successful rule- based
system built and also abundance of rule- based expert software
that is available easily. Besides, rule base expert system is a
representation of the human beings natural reasoning and
problem solving paradigm. It models human’s production
system using the following modules.
your own new copy.
Expert
Knowledge Knowledge Inference User User

Engineer Engineer Engine
Interface
Data
STRUCTURE OF A RULE BASE EXPERT SYSTEM MODEL
 Knowledge base models a human’s long term memory as

asset of rules.
 Working memory- models a human’s short term memory
and contains problems facts both entered by the firing of the
rules.
 Inference engine- model human reasoning by combining
problem facts contained in the working memory with rules
contained in the knowledge base to infer new information.
Based on these concepts of reasoning which emulates the
human problems solving strategies the expert system is
structured accordingly to the fundamentals of it.
As used in the paradigm of problem – solving by this expert
system for car faults diagnosis, the expert system has four
basic elements which are adapted from the model of rule based
system. Once the user logs in to the expert system, they will
be asked questions which should be modelled according to the
current problems. These new information will be entered to the
working memory where the system will match this information
with the knowledge contained in the knowledge base to infer
new facts.
Eventually the system and the conclusion is also entered
into the working memory before displaying to the user through
the interface. The four modules involved in the rule- based
expert system are;
 Knowledge base
 Working memory
 Inference engine
 Interface
3.4.2 INFERENCE TECHNIQUES

Knowledge processing in experts system is based on the
insight gained from the way human’s reason, how they work
with information on a given problem together with their general
knowledge of the problems domain.
The human reasoning process using techniques called
inference. In developing the experts system for car faults
diagnosis, the developer used the forward chaining inference
techniques. From the several inference techniques that exist,
forward changing was selected to be used in the development
of this expert system. This is because in car maintenance and
troubleshooting problems, there are quite many possibilities we
may face, with meant different parts of car with different kinds
your own new copy.
of damages which need different solutions and troubleshooting.

Therefore forward chaining is believed to be suitable for their
inference process of this system.
SYSTEM FLOW CHART
Insert information in the

working memory
Check rule Check next rule
Add conclusion to Premise Rules

working memory s match remai
Yes No
the n
Workin
g
memor
y
Display conclusion
to user Stop
3.4.3 FLOWCHART OF THE PROGRAM
START
Display splash
screen
Display login
screen
Is
passwor N
d
correct
?
Y
Connect to database
Y
Display login screen

B C
A Y
Exit Stop
progra
m
Write data Print Show details of
receipts all registered
entries to
client
database
Registration Print receipts View reports
Show client details and Connect too data

Enter client Connect too data
faults screen Y
details base Y base
A B C
Write data entries to
database
Y
your own new copy.
3.5 PROGRAM DESIGN

The choice of programming language was visual basic 6.0
(enterprise edition). This language is chosen for its ease of use,
its object oriented programming (OOP) configuration and its
ability to comfortably create an easy- to use graphics user
interface (GUI) for the convenience of the novice computer
users.
3.5.1 HIGH LEVEL MODEL OF THE PROPOSED SYSTEM
Consultation
Interview Signs
Diagnosis
Problems cause
Corrective measures
HIGH LEVEL MODEL OF THE PROPOSED SYSTEM
CHAPTER FOUR
SYSTEM IMPLEMENTATION
4.1 INTRODUCTION
your own new copy.
Implementation is to carrying out execution, or practices

of a plan, a method or any design for doing something. As
such, implementation is the action that must follow any
preliminary thinking in order for something to actually happen.
In an information technology context, implementation
encompasses all the processes involved in gathering new
software or hardware operating properly in its environment,
including installation, configuration, running, testing and
making necessary changes. The word deployment is sometime
used to mean the same thing.
Before the designed system can be fully implemented,
there must be some skeletal structure for the initial stage of
development each component of this structure is tested for its
accuracy and stability. This involves a top down testing of the
modules to ensure that each phase of the design is error free.
When this is ascertained, other layers of complexity are
added prior to the full operation of the package, it is important
that there is an instruction for the end- user to ensure that the
package is used with smooth operation.
4.2 SYSTEM REQUIEMENTS

In installing any software, it is absolutely necessary to specify
the kind of system on which it would run, and the minimum
system specifications for which the program would run at an
optimum. This comprises of both the hardware and software
components.
Minimum hardware requirements:

 Intel Pentium IV 512MHz processor/Amd Athlon
processor.
 512 MB RAM
 14 SVGA color monitor.
 20 GB hard disk space.
 Laser jet printer.
 External harddisk for backup.
MINIMUM SOFTWARE REQUIREMENTS.

 Microsoft visual basic 6.0.
 Window 2000/XP
4.3 TESTING
The integration of every part of the expert system was
then tested to ensure that the prototype works properly,
according to the requirement and basic concept of the expert
system.
The testing was done by a verified person especially the
target user in the first places as to get a verified result. When
errors were identified, the correction was made in any of the
phase where necessary. Beside the programming structure, the
interface of the system was also taken into account within the
your own new copy.
testing phase. This is to make sure that the system can be

easily used and understood by the user.
4.4 MAINTENANCE
From time to time, the prototype will be maintained and
followed up to make sure that it is working properly and the
most important thing is that the system will always be reliable,
considering the current situation of the system domain.
The knowledge base may have to be updated from time to
time depending on the changes that may happen especially
from the side of the knowledge sources, to meet the current
need. It might be useful anymore in the future as it doesn’t suit
the need for that time major system requirement changes may
also occur that would require a reformulation of system
specification. Therefore, it is important that an effective
maintenance program be established for an expert system.
When the package is up and running there is need to
ensure that the system will always run at an optimum and is
virtually error free; in the event of breakdown, there must be
some procedure by which recovery can be made with minimal
stress.
There are three major types of maintenance; preventive,
adaptive and corrective maintenance. Preventive maintenance
involves the steps which are applied from time to time to
ensure that there is no breakdown of the system, for instance,
making backup of data in the system. Adaptive maintenance is
the continuous improvement in the code and design of the
program to heighten its optimality and durability. Corrective
maintenance involves the troubleshooting of problems
whenever they arise. All maintenance procedures to be found
within the documentation that comes with the package; the
purpose of this being to ensure error free running of the
program.
4.5 PROGRAM DOCUMENTATION

After the proposed system is designed it is necessary to
make some form of documentation, which will guide the user
through the processes of installation, running and
troubleshooting of the software package.
Documentation is imperative in any successful software
design project. Considering the fact that most and users of
developed software packages are not computer gurus
themselves it is very important that the literature
accompanying such a product is clear, concise, with a straight
forward language that is understandable to the average
individual.
The accompanying documentation contains details on the
computer requirements for installation of the package, both
hardware and software. It also inform on the steps by which
the package is to be installed as well as the instruction on it is
to be run, its user environment, input and output process,
your own new copy.
explanation and help mechanisms. The documentation also

includes a manual for troubleshooting in case a problem arises
with the use of the package.
It is advisable to include an appendix containing the codes
for the program, so that in the absence of the original
programmer(s) the software can be understood and managed
by any other competent programmer.
4.5.1 SAMPLE INPUT/OUTPUT DATA FORMATS

The customer will fill the “client registration form” which
has the following content; customer name, vehicle name, type,
date, license number, engine number, class number, and year
of purchase with customer’s residence.
The data will be uploaded with pictures of your car and
your data. You check the list of probable faults and click on
your car’s fault a list of probable Solution will show. After you
must have applied these solutions, you click on “solved”.
Receipt will be prepared for you.
Example.
Input symptom “blue exhaust fumes”
Fault: “Greasy oil (90%)”
Output correction “change lubrication oil” or “empty oil pump”
Click on solved and wait for your receipt on repairs carried out
on your vehicle.
Fault “cooling fault (60%)” Or “building of carbon deposits in
cylinder (70%) “OR” cleans out cylinders “OR” flush fuel tank,
change fuel” click on solved and wait for your receipt on repairs
carried out on your vehicle.
4.5.2 LOADING THE PACKAGE

There are several ways by which the package can be
loaded:
 Running the installation package. Copy the entire content of
the setup disks on the hard disk drive (c/>dir) and double
click the setup icon.
 On the desktop click on start> settings > control pad> add/
remove program; then follow instructions on the screen.
 Copy complied exe version of the system in a folder with the
file on the hard dick drive with other files. Then run. Exe file.
4.5.3 EXITING
Select exit on the menu or select close from the top
right hand side of the window.
your own new copy.
CHAPTER FIVE
5.0 SUMMARY, RECOMMENDATION & CONCLUSION
5.1 SUMMARY
It cannot be denied that the role of expert systems in
almost every part of human life is getting bigger. This is so
because of the performance that the expert system has shown
of what it can do to help human beings. Peoples lives seen to
be easier in many ways with the presence of expert systems.
Academically, the expert system can help humans by
aiding the human expert function whenever the expert can’t be
accessed or by assisting the human experts in situations where
he/she has to cover many things. In this case the expert may
be useful to execute routine tasks and let the human experts to
do the rest, especially the more difficult jobs.
This expert system for car fault diagnosis is believed to be
an excellent idea as another application of expert systems and
how we can utilize the enormous function of it. In fact, there
are other domains which are suitable to be introduced to the
implementation of expert system and get the maximum
achievement with it. Although there are also some criticism and
issues regarding the development of expert system which
relates to the issues of reliability and human social life, efforts
have been discussed to overcome those problems.
5.2 RECOMMENDATION
The prototype of system was developed in a limited time
and resources and thus it is not all that compatible and useful
enough to be implemented in the really world yet. There must
be so many other steps to be taken in refining the errors and
rules before it can really be used in the real situation. When
this is done, this expert system for car fault diagnosis would be
ready to be use to assist all the car owners out there in
situations where they have problems with their cars, so they
can handle these problems themselves. Time and distance
would no longer be constraints to them.
5.3 CONCLUSION
This proposed system can help inexperienced mechanics
or drivers in providing decision support system, interactive
training tools and expert advice. Using this system loss of
customer and income due to lack of knowledge can be avoided.
Having this expert system may allow mechanics to do
more work in less time, thus bringing in more revenue. And
mechanic will also gain through improved productivity.
your own new copy.
REFERENCES
Adams, R & Bath N,(1999). An expert system based

algorithm for short load forecast. Texas USA; Swat Press.
AEC (Architectural Energy Corporation). 2003. Final

Report: Energy efficient and affordable commercial and
residential buildings. Report prepared for the California
Energy Commission. Report number
Andersen, K.K., and T.A. Reddy, 2002. The error in

variables (EIV) regression approach as a means of
identifying unbiased physical parameter estimates:
Application to chiller performance data. International
Journal of Heating, Ventilating, Air Conditioning and
Refrigerating Research 8(3):295-309.
Bailey, M.B. 1998. The design and viability of a

probabilistic fault detection and diagnosis method for
vapor compression cycle equipment. Ph.D. thesis, School
of Civil Engineering of University of Colorado, Boulder,
Colorado.
Basri, H (1998). An expert system for planning landfill

restoration, water science and technology, New Delhi
USA; Inlier limited.
Bendapudi S., and J.E. Braun. 2002. A review of literature

on dynamic models for vapor compression equipment. HL
2002-9, Report #4036-5, Ray Herrick Laboratories,
Purdue University.
Bourdouxhe, J.P., M. Grodent, J. Lebrun, and C. Saavedra.
(1994a). A toolkit for primary HVAC system energy
calculation—Part 1: Boiler model. ASHRAE Transactions
100(2):759-73.
Bourdouxhe, J.P., M. Grodent, J. Lebrun, C. Saavedra, and
K. Silva (1994b). A toolkit for primary HVAC system
energy calculation—Part 2: Reciprocating chiller models.
ASHRAE Transactions 100(2):774-86.
Brown Franklin Lee, Lebeck A. O., 1997, Cars, Cans and

Dumps, New Mexico.
Bourdouxhe, J.P., M. Grodent, and J. Lebrun. 1997.

HVAC1 Toolkit: Algorithms and Subroutines for Primary
HVAC Systems Energy Calculations. Atlanta: American
Society Heating Refrigeration Air Conditioning Engineers,
Inc.
Brambley, M.R., R.G. Pratt, D.P. Chassin, and S.

Katipamula. (1998). Automated diagnostics for outdoor air
ventilation and economizers. ASHRAE Journal 40(10):49-
55 [October].
Brandemuehl, M.J., and S. Gabel. 1994. Development of a

toolkit for secondary HVAC system energy calculations.
Braun, J.E. (1990). Reducing energy costs and peak

electrical demand through optimal control of building
thermal mass. ASHRAE Transactions 96(2):876-88.
Braun, J.E. 1999. Automated fault detection and

diagnostics for the HVAC&R industry. International Journal
of Heating, Ventilating, Air Conditioning and Refrigerating
Research 5(2):85-86.
Breuker, M.S. 1997. Evaluation of a statistical, rule-based

fault detection and diagnostics method for vapor
compression air conditioners. Master's thesis, School of
Mechanical Engineering, Purdue University, West
Lafayette, Indiana.
your own new copy.
Breuker, M.S., and J.E. Braun. 1998a. Common faults and

their impacts for rooftop air conditioners. International
Breuker, M.S., and J.E. Braun. 1998b. Evaluating the
performance of a fault detection and diagnostic system for
vapor compression equipment. International Journal of
Heating, Ventilating, Air Conditioning and Refrigerating
Research 4(4):401-425. Car Engine Products in The UK's
Leading Online Car Accessory Store,
http://www.speeding.co.uk/acatalog/engine.html
Car: engine: combustion,

http://www.halfbakery.com/category/Car_3a_20Engine_3
a_20Combustion
Castro, N.S., J. Schein, C. Park, M.A. Galler, S.T. Bushby,

and J. M. House. (2003). Results from simulation and
laboratory testing of air handling unit and variable air
volume box diagnostic tools. National Institute of
Standards and Technology, Gaithersburg, MD, NISTIR
6964.
Castro, N. 2002. Performance evaluation of a reciprocating

chiller using experimental data and model predictions for
fault detection and diagnosis. ASHRAE Transactions
108(1).
Chen, J., and R.J. Patton. 1999. Robust Model-Based
Fault-Diagnosis for Dynamic Systems. Norwell,
Massachusetts:Kluwer Academic Publishers.
Cho, H. J., & Park, J. K. (1997). An expert system for fault

Section diagnosis of power systems using fuzzy relations.
IEEE Transactions on Power Systems, 12, 342–348.
Cikanek, H.A., III. 1986. Space Shuttle main engine
failure detection. IEEE Control Systems Magazine 6(3):13-
18.
Comstock, M.C., B. Chen, and J.E. Braun. 1999. Literature

review for application of fault detection and diagnostic
methods to vapor compression cooling equipment. HL
1999-19, Report #4036-2, Ray Herrick Laboratories,
Purdue University.
Comstock, M.C., J.E. Braun, and E.A. Groll. 2001. The

sensitivity of chiller performance to common faults.
International Journal of Heating, Ventilating, Air
Conditioning and Refrigerating Research 7(3).
Daoliang Lia, Zetian Fua, Yanqing Duanb (2002). Fish-

Expert: a Webbased expert system for fish disease
diagnosis, Expert Systems with Applications, 23, 311-320.
De Kleer, J., and J.S. Brown. 1984. A qualitative physics

based on sonfluence. Artificial Intelligence 24:7-83.
Deschamps, D., & Fernandes, A. M. (2000). An expert

system to diagnosis periodontal disease. Proceedings of
Sixth Internet World Congress for Biomedical Sciences in
Ciudad Real, Spain.
Dexter, A., and J. Pakanen (eds.). 2001. International

Energy Agency Building Demonstrating Automated Fault
Detection and Diagnosis Methods in Real Buildings.
Technical Research Centre of Finland, Laboratory of
Heating and Ventilation, Espoo, Finland.
Dexter, A.L., and D. Ngo. 2001. Fault diagnosis in air-

conditioning systems: A multi-step fuzzy model-based
approach. International Journal of Heating, Ventilating, Air
Conditioning and Refrigerating Research 7(1):83-102.
your own new copy.
Dhaliwal, J. S., & Benbasat, I. (1996). The use and effects

of Knowledge based system explanations: theoretical
foundations and a framework for empirical evaluation.
Information Systems Research, 7, 342–362.
Donald, H & Pauline, B (2004). Computer graphics and

expert system with open GL, person prentice Hall, NJ USA.
Fourth International Conference on System Simulation in

Buildings. IBPSA Building Simulation '95, Madison,
Wisconsin, August 14-16, 1995.
Frank, P.M. 1990. Fault diagnosis in dynamic systems

using analytical and knowledge-based redundancy –A
survey and some new results. Automatica 26:459-474.
Frank, P.M. 1997. New developments using AI in fault

diagnosis. Engng. Applic. Artif. Intell. 10(1):3-14.
Georgescu, C., A. Afshari, and G. Bornard. 1993. A model-
based adaptive predictor fault detection method applied to
building heating, ventilating, and air-conditioning process.
TOOLDIAG’ 93, organized by Département d’Etudes et de
Recherches en Automatique, Toulouse, Cedex, France.
Freda, K & Winkelbauer, L. (2002): A Hybrid expert

system, GIS and simulation modeling for environmental
and technology risk management,New York USA;McGraw
hill companies pp.385 - 541
Gertler, J. 1988a. Survey of model-based failure detection

and isolation in complex plants. IEEE Control Systems
Magazine 8(6):3-11.
Gertler, J. 1998b. Fault Detection and Diagnosis in

Engineering Systems. New York: Marcel Dekker.
Ghiaus, C. 1999. Fault diagnosis of air-conditioning
systems based on qualitative bond graph. Energy and
Buildings 30:221-232.
Glass, A.S., P. Gruber, M. Roos, and J. Todtli. 1995.

Qualitative model-based fault detection in air-handling
units. IEEE Control Systems Magazine 15(4):11-22.
Gordon, J.M., and K.C. Ng. 1995. Predictive and diagnostic

aspects of a universal thermodynamic model for chillers.
International Journal of Heat and Mass Transfer
38(5):807-18.
Gordon, J.M., and K.C. Ng. 2000. Cool Thermodynamics.
Cambridge, UK: Cambridge International Science
Publishing.
Greitzer, F.L., and R.A. Pawlowski. 2002. Embedded

prognostics health monitoring. Presented at the
Instrumentation Symposium Embedded Health Monitoring
Workshop, May 2002 PNNL Report Number PNNL-SA-
35920, Pacific Northwest National Laboratory, Richland,
Washington.
Guyon, G., and E. Palomo. 1999. Validation of two French

building energy programs—Part 2: Parameter estimation
method applied to empirical validation. ASHRAE
Transactions 105(2):709-20.
Guvenir, H. A., & Emeksiz, N. (2000). An expert system

for the differential diagnosis of erythemato-seuamous
diseases. Expert Systems with Applications, 18, 43–49.
Haves, P., T. Salsbury, and J.A. Wright. 1996. Condition

monitoring in HVAC subsystems using first principles.
Himmelblau, D.M. 1978. Fault Detection and Diagnosis in

Chemical and Petrochemical Processes. New York: Elsevier
Scientific Publishing Company.
your own new copy.
How stuff works,

http://auto.howstuffworks.com/engin.htm,
http://science.howstuffworks.com/fire-engin.htm
House, J.M., H. Vaezi-Nejad, and J.M. Whitcomb. 2001. An
expert rule set for fault detection in air-handling units.
ASHRAE Transactions 107(1).
Huang, Q. M., Li, X. X., Jiang, Y. R., & Qian, Y. (2001). A
Fault diagnosis expert system based on fault tree analysis
for lubricating dewaxing process. Computers and Applied
Chemistry, 18, 129–133.
Hyvärinen, J,. and S. Kärki (eds.). 1996. International
Energy Agency Building Optimisation and Fault Diagnosis
Source Book. Technical Research Centre of Finland,
Laboratory of Heating and Ventilation, Espoo, Finland.
Isermann, R. 1984. Process fault detection based on
modeling and estimation methods–A survey. Automatica
20(4):387-404.
Isermann, R., and P. Ballé. 1997. Trends in the application
of model-based fault detection and diagnosis of technical
process. Control Eng. Practice 5(5):709-719.
Jeff Pepper (1990). An Expert System for Automotive

Diagnosis in Ray Kurzweil's book, The Age of Intelligent
Machines.
Jia, Y., and T.A. Reddy, 2003. Characteristic physical

parameter approach to modeling chillers suitable for fault
detection, diagnosis and evaluation. ASME Journal of
Solar Energy Engineering 125:258-265.
Jiang, W., and T. A. Reddy. 2003. Reevaluation of the

Gordon-Ng performance models for water-cooled chillers.
Jim, P (2001). A webbased ITS controlled by a Hybrid
expert system, Nwodo Street Owerri. Nwabugo prints.
Joseph Giarratano, Gary Riley (2004). Expert Systems:
Principles andProgramming, Fourth Edition.
Jones A R (2004), Combustion Physics. Imperial Collage,

London,
http://www.chroma.med.miami.edu/~idickers/m2-
engine.html
Kay, H. 1998. SQSIM: A simulator for imprecise ODE

models. Computers and Chemical Engineering 23(1):27-
46.
Kaldorf, S., and P. Gruber. 2002. Practical experiences

from developing and implementing an expert system
diagnostic tool. ASHRAE Transactions 108(1):826-840.
Kaler, G.M. 1988. Expert system predicts service. Heating,

Piping, Air Conditioning 11:99-101.
Kaler, G.M. 1990. Embedded expert system development

for monitoring packaged HVAC equipment. ASHRAE
Transactions 96(2):733.
Karki, S., and S. Karjalainen. 1999. Performance factors
as a basis of practical fault detection and diagnostic
methods for air-handling units. ASHRAE Transactions
105(1):1069-1077.
Katipamula, S., R.G. Pratt, D.P. Chassin, Z.T. Taylor, K.
Gowri, and M.R. Brambley. 1999. Automated fault
detection and diagnostics for outdoor-air ventilation
systems and economizers: Methodology and results from
field testing. ASHRAE Transactions 105(1).
Katipamula, S., R.G. Pratt and J.E.Braun. 2001. Building
Systems diagnostics and predictive maintenance,chapter
7.2 in CRC Handbook for HVAC&R Engineers (J. Kreider,
ed.). Boca Raton, Florida: CRC Press.
Katipamula, S., M.R. Brambley, and L. Luskay. 2002.
your own new copy.
Automated proactive techniques for commissioning air-

handling units. Journal of Solar Energy Engineering
125:282-291.
Katipamula, S, M.R Brambley, N.N Bauman, and R.G Pratt.

2003. Enhancing building operations through automated
diagnostics: Field test results. In Proceedings of 2003
International Conference for Enhanced Building
Operations, Berkeley, CA.
Kilma, J. 1990. An expert system to aid trouble-shooting
of operational problems in solar hot water systems.
Kumar, S., S. Sinha, T. Kojima, and H. Yoshida. 2001.
Development of parameter based fault detection and
diagnosis technique for energy efficient building
management system. Energy Conversion and
Management 42:833-854.
Lebrun, J., and J-P Bourdouxhe. 1996. Reference Guide for

Dynamic Models of HVAC Equipment (ASHRAE Research
Project 738). Atlanta: American Society of Heating,
Refrigerating and Air-Conditioning Engineers, Inc.
Lee, W.Y., C. Park, and G.E. Kelly. 1996a. Fault detection

of an air-handling unit using residual and recursive
parameter identification methods. ASHRAE Transactions
102(1):528-539.
Lee, W.Y., J.M. House, C. Park, and G.E. Kelly. 1996b.

Fault diagnosis of an air-handling unit using artificial
neural networks. ASHRAE Transactions 102(1):540-549.
Mangoubi, R.S. 1998. Robust Estimation and Failure

Detection. Springer-Verlag.
Markham, H.C ,(2001). An internet – based experts
system for teaching introductory data structures.Missouri
USA, Strata limited
Martin, Linda and Taylor, Wendy, A Booklet About CLIPS

Applications, NASA, Lyndon B. Johnson Space Center,
1991.
McKellar, M.G. 1987. Failure diagnosis for a household

refrigerator. Master's thesis, School of Mechanical
Engineering, Purdue University, West Lafayette, Indiana.
Morisot, O., and D. Marchio. 1999. Fault detection and

diagnosis on HVAC variable air volume system using
artificial neural network. Proc. IBPSA Building Simulation
1999, Kyoto, Japan.
NASA, Lyndon B. Johnson Space Center, CLIPS Basic

Programming Guide, 1991.
Ngo, D., and A. L. Dexter. 1999. A robust model-based

approach to diagnosing faults in air-handling units.
ASHRAE Transactions 105(1).
Norford, L.K., and R.D. Little. 1993. Fault detection and

monitoring in ventilation systems. ASHRAE Transactions
99(1):590-602.
Norford, L.K., J.A. Wright, R.A. Buswell, D. Luo, C.J.

Klaassen, and A. Suby. 2002. Demonstration of fault
detection and diagnosis methods for air-handling units
(ASHRAE 1020-RP). International Journal of Heating,
Ventilating, Air Conditioning and Refrigerating Research
8(1):41-71.
Patel, S.A., and A.K. Kamrani. 1996. Intelligent decision

support system for diagnosis and maintenance of
automated systems. Computers and Industrial
Engineering 30(2):297-319.
your own new copy.
Patton, R.J., P. Frank, and R. Clark. 1989. Fault Diagnosis

in Dynamic Systems, Theory and Application. Prentice
Hall.
Patton, R.J., C. Fantuzzi, and S. Simani. 2003. Model-

Based Fault Diagnosis in Dynamic Systems Using
Identification Techniques. New York: Springer-Verlag.
Patrick, m (2006): www. Search wind-development

techterms.com.
Pau, L.F. 1981. Failure Diagnosis and Performance

Monitoring. New York: Marcel Dekker.
Peitsman, H.C., and V. Bakker. 1996. Application of black-

box models to HVAC systems for fault detection. ASHRAE
Transactions 102(1):628-640.
Peitsman, H.C., and L.L. Soethout. 1997. ARX models and

real-time model-based diagnosis. ASHRAE Transactions
103(1):657-671.
PECI (Portland Energy Conservation Inc.) and Battelle

Northwest Division. 2003. Methods for automated and
continuous commissioning of building systems. ARTI
Report ARTI-21CR/610-30040-01. Arlington, Virginia: Air
Conditioning and Refrigeration Technology Institute.
Available on the Web at
http://www.arti-
21cr.org/research/completed/finalreports/30040-final.pdf.
P500-03-096, Architectural Energy Corporation, Boulder,

Colorado. Available on the Web at
http://www.archenergy.com/cec-eeb/P500-03-096-rev2-
final.pdf.
Rabl, A. 1988. Parameter estimation in buildings: Methods
for dynamic analysis of measured energy use. Journal of
Solar Energy Engineering 110:52-66.
Rebuilt Auto Car N' Truck Engines,

http://www.rebuilt-auto-engines.com,
Reddy, T. 1989. Application of dynamic building inverse

models to three occupied residences monitored non-
intrusively. Thermal Performance of the Exterior
Envelopes of Buildings IV. ASHRAE/DOE/BTECC/CIBSE.
Reddy, T.A., and K.K. Andersen. 2002. An evaluation of

classical steady-state off-line linear parameter estimation
methods applied to chiller performance data. International
Reddy, T.A., D. Niebur, K.K. Andersen, P.P. Pericolo, and

G. Cabrera. 2003. Evaluation of the suitability of different
chiller performance models for on-line training applied to
automated fault detection and diagnosis. International
Refrigerating Research 9(4).
Riemer, P.L, J.W. Mitchell, and W.A. Beckman. 2002. The

use of time series analysis in fault detection and diagnosis
methodologies. ASHRAE Transactions 108(2).
Rossi, T.M. 1995. Detection, diagnosis, and evaluation of

faults in vapor compression cycle equipment. Ph.D. thesis,
School of Mechanical Engineering, Purdue University, West
Lafayette, Indiana.
Rossi, T.M., and J.E. Braun. 1997. A statistical, rule-based

fault detection and diagnostic method for vapor
compression air conditioners. International Journal of
Heating, Ventilating, Air Conditioning and
your own new copy.
Refrigerating Research 3(1):19-37. Salsbury, T.I., and

R.C. Diamond. 2001. Fault detection in HVAC systems
using model-based feedforward control. Energy and
Buildings 33:403-415.
Shiozaki, J., and F. Miyasaka. 1999. A fault diagnosis tool
for HVAC systems using qualitative reasoning algorithms.
Proceedings of the Building Simulation ’99, 6th IBPSA
conference, Kyoto, Japan.
Showcars, OPEL Catalogue,

http://www.showcarsbodyparts.
com/opel.html. Mercedes Car Parts, Mercedes Catalogues,
A26, A27, A28, A28.6,
Shu-Hsien Liao (2005). Expert system methodologies and

applications -a decade review from 1995 to 2004, Expert
Systems with Applications,28, 93-103.
Sisk, D.R., M.R. Brambley, T.A. Carlon, and R.S. Briggs.

2003. Automated Diagnostics Software Requirements
Specification, Version 1.1. Battelle Report PNWD-3316.
Battelle Northwest Division, Richland, Washington.
Available on the web at
http://www.archenergy.com/cec-eeb/P2-Diagnostics/P2
Diagnostics_Reports/P5/D-2.5.4a-SoftwareR
equirementsSpecification1-1pnwd3316.pdf.
Smith R, Aderson H, and Morris J E (2004), Cylinders and

Cycles, Physics Department, Victoria University,
Wellington, New Zealand.
Sonderegger, R.C. 1977. Dynamic models of house

heating based on equivalent thermal parameters. Ph.D.
thesis, Center for Energy and Environmental Studies
Report No. 57. Princeton University, Princeton, NJ.
Sreedharan, P., and P. Haves. 2001. Comparison of chiller
models for use in model-based fault detection.
International Conference for Enhanced Building Operations
(ICEBO), organized by Texas A&M University, Austin, TX.
Stallard, L.A. 1989. Model based expert system for failure

detection and identification of household
refrigerators. Master's thesis, School of Mechanical
Engineering, Purdue University, West Lafayette, Indiana.
Stone Age Corporation and Car.com,
http://www.car.com/applications/engine/work.html
\
Subbarao, K. 1988. PSTAR—Primary and secondary terms

analysis and renormalization: A unified approach to
building energy simulations and short-term monitoring.
SERI/TR-253-3175.
Syed, S & Moyer, R. (1998). An intelligent home- based

healthcare information and diagnostics environment,
health informatics research group, school of computer
sciences, university sains makysia. New York; McGraw hill
Companies.
U Kiencke and L Nielsen, Automotive Control Systems: For
Engine, Driveline, and Vehicle. Berlin: Springer, 2000.
Venkatasubramanian, V., R. Rengaswamy, K. Yin, and S.

N. Kavuri. 2003a. A review of process fault detection and
diagnosis, Part I: Quantitative model-based methods.
Computers in Chemical Engineering 27:293-311.
Venkatasubramanian, V., R. Rengaswamy, K. Yin, and S.
N. Kavuri. 2003b. A review of process fault detection and
diagnosis, Part II: Qualitative models and search
strategies. Computers in Chemical Engineering 27:313-
326.
Wagner, J., and R. Shoureshi. 1992. Failure detection
diagnostics
your own new copy.
for thermofluid systems. Journal of Dynamic Systems,

Measurement, and Control 114(4):699-706.
Wiig, K. M. (1994). Knowledge management, the central
Management focus for intelligent-acting organization.
Arlington: Schema Press.
Willsky, A. S. 1976. A survey of design methods for failure

detection in dynamic systems. Automatica 29:601-611.
Yoshida, H., T. Iwami, H. Yuzawa, and M. Suzuki. 1996.
Typical faults of air-conditioning systems, and Fault
detection by ARX model and extended Kalman filter.
Yoshida, H., and S. Kumar. 1999. ARX and AFMM model-
based on-line real-time data base diagnosis of sudden
fault in AHU of VAV system. Energy Conversion &
Management 40:1191-1206.
Yu Qian, Xiuxi Li, Yanrong Jiang, Yanqin Wen (2003). An
Expert system for real-time failure diagnosis of complex
chemical processes, Expert Systems with Applications, 24,
425-432.
Zmeureanu, R. 2002. Prediction of the COP of existing

rooftop units using artificial neural networks and minimum
number of sensors. Energy and Buildings 27:889-904.
APPENDIX I
PROGRAM SOURCE CODE
Dim sql As String
Private Sub cboNatureofFaults_Click()

If cboNatureofFaults.ListIndex = 0 Then
txtProbableFaults.Text = "» Battery terminal connections loose" _
& vbCrLf & "or corroded Weekly checks." _
& vbCrLf & "» Battery discharged or faulty." _
& vbCrLf & "» Broken, loose or disconnected wiring in" _
& vbCrLf & "the starting circuit." _
& vbCrLf & "» Defective starter solenoid or switch." _
& vbCrLf & "» Defective starter motor." _
'& vbCrLf & "» Starter pinion or flywheel/drive plate ring" _
& vbCrLf & "gear teeth loose or broken." _
& vbCrLf & "» Engine earth strap broken or disconnected."
'probable solution
txtProbableSolution.Text = "Tighten your Battery terminal connections" _
& vbCrLf & "Connect broken strap and start car"
ElseIf cboNatureofFaults.ListIndex = 1 Then
txtProbableFaults.Text = "» Fuel tank empty." _
& vbCrLf & " » Battery discharged (engine rotates slowly)." _
& vbCrLf & "Battery terminal connections loose" _
& vbCrLf & "or corroded (“Weekly checks”)." _
& vbCrLf & "Ignition components damp or damaged." _
& vbCrLf & "Broken, loose or disconnected wiring in" _
& vbCrLf & "the ignition circuit." _
& vbCrLf & "» Worn, faulty or incorrectly-gapped spark plugs." _
& vbCrLf & "» Faulty choke or carburetor." _
& vbCrLf & "» Fuel injection system fault." _
& vbCrLf & "» Major mechanical failure (e.g. broken timing chain)"
txtProbableFaults.Text = "» Battery discharged." _
& vbCrLf & " » Battery terminal connections loose" _
& vbCrLf & "or corroded (“Weekly checks”)." _
& vbCrLf & "» Other ignition system fault." _
& vbCrLf & "» Low cylinder compressions"
txtProbableFaults.Text = "» Air filter element dirty or clogged." _
& vbCrLf & "» Low cylinder compressions."
txtProbableFaults.Text = "» Starter pinion or flywheel/drive plate ring" _
& vbCrLf & "gear teeth loose or broken." _
& vbCrLf & "» Starter motor mounting bolts loose or missing." _
your own new copy.
& vbCrLf & "» Starter motor internal components worn or damaged"
txtProbableFaults.Text = "» Worn, faulty or incorrectly-gapped spark plugs." _
& vbCrLf & "» Vacuum leak at the carburetor, throttle body," _
& vbCrLf & "inlet manifold, or associated hoses." _
& vbCrLf & "» Faulty carburetor." _
& vbCrLf & "» Fuel injection system fault."
txtProbableFaults.Text = "» Vacuum leak at the carburetor, throttle body," _
& vbCrLf & "» Fuel filter choked." _
& vbCrLf & "» Fuel pump faulty, or delivery pressure low." _
& vbCrLf & "» Fuel tank vent blocked, or fuel pipes restricted." _
txtProbableFaults.Text = "» Timing belt incorrectly fitted or tensioned." _
& vbCrLf & "» Fuel filter choked." _
& vbCrLf & "» Uneven or low cylinder compressions." _
& vbCrLf & "» Brakes binding." _
& vbCrLf & "» Clutch slipping."
txtProbableFaults.Text = "» Timing belt incorrectly fitted or tensioned." _
txtProbableFaults.Text = "» Loose or faulty electrical connections" _
& vbCrLf & "in the ignition circuit." _
& vbCrLf & "or inlet manifold." _
txtProbableFaults.Text = "» Incorrectly-adjusted idle speed." _
& vbCrLf & "» Air filter element clogged." _
& vbCrLf & "» Camshaft lobes worn." _
& vbCrLf & "» Timing belt incorrectly tensioned." _
& vbCrLf & "» Fuel injection system faul"
txtProbableFaults.Text = "» Worn, faulty or incorrectly-gapped spark plugs." _
& vbCrLf & "» Faulty spark plug HT leads." _
& vbCrLf & "inlet manifold or associated hoses." _
& vbCrLf & "» Distributor cap cracked or tracking internally." _
& vbCrLf & "» Disconnected, leaking," _
& vbCrLf & "or perished crankcase ventilation hoses."
txtProbableFaults.Text = "» Fuel filter choked." _
& vbCrLf & "» Fuel tank vent blocked, or fuel pipes restricted." _
& vbCrLf & "» Faulty spark plug HT leads." _
& vbCrLf & "» Distributor cap cracked or tracking internally." _
& vbCrLf & "» Faulty ignition coil." _
txtProbableFaults.Text = » _
& vbCrLf & "» Faulty oil pressure sensor.""Low oil level, or incorrect oil grade." _
& vbCrLf & "» Worn engine bearings and/or oil pump." _
& vbCrLf & "» Excessively high engine operating temperature." _
& vbCrLf & "» Oil pressure relief valve defective." _
& vbCrLf & "» Oil pick-up strainer clogged"
txtProbableFaults.Text = "» Excessive carbon build-up in engine." _
& vbCrLf & "» Excessively high engine operating temperature."
txtProbableFaults.Text = "» Ignition timing incorrect/ignition system fault." _
& vbCrLf & "» Incorrect grade of spark plug." _
& vbCrLf & "» Incorrect grade of fuel." _
& vbCrLf & "» Vacuum leak at carburetor, throttle body," _
& vbCrLf & "inlet manifold or associated hoses." _
& vbCrLf & "» Excessive carbon build-up in engine." _
your own new copy.

txtProbableFaults.Text = "» Leaking inlet manifold or throttle body gasket." _
& vbCrLf & "» Leaking exhaust manifold gasket" _
& vbCrLf & "» Leaking vacuum hose." _
& vbCrLf & "» Blowing cylinder head gasket"
txtProbableFaults.Text = "» Worn valve gear or camshaft." _
& vbCrLf & "» Incorrect valve clearances." _
& vbCrLf & "» Ancillary component fault (water pump, alternator, etc)."
Else: txtProbableFaults.Text = _
"» Worn big-end bearings (regular heavy" & vbCrLf & _
"knocking, perhaps less under load)." & vbCrLf & _
"» Worn main bearings (rumbling and knocking," & vbCrLf & _
"perhaps worsening under load)." & vbCrLf & _
"» Piston slap (most noticeable when cold)." & vbCrLf & "» Ancillary component fault
(water pump, alternator, etc)."
End If
End Sub
Private Sub cmdGo_Click()

On Error Resume Next
Dim strSearch As String
sql = "SELECT * FROM Registration WHERE Chasis_Number = '" &
txtChasisNumber.Text & "'"
Data1.RecordSource = sql
Data1.Refresh
'Me.Hide
DataBinding
End Sub
Private Sub DataBinding()
With Data1.Recordset
txtClientName.Text = !Client_Name
txtEngineNumber.Text = !Engine_Number
'!Chasis_Number = txtChasisNumber.Text
txtYearofPurchase.Text = !Year_of_Purchase
txtStateofPurchase.Text = !State_of_Purchase
End With
End Sub
Private Sub cmdLogin_Click()
If txtUserName.Text = "Henry" And txtPassword.Text = "Kelechi" Then
frmControlPanel.Show
Else
MsgBox "Access denied, Try again", vbInformation, "Login"
txtUserName.Text = "": txtPassword.Text = ""
End If
End Sub
Private Sub cmdModel_Click()

frmModels.Show
End Sub
Private Sub cmdRefresh_Click()

txtClientName.Text = "": txtEngineNumber.Text = "": txtChasisNumber.Text = "":
txtYearofPurchase.Text = "": txtStateofPurchase.Text = "": cboNatureofFaults.Text = ""
txtProbableFaults.Text = "": txtProbableSolution.Text = "": txtClientName.SetFocus
End Sub
Private Sub cmdReportCase_Click()

On Error Resume Next
With dbConnect.Recordset
.AddNew
!Client_Name = txtClientName.Text
!Engine_Number = txtEngineNumber.Text
!Chasis_Number = txtChasisNumber.Text
!Year_of_Purhase = txtYearofPurchase.Text
!State_of_Purchase = txtStateofPurchase.Text
!Nature_of_Faults = cboNatureofFaults.Text
!Probable_Faults = txtProbableFaults.Text
!Probable_Solution = txtProbableSolution.Text
.Update
End With
MsgBox "Case Reported", vbInformation, "Case Report"
cmdRefresh_Click
Exit Sub
End Sub
Private Sub cmdTips_Click()

frmTips.Show
End Sub
Private Sub Form_Load()

With cboNatureofFaults
.AddItem "Engine fails to rotate when attempting to start"
.AddItem "Engine rotates, but will not start"
.AddItem "Engine difficult to start when cold"
.AddItem "Engine difficult to start when hot"
.AddItem "Starter motor noisy or excessively-rough in engagement"
.AddItem "Engine hesitates on acceleration"
.AddItem "Engine stalls"
.AddItem "Engine lacks power"
.AddItem "Engine backfires"
.AddItem "Engine starts, but stops immediately"
.AddItem "Engine idles erratically"
your own new copy.
.AddItem "Engine misfires at idle speed"

.AddItem "Engine misfires throughout the driving speed range"
.AddItem "Oil pressure warning light illuminated with engine running"
.AddItem "Engine runs-on after switching off"
.AddItem "Engine noises Pre-ignition (pinking)or knocking during acceleration or under
load"
.AddItem "Whistling or wheezing noises"
.AddItem "Tapping or rattling noises"
.AddItem "Knocking or thumping noises"
End With
End Sub
Private Sub lblClose_Click()

Unload Me
End Sub
Dim sql As String
Private Sub cmdCancel_Click()

txtClientName.Text = "": txtLocation.Text = "": txtMobilePhone.Text = "":
cboVehicleType.Text = ""
txtLisenceNumber.Text = "": txtEngineNumber.Text = "": txtChasisNumber.Text = "":
txtDate.Text = ""
txtYearofPurchase.Text = "": cboStateofPurchase.Text = "": txtClientName.SetFocus
End Sub
Private Sub cmdClose_Click()

Me.Hide
End Sub
Private Sub cmdDelete_Click()

'delete code here
Dim strDelete_Record As String
Dim strdelete As String
strdelete = "No Record Found/Your database is empty"
strDelete_Record = "Record Deleted"
With dbCon.Recordset
.Delete
MsgBox strDelete_Record, vbInformation, "NGI EMP INF SYS"
.MoveNext
If .EOF Then
.MoveFirst
MsgBox strdelete, vbCritical, "Automobile Fault DetectionS"
End If
'ElseIf .BOF Then
'.MoveFirst
'Else
'End If
End With
End Sub
Private Sub cmdDiagnosis_Click()

frmFaultDiagnosis.Show
End Sub
'Dim sql As String
Private Sub cmdGo_Click()

Dim strSearch As String
sql = "SELECT * FROM Registration WHERE Chasis_Number = '" & txtSearch.Text &
"'"
dbCon.RecordSource = sql
dbCon.Refresh
Me.Hide
DataBinding
End Sub
Private Sub DataBinding()
frmClientregistration.Show
On Error GoTo err
txtClientName.Text = !Client_Name
txtLocation.Text = !Location
txtMobilePhone.Text = !Mobile_Phone
cboVehicleType.Text = !Vehicle_Type
txtLisenceNumber.Text = !Lisence_Number
txtEngineNumber.Text = !Engine_Number
txtChasisNumber.Text = !Chasis_Number
txtDate.Text = !Date
txtYearofPurchase.Text = !Year_of_Purchase
cboStateofPurchase.Text = !State_of_Purchase
End With
err:
MsgBox err.Description, vbCritical, "Search Error"
End Sub
Private Sub cmdSubmit_Click()
'On Error Resume Next
.AddNew
!Client_Name = txtClientName.Text
!Location = txtLocation.Text
!Mobile_Phone = txtMobilePhone.Text
!Vehicle_Type = cboVehicleType.Text
!Lisence_Number = txtLisenceNumber.Text
!Engine_Number = txtEngineNumber.Text
!Chasis_Number = txtChasisNumber.Text
your own new copy.
!Date = txtDate.Text
!Year_of_Purchase = txtYearofPurchase.Text
!State_of_Purchase = cboStateofPurchase.Text
.Update
End With
MsgBox "Client registered", vbInformation, "Registration"
cmdCancel_Click
Exit Sub
End Sub
Private Sub Label3_Click()

Unload Me
End Sub
Dim sql As String
Private Sub cmdClientsRecords_Click()
frmViewDiagnosisRecords.Visible = False
frmViewClientsRecords.Visible = True
End Sub
Private Sub cmdDiagnosis_Click()

frmViewClientsRecords.Visible = False
frmViewDiagnosisRecords.Visible = True
End Sub
Private Sub cmdSearchCriteria_Click()

frmViewClientsRecords.Visible = True
If cmdSearchCriteria.ListIndex = 0 Then
sql = "SELECT * FROM Registration WHERE mobile_Phone IS NOT NULL"
Data1.Refresh
ElseIf cmdSearchCriteria.ListIndex = 1 Then

sql = "SELECT * FROM Registration WHERE Chasis_Number LIKE '%IM%'"
Data1.Refresh
ElseIf cmdSearchCriteria.ListIndex = 2 Then

sql = "SELECT * FROM Registration WHERE Lisence_Number IS NOT NULL"
Data1.Refresh
Else 'cmdSearchCriteria.ListIndex = 3 Then

sql = "SELECT * FROM Registration WHERE STATE_of_Purchase IN
('ABUJA','LAGOS','IMO','ENUGU')"
Data1.Refresh
End If
End Sub
Private Sub Command1_Click()

DataReport1.Show
End Sub
Private Sub Form_Load()

With cmdSearchCriteria
.AddItem "Mobile Phone"
.AddItem "Chasis Number"
.AddItem "Vehicle Number"
.AddItem "State of Purchase"
End With
End Sub
Private Sub lblClose_Click()

Unload Me
End Sub
APPENDIX II
PROGRAM OUTPUT
your own new copy.
your own new copy.

Design and Implementation of An Expert Management System For Automobile Fault Detection and Diagnosis

Uploaded by

Document Information

Original Description:

Original Title

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

Design and Implementation of An Expert Management System For Automobile Fault Detection and Diagnosis

Uploaded by

Copyright:

Available Formats

DESIGN AND IMPLEMENTATION OF

AN EXPERT MANAGEMENT SYSTEM FOR

A PROJECT RESEARCH SUBMITTED TO THE

This is to certify that this project written by ---------- with

I dedicate this work to Almighty God.

Very sincerely, my first greeting goes --------------------

2.3 Testing Expert System 19

1.1 BACKGROUND OF THE STUDY

1.2 STATEMENT OF THE PROBLEM

In dealing with problems of a car and troubleshooting,

1.3 OBJECTIVES OF THE STUDY

1.4 SIGNIFICANCE OF THE STUDY

 Expert system are not vulnerable to problems such as

1.5 SCOPE OF THE STUDY

1.6 LIMITATION OF THE STUDY

1.8 DEFINITION OF TERMS

ignition, fuelling and various mechanical engine

that emulates the decision making ability of a human expert”.

at an integrated recommendation (Edmunels, 2008, Liebowitz,

2.2 THE CONCEPTUAL STRUCTURE OF AN EXPERT

2.2.1 Problem Assessment

Task 5: Select the best project

2.2.2 Knowledge Acquisition

2.2.3 Knowledge Representation

(Townsend, 2007). The knowledge engineer, working with the

2.3 TESTING EXPERT SYSTEM

may be necessary before making a final version of the system

So, doctors have to come up with quick guesses about likely

3.3 KNOWLEDGE ACQUSITION

3.3.1 DOMAIN EXPERT

The domain expert is the individual who is a professional

blocked fuel filter 4.0 Replace fuel filter

FIGURE 3.1 CONSULTATION TABLE

3.3.5 CORRECTION/ EXPLANATION

3.4 SYSTEM DESIGN

have been designed, the development phase was started for

3.4.1 RULE BASED DEVELOPMENT MODEL

Knowledge Knowledge Inference User User

STRUCTURE OF A RULE BASE EXPERT SYSTEM MODEL

 Knowledge base models a human’s long term memory as

3.4.2 INFERENCE TECHNIQUES

of damages which need different solutions and troubleshooting.

SYSTEM FLOW CHART

Insert information in the

Check rule Check next rule

Add conclusion to Premise Rules

Display login screen

Show client details and Connect too data

3.5 PROGRAM DESIGN

HIGH LEVEL MODEL OF THE PROPOSED SYSTEM

Implementation is to carrying out execution, or practices

4.2 SYSTEM REQUIEMENTS

Minimum hardware requirements:

MINIMUM SOFTWARE REQUIREMENTS.

testing phase. This is to make sure that the system can be

4.5 PROGRAM DOCUMENTATION

explanation and help mechanisms. The documentation also

4.5.1 SAMPLE INPUT/OUTPUT DATA FORMATS

4.5.2 LOADING THE PACKAGE

Adams, R & Bath N,(1999). An expert system based

AEC (Architectural Energy Corporation). 2003. Final

Andersen, K.K., and T.A. Reddy, 2002. The error in