Anyone know how to do this?

Placing this byte into the data stream...

L0040 EQU $040 ; DIAG MW1
; b7 = map low error in effect, malf 34
; b6 = map high error in effect, malf 33
; b5 = tps high error in effect, malf 22
; b4 = aldl blink out mode
; b3 =
; b2 = tps low error in effect, malf 21
; b1 =
; b0 = mode 10 cmd cleared errors

 

You need to first patch the BIN to place that byte into the ALDL stream. Select a location that has data you don't care about (don't use), and change it to address $0040 (2 bytes).

Once this is done and a chip burned, can then alter the XDL file to display the four bit values.

RBob.

 

I think that makes sense. Again I'm hex ignoramus.

Do I need to make another run with the car? Or is the data actually in my current data log and ready to be retrieved with the updated bin?

 

You would need to make another run.

the patching of the bin changes what is sent through the ALDL stream. So what this byte would send through the ALDL stream is not yet in any of your existing logs.

The error codes should be there though. I'm not sure I've come across any datastream without them, other than maybe the early C3 type ECMs, it's been so long since I played with one, I don't recall what the datastream had in it, other than it was agonizingly slow.

 

RBob, sorry for sounding so dumb here... What address in the $8D code is not used such that I can put this 0040 value there?

 

See picture, open hex editor (CTRL+H), the highlighted 2 bytes are the ones to change. They are the EGR DC% in the ALDL stream. Note that address at the bottom: 909

Change those two bytes ($01 $23) to: $00 $40

Commit the changes, close the hex editor, then save the BIN. Now the 31st byte of the data stream will have the DIAG MW1 in that location.

RBob.

 

Awesome! Thanks!! I'll try this out hopefully this weekend if I get the chance.

One other thing I've done is start from a fresh ANHT bin and re-input all my changes. I'm wondering if somehow something got corrupted in the bin I was using.

 

Use the compare feature of Tuner Pro to see what has changed in the BIN.

RBob.

 

Ok, I made the changes and the compare in Tunerpro confirms they're the only changes, and they match what you've indicated.

When I burn the chip and put it in the car, turn on the ignition, the fans come on.

Went back and burned the baseline bin, no fans.

Burned the updated bin again, and fans come on.

When I pull up the updated bin in Tunercat, I get the error - "Warning: A checksum in the selected source file is incorrect. Proceed anyway?"

Did I miss something?

BTW, thanks very much RBob for the time you're spending on this. When we get this solved, I really want to finish up this bin so I can post it for Miniram startbin 1.02. Do what I can to pay the help forward...

 

Along with the fans the SES should be flickering, there is a SES light?

You need to save the BIN to update the checksum after patching it.

RBob.

 

SES light is not flickering.

Here's the exact process I went through... actually tried it two ways

Iteration 1

1.) CTRL-H, pull up Hex Editor, went to specified address
2.) Changed the 01 to a 00 and the 23 to a 40
3.) Action => Commit Changes
4.) Action => Close
5.) File => Save-As => my new file name

Fans come on with ignition switch, SES light comes on but does not blink

Tunercat unable to open the file, gives warning I indicated above.

Iteration 2

1.) CTRL-H, pull up Hex Editor, went to specified address
2.) Changed the 01 to a 40 and the 23 to a 00
3.) Action => Commit Changes
4.) Action => Close
5.) File => Save-As => my new file name

Fans do not come on with ignition switch, SES light still on but does not blink (this is actually typical prior to starting the engine).

WIth Tunerpro connected to ALDL, I don't see the updated data stream with the new values.

Tunercat unable to open the file, gives warning I indicated above.

 

Makes no sense at all. One thing is that the SES should do a blink-off at key-on, engine-off. This is every time after the key has been off for at least 5 seconds. If it doesn't then there is something wrong there.

I had a thought, maybe Tuner Pro doesn't think that the BIN was changed and isn't updating the checksum. Try making a change to a random parameter before saving the BIN. Can change it to the same value that is there, just as long as TP sees a change to a parameter.

If that doesn't work email the patched BIN to me and I'll take a look at it.

RBob.

 

Oh, yeah, it does blink one time like you say when I have a "good" chip in there. That is normal.

With the updated chip per our changes earlier, I don't get the blink and then fans come on.

So, for your suggestion, I went ahead and modified the hex again by putting the same 13 in address 000000 as was already there. Same process as above.

I then did another one at another address, this time 00000E1, put in the same 77 that was there.

Results in both cases => Standard 1 blink and no fans. However, Tunercat still can't open the bin.

So, I'm making your changes again per my iteration 1 above and am e-mailing the bin to you.

Thanks again, I really appreciate the help here!