The car isn't knocking or pulling timing, he's logging too many parameters and the sample rate sucks (mentioned above). I usually only log timing and rpm's on my pocketlogger and the curves look much better. I see 18-21 degrees of timing at WOT on pump gas and 20-23 degrees on race gas. The very instant you begin to let off the throttle, timing soars to 35+ degrees. That's why you see ~7000 rpms and 38 degrees of timing - they aren't being logged at the same time, so to speak.

 

Exactly, thats what I was trying to say. My car does the same thing when I start to back off. The ECU sees that the THR application is backing off and begins to make timing and all sorts of other adjustments right away. In regards to the stock O2 sensor. Yeah a wideband is much better, but they arent terribly innaccurate stock (unless they use a totally different one than on DSM's)

Brian

 

All those timing numbers look normal.

In a car running this much boost timing is going to drop way off when you are at peak boost. This is why you are seeing such low numbers from 4-5k. As rpms rise, more timing is needed in order to get the ignition to be complete at the right point in the stroke of the piston (TDC). Also, assumuing the car is tapering boost like stock, then less boost means more timing is available. 91 octane will SEVERELY hamper your timing numbers.

The reason that timing is so low from 4-5k is for safety's sake. Mitsu is running tons of fuel and low timing in these high boost situations to prevent detonation.

 

Not to be a PIA, but I think it is important that you guy's understand this. Here is the range of a typical narrow band O2 sensor like the one in the EVO, and why you see 1.0V at WOT on the EVO.

Volts A/F ratio

.1 17:1
.2 16.5
.3 16:1
.4 15.4
.5 14.9
.6 14.4
.7 13.8
.8 13.2
.9 12.7
.985 12.1

For safety reasons you do not want to be any where near the range of the stock O2 sensor at WOT, especially if your running higher boost. Trust me when I tell you the stock O2 is worthless at WOT, for test and tune a wide band is the only way to monitor A/F ratios.

 

Is this what I need to get a "pocket logger"?

1. Palm Pilot or Laptop
2. OBDII Software
3. cable?

I wanna get my own pocket logger, any good sites for more info?

 

Jimmy,

I'm doing a lot of research on getting a cheaper Pocket/Laptop logging solution. www.pocketlogger.com is the logger that my friend Brian (SoCaliEclipse) used on my car. www.injectoclean.com and www.scantool.net are some other avenues I'm checking out. The only thing that's really unclear is the actual cable itself. It depends on what software you use. Some of the pinouts are different for the same cable. I'll keep everyone in here posted.

Rob

 

rob i have been researching the same thing over the last week as I am looking to get an obd-II setup running with my laptop or pocketpc.

lets talk about this and see if we cant get something ironed out.

I am sure between the two of use we can figure this all out

 

Anybody find more info on this? Here's what I found out so far (it gets somewhat technical). I'm planning to write my own software, but I'm looking for the cheapest interface with the highest data rate. Besides scantool.net that Coolguy949 mentioned, one that I'm considering is at http://www.obddiagnostics.com.

Can anyone confirm that the Evo uses the ISO9141 protocol?

My understanding is that the cables must be compatible with the interface, not the software. The software must be compatible with the interface. At first I assumed that you could get an OBDII to serial cable, and have software that could understand the signals. But as it turns out, you need an interface box to translate the signals from ODBII to serial. You have a cable going from the OBDII port in your car to the interface box, then you have a serial cable from the interface to your laptop/pda. Then software on your laptop/pda talks to the interface, which in turn talks to your ECU via the OBDII port. The signals at the OBDII connector aren't compatible with the PC's serial port, so they need an interface box in between to translate.

OBDII has specific commands, but the interfaces themselves add to these. The software you use must understand the specific protocol that the interface requires, because it must send interface-specific commands along with the standard OBDII requests. For example, there's an OBDII command you can send to the ECU that says "Give me the current engine RPM." The software must understand how to communicate with the interface to send this command to it, and to understand it's response. Both the command and the response contain the actual OBDII data, but have some additional interface-specific crap added to it.

In summary, what you need to get data logging is:

1. An interface box.
2. A cable from the OBDII connector in your car to the box.
3. A cable from the box to your laptop/pda.
4. Software for your laptop/pda that works with your interface box.

The interfaces generally come with the cables, and some software that can at least display live data. Some have software that can log the data. Some can also check and clear CEL codes (this is part of the OBDII standard). There doesn't seem to be too much software out there that works with multiple interfaces, so you'll generally have to go with whatever software the interface manufacturer provides.

Now when I talk about an "interface", I'm referring to the box that sits between your OBDII connector in your car and your laptop. There's an additional thing to consider, which is the OBDII protocol. This depends on your specific make & model of car. AFAIK, the Lancer and Evo both use the ISO9141 protocol. The interface determines which protocols are supported, not the software. Some interfaces support multiple protocols, so they could work not only in your Evo, but also your Mom's Cavalier. Also, if your car speaks ISO9141, and your interface box supports ISO9141, then any software that works with your interface box will be able to talk to your car.

Any corrections, clarifications, additional info would be greatly appreciated.

 

So what, or where is the best place to get the software/box? I'm running laptop. I'm looking at http://www.obddiagnostics.com but one that will also read OBD I would be nice also.