DIY 22P cable preparation

Usually found on e-bay named 22 Pin OBD1 to 16Pin OBD2 or something alike. 

 

Depending on vendors , internal wire count and color will vary so no definitive color code is to be shared. You need to find out which pin out your own cable uses.

Here are the tools of the trade today

 

First of all please draw the diagnosis box Pinout , found in toyobd1 glossary dialog on a paper sheet. this will be very useful when you will be testing continuity and when you will be soldering to the OBD1READ at a later time.

    

 

 Here are the steps needed before finding out the cable pin out

• buy a cable
• chop off the OBD2 end with heavy duty scissors. use tweezers to make a cleaner cut on the individual wires.
• using the tweezers or specialized sleeve cuter remove external sleeve from the black cable ,about 1.5" of it
• using the wire stripper, strip all individual wires 

Using a multimeter or anything capable to test wire continuity you will find out which are the wire of interest.

Write down the cable pin out as you find it on your paper sheet

After the elimination process is complete, simply chop off unused wires.

 

At that point the cable is ready for being soldered onto an OBD1READ board.

The soldering to an OBD1READ board will be documented at a later time.

OBD1READ :: What if your ECU is supported, but your wiring harness is missing wires?!

In the 90s TOYOTA decided to save money on wires...sometimes!

The diagnosis box will show spaces for signals and those signals won't have any wires and contact going to them. Looking inside the ECU can prove the ECU pinout is OK for OBD1READ to work. You would find TE2,VF,B+ and E1 at the ECU printed circuit board, but TE2 would be missing in the engine wiring harness that goes to the Diagnosis Box. Without TE2 it is not possible to trigger data output,so we need to get TE2 into the diagnosis box.

You can also be in this situation if you updated your ECU to a newer sibling , using an older wiring harness.
here is a few examples
ST165->92+ 3S-GTE
90-91 ST185->92+ 3S-GTE
90-91 EP82-> 92+ 4E-FTE

Here is what you can do to make your wiring harness OK to for use with OBD1READ.

 I suggest using micro screw drivers to work on releasing the contacts from a connector and diagnosis box, it takes some time to master this. I will not go into depth on this subject in this post.(You will probably need to do this to get your spare contacts from a junkyard harness)

You need to find TE2 inside the ECU,

Then you need to add a new contact wire to the corresponding ECU connector.

After you have a contact going into the connector you need to solder a wire to it and run that wire to the Diagnosis box.

At the diagnosis box you will need to install a contact for the missing TE2 pin and solder that contact with the wire you just installed. this is exactly like on the ECU connector except the contact is different from the ECU connector

After this you will be able to trigger the OBD1 data output like any supported cars.
You can use this proccedure to test that your wire addition worked

Cars that are known to be missing the TE2 wire but having supported ECUs

-1994 Toyota Corona 4A-FE Euro and JDM

TOYOBD1 Android Datalogger :: Exporting data out of TOYOBD1

With TOYOBD1 it is possible to export data out of your Android phone.

Why for?

• to import in a spreadsheet program for custom calculations.
• to import back in another Android cell phone, say a friends phone for playback.
• to share TOYOBD1 data with a CarTester8000 users.
• to build an approximation of Ignition and Fuel maps from past recorded data.
• to have a backup files.

 First of all lets understand how the TOYOBD1 data is kept inside your Android phone.

TOYOBD1 uses an SQL database to store every log entry that was received from your OBD1READ device. It allows to record huge amount of data and makes it easy to precisely extract only what is meaningfull in specific conditions.

The design of the database makes it possible to keep log entries recorded with your phone and from someone else's phone without conflict and duplicate data. it also makes it possible to extract only specific data between a start date and end date.

Let's Export something  now!

Prior to exporting, a field need to be inputed in the Engine Configuration Dialog.
it is the 'Your car's description' field. You want this to be human readable for the people to whom you would send your log file for import.

for instance here are suggestions:
John Doe 4A-GE AE101
ZF 1UZ-FE SC400

when exporting data you will need to choose what kind of file you want to generate.

• CSV file for spreadsheet applications and TOYOBD1 import feature
• CTR file for use with CarTester8000 PC application
• CSV spreadsheet ignition map file 
• CSV spreadsheet fuel map file
• CSV spreadsheet both ignition and fuel map file

Next is the file name.By default a unique time based filename is suggested, change as needed.

The suggestd start date is by default a week ago, change as needed.
The suggested end date is by default today, change as needed.
The source, this is where you choose a car's description from the existing description
The ecu ID, you must remember what was your ecu ID number and choose it now.

when everything is choosen you simply press the 'Export Data' button.
processing time will vary depending on how much data is found for the search criterias you selected.
(this process can take minutes to complete if you export more than a month of data)

TOYOBD1 Android datalogger :: Connecting OBD1READ

First of all I suggest that you do the device recognition and pairing not in TOYOBD1 but in your phone`s Operating system BT configuration screen. 

As soon as this is solved, start TOYOBD1 and go in the 'configure Bluetooth com' dialog to choose a Bluetooth device that will be saved in the application preferences

 Select the device of your choice and go back to the main dialog, that device will be saved in the application preferences now.

After you have chosen your OBD1READ device you can now connect to it in the main menu using  'Start/Stop Logging' and enjoy your car's data stream!

TOYOBD1 Android Datalogger :: Correct speedometer error due to wheel size

Sometimes in life you get to wear shoes that are too big or too small, it happens to cars too,sometimes by choice, sometime out of necessity...

In TOYOBD1 you can configure the application to take into account an 'incorrect' wheel size.
doing so will make sure the MPG calculator and speedometer input is accurate.

the Speedometer correction factor can be adjusted in the 'Configure Displayed fields' dialog.
the value must be a positive value greater than 0.0
correct wheel size value for your ecu would be 1.0

 Here`s a good example, my own car! wheel size is way off from what the ecu is expecting.
AE102 corolla, 3VZ-FE V6 and MT Camry transaxle, ae102 wheels

this car needs a 0.85 wheel size ratio to get correct speed and MPG figures in TOYOBD1.
Fact is, the corolla wheel size is in the 185/65/14 range but the native CAMRY wheel size is in the 205/65/15 range.

To find out what is the correct wheel size ratio I use a GPS device to find out constant speed at around 100kmh / 60 mph and adjust the ratio as needed in TOYOBD1 to see the results. (Please don't endanger yourself doing everything alone, ask a friend) When you have found the correct ratio try it at various constant speeds to make sure it still fits with GPS readings.

TOYOBD1 Android Datalogger :: Custom Configuration of an engine

  ...Sometimes it may be necessary to make a custom engine configuration...

-You found a new supported engine!( contact me so the known list grows)
-You changed the injector size on your engine and want the MPG calculations to reflect those changes.

Heres the customizable fields and what they mean.

**********************************************************************************

'Engine preset configurations' 

this is a list of engines known to work and that have built-in  configurations, you choose one similar to yours and then modify other fields as needed.

**********************************************************************************

'metering system' 

this is what the ECU uses to measure the air flow in the engine. 

Here is how to know what to choose

VAF sensor ( V.ane A.ir F.low )

Not all VAF engines uses the same sensor curve AND housing size, but they all share the same layout and are easily recognized.

MAP sensor ( M.anifold A.ir P.ressure )

Working in pair with an I.ntake A.ir T.emperature Sensor this MAP sensor feeds the ecu with data on how to calculate engine flow at that particular moment. Not all toyota MAP sensors share the same voltage curve. there is two groups the Non turbo and turbo MAP sensors. even throughout the Turbo map sensor not all engines have the same exact voltage curve.

MAF sensor ( M.ass A.ir F.low )

This one is rare among OBD1 toyota but existant. The design is generally some sort of hot wire device that measure the speed of the air flowing through a conduit with a known area. this gives the ECU a cfm value to use for it's calculations...

All Other system 0-5V

This is all other measurement systems that have not yet been correctly quantified due to their rare usage on the OBD1 Toyotas .For instance here is picture the 1UZ-FE Kármán vortex air flow meter.
For those devices the [ 0.0 ,5.0 ]v raw signal is displayed.

**********************************************************************************

'Throttle position sensor' 

ANALOG

This sensor has got 4 pins going into it.
it tells the ECU how much the accelerator pedal is depressed with enough precision to make it worthwile.

 DIGITAL

This sensor has got only 3 pins going into it.
That sensor type is not frequently used, mainly on low complexity ECUs. For instance ( MT 4E-FE,5E-FE,4E-FTE, early MT 3S-FE and early MT 5S-FE). that sensor can only tell if the throttle is at rest, at W.ide O.pen T.hrottle or somewhere in between. those ECUS dont seems to implement any tps based accel enrichment logics and switching to a stand alone ECU necessitate installing an analog TPS in it's place.

**********************************************************************************

'Show Ox2 data'

Only V engines have a second oxygen sensor whose data is available. it does not apply to an inline engine.

***********************************************************************************

'Instantaneous MPG calculation'

'number of injectors' this is the number of cylinders your engine have unless this is some sort of Central injector system when you would only have one :S

'size of injectors in CC' this is the capacity of flow of your injectors in CC/minute 

'number of injection events per 2 engine revolutions' it should always be 1.

TOYOBD1 Android Datalogger :: How to install the OBD1READ

Today I will show you how to install your OBD1READ unit to a compatible car.

First lets take a look at your package content.

1 OBD1READ device ready for installation.

1  user manual that explains how to install the device. 

This user manual explains what kind of problems you may encounter while installing and how to overcome them or where to get support if you cant handle them alone.

Sorry, blue is the only color available to choose from!!

The pdf file for the user manual can be downloaded here!

Before doing anything you must know what must be connected for the system to work.

Quite easy! 4 wires need to be connected inside a diagnosis box in the engine bay.

1- B+ : this is the 12v power line. it will power OBD1READ when ignition key is on.

2- E1 : this is the power ground for OBD1READ, it is also the signal ground with the ecu. 

3- TE2 : this one activates the OBD1 data stream coming from the ecu.

4- VF1 : this is where the OBD1 data stream comes through.

Be aware that inverting B+ and VF1 can damage permanently the OBD1READ device. Dont invert them!

The safest way to hook them is to start with B+, then VF1, then TE2 ,then E1

*the green wires can be inverted together

Please take note that some luxury and sports car, LS400, mk4 supras, SC400 and Soarer will need a jumper to be placed in another diagnostic port under the dashboard. Details for those cars are available in the application glossary dialog.

Here are some of the diagnostic boxes shapes you may encounter in your engine bay.

The needed contacts should be already in the diagnostic box if your car is compatible.In the case of an engine swap with custom wiring, say Starlet 2E -> 4E-FTE you may need to add the missing wires and contacts in the diagnostic box to be compatible.

 Simply connect the 4 wires into the diagnostic boxes and make sure the OBD1READ device sits high in the engine bay (best for BT signal strength). Also take care to secure the device so that it does not fall off the car!!

At that point you are ready to power up the car and configure your cell phone and TOYOBD1.

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

TOYOBD1 Android datalogger :: Engines supported

 Here is a compatibility list of engines using TOYOBD1 with OBD1READ.

Petrol Engines that were test proven

• USDM 3VZ-FE 
• JDM 1992+ 4E-FTE EP82
• JDM 4A-GE AE111(blacktop)
• JDM 2JZ-GTE JZA80
• USDM 1994 2JZ-GE JZA80
• USDM 2JZ-GTE JZA80
• JDM 1JZ-GTE JZZ30,JZX90,JZA70,JZX81
• JDM 1JZ-GTE VVT-i JX100 1998 and earlier ONLY
• JDM 1992-1993 3S-GTE
• USDM 1992-1993 celica 5S-FE 
• 1994-1995 CELICA 5S-FE 
• USDM 1UZ-FE SC400 and LS400
• JDM 3S-GTE ST205 WRC
• USDM 4A-FE 1993
• 1991+ 3VZ-E Pickup and 4Runner
• USDM 22R-E 94-95 
• JDM 4A-GE AE101(silvertop)
• 1992-1993 REV2 3S-GE (SW20) 89661-17370
• ST202 3S-GE
• SW20 1992+ 3S-GTE
• EE101 4E-FE
• EP91 4E-FE
• EP91 4E-FTE
• USDM 7A-FE 1993 
• JDM 2TZ-FE 1994 and above
• JDM 5E-FHE EL54 (2nd generation) 
• Land Cruiser 1FZ-FE(more details to come about supported years)
• 88-92 Cressida A/T 7M-GE
• 88-91 2VZ-FE 89661-32590 ES250 and 2.5 V6 camry
• late 2TZ-FE (map sensor system)  
• 5E-FE GEN2 PASEO UK 89661-16490 

Diesel engines that were proven to work

•  european diesel 2C-E corolla 
• 1995 1KZ-TE Diesel Land Cruiser (Africa)   
• Toyota Estima 3C-TE ( toyota estima )

Engines that are believe to work but not yet tested

• All JDM engines past 1992 with a TE2 ,E1,B+ and some sort of VF(1) pin in their diagnosis box should work.
• Some non JDM engines between 1992 and prior OBD2
• AE101 4A-GZE
• 2RZ-FE depending on maket
• Avenis turbo diesel 2C-TE 
• early VVti 2JZ-GE JZX100
• Crown 2L-TE and 2L-THE 
• late Crown GS13X 1G-GE 
• 1G-GZE
• late 1G-GTE (mark 2, cresta, chaser)

Engines that are clearly known to not be working

• Anything under 1988
• Most simple Toyota engines before 1992 (3E-E,2E-E,3S-FE,3S-GE,4A-FE,4A-GE)
• All OBDII engines (PLEASE LOOK AT THE JDM OBD2 ENGINES LIST BELOW)
• 1MZ-FE
• 5VZ-FE
• All 16V 4A-GE  
• 3E-E and 2E-E all years 
• full mechanical Diesels
• first generation 5E-FE 
• first generation 5E-FHE
• 90-91 4E-FTE 
• 90-91 3S-FE 
• 90-91 3S-GE
• 90-91 5S-FE
• 90-91 3S-GTE
• AW11 4A-GZE
• Supra 7M-GE
• LN130 2L-TE
• early 1G-GTE (GA70,GZ20)
• 7M-GTE (http://i88.photobucket.com/albums/k162/crzywhtrican576/supradiag89.jpg) 
• 1990-1993 2TZ-FE
• 2TZ-FZE(OBDII)
• 1UZ-FE VVTI

Here is a list of JDM OBDII engines  that can't work with TOYOBD1.

To know if your engine is OBDII ,easy way is to find the SIL pin on the pin out.
no OBDI Toyota will have that pin.

*for those desperately seeking to datalog on those OBDII engines it is said that with a recent ELM327 scanner it can be done. But the elm327 must be configured by the application accordingly prior to this. As I have no recent ELM327 scanner my quest ended there. maybe another time...

• late years 1JZ-GTE VVTI http://i50.photobucket.com/albums/f302/ace1312/jzx110-3-1-1.jpg
• 2JZ-GTE VVTI http://wilbo666.pbworks.com/w/page/42173082/2JZ-GTE%20VVTi%20JZS161%20Aristo%20Engine%20Wiring
• ST215 3S-GTE http://i10.photobucket.com/albums/a105/azian_advanced/Celica%20Parts%20Diagrams/ST2153SGTEECUPinoutDiagram.png
• ST202 BEAMS 3S-GE http://www.6gc.net/forums/index.php?showtopic=91467