PDA

View Full Version : P0300 problems no more...



earlyapex aka jack ass
10-27-2008, 10:02 PM
The open source community strikes again.

This is possibly HUGE for the 03-04 guys that throw P0300's more than there are days in the week.

Once I test and confirm, this is something I will offer to the needed in my tunes.

http://forums.evolutionm.net/showthread.php?t=377898

smack
10-27-2008, 10:10 PM
wow, someone should pass this one on to the mitsu dealers :lol:

just shows that there are still some smart kids out there...

Positron
10-27-2008, 10:13 PM
woo hoo!

EvoTio
10-27-2008, 10:18 PM
Wow, this is some great news!

earlyapex aka jack ass
10-27-2008, 10:20 PM
just shows that there are still some smart kids out there...


very.

There is another one I am beta testing tomorrow.

3D knock control for the stock ecu.

This is also HUGE.

Matz
10-27-2008, 10:37 PM
I will be PM'ing you once I pull the code. I always get a CEL, but it might actually not be a P0300 this time around. What other info do you need beside the code? Should I just give you a screenshot from ECU+?

nightwalker
10-27-2008, 11:57 PM
I get a p0300, but I turned the boost down, and it hasn't come back, so I think mine is boost related.

RREVOVIII
10-28-2008, 09:05 PM
mine went away without doing this.... it used to pop twice a week of just driving my way to work and home! mostly come's out during cruising on the freeway...

MR EVO 8
10-28-2008, 09:27 PM
Yes! We can PASS smog now!

MarkSAE
10-28-2008, 09:35 PM
This fix just disables the P0300 right? Will a smog machine be able to detect that this check is being bypassed?

MR EVO 8
10-29-2008, 05:03 AM
This fix just disables the P0300 right? Will a smog machine be able to detect that this check is being bypassed?


I doubt the OBDII scanner would pick anything up...I'll confirm it when Bryan retunes my car.

chrisw
10-29-2008, 08:15 AM
The open source community strikes again.

This is possibly HUGE for the 03-04 guys that throw P0300's more than there are days in the week.

Once I test and confirm, this is something I will offer to the needed in my tunes.

http://forums.evolutionm.net/showthread.php?t=377898


Bryan, I need to get this ASAP... my evo is getting close to it's first smog check

Matz
10-29-2008, 09:51 AM
Bryan, I need to get this ASAP... my evo is getting close to it's first smog check


I am dreading that day. Will have to remove some stuff and maybe get a retune if I don't have something from the earlier CB Tuning days. Is it possible to get a new flash that will pass smog? I have no idea what to expect here.

chrisw
10-29-2008, 10:07 AM
for the most part I think I am ok. I have a new-ish EVO IX cat and I am certain that I can get my idle stable enough for the test.

I suspect that with our cars, you just have to make sure you have a nice conservative tune under 3000 rpm...

earlyapex aka jack ass
10-29-2008, 10:31 AM
This fix just disables the P0300 right? Will a smog machine be able to detect that this check is being bypassed?


Good question, I'll put it on my Evo and see if the readiness test works.

earlyapex aka jack ass
10-29-2008, 10:32 AM
for the most part I think I am ok. I have a new-ish EVO IX cat and I am certain that I can get my idle stable enough for the test.

I suspect that with our cars, you just have to make sure you have a nice conservative tune under 3000 rpm...


You are going to try to pass the smog test with those M3 cams?

leaveit2bevo
10-29-2008, 12:18 PM
whats the advantage of 3d knock control?

earlyapex aka jack ass
10-29-2008, 12:20 PM
whats the advantage of 3d knock control?


Reduce or Increase knock sensor sensitivity at any rpm and load

Great for built motors, noisey trans and clutches, etc

I think this was the final "Stand-alone can do better" factor. In fact the factory knock control system is miles better than most stand alones.

Evo8urv8
10-29-2008, 12:26 PM
Good question, I'll put it on my Evo and see if the readiness test works.


Lemme know how it goes since we both have the same year. :D

KevOVIII
10-30-2008, 10:46 AM
This ROM mod works great. Usually I get the code while crusing on the freeway or driving through a parking lot. Nothing yet... no pending codes either.

I believe mrfred "fixed" the issue. :)

chrisw
10-30-2008, 01:33 PM
for the most part I think I am ok. I have a new-ish EVO IX cat and I am certain that I can get my idle stable enough for the test.

I suspect that with our cars, you just have to make sure you have a nice conservative tune under 3000 rpm...


You are going to try to pass the smog test with those M3 cams?


they are only M2's. :cool: I think there is a post around here where someone got the M2's to pass, barely...

earlyapex aka jack ass
10-30-2008, 01:41 PM
they are only M2's. :cool: I think there is a post around here where someone got the M2's to pass, barely...




Sorry I always get confused between the 8's and 9's because cosworth made it confusing

M1 for Evo 8 = 270/270 10.2/10.2
M2 for Evo 8 = 280/280 11.0/11.0
M2 for Evo 9 = 272/272 11.0/11.0
M3 for Evo 9 = 280/272 11.6/11.0

DaveLC2
10-30-2008, 02:25 PM
Wow that's too cool! My 03 threw a P0300 so often that damn light burned out :lol:

Dave

chrisw
10-30-2008, 03:23 PM
they are only M2's. :cool: I think there is a post around here where someone got the M2's to pass, barely...




Sorry I always get confused between the 8's and 9's because cosworth made it confusing

M1 for Evo 8 = 270/270 10.2/10.2
M2 for Evo 8 = 280/280 11.0/11.0
M2 for Evo 9 = 272/272 11.0/11.0
M3 for Evo 9 = 280/272 11.6/11.0


but wait until the X's are out to add to the "clarity" accross product lines... :P

earlyapex aka jack ass
10-30-2008, 03:47 PM
they are only M2's. :cool: I think there is a post around here where someone got the M2's to pass, barely...




Sorry I always get confused between the 8's and 9's because cosworth made it confusing

M1 for Evo 8 = 270/270 10.2/10.2
M2 for Evo 8 = 280/280 11.0/11.0
M2 for Evo 9 = 272/272 11.0/11.0
M3 for Evo 9 = 280/272 11.6/11.0


but wait until the X's are out to add to the "clarity" accross product lines... :P


already out lol

MX1 for Evo 10 = 266/266 10.8/10.4

Positron
11-05-2008, 09:11 PM
any update on p0300 Bry?

chrisw
11-05-2008, 09:40 PM
any update on p0300 Bry?


I have put about 100 miles or so with this patch. So far so good! When I do get knock, it's just after peak torque, where you would normally expect the 4g63 to knock.

Also, a new bit was discovered that disables the lean spool routine in the rom. This should be more effective than tweaking the start and stop RPM points.

http://forums.evolutionm.net/showthread.php?t=375174

earlyapex aka jack ass
11-05-2008, 09:45 PM
any update on p0300 Bry?


I've been driving around an X for the last 4 days...

I'll be back to my regular life tomorrow. ;)

dabaysevo
11-05-2008, 10:19 PM
^Who's X?

MR EVO 8
11-06-2008, 06:13 AM
^Who's X?


D7's...LOL

warpspeed
11-17-2008, 09:19 AM
Any update to this fix Bryan?

Steiner
01-12-2009, 08:32 PM
I have put about 100 miles or so with this patch. So far so good! When I do get knock, it's just after peak torque, where you would normally expect the 4g63 to knock.

Also, a new bit was discovered that disables the lean spool routine in the rom. This should be more effective than tweaking the start and stop RPM points.

http://forums.evolutionm.net/showthread.php?t=375174That EvoM thread was like reading another language! So will this fix or the one on Evo or ANYTHING fix those Evos that throw a P0300 code because of lopy cams. Every time that CEL lights up I pull the code with Scan Tech and it's invariably P0300.

chrisw
01-12-2009, 08:35 PM
you are basically turning off the p0300 routine itself, so the ECU never checks. I have almost a thousand miles with the p0300 check turned off.

it's wonderful...

lqdchkn
01-12-2009, 08:36 PM
The fix disable the P0300 entirely. It tells the ecu it no longer run the routine that even searches for it.

^^^^^Ummm yeah what he said. :D

Steiner
01-12-2009, 08:39 PM
Chris are you using the link that Bryan posted at the start of the thread?

RREVOVIII
01-12-2009, 08:40 PM
you are basically turning off the p0300 routine itself, so the ECU never checks. I have almost a thousand miles with the p0300 check turned off.

it's wonderful...
just P0300 code alone not the CEL?

earlyapex aka jack ass
01-12-2009, 08:41 PM
just P0300 code alone not the CEL?

It will not throw a CEL because of a P0300.

whtrice
01-12-2009, 08:43 PM
I use it and it works great.

chrisw
01-12-2009, 08:48 PM
Chris are you using the link that Bryan posted at the start of the thread?

yes. I modified my own ROM using the info from that thread.

RREVOVIII
01-12-2009, 08:52 PM
It will not throw a CEL because of a P0300.

cool thanks!

Steiner
01-12-2009, 09:03 PM
And this works for any USDM Evo VIII or IX?

whtrice
01-12-2009, 09:06 PM
I can vouch for a IX with a 88590015 rom.


And this works for any USDM Evo VIII or IX?

oneillevo
01-12-2009, 09:28 PM
I am waiting until my VIII throws P0300 again to do this so I will keep this thread posted for Rom ID 941700015

Steiner
01-16-2009, 11:23 PM
The extent of my experience with ECUflash is switching between maps or "hex" files. The instructions to fix the p0300 CEL says "copy the new periphery bit definitions to your ROM xml file, relaunch ECUFlash, and find Periphery2 bit4". Is a ROM xml file the same as a hex file or do I need to open the hex file with another application in order to edit the values? Sorry I don't get it.

KevOVIII
01-16-2009, 11:37 PM
Assuming you used the default directory during installation, it should be located here:
C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo\ YOUR_ROM_ID_HERE

I'm not sure what your rom id is, but mine is 96530006.xml (switched from 96940011.xml)

Steiner
01-16-2009, 11:45 PM
Ah OK I got it now. I've got 20+ ROM files in that folder. How do I identify the right one to edit?

Steiner
01-17-2009, 12:07 AM
I dunno maybe I'm fucking retarded but I've followed the instructions and regardless of the ROM file I edit (yes I edited all 23) I open my hex file and bit4 and bit5 are already set to "0".

KevOVIII
01-17-2009, 12:39 AM
Not sure if you still need to id your rom, but to do it:
1) Open EcuFlash and load your rom
2) Click on the "+" next to ROM Info
3) Look at the Internal ID value for your rom id


For your other post:
1) Put this into YOUR_ROM_ID.xml file (preferrably at the bottom before </rom>):
<table name="ECU Periphery2" category="ECUPeriphery" address="fca" type="1D" level="1" scaling="Hex16"/>
2) Open EcuFlash and load your rom
3) Open ECU Periphery2 under the ECUPeriphery category
4) Change the value EFDF to EFCF by typing "0xEFCF" (without quotes) and press return

However, if you're editing the bits using 0's and 1's then just make sure the ECU Periphery2 (FCA) bits for 4 and 5 are both 0.


Hope this helps.

Steiner
01-17-2009, 03:35 AM
4) Change the value EFDF to EFCF by typing "0xEFCF" (without quotes) and press return
Thanks Kev. I was able to do everything except the editing the EFDF value. No matter what I press it won't change. I see "EFDF" is highlighted but it won't change when I follow your instructions.

chrisw
01-17-2009, 09:51 AM
steiner,

make sure you are in developer mode, then try again. IF that doesn't work then something sqrewie is going on.

KevOVIII
01-17-2009, 12:55 PM
Hmmm... It's at level 1 so you should have been able to make changes. I'm not at my computer at the moment so I can give you instructions.

You're welcome. :)

Steiner
01-17-2009, 01:50 PM
Thanks for the help guys. I went from advanced to developer and now all is well. I've been playing around with an old pump gas map for practice before I change my current map. Does anybody have a screenshot of what the metadata column should look like if this has been done properly? I have a "periphery" and an "ECUperiphery" section. I'm wondering if I should have or need both.

whtrice
01-17-2009, 02:00 PM
Is this what you are looking for?

http://i137.photobucket.com/albums/q237/amxman/steiner.jpg




Thanks for the help guys. I went from advanced to developer and now all is well. I've been playing around with an old pump gas map for practice before I change my current map. Does anybody have a screenshot of what the metadata column should look like if this has been done properly? I have a "periphery" and an "ECUperiphery" section. I'm wondering if I should have or need both.

Steiner
01-17-2009, 02:09 PM
Yes that's what I was looking for. Thanks. My column looks different though. Under "ROM info" I have "Periphery" and "ECUPeriphery" in that order. Should I have both of those or did I add something I shouldn't have?

whtrice
01-17-2009, 02:22 PM
Like in the screen shot you should have periphery and under that I have 12 ecu periphery locations:

This is the table in my evo9base xml file

<!-- *** ECU PERIPHERY *** -->
<table name="ECU Periphery00 Hex" category="Periphery" address="f9a" type="1D" level="2" scaling="Hex16"/>
<table name="ECU Periphery0 Hex" category="Periphery" address="faa" type="1D" level="2" scaling="Hex16"/>
<table name="ECU Periphery1 Hex" category="Periphery" address="fba" type="1D" level="2" scaling="Hex16"/>
<table name="ECU Periphery2 Hex" category="Periphery" address="fca" type="1D" level="2" scaling="Hex16"/>
<table name="ECU Periphery3 Hex" category="Periphery" address="fda" type="1D" level="2" scaling="Hex16"/>
<table name="ECU Periphery4 Hex" category="Periphery" address="fea" type="1D" level="2" scaling="Hex16"/>
<scaling name="blobbits" storagetype="bloblist" storagebits="1">
<data name="0" value="00"/>
<data name="1" value="01"/>
</scaling>
<table name="ECU Periphery00 (F9A) Bits" category="Periphery" address="f9a" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15</data>
<data>bit.14</data>
<data>bit.13</data>
<data>bit.12</data>
<data>bit.11</data>
<data>bit.10</data>
<data>bit.9</data>
<data>bit.8</data>
<data>bit.7</data>
<data>bit.6</data>
<data>bit.5</data>
<data>bit.4</data>
<data>bit.3</data>
<data>bit.2</data>
<data>bit.1</data>
<data>bit.0</data>
</table>
</table>
<table name="ECU Periphery0 (FAA) Bits" category="Periphery" address="faa" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15</data>
<data>bit.14</data>
<data>bit.13</data>
<data>bit.12</data>
<data>bit.11</data>
<data>bit.10</data>
<data>bit.9</data>
<data>bit.8</data>
<data>bit.7</data>
<data>bit.6</data>
<data>bit.5</data>
<data>bit.4</data>
<data>bit.3</data>
<data>bit.2</data>
<data>bit.1</data>
<data>bit.0</data>
</table>
</table>
<table name="ECU Periphery1 (FBA) Bits" category="Periphery" address="fba" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15</data>
<data>bit.14</data>
<data>bit.13</data>
<data>bit.12</data>
<data>bit.11</data>
<data>bit.10</data>
<data>bit.9</data>
<data>bit.8</data>
<data>bit.7</data>
<data>bit.6</data>
<data>bit.5</data>
<data>bit.4</data>
<data>bit.3</data>
<data>bit.2</data>
<data>bit.1</data>
<data>bit.0</data>
</table>
</table>
<table name="ECU Periphery2 (FCA) Bits" category="Periphery" address="fca" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15</data>
<data>bit.14</data>
<data>bit.13</data>
<data>bit.12</data>
<data>bit.11</data>
<data>bit.10</data>
<data>bit.9</data>
<data>bit.8</data>
<data>bit.7</data>
<data>bit.6</data>
<data>bit.5</data>
<data>bit.4</data>
<data>bit.3</data>
<data>bit.2</data>
<data>bit.1</data>
<data>bit.0</data>
</table>
</table>
<table name="ECU Periphery3 (FDA) Bits" category="Periphery" address="fda" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15</data>
<data>bit.14</data>
<data>bit.13</data>
<data>bit.12</data>
<data>bit.11</data>
<data>bit.10</data>
<data>bit.9</data>
<data>bit.8</data>
<data>bit.7</data>
<data>bit.6</data>
<data>bit.5</data>
<data>bit.4</data>
<data>bit.3</data>
<data>bit.2</data>
<data>bit.1</data>
<data>bit.0</data>
<table name="ECU Periphery4 (FEA) Bits" category="Periphery" address="fea" type="2D" level="2" scaling="blobbits">
<table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
<data>bit.15</data>
<data>bit.14</data>
<data>bit.13</data>
<data>bit.12</data>
<data>bit.11</data>
<data>bit.10</data>
<data>bit.9</data>
<data>bit.8</data>
<data>bit.7</data>
<data>bit.6</data>
<data>bit.5</data>
<data>bit.4</data>
<data>bit.3</data>
<data>bit.2</data>
<data>bit.1</data>
<data>bit.0</data>
</table>
</table>


Yes that's what I was looking for. Thanks. My column looks different though. Under "ROM info" I have "Periphery" and "ECUPeriphery" in that order. Should I have both of those or did I add something I shouldn't have?

Steiner
01-17-2009, 02:50 PM
I officially don't get it. There are just too many inconsistencies in the instructions on EvoM. It says to copy the 1.35 definitions to your ROM (I'm running 96940011 on an '05 VIII RS with version 1.40.2178 of EcuFlash) but then two lines down it says...

"If you are using an older version of ECUFlash, then copy the entry shown below to your XML file (save the xml file, and then relaunch ECUFlash):

<table name="ECU Periphery2" category="ECUPeriphery" address="fca" type="1D" level="1" scaling="Hex16"/>"

I've copied the 1.35 definitions and I also pasted that last line of code onto my ROM. Did I need to do that? I'm wondering if I've got extra code in there I don't need now.

KevOVIII
01-18-2009, 02:53 AM
Yes that's what I was looking for. Thanks. My column looks different though. Under "ROM info" I have "Periphery" and "ECUPeriphery" in that order. Should I have both of those or did I add something I shouldn't have?

If they display the same values, then you can probably delete one of them. People have differents ways of naming the Periphery stuff.

A screen shot would help. :)

KevOVIII
01-18-2009, 02:56 AM
I officially don't get it. There are just too many inconsistencies in the instructions on EvoM. It says to copy the 1.35 definitions to your ROM (I'm running 96940011 on an '05 VIII RS with version 1.40.2178 of EcuFlash) but then two lines down it says...

"If you are using an older version of ECUFlash, then copy the entry shown below to your XML file (save the xml file, and then relaunch ECUFlash):

<table name="ECU Periphery2" category="ECUPeriphery" address="fca" type="1D" level="1" scaling="Hex16"/>"

I've copied the 1.35 definitions and I also pasted that last line of code onto my ROM. Did I need to do that? I'm wondering if I've got extra code in there I don't need now.


You probably have extra code in there. However, you can keep both since they display the same thing but differently. I have both types like whtrice.

evocowboy
01-18-2009, 03:21 AM
I've been throwing that one alot lately according to pocket scanner. should try this method yer talking about when I get a much needed re-tune.

KevOVIII
01-19-2009, 02:35 AM
You can do it yourself if you have a Tactrix cable and laptop... or know someone who does. :) It's worth the trouble of not seeing the light stay on all the time.

oneillevo
01-24-2009, 01:54 PM
Jan. 23 2009

As promised the next time I get a P0300 I would try this out for Rom Id: 94170015

I had EcuFlash 1.30 and just downloaded the new one EcuFlash 1.40 and added the definitions. It was real simple. I cleared the code with Scan Tech and then uploaded the new edited rom.

So far so good.

Steiner
01-24-2009, 04:21 PM
+1

I did the exact same thing last weekend and haven't thrown a CEL since.

whtrice
01-24-2009, 05:08 PM
Glad to here you got things working! :icon_wink:


+1

I did the exact same thing last weekend and haven't thrown a CEL since.

Steiner
01-24-2009, 05:42 PM
Thanks for your help. I think the instructions on EvoM are a little assumptive for intermediate users but, in the process of troubleshooting and asking questions, I got it working. If anybody is looking for a moron's version of how to implement this fix shoot me a PM. I'm your man! :)

oneillevo
01-25-2009, 12:31 AM
Thanks for your help. I think the instructions on EvoM are a little assumptive for intermediate users but, in the process of troubleshooting and asking questions, I got it working. If anybody is looking for a moron's version of how to implement this fix shoot me a PM. I'm your man! :)

+1 I would have to agree. The EVOM post assumed that people knew how to edit the xml. Post up the Morons version so we wont get any people to continue to ask the same questions.

oneillevo
01-26-2009, 05:49 PM
Got bored and made a quick video!
O24x0yfKYZk&fmt=18

chrisw
01-26-2009, 05:52 PM
you have way too much time on your hands.

oneillevo
01-26-2009, 06:01 PM
you have way too much time on your hands.

:mswerd: That I do!

Steiner
01-26-2009, 06:16 PM
Got bored and made a quick video!
O24x0yfKYZk&fmt=18Very cool. More people than will ever admit will benefit from that video. If you haven't done so already you should post that on the EvoM p300 thread.

krispytapa
01-29-2009, 05:40 PM
I'm getting the p0300 every time I get on the freeway now. :( I tried to do this patch/fix but I can't read the ROM from my ECU. I tried the unlocker on 2 different notebooks w/ 2 different ECUflash's (1.41 and 1.29) and I have a new battery. My only guess is my tatrix(sp?) cable is bad. Can someone lend my their cable to see if my cable is the problem, please. I will limp my car to where ever you are. w/in reason. :D

This is what I keep getting from Ecuflash.

[00:48:01.503] sending init sequence 1 (0001)
[00:48:04.758] sending init sequence 1 (0003)
[00:48:08.022] sending init sequence 1 (FFFF)
[00:48:11.267] sending init sequence 1 (F0F0)
[00:48:14.011] no response to any known code

Thanks,
MIke

whtrice
01-29-2009, 05:53 PM
Bryan taught me this one...Try downloading you ROM with the engine idling.Or do you have a logging program you can run to see if your cable is transfering data. At idle you would see rpm, IAT's etc


I'm getting the p0300 every time I get on the freeway now. :( I tried to do this patch/fix but I can't read the ROM from my ECU. I tried the unlocker on 2 different notebooks w/ 2 different ECUflash's (1.41 and 1.29) and I have a new battery. My only guess is my tatrix(sp?) cable is bad. Can someone lend my their cable to see if my cable is the problem, please. I will limp my car to where ever you are. w/in reason. :D

This is what I keep getting from Ecuflash.

[00:48:01.503] sending init sequence 1 (0001)
[00:48:04.758] sending init sequence 1 (0003)
[00:48:08.022] sending init sequence 1 (FFFF)
[00:48:11.267] sending init sequence 1 (F0F0)
[00:48:14.011] no response to any known code

Thanks,
MIke

krispytapa
01-29-2009, 05:59 PM
whtrice. i'll try both.

thanks,
MIke

krispytapa
01-29-2009, 06:22 PM
downloading ROM while idling didn't work. mitsulogger is logging and working fine. any other thoughts?

MIke

whtrice
01-29-2009, 06:43 PM
So you did try the unlocker before starting up ecuflash?

krispytapa
01-29-2009, 07:16 PM
So you did try the unlocker before starting up ecuflash?

yes, on both 1.29 and 1.41. but i'll try again just in case.

Tripperfx3
01-29-2009, 07:23 PM
I was wondering will this work on an VIII and still pass emissions? I have something similar, but my car won't pass emissions. It says the ECU isn't ready.

whtrice
01-29-2009, 07:34 PM
The P0300 state should not affect readiness. There isn't a not ready state for the misfire test.



I was wondering will this work on an VIII and still pass emissions? I have something similar, but my car won't pass emissions. It says the ECU isn't ready.

oneillevo
01-29-2009, 11:13 PM
yes, on both 1.29 and 1.41. but i'll try again just in case.

Try Scan Tech: http://www.aktivematrix.com/forum/dload.php?action=file&file_id=27

While in idle see if it reads. If it doesnt then it may be a cable issue.


I'm getting the p0300 every time I get on the freeway now. :( I tried to do this patch/fix but I can't read the ROM from my ECU. I tried the unlocker on 2 different notebooks w/ 2 different ECUflash's (1.41 and 1.29) and I have a new battery. My only guess is my tatrix(sp?) cable is bad. Can someone lend my their cable to see if my cable is the problem, please. I will limp my car to where ever you are. w/in reason. :D

This is what I keep getting from Ecuflash.

[00:48:01.503] sending init sequence 1 (0001)
[00:48:04.758] sending init sequence 1 (0003)
[00:48:08.022] sending init sequence 1 (FFFF)
[00:48:11.267] sending init sequence 1 (F0F0)
[00:48:14.011] no response to any known code

Thanks,
MIke

From what I gather from Aktive Matrix is that there may be several reasons why its not reading.
-Locked ECU
-Bad Cable
-Bad Version of EcuFlash
-Combination of all of the above

Possible fixes
+ Use a battery booster (low voltage may make it difficult to flash)
+ Check the cable (test on a different EVO)
+ Try a different computer/laptop

Please refer to this: http://www.aktivematrix.com/forum/viewtopic.php?t=366&sid=494a2df12b48a1e8fdca8ae0e7bfb752

From your description it sounds like a bad cable.

Steiner
01-29-2009, 11:38 PM
Not to throw more fuel on the fire, but ever since I updated Ecuflash to version 1.40 my Scantech no longer connects. I tried everything and nothing seemed to work. The good news is I don't throw CEL's anymore so...

oneillevo
01-29-2009, 11:57 PM
LOL Good to hear. However, I never thought about that. Maybe I will take out the laptop to the car and try Scan Tech. It never occurred to me about having any affect after installing EcuFlash 1.40

Tripperfx3
01-30-2009, 01:42 AM
Sorry... Ignore my post. I'm sick and was thinking of something else lol.

Steiner
01-30-2009, 02:16 AM
LOL Good to hear. However, I never thought about that. Maybe I will take out the laptop to the car and try Scan Tech. It never occurred to me about having any affect after installing EcuFlash 1.40You know I could probably mess around with the drivers a little more but my concern in that once Scantech is working again then Ecuflash will take a dump on me. If I had to pick one of the two obviously the chose is easy.

warpspeed
02-02-2009, 06:00 PM
I was wondering if anyone here can let me borrow their tactrix cable or better yet, if anyone around the Fairfield area has done this can do it for me. Like I said I can probably do it with a borrowed cable or if someone nice here can do it for me.

thanks in advance.

earlyapex aka jack ass
02-03-2009, 11:18 AM
Howdy all,

As of this week I have decided to move all my efforts into another local Evo community.

It was a good stretch here and I was glad to be part of the community as a whole and not just "another vendor"

Pretty much all of this community I am a part of moved on, and rightfully so for many reasons, so I have chosen to follow as well as at the end of the day, I own a Evo and I am a member of that said community.

It's a huge bummer it has come to this, but people have dropped the ball and this is the outcome.

All tech, power, data and all other findings by me moving forward will no longer be posted on this website.

You all know where to find me.

:band: on.