RALLInspired Performance

Two more done. This time on a 2007 3.0 AT ecu and a 2017 ECU.

It's cheaper than a new ecu in most cases! The subaru client tried to install a Cobb Access port onto the non turbo ecu. I don't know how they managed to force the Cobb AP to even attempt an install but it didn't turn out well, obviously.

The Mitsubishi ECU became stuck during a read attempt, most likely due to a voltage drop. These ecus can take around 10 to 15 minutes to complete a read and it's taxing on older batteries since the radiator fans kick on during a read or flash.

All fixed and shipped back!

World first? With the help of Hamish from EvoScan i have finally sorted out proper logging via EvoScan of the newer 2014/2015+ SH based Mitsubishi ECUs!!! I tried searching for the proper routines to patch YEARS AGO and i just could never get it. I speak M32R and SH is just... different. Granted this was nearly 8 years ago and I've come a long ways since then!

With some encouragement from Hamish i went deep to try to figure this out. Once i had a test patch Hamish helped me sort out the proper requests ID format for use with his software. After fixing a few bugs, i can call and log ANY RAM address in the chip memory. Logging of the SH72531 is now a full go!!! FINALLY!!!!

I will note we spent HOURs on this today and when asked how much he wanted for his time gave me his response (in the pic)

Ladies and gentlemen we never stop pushing. There are people who make all sorts of claims but understand who has been developing non stop to move the platform FORWARD.

Support Hamish at www.evoscan.com
Support my work and development here: https://www.patreon.com/RALLInspiredECUDevelopment
For orders:
www.rallinspired.com

Also attached a screen shot of the OBD protocol for ECU voltage vs the direct RAM address call using mode 23.