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)

Dirt cheap portable MAF sensing

A while ago I realized that a portable MAF sensor would be nice to have. That sensor can be useful to sense engine health or how well it can perform. The idea came to use a junkyard OBDII ECU who came equipped with a MAF sensor.

 An OBDII ECU?

Here are some advantages to go down this route

• to get quantified readings from the sensors,no need to discover the OBDII sensors curves. You simply request a particular sensor reading. for instance what interest us today is the MAF sensor reading which returns a g/s flow rate.
• It is easy to interface an OBDII ECU to a PC or cellphone.
• It is easy to find a suitable ECU + matching MAF sensor in a junkyard for cheap
• There is many software options to interface to OBDII ECUs.

As I am a Toyota fan I looked toward the Toyota 3.0L V6 ECU using MAF sensors, what was available in junkyards at that time was the 1995 Camry 1MZ-FE ecu, that MAF sensor can be installed inline which helps when installing, that particular MAF sensor should be able to read engine air flow from comparable power levels engine which is sufficient this time.

How do we get this brillant concept to life now?

I choose to use the OBDII ECU as a portable unit, lying on the car floor, running a long cable to the MAF on the engine, getting power through the cigarette lighter port.

You need to build a minimalist wiring harness for this ECU to work on your car. Remember that you want just 3 things, the OBDII ECU, it`s MAF, and an OBDII connector, it really is not that hard to do, something like 10 wires.

After you made sure your ECU is powered correctly and all needed wires are going to their rightful places it is time to get some data out of that setup. The good old ELM327 comes handy for this, you can buy BT OBD2 adapters, USB obd2 adapters, probably even RS232 obd2 adapters, there is also many software out there to read data from an OBD2 ECU that can be used to glance at the data.

What to do with it then?

What I want to do with my MAF sensor is to plot unknown flow curve of various VAF sensor from non OBDII engine, comparing readings from the OBD2 ECU through time vs those of the unit tested.

(Take note to never install a MAF behind something that could make turbulence such as a VAF, you will get erratic readings... MAF in front of VAF gives good results!, take also note that this is a temporary test setup  )

And now the resulting flow curve for the VAF sensor