TOYOBD1 :: OVERVIEW

SYSTEM REQUIREMENTS

TOYOTA OBD1 compliant ECU 
Phone or table running Android 2.3.3 or higher with Bluetooth capabilities
OBD1READ device connected to your car

outdated overall demonstration(2014)

SENSOR MONITORING 

 Most engine sensors reading are available

1. Engine RPM
2. Throttle position sensor state
3. VAF or MAF or MAP sensor reading 
4. Oxygen sensors state, either RICH or LEAN
5. Engine coolant temperature
6. Car speed 
7. IDL switch state 
8. Knock sensor state (either knocking badly or not at all.)
9. Neutral start switch state
10. Starter switch state

Some calculated fields are available 

1. Car fuel consumption in MPG,KM/L, L/100KM
2. Injector duty cycle

 Some output values are available

1. Ignition angle
2. Idle air control valve state
3. Injector opening duration
4. Short term fuel trims
5. Acceleration enrichment state
6. After start enrichment state
7. Closed or Open loop state
8. ECU self-diagnostic state
9. Warm-up enrichment state

GRAPHICAL VIEW

TEXT VIEWS

GAUGES VIEW

TRIP COMPUTER 

A trip computer mode is available for those interested in monitoring fuel consumption through time

THERMAL ALARM 

A thermal alarm feature is built into the application in case coolant temperature rise above 100C (default value which can be altered )this might save you a lot of trouble some day.

CARPUTER MODE

You can let the tablet control when it connects to the car and when it goes to sleep as long as you configured the app to do so.

DATA LOGGING

All data frame received from the ECU is kept in a database on the phone and is available for export to .CSV for spreadsheet analysis and custom algorithms inputs.You can import data from someone else phone and replay that data from your phone.

DIAGNOSING WITHOUT EVEN BEING THERE

Using this application you can know quickly if there are bad or missing sensor readings from logs you send to someone else. With such logs it is possible to point toward a culprit to the issues without even seeing the car yourself.

  Simple test cases

1. TPS IDL switch operation
2. TPS analog signal operation
3. Map sensor operation
4. Coolant temp sensor operation
5. Detect engine overheating
6. Ox sensor operation
7. transmission speed sensor operation
8. Sticky STA starter switch signal.
9. Error code brewing but not yet thrown by the ECU.

Advanced test cases

1. Recognize bad engine vacuum from MAP sensor reading.
2. Detect a bad thermostat through coolant temp monitoring.
3. Gauge engine performance through VAF sensor monitoring.
4. Gauge fueling issues through ox sensor, injector duration and short term fuel trim monitoring.
5. feedback for Flap door AFM tuning for engine with VAF sensors.

DATA MINING PRIOR TO A STAND ALONE ECU INSTALL

Using this application you can extrapolate data to build a base file configuration for a fully configurable ECU.

1. Cranking ignition timing
2. End point of warm up enrichment for your engine( this varies a lot on different ecu models. some stop early, some quite late)
3. Base ignition timing at hot idle
4. base fuel maps, (you need to take the time to log in every engine loads while being in OPEN loop mode) this can be tedious because of the obd1 protocol.
5. base ignition timing( same method here)
6. Idle air control valve usage strategy used for your engine.
7. When the Closed loop control switches to Open loop