I'm running donners 88586714 DMA live map sd 2.0 based on v7

I noticed that making wgdc adjustments about a week or two ago somehow corrupted that flash. I copied the tables over to a fresh rom and have been tuning ever since. Donner reduced the ve table to make room for sd. However the issue he described that would be the problem is not what's happening if alt map space ate the sd table or something like that.

I can try a quick flash of a 88592715 rom I might have. It's untuned for this set up but a quick log would show positive or negative

Mrfred I have flashed a couple times again same issue. I will try an older version of my rom to see if this is corrupted again

 

Fox- als testing is tough. I have put very silly values in silly tables over the time I've done this. If reliability like this will be a problem then maybe a real ecu/ems is my destiny.

I wonder if the ecu is damaged, can it be repaired?

Ot but sas als related

Either way Todd is donating a valve I presume is from a cosworth with remote housing to me and I'm going to ground that relay so it opens upon sas tables.

I was practicing last night and what ends up being the case, bear in mind I have a bov vta. Lift -slight pause of vacuum, sas provides fuel after pause, makes the switch to alt maps, and my mani sees 4-6 psi with 30% tps . Mean while my bov is screaming

 

Flashing a USDM 8859 rom now...

 

Didn't work aswell as an old version of 8858 .

And 2.7 doesn't do the trick . Sigh

 

Can you use someone else's car to see if evoscan works on theirs?

I can't see the ecu going bad from too many flashes, but I could be wrong.

 

That's because only a hand full of people had to flash that many times, including Ratsbud who's been working on the ALS project.
Based on a similar experience I had, I think the ecu is beyond repair

Ratsbud, sounds good in regard to the cosworth valve, do you have a picture of it? post it on the als thread.

 

I've flashed my ecu over 150+ times... that's why I find it interesting.

Let us know if something fixes the problem 211rat

 

Ok, what portion of the ecu is the one that goes bad. If there's a part available why couldn't a new one be substituted?

anyone know the crank and cam signal pattern? I'm inquiring for megasquirt and need to know that

 

I've reflashed mine well over 400 times, and I'm the third owner, so don't know how many times it was reflashed prior to my ownership. Still works fine (knock on wood).

 

The flash memory where the rom is stored is what can go bad. It looses its ability to retain the data or possibly not provide the correct value when requested by the processor. I think the tephra roms have the potential to be more problematic because every time the ecu is flashed, the entire rom is rewritten to the flash memory. The factory rom only flashes the first 100 kilobytes or so where all the factory tables are stored. I would think that if the flash memory were going bad, ecuflash would give read/write errors.

 

Well by rearranging my logging items carefully I can get by with everything shifted one column to the left into log notes.

Will have to do for now

Ill keep checking too maybe something in my cable went bad? Funny how both laptops and both versions experience the same issue. Leads me to 2 other paths.. Ecu & op cable.

I need to find another Mitsubishi to log!

 

This

Good luck man, keep us updated

 

Purchased a used ecu update soon..

 

In for more updates ... good luck man

 

Haven't got the new ecu yet but my innovA scan tool displays data correctly!