which DSM's have the flash port ???
or we all must wire pin 79 to the OpenPort?
sorry for making a lot of question but this is a FAQ thread
i am willing to bet that you should be able to pull the flash port out of any Mitsubishi that can be flashed ... 98 and newer, gallant, eclipse, lancer. etc. etc. after all that flash connector is he same one they use for the EVO's.
Advertisement
To browse the forums without the advertisements above, Login/Register
Hamish said there was a problem with DTCs that he hadn't been aware of before, he accidentally broke them in a few versions. The newest (beta) version IIRC has them fixed.
DTCs are weird with Tectrix 1.3 and EvoScan 2.5 too. I couldn't log 15 out of 20 DSMs, none of 3000GTs, 2 Galants, Chrysler 300C and bunch of other cars. Either the cable is wrong, or OBD2 stuff is real beta...
Ceddy,
What changes have you made to your MD346675 rom and reflashed back to your ecu?
and are you happy with the results?
I pulled the rom out of my 98 awd = MD346676
I also have a couple of evo 5 rom files I have browsed.
Ceddy,
What changes have you made to your MD346675 rom and reflashed back to your ecu?
and are you happy with the results?
I pulled the rom out of my 98 awd = MD346676
I also have a couple of evo 5 rom files I have browsed.
Has anyone else been flashing the 98/99 H8 ecu?
So far I've put 1150cc injectors in, and they idle like stock 450s.
And I leaned out the fuel maps up top where they are super rich.
And I tried out full time open loop, which works great.
My 14 year old radiator decided to blow up. so I'm waiting on a new one.
FedEx should have it here by the weekend.
I haven't decided which maps to use yet.
I have 7.8:1 compression motor with a HX-35 at ~25 psi.
I was thinking about using the EVO6 Tommi Makinen or RalliArt maps, but haven't studied all the maps yet.
I should have more results next week:
I'll try out map axis rescaling.
MAF scaling.
And I should be able to hit fuel cut easily with the HX-35, so I can test fuel cut removal.
If anyone else has a flash image besides the EM2055-0011(98 GST), post it up.
It work be nice to see how the map selection works. And if the two sets of maps are FWD/AWD or California/Federal. We should be able to get a Map Selector Switch like the Evo guys have easily. (Different maps for 93 octane and race gas)
By the way, I'm not sure if this is of any interest to anyone here (probably just steve ), but I'm starting to collect relatively high-resolution photos of the PCBs from ECUs that I get my hands on or work with regularly; it's proving to be very helpful to be able to quickly visually reference a board against the associated datasheet.
So anyway, the pictures of my old '99 ECU that the ROM above are from are here and here.
Has anyone managed to spot any difference between revision C and D boards? The second largest chip might have a different serial, but it's unreadable on the board I have, other than that they seem to be equal.
Maybe someone have tried to cross flash AWD<->FWD ROMs or rev C <-> rev D ROMs?
Cross-flashing might cook the ECU, but if it doesn't, settling on latest '99 GSX ROM for all tuning needs would be great, that way we could concentrate our research on one ROM only.
As far as I understand from "Evo ECU in DSM" thread all Evo ROMs/boards are compatible.
Has anyone managed to spot any difference between revision C and D boards? The second largest chip might have a different serial, but it's unreadable on the board I have, other than that they seem to be equal.
Maybe someone have tried to cross flash AWD<->FWD ROMs or rev C <-> rev D ROMs?
Cross-flashing might cook the ECU, but if it doesn't, settling on latest '99 GSX ROM for all tuning needs would be great, that way we could concentrate our research on one ROM only.
As far as I understand from "Evo ECU in DSM" thread all Evo ROMs/boards are compatible.
This is really something that should be done. Right from the get go, make it as easy for yourself and everyone else by using as few ROMs as possible. The Evo guys are just now starting to try this after who knows how many years and 7 or 8 different ROMs that always need to be patched for new updates.
This is really something that should be done. Right from the get go, make it as easy for yourself and everyone else by using as few ROMs as possible. The Evo guys are just now starting to try this after who knows how many years and 7 or 8 different ROMs that always need to be patched for new updates.
It really only became possible recently. For the Evo guys they have to deal with the fact that their cars differ significantly from year to year and market to market. Ours are pretty much similar across the board (USDM at least).
One is when you have different sensors on different cars, and one is when you have different ECUs that won't accept other ROMs, only those which it was designed for.
We know that Evo ECUs have no problems with another ROM, even if it's made for something else with different sensor set in mind.
Speaking of which, I wonder if the JDM Eclipses have flashable ROMs. My car is 96 and it has completely weirdo socketed EERPROM from factory, and it has no emission related equipment, has unheated O2s, and no emission related CELs, that is a factory setup.
It would be interesting to see what JDM 98/99 ECUs have.
I was under the impression that Eclipse != JDM. The EDM and South American DSMs were the only ones to head outside of the continent new AFAIK.
I'm driving a JDM, everything is written in Japanese, timing belt changes, instruments are in kilometers, turn signals are yellow, ABS warnings are written with hieroglyphs.
These are the DTCs I get when I swap to a USDM ECU:
Updated: 18:06:48
6 Diagnostic Trouble Codes Found:
----------------------------------------------
P0135 Heated Oxygen Sensor Heater circuit Bank 1 Sensor 1.
P0141 Heated Oxygen Sensor Heater circuit Bank 1 Sensor 2.
P1400 Manifold Differential Pressure Sensor circuit.
P0443 EVAP System Purge Control Valve circuit.
P0446 EVAP System Vent Control.
P0403 EGR Solenoid.
They are all because of missing equipment, or wiring and so on.
Adding a Flash Connector to a 95-97: Attachment 96830 Attachment 96831
On 95-97s you must add a pin at position 78 of your ECU Harness.
This must be connected to the 2.5mm phono plug on your OpenPort 2.0 cable.
It must be connected to the tip of your phono plug.
I thought pin 78 was the knock sensor. My notes, forgot where I got them from, say its pin 79 that's the flashport pin.
Ceddy,
Did you get a chance to look over the em2056.bin?
It wouldnt let me upload the rom to dsmtuners
I can send it out to others if they want to compare it to EM2055, etc...
Red
Yes, it has the same map addresses as the 2055, but the map axises addresses are different.
I also confirmed the Speed Limiter in the periphery bits is correct, the GST has it enabled and the GSX doesn't.
I'll try to upload the ROMs I have tonight, got 98 GST/GSX, 99 GSX. Still need a 99 GST.
The flash routines look the same in all the ROMs I have, I think cross flashing will work, without bricking the ecu.
I just wanted to note that the new Ecuflash 1.42 has changes made to EM2384, I don't know what the changes are or if it existed before at all (just showed up in a diff someone else did). It may be worth checking out.
The only thing changed in the XML for EM2384 was changing the memory model from H8539F to H8539FA; the definition is still nothing more than a <romid> stub, though. The substantial changes were all to Evo V+ definitions. Here's the full changelog:
Quote:
Originally Posted by EcuFlash ChangeLog
2009-06-27: Version 1.42 released
EcuFlash Related Changes
support for flashing H8/539FA processor (e.g. Evo 6.5) via new H8539FA memory model
add many generic memory models to allow support for arbitrary ROMs from ECUs that EcuFlash has no flashing support for. these are named Generic1K, Generic2K, ... up to Generic2048K, including all powers of 2, plus many other common sizes.
fix programming voltage warning errors in Subaru HC16 kernels
actively pull up OBD pin 9 when communicating with HC16 Subarus to avoid reflash mode initialization problems on some EDM models
add some retries to kernel reads, instead of failing
allow unique ID data in Subaru CAN ROM protected area to be different without requiring this area to be reflashed (which is not allowed). this allows ROMs of the same version to be shared amongst users without refusal-to-flash errors.
fixed error that limited data type to 4 bytes in size (doubles and bloblists can be bigger)
fixed bug in Subaru K-line reflashing that did not initialize the parity mode of the vehicle interface, causing errors if the interface had previously been used with odd or even parity
J2534 DLL Related Changes
(no changes other than new firmware payload)
Firmware Related Changes
fix bug which can cause CAN receive buffer overruns during large ISO15765 transfers
fix bug where resting voltage of adjustable power supply can be low enough to trigger undervoltage protection of voltage multiplexer IC
increase maximum allowable ISO9141 baud rate to be 125000 baud
OK, put my 98 ECU in today. I swapped the coil and injector pins at the harness, and added the flashpin too. I had one isolated incidence of the dreaded low load/rpm knock in the 20+ range, but only for a second and only once.
One thing I noticed though, I did an ecu read using the 96-99 EVO selection since it was the closest thing to our cars, and the load and rpm values on the axis were all gibberish. I'm very new to this software and type of thing in general, so any help is appreciated.
Oh, and for those people who need a pin for the flashport, and don't have automatics, the cruise control computer is in the passenger's side kick panel. The module uses the same pins as the ecu does, and I found that there are two suitable pins for removal, one is red w/yellow stripe - pin 10, and the other is red w/white stripe pin 11. They're only used for automatics, but the wires are still there on manual cars.
Last edited by draculia; 07-05-2009 at 04:06 PM.
Reason: Corrected Information
OK, put my 98 ECU in today. I swapped the coil and injector pins at the harness, and added the flashpin too. I had one isolated incidence of the dreaded low load/rpm knock in the 20+ range, but only for a second and only once.
Is your car smooth @ 2500-3000 RPMs, clutch in, or does it vibrate? Which pins did you swapped?
If you check ECU Internal ID#1 it will tell you your ROM version.
My DEF is for the 20550011, if yours doesn't match the axises will be off and read gibberish.
If you end up getting the P300 Random Misfire CEL, it can be turned off in the Periphery Bits.
Quote:
Originally Posted by draculia
OK, put my 98 ECU in today. I swapped the coil and injector pins at the harness, and added the flashpin too. I had one isolated incidence of the dreaded low load/rpm knock in the 20+ range, but only for a second and only once.
One thing I noticed though, I did an ecu read using the 96-99 EVO selection since it was the closest thing to our cars, and the load and rpm values on the axis were all gibberish. I'm very new to this software and type of thing in general, so any help is appreciated.
Oh, and for those people who need a pin for the flashport, and don't have automatics, the cruise control computer is above the passenger's side kick panel. The module uses the same pins as the ecu does, and I found that there are two suitable pins for removal, one is red w/black stripe and the other is red w/blue stripe I believe. Their positions are 10 and 11 if I recall, and they're only used for automatics, but the wires are still there on manual cars.
), but I'm starting to collect relatively high-resolution photos of the PCBs from ECUs that I get my hands on or work with regularly; it's proving to be very helpful to be able to quickly visually reference a board against the associated datasheet.
