surfer

Just wondering why there isnt a ghetto data logger for wideband?

If people are interested i was thinking of perhaps devising a logger that will interpret the map and rpm signal kinda like the TE2 logger and put the AF in the relative box

is it worth it anyone and if so whos got good ideas for it?

88b16civic

I was thinking of that too as you can tell from my recent posts. I was thinking if run in lets say excel. You can have it generate a smart retune based on the AF it logged for cells and a target AF. This could be a simple algrythem (sp?) based on the differemce in target vs. the average recorded for that cell and the current pulse durration. When I order a wideband, I think im gonna play around setting up an excel worksheet and an embedded macro that will do this.

TurboEF9

The reasoning behing not having A/F was simple.. external memory address for the analog to digital converted value of the O2 sensor in the PM6 (main base code of TE) was in external RAM on the microcontroller. A new serial interrupt handler had to be written that could poll external memory. That has been done. Now, old datalogging code both from ECUControl and TurboEDIT has to be completely rewritten to speak with this handler, and a conversion formula created to calculate A/F ratio from the ADC converted values. Not to mention that the O2 voltage check of the OBD0 has to still be eliminated. Wideband read 0-5, narrowband 0-1, anything over 1v throws a code.

..the long and short of it is, _a lot_ of work hasbeen done to get us this far. It's not an easy task. One doesn't just "start" adapting things that were never meant to be done to an ECU to it and they work.

..feel free to write your own datalogger, I would be interested in seeing your method.

surfer

i wasnt thinking of anything quite so complex as to alter or work with the contents of the rom other than to intercept the raw map and rpm value at the ECU and also a wideband output to a live ------sheet display on the computer so it will display an AF/Lambda in the cell associated with the injector pulse durations. So in theory you can have a quick drive about and log the O2 and then adjust the old fashioned way and test

TurboEF9

That's just it.. if you're gathering information from three different outside sources, the readings you get may be "off" from what the ECU thinks it sees. Even if this is more accurate (to gather from the sensors) it doesn't matter because the ECU is the all end all. What it thinks it sees, is what matters.

surfer

I'm going to address this over on PGMFI to get a bit more info because there has to be a way to do this, the more input the better

quadnie

You can cheaply log the voltage outputs from the (standalone) wideband into a device attached to the rs232 port of your laptop.. that's about all you're going to log, limited voltage outputs, problem of course is the syncing it to everything else on the car, I haven't even seen anything that is capable of connecting that voltage in series to the rpm.

Doofnoil

but wouldn't those three outside sources, in fact, be directly attributed to what's going on inside the ecu?

like say logging the tach from the ecu, then logging the map voltage at the corresponding rpm value, and since the wideband isn't directly unput to the ecu 9i thought just narowband went to ecu?) then the wideband to aslo be independantly recorded on a timed basis. If all of these things are recorded in the same time frame like ten times a second and the data imposed on a graph, it should give a reading of afr vs. boost pressure vs. rpm...

as you can see, I have know idea what I'm talking about so please feel free to enlighten me.

TurboEF9

It's basically, the fundemental difference in how external things read interpret the data.

Like my stock tach vs my an Autometer monster.

..my stock tach could read 7400rpms, while my autometer, being built better, reads 7650.

It's basic interpretation. Datalogging "from" the ECU implies gather data _after_ the ECU has processed it throught he analog to digital converter.

External dataloggers gather information _before_ it hits the ECU.

Sinner

is this the post about why external dataloggers are horrible?

If not, please post the link. This is about the only good think that come from a search.

Nick