VT V6 N/A XDF DTC's

[Rhysk94]

Hey Guys,

Does anyone have a modified xdf based off THE1's enhanced VT NA V6 file.

Have a customer car in for a manual conversion. After selecting the manual check boxes it is still throwing DTC's and a check engine light.
The DTC's haven't been defined and I am not smart enough to figure that out.
Have included a picture showing the DTC's and the boxes checked.

Any help would be much appreciated!

[antus]

Do you have access to kalmaker or know anyone who does? You'd want the W50 or W5x style. You probably need to get the factory calibration W50 bin, set all (or some) of the DTCs on, then off, save each time and compare. to figure out what bytes have the DTCs. Then search the stock byte pattern in the factory OS to find out which bytes they are. Then start setting the ones you need one at a time and saving to observe the changes. Then you can define them in the factory XDF and share it back to help others. If you don't have that one then you'll need to find the closest one you do know and do something similar to try and find the addresses in the A5G bin by pattern. The whole lot of them are an evolution so things change a bit between versions but not completely.

[antus]

I decided to spend some time on this and help you out. I did the digging and got something you can work with. On the left we have W50. I've changed 2 flags. Manual and VSS. I think that's the two you know. Things are named a bit differently so I am not certain. Then I toggled those DTCs by number.

First changes I didnt screen shot, but in W50 address 2010 D4->D5 is the manual flag. 2011 13->93 is the VSS Flag. So together thats D413 -> D593. This was a bit hard to relate back to A5F but I did find D413 at 37BD. I think this is it, and those option flags moved. There are other flags around that area in the factory code. VT V6 v1.91 $A5F has these flags and the line up. So this is not new info, but proves this method of searching is working.

Next we have the image which is the DTCS you need. Kalmaker has EOPT and LOPT. I don't know which is which. One is going to be process error code and one will be mask error code CEL. For your use case it doesn't matter as the auto trans isn't run by the PCM since its gone. I used EOPT, if you need to test which is which then its a little more work.

I masked DTCs 59 67 73 82 97. If you look at the changed values in binary, the flipped bits will align to those flags. I'm not sure if we're talking LSB or MSB and which order in the bin. Maybe later I can spend some more time or someone else can to get a bit more information to help improve the XDF.

You can see that pattern of bytes in the CXWL.A5F in HxD which I think is likely the factory variation you are working with. If you are on a different variant you should be able to pattern match by a few bytes and find that sequence to apply the same change. Note you'll need tunerpro to correct the checksums as well.

I've got each bit change saved out 1 by 1 for more analysis, but I just took too the macro view with all changes as I don't have the time right now to do that.

[Rhysk94]

Cheers Antus, that helps a tonne!
I don't have access to Kalmaker, Still can't buy it unfortunately.
I'll see if I can get those defined into the xdf from that info!
Thats still all half gibberish to me but the more I re read it the more I can follow it an it make sense haha

[antus]

I spent a few mins loading the files I created last night and plotting each bit change. These addresses are for the W50 screen shot, but you can see which bit flipped for each flag. That maps the changes, and you can apply them at the A5G address instead to update the stock XDF.

Code: Select all

DTC 59: (EOPT6)
5929 E7 1110 0111
     C7 1100 0111

DTC 67: (EOPT8)
592A F2 1111 0010
     B2 1011 0010

DTC 73: (EOPT7)
592B F2 1111 0010
     B0 1011 0000

DTC 82: (EOPT8)
592B DF 1101 1111
     DD 1101 1101

DTC 97: (EOPTA)
592D 98 1001 1000
     90 1001 0000

Then I went a step further. I toggled through the STOCK EOPT and LOPT settings and took screen shots. If you look at these one by one and start with one of the stock DTCs above that we know where it is, eg DTC 59 in EOPT 6 you can see which which bit it is in the byte E7/C7 above (3rd from the left), and that its the 3rd flag from the bottom in the EOPT6 screen shot. Now you test in tunerpro to see what it calls that bit number (probably 2 or 4 if its counting from 0, and depending on counting from the left or right).

Now you can map the DTCs from the screen shots to those bytes above, and if you write down any of the others in bits from the other screenshots you can first get a value, and then I expect they'd all be in a row right next to each other in the bin. So you can map them all out for the XDF.

EG EOPT9 has 92 lo fan set (see EOPT9.png), and other flags clear. So that's 1000 0000 or 0000 0001 depending on 'endianness'. We expect EOPT9 to be between EOPT8 and EOPTA and in the screen shot above we can see a value that didn't change, and with a value of 1. So 0000 0001 is a value of 1. There it is. Wash rinse and repeat for the other EOPT and LOPT values, and the descriptions in the screenshots.

Lets do another example. LOPT1.png shows the pattern 1100 0111 from top to bottom. We know from the one above that the bottom of the image is the low byte. So lets record it the other way instead, 11100011. That value is E3 (using programmer mode of windows calc).

LOPT1.png

So we know we found the EOPTs around 36E0 with that address being EOPT6 in the factory bin and through to EOPTA (the last one) at 36E4. So now we look nearby for E3, and it is immedately after EOPTA, so LOPT1 is at 3605. You can check some more (I bet LOPT2 adds up to A2, LOPT3 adds up to C0, EOPT5 will be FE...) as it's very likely EOPT1 to EOPTA and LOPT1 to LOPTA are right next to each other, in that order. You can check more and go forward and backward from where I started. You can get the DTC names from the screenshots. That's enough to make the XDF. Instead of using EOPT and LOPT I'd suggest calling them Process DTC and CEL DTC or something similar to what's in other XDFs.

LOPT1 after EOPTA.jpg

The last piece is does the EOPT mean Process or CEL? And the other for LOPT. Looking at the manual EOPT seems to be Process DTC, LOPT seems to be 'Light' eg Disable DTC CEL.
So, now i've gone through all that, you probably would be better to mask the CEL flags not the process flags in your application.

If you put any or all of them in an XDF please share.

[antus]

And to wrap it up, this will be all the Process DTC bytes (10 bytes, 8 flags in each byte) followed by all the CEL Enable DTCs. So now you just need to build the XDF and name them from screen shots.

[Rhysk94]

I appreciate all your work here!

I won't lie, that is all above my paygrade. Slowly learning and making sense of the process tho!

Cheers!

[antus]

I decided to try and use AI to process this data in to something easier to use. I found a tool that can 'read' images and described how to read these images and what they meant. It was a trial so I had to do 3 at a time. Other similar, better tools probably exist. Once I had gathered them (and added EOPT6 because I noticed it was missing) I asked to make one formatting change at a time, changing wording, and then described the pattern of addresses. I think this all right and probably easier to work from. Next step would be to take this and an example of a flag section in an XDF and tell the AI how to map these values in to the XDF. See if it can output a block of XML that can be pasted in to an XDF. The XDF header says 'dont hand edit, trust me' and I have noticed that its easy to break tunerpros memory management. So if doing this way you need to load the XDF and save it again before doing anything else. Then quit tunerpro to refresh it and load the XDF again, by the second load any memory issues should be solved. Then do some testing and keep an eye out for weirdness. I think it would be good, but there is a risk with that method. Also now there is a method we could start looking at other MAF model XDFs, perhaps with a goal of getting DTCs in to all of the enhanced bins.

I've also noticed there is a set of POPT (Powertrain DTCs) and QOPT flags for 'volatile codes' related to POPT. I don't think QOPT is needed, but we might need POPT DTC flags. However they only seem to be the same DTCs again. I don't know, for example, what a powertrain DTC 47 18x crank would be when we have DTC 47 18x crank already. So maybe I'll forget those unless there are reports that the ones we have are not working, or if anyone has anything to add about powertrain DTCs. Actually, is there a transmission DTC light? Maybe LOPT controls which DTCs light the CEL, and POPT controls which light the CTL (Check Transmission Light?) Is this a thing on a VT? POPT Values in order from 1 to 9 are 63 A2 00 00 18 60 F2 8F 00.

After talking to chatgpt a bit and verifying a few things, I've reworded this to use industry term MIL and described powertrain or engine flags to set MIL. It's the same light, but different places to mask it for engine and transmission/powertrain code banks to set it. So to stop MIL lighting up you'd want to make sure Engine Enable MIL DTC xx and Powertrain Enable MIL DTC xx are both clear.

Anyhow, the data is now in text format here:

Process DTCs 1 (0x36DB):

Bit 7 = DTC 13 ro2 slo
Bit 6 = DTC 14 clt hi
Bit 5 = DTC 15 clt lo
Bit 4 = DTC 16 clt unstable
Bit 3 = DTC 17 clt pullup
Bit 2 = DTC 18 egr flow
Bit 1 = DTC 19 tps stuck
Bit 0 = DTC 21 tps hi

Process DTCs 2 (0x36DC):

Bit 7 = DTC 22 tps lo
Bit 6 = DTC 23 iat lo
Bit 5 = DTC 24 vss loss aut
Bit 4 = DTC 25 iat hi
Bit 3 = DTC 26 iat unstable
Bit 2 = DTC 27 psa open
Bit 1 = DTC 28 psa short
Bit 0 = DTC 29 egr posn

Process DTCs 3 (0x36DD):

Bit 7 = DTC 31 tdm signal
Bit 6 = DTC 32 maf signal
Bit 5 = DTC 33 bap hi
Bit 4 = DTC 34 bap lo
Bit 3 = DTC 35 idle speed
Bit 2 = DTC 36 vacuum leak
Bit 1 = DTC 37 unused
Bit 0 = DTC 38 unused

Process DTCs 4 (0x36DE):

Bit 7 = DTC 39 unused
Bit 6 = DTC 41 est
Bit 5 = DTC 42 bypass
Bit 4 = DTC 43 esc
Bit 3 = DTC 44 ro2 lean
Bit 2 = DTC 45 ro2 rich
Bit 1 = DTC 46 crank
Bit 0 = DTC 47 18x signal

Process DTCs 5 (0x36DF):

Bit 7 = DTC 48 cam signal
Bit 6 = DTC 49 cam-18x sync
Bit 5 = DTC 51 nrom
Bit 4 = DTC 52 bat high lt
Bit 3 = DTC 53 bat high st
Bit 2 = DTC 54 bat unstable
Bit 1 = DTC 55 ad err
Bit 0 = DTC 56 loaded lean

Process DTCs 6 (0x36E0):

Bit 7 = DTC 57 inj monitor
Bit 6 = DTC 58 tft hi
Bit 5 = DTC 59 tft lo
Bit 4 = DTC 61 unused
Bit 3 = DTC 62 unused
Bit 2 = DTC 63 lo2 slo
Bit 1 = DTC 64 lo2 lean
Bit 0 = DTC 65 lo2 rich

Process DTCs 7 (0x36E1):

Bit 7 = DTC 66 32 sol cct
Bit 6 = DTC 67 tcc ctsol
Bit 5 = DTC 68 slip
Bit 4 = DTC 69 tcc stuck on
Bit 3 = DTC 71 unused
Bit 2 = DTC 72 vss int aut
Bit 1 = DTC 73 pcs
Bit 0 = DTC 74 unused

Process DTCs 8 (0x36E2):

Bit 7 = DTC 75 bat lo st
Bit 6 = DTC 76 stft delta
Bit 5 = DTC 77 unused
Bit 4 = DTC 78 ltft delta
Bit 3 = DTC 79 trans fluid temp high
Bit 2 = DTC 81 23 sol cct
Bit 1 = DTC 82 12 sol cct
Bit 0 = DTC 83 tcc pwmsol

Process DTCs 9 (0x36E3):

Bit 7 = DTC 84 unused
Bit 6 = DTC 85 unused
Bit 5 = DTC 86 unused
Bit 4 = DTC 87 unused
Bit 3 = DTC 88 unused
Bit 2 = DTC 89 unused
Bit 1 = DTC 91 qdm fault
Bit 0 = DTC 92 lo fan

Process DTCs A (0x36E4):

Bit 7 = DTC 93 snef (knock circuit)
Bit 6 = DTC 94 vss loss man
Bit 5 = DTC 95 torque error
Bit 4 = DTC 96 freon sensor
Bit 3 = DTC 97 purge
Bit 2 = DTC 98 unused
Bit 1 = DTC 99 unused
Bit 0 = DTC 00 unused

Engine Enable MIL DTCs 1 (0x36E5):

Bit 7 = DTC 13 ro2 slo
Bit 6 = DTC 14 clt hi
Bit 5 = DTC 15 clt lo
Bit 4 = DTC 16 clt unstable
Bit 3 = DTC 17 clt pullup
Bit 2 = DTC 18 egr flow
Bit 1 = DTC 19 tps stuck
Bit 0 = DTC 21 tps hi

Engine Enable MIL DTCs 2 (0x36E6):

Bit 7 = DTC 22 tps lo
Bit 6 = DTC 23 iat lo
Bit 5 = DTC 24 vss loss aut
Bit 4 = DTC 25 iat hi
Bit 3 = DTC 26 iat unstable
Bit 2 = DTC 27 psa open
Bit 1 = DTC 28 psa short
Bit 0 = DTC 29 egr position

Engine Enable MIL DTCs 3 (0x36E7):

Bit 7 = DTC 31 tdm signal
Bit 6 = DTC 32 maf signal
Bit 5 = DTC 33 bap hi
Bit 4 = DTC 34 bap lo
Bit 3 = DTC 35 idle speed
Bit 2 = DTC 36 vacuum leak
Bit 1 = DTC 37 unused
Bit 0 = DTC 38 unused

Engine Enable MIL DTCs 4 (0x36E8):

Bit 7 = DTC 39 unused
Bit 6 = DTC 41 est
Bit 5 = DTC 42 bypass
Bit 4 = DTC 43 esc
Bit 3 = DTC 44 ro2 lean
Bit 2 = DTC 45 ro2 rich
Bit 1 = DTC 46 crank
Bit 0 = DTC 47 18x signal

Engine Enable MIL DTCs 5 (0x36E9):

Bit 7 = DTC 48 cam signal
Bit 6 = DTC 49 cam 18x sync
Bit 5 = DTC 51 prom
Bit 4 = DTC 52 bat high lt
Bit 3 = DTC 53 bat high st
Bit 2 = DTC 54 bat unstable
Bit 1 = DTC 55 ad err

Engine Enable MIL DTCs 6 (0x36EA):

Bit 7 = DTC 57 inj monitor
Bit 6 = DTC 58 tft hi
Bit 5 = DTC 59 tft lo
Bit 4 = DTC 61 unused
Bit 3 = DTC 62 unused
Bit 2 = DTC 63 lo2 slo
Bit 1 = DTC 64 lo2 lean
Bit 0 = DTC 65 lo2 rich

Engine Enable MIL DTCs 7 (0x36EB):

Bit 7 = DTC 66 32 sol cct
Bit 6 = DTC 67 tcc tcl sol
Bit 5 = DTC 68 slip
Bit 4 = DTC 69 tcc stuck on
Bit 3 = DTC 71 unused
Bit 2 = DTC 72 vss int aut
Bit 1 = DTC 73 pcs
Bit 0 = DTC 74 unused

Engine Enable MIL DTCs 8 (0x36EC):

Bit 7 = DTC 75 bat lo st
Bit 6 = DTC 76 stft delta
Bit 5 = DTC 77 unused
Bit 4 = DTC 78 tft delta
Bit 3 = DTC 79 trans fluid temp high
Bit 2 = DTC 81 23 sol cct
Bit 1 = DTC 82 12 sol cct
Bit 0 = DTC 83 tcc pwm sol

Engine Enable MIL DTCs 9 (0x36ED):

Bit 7 = DTC 84 unused
Bit 6 = DTC 85 unused
Bit 5 = DTC 86 unused
Bit 4 = DTC 87 unused
Bit 3 = DTC 88 unused
Bit 2 = DTC 89 unused
Bit 1 = DTC 91 qdm fault
Bit 0 = DTC 92 lo fan

Engine Enable MIL DTCs A (0x36EE):

Bit 7 = DTC 93 snef (knock circuit)
Bit 6 = DTC 94 vss loss man
Bit 5 = DTC 95 torque error
Bit 4 = DTC 96 freon sensor
Bit 3 = DTC 97 purge
Bit 2 = DTC 98 unused
Bit 1 = DTC 99 unused
Bit 0 = DTC 00 unused

Powertrain Enable MIL DTCs 1 (0x36FA):

Bit 7 = DTC 13 ro2 slo
Bit 6 = DTC 14 clt hi
Bit 5 = DTC 15 clt lo
Bit 4 = DTC 16 clt unstable
Bit 3 = DTC 17 clt pullup
Bit 2 = DTC 18 egr flow
Bit 1 = DTC 19 tps stuck
Bit 0 = DTC 21 tps hi

Powertrain Enable MIL DTCs 2 (0x36FB):

Bit 7 = DTC 22 tps lo
Bit 6 = DTC 23 iat lo
Bit 5 = DTC 24 vss loss aut
Bit 4 = DTC 25 iat hi
Bit 3 = DTC 26 iat unstable
Bit 2 = DTC 27 psa open
Bit 1 = DTC 28 psa short
Bit 0 = DTC 29 egr posn

Powertrain Enable MIL DTCs 3 (0x36FC):

Bit 7 = DTC 31 tdm signal
Bit 6 = DTC 32 maf signal
Bit 5 = DTC 33 bap hi
Bit 4 = DTC 34 bap lo
Bit 3 = DTC 35 idle speed
Bit 2 = DTC 36 vacuum leak
Bit 1 = DTC 37 unused
Bit 0 = DTC 38 unused

Powertrain Enable MIL DTCs 4 (0x36FD):

Bit 7 = DTC 39 unused
Bit 6 = DTC 41 est
Bit 5 = DTC 42 bypass
Bit 4 = DTC 43 esc
Bit 3 = DTC 44 ro2 lean
Bit 2 = DTC 45 ro2 rich
Bit 1 = DTC 46 crank
Bit 0 = DTC 47 18x signal

Powertrain Enable MIL DTCs 5 (0x36FE):

Bit 7 = DTC 48 cam signal
Bit 6 = DTC 49 cam-18x sync
Bit 5 = DTC 51 prom
Bit 4 = DTC 52 bat high lt
Bit 3 = DTC 53 bat high st
Bit 2 = DTC 54 bat unstable
Bit 1 = DTC 55 ad err
Bit 0 = DTC 56 loaded lean

Powertrain Enable MIL DTCs 6 (0x36FF):

Bit 7 = DTC 57 inj monitor
Bit 6 = DTC 58 tft hi
Bit 5 = DTC 59 tft lo
Bit 4 = DTC 61 unused
Bit 3 = DTC 62 unused
Bit 2 = DTC 63 lo2 slo
Bit 1 = DTC 64 lo2 lean
Bit 0 = DTC 65 lo2 rich

Powertrain Enable MIL DTCs 7 (0x3700):

Bit 7 = DTC 66 32 sol cct
Bit 6 = DTC 67 tcc ctsol
Bit 5 = DTC 68 slip
Bit 4 = DTC 69 tcc stuck on
Bit 3 = DTC 71 unused
Bit 2 = DTC 72 vss int aut
Bit 1 = DTC 73 pcs
Bit 0 = DTC 74 unused

Powertrain Enable MIL DTCs 8 (0x3701):

Bit 7 = DTC 75 bat lo st
Bit 6 = DTC 76 stft delta
Bit 5 = DTC 77 unused
Bit 4 = DTC 78 ltft delta
Bit 3 = DTC 79 trans fluid temp high
Bit 2 = DTC 81 23 sol cct
Bit 1 = DTC 82 12 sol cct
Bit 0 = DTC 83 tcc pwmsol

Powertrain Enable MIL DTCs 9 (0x3702):

Bit 7 = DTC 84 unused
Bit 6 = DTC 85 unused
Bit 5 = DTC 86 unused
Bit 4 = DTC 87 unused
Bit 3 = DTC 88 unused
Bit 2 = DTC 89 unused
Bit 1 = DTC 91 qdm fault
Bit 0 = DTC 92 lo fan

[Rhysk94]

Holeee moley!
That's insane!
Cheers Antus, now that I cna definitely understand what to do.
I'll get an xdf edited through next week and post it up for everyone!

[antus]

Thanks for the offer! I just edited the data so grab it again if you downloaded. I'm looking at if I can generate some XML and paste it in to an XDF and in testing I noticed that tunerpro bit order and my bit order were opposite, and also I hadnt updated the address for powertrain DTCs for A5G. So thats corrected in the earlier post. Im playing around with generation now, if I am successful I might have an updated XDF tonight. But we'll see. As always the AIs look promising then start getting things wrong. Maybe traditional code would be better! (actually might ask the AI to write a program to make the edits, rather than output XML... hmmm).