Playing around with the 2.7 software (ECU and TCU)

[Adrian D]

Hmm, you can get the a Tricore toolchain, they should be available for free and use
objdump for disassembly.

[RTB]

Came across some old tuning stuff I had. Found a debugger that seems to have worked.

This should keep me busy. From the original file.

[Adrian D]

Just make sure endianess and instruction set are correct

[RTB]

Well, it was an exciting day there for a while. Now, not so much.

The MPPS finally arrived. I had read that it works with Windows 10,so gave it a go. Plugged it up, and read the ECU info fine. Went to read the data and it failed. Tried again, same thing.

Ok, so went and got the Windows 7 laptop. I know it works with that. That won't even wake the ECU. Car starts fine, ECU seems ok. MPPS just can't even wake it.

Check with DiagPro. No faults. Data reads ok.

So back to the XP laptop. Same as windows 10. Reads the ECU info fine, just wont bring in the data.

Looks like my MPPS is dodgy. It wasn't even the cheapest one.

Now I need to wait another month I guess. KESS should be here soon, so that will give me a new toy.

[Adrian D]

BOOOOOOO!

I think I bought the cheapest I could find closer to home. Same with KESS.

[RTB]

Yep, seems there are none anywhere near me. I'd go pick one up if I could.

Bought the cheapest KESS I could find. About middle of the range on the MPPS, and it failed....

Going to give it another go tomorrow, then just find a cheap scummy MPPS and get it on it's way.

Then finally get some of my planned changes made and post them here.....

[RTB]

So today saw a heap of success, but ended in failure.

I tried communicating with the MPPS V13 software.No joy as before. I was also supplied with V12 software so figured I would give it a go. Wham, straight up it was working perfectly. Reliable reading of the ECU ID. Did an ECU read and saved my maps. Yay!!!

Then, wrote the original file back to the ECU. That moment when it says "Erasing Flash" is always a butt tightening event, but the write went well, I held my breath the entire time, and the engine still ran. Yay once more.

So I head up and made a simple change. Similar to what AdrianD did early in this post with the 0% throttle IQ amounts, but I left only the 950 RPM value at 5. In my mind this should soften the approach to idle, but still give me the "deceleration fuel cut-off" I am looking for. Either way, it will test my ability to successfully do this job.

Verified the changes in WinOLS. All looked good. Fixed the checksum and verified again. The checksum changes now showed up in WinOLS too. Awesome I say. Time to go write it into the ECU.

Now I am back to where I was in the beginning. Can't read the ECU ID, Can't do a full read. Program just crashed the moment it tries to read.

So I am giving up for the night.