openecu.org

This is some great news. Glad to see that this thread is getting some attention. So then there are XML definitions available for the USDM 2.4L ECU?

The Austrlian 4G69 ECU we sent to you we can read and write back to the ECU, but when we currently write back it bricks the ECU, as for whatever reason, its not writing either the full information back or something similiar to that. I have already had to replace one ECU, Etac controller and ignition barrel / keys on a customer car who was our test vehicle so dont' really want to go through that again. I still have the ECU, Etac and keys from that car in the hopet hat we can bring the ecu back to life again.

Let me know what I can do to provide you in logs etc to show whats happening.

tapki wrote:example.xml

<rom>
<romid>
<xmlid>000000E6</xmlid>
<internalidaddress>f52</internalidaddress>
<internalidhex>000000E6</internalidhex>
<caseid>none</caseid>
<ecuid>none</ecuid>
<make>Mitsubishi</make>
<market>USDM</market>
<model>LancerRalliArt</model>
<submodel>N/A</submodel>
<transmission>Auto</transmission>
<year>2004</year>
<flashmethod>mitsubootloader</flashmethod>
<memmodel>M32176F6</memmodel> *It can't be flashed with M32176F4 correctly (default for RalliArt 512K)
<checksummodule>mitsucan</checksummodule> *Without CHKSUM I've got a CEL and misfires
</romid>

for 1.42 I'm used a file from 1.43.170? beta, becouse of 1.43 crashed in Vista, but under XP everything was fine.

folder: "read templates"
file: read_mitsum32176f6boot.xml :

<rom>
<romid>
<xmlid>read_mitsum32176f6boot</xmlid>
<make>Mitsubishi</make>
<market>ALL</market>
<model>Colt</model>
<submodel>(768k)</submodel>
<year>2006+?</year>
<flashmethod>mitsubootloader</flashmethod>
<memmodel>M32176F6</memmodel>
<checksummodule>mitsucan</checksummodule>
</romid>
</rom>


I don't read with RA 2004-2006, it won't work for me


I'm used next string "Colt 762K" 2006+ for all 4G69

Hello,

We convert our original Outlander Turbo 512kb rom file to 768k and edit the memmodel to M32176F6 and the checksum in the xml to able to open it by Ecuflash as you posted. The crc checksum problem was gone when you open the converted file.
We coundn't write in the converted file with M32176F6 in the xml, here is the log :

[23:14:10.213] EcuFlash Version 1.43.3252
[23:14:10.213] OS Version Windows 7
[23:14:10.213] Qt Version 4.6.2
[23:14:10.227] 62 memory models read.
[23:14:10.228] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[23:14:10.467] 358 ROM metadata models scanned.
[23:14:10.467] checksum module "subarudbw" loaded.
[23:14:10.467] checksum module "mitsucan" loaded.
[23:14:10.467] checksum module "mitsuh8" loaded.
[23:14:10.467] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[23:14:10.468] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[23:14:10.468] flashing tool "wrx02" loaded.
[23:14:10.468] flashing tool "wrx04" loaded.
[23:14:10.468] flashing tool "sti04" loaded.
[23:14:10.469] flashing tool "sti05" loaded.
[23:14:10.469] flashing tool "mitsukernel" loaded.
[23:14:10.469] flashing tool "mitsukernelocp" loaded.
[23:14:10.469] flashing tool "mitsubootloader" loaded.
[23:14:10.469] flashing tool "shbootmode" loaded.
[23:14:10.470] flashing tool "shaudmode" loaded.
[23:14:10.471] flashing tool "subarucan" loaded.
[23:14:10.471] flashing tool "subarucand" loaded.
[23:14:10.471] flashing tool "mitsucan" loaded.
[23:14:16.603] C7280009 (56 tables) inheriting evo10base (101 tables)
[23:14:16.629] 786432 byte image read.
[23:14:28.776] J2534 API Version: 04.04
[23:14:28.776] J2534 DLL Version: 1.00.3210 Nov 22 2010 23:18:50
[23:14:28.776] Device Firmware Version: 1.11.3209
[23:14:28.776] Device Serial Number: TALz8Qnz
[23:14:43.356] sending init sequence 1 (0001)
[23:14:44.368] got 0x05 response
[23:14:44.368] sending init sequence 2
[23:14:44.374] got 0x1A response instead of 0x1B
[23:14:44.378] sending init sequence 3
[23:14:44.732] entering bootloader
[23:14:44.741] interface close
[23:15:57.861] 786432 byte image read.
[23:17:30.081] 786432 byte image written.
[23:19:26.986] 786432 byte image written.
[23:20:11.674] 786432 byte image written.
[23:20:16.773] J2534 API Version: 04.04
[23:20:16.773] J2534 DLL Version: 1.00.3210 Nov 22 2010 23:18:50
[23:20:16.773] Device Firmware Version: 1.11.3209
[23:20:16.773] Device Serial Number: TALz8Qnz
[23:20:30.065] sending init sequence 1 (0001)
[23:20:31.104] got 0x05 response
[23:20:31.104] sending init sequence 2
[23:20:31.118] got 0x1A response instead of 0x1B
[23:20:31.118] sending init sequence 3
[23:20:31.469] entering bootloader
[23:20:31.483] interface close


Also we can read out ever the Outlander turbo ecu with Colt 786k.

Mitsiman wrote:The Austrlian 4G69 ECU we sent to you we can read and write back to the ECU, but when we currently write back it bricks the ECU, as for whatever reason, its not writing either the full information back or something similiar to that. I have already had to replace one ECU, Etac controller and ignition barrel / keys on a customer car who was our test vehicle so dont' really want to go through that again. I still have the ECU, Etac and keys from that car in the hopet hat we can bring the ecu back to life again.

Let me know what I can do to provide you in logs etc to show whats happening.

We have the same problem with Outlander turbo ! The car run again because Colby make us a special Ecuflash the 1433252 beta what can write back an italian tuner rom with our immoby code ! We can not change any other table because the car start up with 3cylinder and flashing CEL .

cboles wrote:If someone has an ECU that isn't flashing correctly that they are willing to send it in, I would be happy to fix the problem for them. The problem with a lot of these Mitsu ECUs is that there are slight variations in the bootloader, memory size, erase block size, checksum, etc. between different models that are causing these problems. I think I already have all of the pieces - it just takes some experimentation to get the right combination of a particular ECU. Part of the problem can be fixed by coding on my part - part of the problem will be getting feedback as to what flashing options work with what models so I can put more detailed selections into the read options list.

Colby

Hello!

We appreciate your effort on making exotic Mitsu ECUs problem free. We would be happy to give a hand in testing/giving fast(<24h) feedback on your code. We hope this will help you to solve easily the outlander turbo and other special mitsu ECUs problems...

Bump for solution ! Colby please when you have time take a moment on the Ecuflash beta what coud be the problem with the cheksums ! Thank you ! Gergo

Colby or someone how can we help to solve the Outlander turbo reflashing problem with the check sums ? If we can send out an Ecu to you would help ? THank you !

Colt czt : Do we know any succes writing process with the Colt czt ? What Ecuflash ? Honestly I'm fraid too write in the ecu before confirm any succes! It has the chekcsum problem too or not ? I find this, any comment please Colby Evoscan is it really working ?
http://www.rpw.com.au/shop/index.php?option=com_content&task=view&id=200&Itemid=40

RPW has successfully worked with EcuFlash and Evoscan to enable the stock ECU to now be re flashed. RPW Stage 1 tunes are now available for sale. Below is an outline of just some of the things we can do

Adjust the fly by wire throttle maps to improve throttle response / smoothness of power
Retune the fuel and ignition curves to maximise power
Modify the mivec changeover point to maximise torque / power
Alter boost levels by use of pills / restrictors or allow use of after market boost controller
Play with torque request maps to remove CEL check codes
Removal of CEL Codes

Ready to donate the solution !

It is the great write-up what is the issue :

'Im currently using ecuflash 1.43.3150b beta and using the mitsubootloader to work with colts and lancer ralliarts. I can read the rom fine and upload it to the computer but when attempting to change any info in the rom within ecuflash or any external hex editor the checksum changes and once reflashed to the ecu a flashing check engine light occurs with an internal memory checksum issue. The actual rom data itself is changed and works(tested by changing init code and seeing if it changed in ecu) but there is issue of checksum. Tried in normal mode, recovery mode and benched ecu. modules used are mitsubootloader and mitsucan. In disassembly the checksum sub routine can be found for the reference points but its painstaking to have to find each segment. "

Just wanted to drop by and ask where this all went XD

Marcello wrote:i do them with serial suite piasini it work great

How does that work?
I looked up the PIasini master suite, you plug the Piasini box directly to the ECU, correct?
And is the map defined? Or do you have to modify it in hex?

Marcello wrote:

ElDominio wrote:

Marcello wrote:i do them with serial suite piasini it work great

How does that work?
I looked up the PIasini master suite, you plug the Piasini box directly to the ECU, correct?
And is the map defined? Or do you have to modify it in hex?

the suite is only to read and write ecu the software don't edit i edit in winols
i make the defs directly in winols

I'd like to ask for the definitions, but you probably want to keep them lol
Still, how would I plug the Ralliart ECU to the Piasini? Would I have to use the seperate cables or can I use the OBD2 plug?