Emisson validation system

An emissions validation system is comprised of a plurality of sensors (42), (36), (26) and (34) for monitoring the various emissions and diagnostic aspects of a vehicle (10). An emissions validation system (18) is operable upon refuelling through a refuelling line (20) to interface through an interface (14) to a CPU (28). The CPU (28) retrieves the stored dam and transfers it through the interface (14), through an electrical line (22) to a main CPU (26) in the emissions validation system (18). The main CPU (26) then evaluates this dam, in addition to monitoring the amount of fuel that is placed back into the vehicle's tank (32). This allows a complete record of the vehicles history to be maintained.

BACKGROUND OF THE INVENTION 
In recent years, the reduction of emissions has received an increasing 
amount of attention. Although there have been a number of relatively low 
emission alternatives to the internal combustion engine, the internal 
combustion engine utilizing diesel or gasoline has survived, due in part 
to the ability of engineers to constantly improve emission controls and 
maintain the internal combustion engine at governmental specified 
standards. However, one problem that exists with respect to emission 
control systems is with respect to maintaining the controls in some state 
of repair. As such, an automobile when it leaves the factory may meet 
emission standards, but this can change over time such that the bulk of 
the vehicles on the road no longer come close to meeting emission 
standards. One method employed by municipalities to reduce emissions has 
been to require periodic inspections that utilize computerized systems to 
measure the emissions, with the result that a validation sticker is not 
provided to the owner of the vehicle unless the emission tests have been 
passed. If not passed, the owner of the vehicle is given a certain amount 
of time to repair the vehicle and bring it within the standards. Although 
the systems have improved the level of emissions entering the environment, 
they typically operate on a periodic basis and are relatively easy to 
tamper with. 
Another alternative that has been looked into is alternative fuel systems 
such as natural gas and propane, as these are cleaner burning fuels. 
Typically, the average consumer does not purchase this type of fuel and 
the vehicles that can burn them, due to the relatively difficult access to 
these fuels. However, governments and large organizations do have the 
ability to switch over to these type of fuels, since they typically 
maintain their own fuel supply. Further, the government has introduced 
certain incentive plans that provide tax breaks, etc., for an organization 
or municipality that provides a plan for reducing overall emissions with 
vehicles that can burn these fuels. 
SUMMARY OF THE INVENTION 
The present invention disclosed and claimed herein comprises an emission 
validation system. The emission validation system includes a vehicle 
fueling system associated with a vehicle and a fuel station for dispensing 
fuel from a main fuel tank to the fuel tank of the vehicle. The vehicle 
fueling system has associated therewith a sensor for sensing performance 
parameters of the vehicle, the performance parameters including emission 
parameters. A memory device is provided for averaging and storing the 
operating parameters over a predetermined period of time to provide a 
history of the operating parameters over the predetermined period of time. 
A vehicle interface device is operable to access the stored history 
information from the memory device in conjunction with fuel being input to 
the fuel tank through a fuel intake port. The fuel station includes a fuel 
station interface device that is operable to be interfaced with the 
vehicle interface device to allow the accessed history information to be 
transferred through the fuel station interface device to a processor. A 
fuel dispensing system is operable to dispense fuel from the main fuel 
tank to the vehicle tank through the intake port with a fuel flow meter 
operable to sense the fuel delivered to the vehicle. The processor is 
operable to control the vehicle interface device and the fuel station 
interface device to access the stored history from the memory device and 
the vehicle to update a main database. The main database contains the 
overall operating history of the vehicle, which is updated for each 
fueling operation. 
In another aspect of the present invention, the history stored in the 
memory device comprises a history of the performance parameters over a 
period of time between fueling operations. Upon receiving a request for 
fuel delivery to the vehicle, the fueling station is also operable to 
compare the accessed history information with predetermined history 
standards. If the accessed history information meets or exceeds these 
predetermined history standards, fuel is delivered to the vehicle. 
However, if the accessed history information does not meet the 
predetermined history standards, the fuel delivery to the vehicle is 
inhibited. 
The vehicle interface device and fuel station interface device comprise 
mated connectors. The vehicle interface device connector is disposed 
proximate to the fuel intake port such that the fuel station interface 
device connector can be mated thereto prior to initiating the fueling 
operation and wherein the fuel delivery device is disposed within the 
intake port. 
An alternate embodiment of the vehicle interface device and fuel station 
interface device comprises an IC card. The IC card has associated 
therewith a memory and processing system and an interface connector. The 
interfaced connector is operable to be interfaced with a card reader on 
the vehicle, which card reader is operable to interface with the memory 
device to allow access of the stored history information for transfer to 
the memory in the IC card. The IC card is then transferred to the fuel 
station and an associated IC card reader disposed thereat. The information 
in the memory associated with the IC card can then be transferred to the 
processing system.

DETAILED DESCRIPTION OF THE INVENTION 
Referring now to FIG. 1, there is illustrated a perspective view of the 
emission validation system for delivering fuel to a vehicle. A vehicle 10 
is provided, which has an inlet 12 for receiving fuel and an emissions 
validation interface 14. An emissions validation system 18 is provided, 
which is operable to deliver fuel to the inlet 12 through a fuel supplying 
hose 20. In addition, an electronic cable 22 is provided for interfacing 
with interface 14. Whenever fuel is delivered to the vehicle, information 
is transmitted between the automobile 10 and the emissions validation 
system 18. 
Referring now to FIG. 2, there is illustrated a schematic view of the 
automobile 10 and the emissions validation system 18. The automobile 10 
has a plurality of sensors associated therewith. An automobile engine 24 
has associated therewith sensors 26, which are routed to a central 
processing unit (CPU) 28 through wires 30. Additionally, a fuel tank 32 is 
provided which is interfaced with the inlet 12. The fuel tank 32 has a 
sensor 34 associated therewith to determine the various fuel levels. The 
mileage of the car is determined by a sensor 36, which is disposed on a 
drive shaft 38 that drives the wheels of the vehicle. Further, an exhaust 
system 40 associated with the car has an emissions sensor 42 associated 
therewith. The sensor 34, the sensor 36 and the sensor 42 are all 
connected to the CPU 28. 
The CPU 28 is connected through a cable 40 to the interface 14, which is 
connected to a main CPU 26 in the emissions validation system 18. Fuel is 
provided through the hose 20 and controlled with a fuel flow meter 22. The 
fuel flow meter provides an input to the main CPU 26 to determine how much 
fuel is being input to the vehicle 10 from a main tank 44. 
The emissions validation system 18 is operable to collect emissions data 
from the vehicle 10 with the sensors associated with the vehicle 10 being 
essentially modifications of conventional engines and exhaust monitoring 
systems used on motor vehicles and/or stationary combustion engines (such 
as portable electric power generators and air compressors). The emissions 
validation system 18 collects data through electrical signals received 
from the sensors on the engine and an exhaust system. The sensors are 
located in the exhaust stream near the exit vent of the exhaust pipe, 
after the pollution control system and muffler. The type of sensors that 
are utilized are electopotentiometric gas specific sensors for oxygen, 
carbon monoxide, carbon dioxide, oxides of sulfur, oxides of nitrogen, 
hydrocarbons, and heavy metals such as lead suspensions and tetraethyl 
lead; mass spectrometric detectors capable of generating an analog or a 
digitized signal representing intensities of ions characteristic of the 
above compounds and substances; gas chromatography separation and sensor 
systems capable of generating signals for the above substances, and 
spectrometers generating signals indicating intensity of absorption of 
light for various atomic and molecular modes of absorption of those 
compounds. Examples of types of electrochemical sensors are: Dynamation, 
Inc. Model 929, McNeill International Model 3E for CO, Models 3NT or 3NSS 
for NO, Model 3NDH for NO.sub.2, Models 3ST and 3SS for SO.sub.2, 
Bacharach Sentinel 4 Model for CO, SO.sub.2, NO, NOX, total hydrocarbons; 
the Industrial Scientific Model TMX410. Examples of gas chromatographic 
sensors are Dynamation Model CGM gas monitor, and HP 92 manufactured by 
Hewlett Packard. Examples of mass spectrometer sensors are Bruker-Franzen 
Model MM1, Teledyne Model CBMS, Milton Roy, Fisons Instruments UG Prima 
600X. Examples of Spectra sensors are the McNeill CO.sub.2 ambient 
monitor, Horiba HRE-2362A, Servomex Model 2500, Teledyne Analytical 
Instruments Model 911. 
The signals that are collected in the automobile are propagated by the 
sensors through the insulated wires connected to the CPU 28 to the 
interface device 14. The interface device 14 is an electrical or optical 
cable manifold that is located next to the refilling point of the fuel 
tank on the vehicle. However, as will be described hereinbelow, this 
information could be transferred to an IC card for storage therein and 
transfer to a similar card reader on the emissions validation system 18. 
The interface 14 channels the wires from the CPU 28 into a standard 
electrical or optic fiber connector mounted to be accessible when the fuel 
cap protector is open. The connector mates to a matching connector on the 
electrical cable 22 that is attached to the fuel line 20 on a bearing 
mount in such a manner that the rotation of the refueling line does not 
twist a cable leading from the end of the refueling line to the fuel pump 
housing. 
In addition to information from the sensors, signals generated by the CPU 
28 also provide information regarding vehicle identification codes. A 
vehicle identification code generator is provided that reads signals from 
the vehicle engine Ignition Control System, through wires or fibers 
connected to a module typically located under the vehicle dashboard 
display. The vehicle identification code generator collects Ignition 
Control System data and reads out the vehicle identification, vehicle 
mileage and other data in response to a control signal sent from the 
computer. When the vehicle emission system 18 collects the various data, 
it is used to determine the following items: 
1. VMT (Vehicle Miles Travelled) per vehicle and for fleets; 
2. Fuel economy (both VMT divided by fuel quantity and VMT divided by fuel 
costs) for each vehicle and fleet; 
3. Emissions per vehicle and for aggregate fleet of measured pollutants on 
daily, weekly, monthly and annual basis; 
4. Identification of vehicles operating outside relevant regulatory 
emission standards; 
5. Volume of emissions above or below standards per vehicle and for 
aggregate fleet; 
6. EPA vehicle emission credits earned for vehicles operating at levels 
better than required by relevant standards. 
Referring now to FIG. 3, there is illustrated a block diagram of the 
electronics for the fueling system on the fueling station. The refueling 
system on the vehicle is comprised of a transfer interface 50 that is 
interconnected with the cable 22 to provide a data path. The fuel tank 32 
is connected to the fuel intake port 12 to fuel line 20. The fueling 
station is comprised of a central processing unit (CPU) 52 and a memory 
54, that CPU 52 and memory 54 corresponding to the main CPU 26 in FIG. 2. 
A transfer interface 26 is provided at the fueling station for interfacing 
with the cable 22. The output of the transfer interface 56 is connected 
through an I/O interface 58 to the CPU 52. Additionally, a fuel flow meter 
60 and fuel level sensor 62 are provided to interface between the fuel 
tank 44 and the I/O interface 58. Further, a modem 66 is provided for 
interfacing with the CPU 52 and memory 54 to allow the system to interface 
through a telephone line with the main station or through a network I/F. 
Referring now to FIG. 4, there is illustrated a detailed block diagram of 
the CPU 28 and the associated circuitry for storing the data. The CPU 28 
is connected through a digital bus 70 to a memory 68. The digital bus 70 
is generally comprised of a data bus and an address bus. The memory 68 is 
generally comprised of non-volatile Read Only Memory (ROM) for storing the 
program instructions and also comprised of some scratch pad Random Access 
Memory (RAM). A data storage and transfer device 72 is also provided which 
is generally comprised of Random Access Memory. The Random Access Memory 
is typically volatile, but can be made non-volatile by using battery 
backed-up RAMs. The power supply in the battery 73 is provided for 
powering the overall system. However, battery backed-up RAMs typically 
comprise small lithium cells that are associated therewith and made an 
integral part of the package. Further, lithium cells can be provided on 
the board on which the CPU 28 and data storage and transfer device 72 are 
disposed. The data storage and transfer device 72 is operable to be 
interfaced through the cable 40 to the transfer interface 50. When the 
cable 22 is connected to the transfer interface 50, thus connecting it to 
the transfer interface 56, the data storage and transfer device 72 senses 
this and initiates the dam transfer. 
The CPU 28 communicates with an analog-to-digital (A/D) I/O interface 76 
through a digital bus 74. The A/D interface 76 is operable to interface 
with a sensor bank 70 and the vehicle engine and exhaust system through a 
plurality of analog lines 78. The sensors 80 comprise a bank of sensors 
which generally define the sensor 42. However, it should be understood 
that the sensor bank 80 also represents the other sensors 34, 36 and 26, 
which monitor other aspects of the system. Further, the analog lines 78 
can also interface with various diagnostic sensors. Additionally, other 
processors that are built into the vehicle can generate digital data which 
can be transferred through a digital interface (not shown) to the CPU 28. 
The CPU 28 is then operable to route this information to the data storage 
and transfer device 72. The data storage and transfer device 72 is 
comprised of a dual port RAM. 
The fueling station is generally comprised of the emissions validation 
system 18, which is operable to communicate with a central data collection 
and transfer facility 82, the central data collection and transfer 
facility 82 having a modem or network I/F 84 that can communicate with the 
modem or network I/F 66 through a communication link 86. In this manner, 
the data that is received through the transfer interface 56 at the fueling 
station can be immediately transferred to the central data collection and 
transfer facility. Typically, this data is buffered at the fueling station 
and then transferred at a later time, either upon initiation by the 
fueling station or in response to a poll from the central data collection 
and transfer facility. This type of data processing is conventional with 
respect to credit verification in Automatic Teller Machines (ATMs). 
Referring now to FIG. 5, there is illustrated an alternate embodiment of 
the invention, wherein the dam is not transferred through a transfer 
interface device. In the system illustrated in FIG. 5, the vehicle CPU 28 
interfaces with a card reader interface 90. The card reader interface 90 
is operable to interface with an IC card 92. The IC card 92 is the type of 
card that is referred to as a "smart" card. This type of card is typically 
a rectangular-shaped, thin, laminated member having a memory 94 and a 
processing unit 96 associated therewith. Additionally, the IC card 92 has 
a battery associated therewith. Some type of connector is provided for 
interfacing with the card reader 90, such that when the IC card 92 is 
inserted into the card reader interface 90, processing instructions in the 
IC card 92 can interface with the card reader interface 90 and to the CPU 
28. This connector typically utilizes an RS232 serial data protocol. This 
allows the CPU 28 to download data into the card reader 92, which card 
reader 92 can also have a prestored identification number associated with 
the card 92. 
The IC card 92 is operable to be removed upon entering a fueling station 
and inserted into a card reader interface 98 and allow the IC card 92 to 
interface with the CPU 26. The CPU 26 can then access the data stored in 
the memory 94 within the card 92. Since this data is comprised in part of 
an identification number, the CPU 26 can then scan its local memory 54 to 
determine if an ID list exists having the ID of the card 92 associated 
therewith. If not, the CPU 26 can then interface with the central data 
collection and transfer facility to validate the card. 
Upon validation of the card, the CPU 26 then allows fuel to be transferred 
to the vehicle through a fuel control valve 100. This information is 
monitored and stored in a main database at the central data collection and 
transfer facility. Further, the data can be stored on the IC card 92, 
which IC card 92 could be integrally associated with the vehicle, similar 
to the operation of a key. Therefore, a complete record of the vehicle's 
emission and fuel usage could be permanently associated with the vehicle 
through the memory 94 in the card 92. Further, a command could be entered 
prior to using the fueling station to transfer data to the IC card 92 
prior to removal. 
Referring now to FIG. 6, there is illustrated a side view of the interface 
50 and 56. Typically, the fuel line 20 is connected to a nozzle 104, which 
nozzle 104 is operable to allow an operator to dispense gas into the fuel 
tank through the inlet 12. Illustrated in FIG. 6 is an optical interface 
utilizing some type of optical fibers with a connection that allows a 
light path to be generated between the transfer interface 50 and the 
transfer interface 56. FIG. 6a illustrates one embodiment wherein a bundle 
of optical fibers 110 is associated with the transfer interface 50, such 
that they abut up against the outermost surface thereof. A second bundle 
of optical fibers 112 is disposed at the transfer interface 56 side with 
the ends thereof abutting up against the outermost surface thereof. The 
two transfer interfaces 50 and 56 are operable to mate in such a manner 
that the ends of the corresponding fibers in bundles 110 and 112 match up 
and allow data transfer to occur therebetween. With such a configuration, 
it is not necessary to have any type of electrical current flowing through 
an electrical connection, which electrical connection could cause a spark 
and be a hazard. 
FIG. 6b illustrates an alternate embodiment of the optical coupling wherein 
a plurality of diodes 114 are disposed on the transfer interface 50 and 
interfaced with a plurality of electrical wires 116, which are connected 
to drivers (not shown). The transfer interface 56 has a plurality of 
opto-receivers 118 which are operable to receive the light emitted from 
the light emitting diodes 50, the light emitting diodes 50 providing for 
transfer of a digital word across the interface. The opto-receivers 118 
are connected through wires 120 to a set of receivers and preamplifiers 
(not shown). 
Referring now to FIG. 7, there is illustrated a flowchart for the operation 
of the vehicle refueling system. The program is initiated at a start block 
122 and then proceeds to a function block 124 to sample the sensor 
outputs. This information is then averaged and stored in the memory 
device, as indicated by a function block 126. The program then proceeds to 
a decision block 128 to determine whether access has been requested 
through the interface device 50. If not, this indicates that a refueling 
operation has not begun. The program would return back to the input of 
function block 124. 
If an access has been requested, the program will flow to a decision block 
130 to determine if a connection has been made. If not, the program loops 
back to the input. If so, the program flows to a function block 132 to 
download the stored parameters and the associated ID of the vehicle. The 
program would then flow to a decision block 134 to wait for all dam to be 
transferred. When all data is transferred, the program flows to a decision 
block 136 to determine whether initialized values are to be returned. As 
described above, certain parameters that are measured, such as fuel level, 
may have initial parameters that are required. These can be returned by 
the fueling station. However, in certain instances, everything is zeroed 
after a refueling operation. If initialized values are returned, the 
program flows to a function block 138 to update the initial values and 
zero the overall averaging operation. If no initialized values are to be 
returned, the program flows around the function block 138, both function 
blocks 138 and the bypass path input to a return block 140. The system 
will then return to the start block 122 and again sample the sensors 124 
and update the stored parameters. 
Referring now to FIG. 8, them is illustrated a flowchart depicting the 
operation in the fueling station. The program is initiated at a start 
block 142 and then proceeds to a decision block 144 to determine whether a 
connection has been requested, i.e., a fueling operation has begun. If 
not, the program loops back to the input of the decision block 144. If a 
connection has been requested, the program flows to a function block 146 
to download data and ID information through the dam link between the 
vehicle and the fueling station. The program then flows to a function 
block 148 to determine if a valid ID was received. If not, the program 
flows to a function block 150 to deny access. However, if a valid ID was 
transferred and compared true with a stored list, the program would flow 
to a function block 152 to compare the history of the averaged data 
accessed from the vehicle to predetermined history standards. These 
predetermined history standards provide a benchmark for the operation. The 
program would then flow to a decision block 154 to determine whether the 
accessed history information meets or exceeds the predetermined standards. 
If not, the program would flow to a function block 156 to generate a 
negative validation report and then to a function block 158 to require the 
system operator to request fuel access before access would be allowed. 
If the accessed history meets or exceeds the predetermined standards, the 
program would flow from decision block 154 to a function block 160 to 
provide a validation okay signal. The program would then flow to a 
function block 162 to generate a validation okay report and then to a 
function block 164 to allow fuel access. The output of function blocks 158 
and 164 then flows to a function block 166 to update the main database for 
the vehicle and for the fleet. The program then flows to a decision block 
168 to determine whether data is to be returned to the vehicle in the form 
of initialized parameters. If not, the program flows to a return block 172 
and, if so, the program flows through a function block 170 to the return 
block 172, function block 170 providing a transfer of initializing 
parameters such as fuel level, fuel provided to the vehicle, etc. 
Referring now to FIG. 9, there is illustrated a flowchart depicting the 
operation of the IC card at the vehicle refueling system. The program is 
initiated at a start block 174 and then proceeds to a decision block 176 
to determine whether the IC card is installed. If not, the program loops 
back to the input to wait for the card to be installed. If a card is 
installed, the program flows to a decision block 178 to determine whether 
the operation is an upload operation, i.e., data is to be transferred to 
the card. If so, the program flows to a function block 180 to transfer 
history data to the card from the vehicle memory device, and then to a 
return block 182. If data is to be downloaded to the IC card, the program 
would flow to a function block 184 to transfer initializing data from the 
card to the vehicle processing system. The program would then flow to a 
function block 186 to initialize and update the overall operating 
parameters of the system and then to a return block 188. 
Referring now to FIG. 10, there is illustrated a flowchart depicting the 
operation of the IC card reader at the fueling station. The program is 
initiated at a start block 190 and then proceeds to a decision block 192 
to determine whether the card has been installed. If not, the program 
loops back to the input. If so, the program flows to a function block 194 
to determine whether the data is to be uploaded. If so, the program flows 
to a function block 196 to transfer initializing values to the IC card and 
then to a return block 198. If data is to be downloaded, the program flows 
from decision block 194 to a function block 200 to transfer data from the 
card to the processing system at the fueling station. The program then 
flows to a function block 202 indicating the operation wherein the ID is 
validated. The program will then flow to the return block 198. 
In summary, there is provided a system that allows automatic monitoring and 
downloading of data from a diagnostic and emissions monitoring system on a 
vehicle. This information is stored in a memory on the vehicle and, at a 
later time, transferred to an emissions validation system. The emissions 
validation system requires this transfer in conjunction with a refueling 
operation. Upon refueling, an interface is effected whereby the diagnostic 
and/or emissions information associated with the vehicle is transferred to 
the emissions validation system and then transferred to a main database 
for evaluation thereof. 
Although the preferred embodiment has been described in detail, it should 
be understood that various changes, substitutions and alterations can be 
made therein without departing from the spirit and scope of the invention 
as defined by the appended claims.