Better datalogging using the stock ECU

[prj]

Well, if you have a car pc, and you can hookup a vag-com interface to it, you'll be able to use all this stuff.

Winlog already provides a real time dash in any configuration you can imagine, so it's only a question of writing the driver that interfaces with the ECU.

I wouldn't do this unless there is a group buy for a such kind of thing though, and you'd still need a custom ecu remap.
That's why it'll be a tuning tool only for now.

[prj]

I love all the useless information, must be the Engineer in me

For things like track days etc, it would be really useful to be able to have various things displayed that aren't. I should really get an integrated WB02 and EGT probe for that sort of thing, would help with testing of chips / cams also.

Once it's done, you can probably buy it for some sort of fee if you want it.
But it'll also need custom ECU chips.

That's why I said - tuning only

[prj]

It is said that a picture is worth more than a thousand words:


Full datalogging nirvana is within reach.

[A80Avant]

what would be most interesting for me who i dont use the motronic anymore is to try and analyse what the LOAD value means on the VAGCOM reading. Because i think it is not the LOAD value found on the motronic tables when you look at a motronic map.Also, how is that compared to the kpa reading that you see on the gauge when the car is on the road.

is that something that you can derive amongst the rest of the work you are doing?

[prj]

I already know...
That value is useless either way. I am only going to use group 0 with custom stuff in it.

[A80Avant]

how is the load then compared to the kpa reading when you are driving around?

i see on the graph you have posted that load reaches its highest in mid rev range and then drops. Now that to me looks to have a similar pattern to boost(map) reading. so? any more info on that please?

[prj]

how is the load then compared to the kpa reading when you are driving around?

i see on the graph you have posted that load reaches its highest in mid rev range and then drops. Now that to me looks to have a similar pattern to boost(map) reading. so? any more info on that please?

You can't compare load and kpa reading, because load is the amount of air in the cylinder, kpa isn't.

[prj]

Who needs VAG-COM anyway?

C:\Users\GM\Documents\Visual Studio 2008\Projects\KWP1281Console\Debug>KWP1281Console.exe COM2
READ: 0
READ: 0
READ: 55
READ: 1
READ: 8A
READ: 55
READ: 1
READ: 8A

[prj]

C:\Users\GM\Documents\Visual Studio 2008\Projects\KWP1281Console\Debug>KWP1281Console.exe COM2
Received text: 4A0907551AA
Received text: 2,2l R5 MOTR
Received text: .RHV HS D02
Received text: PMC 1

[prj]

C:\Users\GM\Documents\Visual Studio 2008\Projects\KWP1281Console\Release>KWP1281Console.exe COM2 0
Starting on COM2...
Block read!
Received text: 4A0907551AA
ACK sent!
Block read!
Received text: 2,2l R5 MOTR
ACK sent!
Block read!
Received text: .RHV HS D02
ACK sent!
Block read!
Received text: PMC 1
ACK sent!
Block read!
Got ACK!
Block read!
00 00 00 00 00 00 FF 00 00 00
Time elapsed: 219
Block read!
00 00 00 00 00 00 FF 00 00 00
Time elapsed: 203

Some notes:
1) Group 0 has 10 values, not 10 values of 3 blocks, like I thought.
So, that means it's 10 customizable channels.
Alternatively it would be possible (and perhaps easier) to hijack a different group, to get 12 values.
I will see what is more viable.
2) The fastest I can read is on average one sample every 210 milliseconds on Group 0. So that's 4.76 samples per second.
A bit faster than VAG-COM. It gave me 4.3-4.4 samples per second.
On group 1+, it is about 228ms, so about 4.39 times per second.

To do:
1) Convert the console application into a winlog driver.
2) Handle error conditions and timeouts properly and automatically reconnect all the time.
3) Modify ECU code to serve the values I need.

Entire program takes 14kb in compiled form.

[UrS4boy]

Good stuff, Dmitri. Keep it up.

[prj]

I have completed this project.
The only thing I would like is find the knock sensor inputs and display them as well.

Attached is a program, which I used for testing and snooping group data.
Here is an example of the output on a non-running engine:

C:\Users\GM\Documents\Visual Studio 2008\Projects\KWP1281Console\Release>KWP1281Console.exe COM2 3
Starting on COM2...
01 C8 00 02 FE 00 03 D0 FF 05 07 1E
01 C8 00 02 FE 00 03 D0 FF 05 07 1E
01 C8 00 02 FE 00 03 D0 FF 05 07 1E
01 C8 00 02 FE 00 03 D0 FF 05 07 1E
01 C8 00 02 FE 00 03 D0 FF 05 07 1E
01 C8 00 02 FE 00 03 D0 FF 05 07 1E
01 C8 00 02 FE 00 03 D0 FF 05 07 1E
01 C8 00 02 FE 00 03 D0 FF 05 07 1E
01 C8 00 02 FE 00 03 D0 FF 05 07 1E
01 C8 00 02 FE 00 03 D0 FF 05 07 1E
01 C8 00 02 FE 00 03 D0 FF 05 07 1E
01 C8 00 02 FE 00 03 D0 FF 05 07 1E
01 C8 00 02 FE 00 03 D0 FF 05 07 1E

You can translate the values using this table:
http://audicom.pagesperso-orange.fr/...0groupe_uk.htm

For all groups except group 0 it contains 3 values per block in the group, for a total of 4 blocks.
The first value tells you which formula to use for translation, the second value is a and the third value is b.

Works with any USB->Serial pass-through cable that works with the older vag-com versions or VCDS-Lite.

This program I wrote for testing. I then proceeded to write a Winlog driver using the class in this program and modified Group 8 in the ECU to have my own 12 values, not following the protocol. That way I can have all the data I need in 1 group.

Here is a sample winlog dash that shows all the data from the ECU (ecu is on bench, so just like ignition ON in the car):

It is of course possible to log everything at the same time as well and review it later using winlogview.

This datalogging functionality can be added to any M2.3.2 ECU, be it ADU/AAN/ABY.
But it requires modifying the software inside the fuel chip. If anyone wants this, I am sure we can come to some sort of agreement.

In combination with the SLC DIY, which also has data logging via winlog, I can now see everything I need to tune the car on one graph!

P.S.
Attached program has almost no error detection, so if you use a bad cable, it can exit by itself etc...
The winlog driver is fully stable and allows to unplug the cable, then plug it back in etc... without any crashes and automatically reconnecting once connectivity is restored.

[prj]

Oh and... pic of the final bench arrangement (spaghetti):

[rj scotty]

[Nuvo]

Very impressive, can you tell me what the little black box on top of the ECU is please? I'm guessing it must be the emulator you use for tuning.