Okay everyone before I get into it I have been searching for answers for weeks pouring over old threads trying to find an answer and I have come close but still haven't found what I'm looking for. I'm new to EvoM (3 months) but not to DSM's.

I bought an 06 Evo and it ran for 2 and a half days and then it took a dump on me. Long story short I forged the rods and pistons and studded it. From what I was told from the previous owner (which I trust as far as i can throw him) it has a rebuilt head with Kelford 272's which seem to check out. I tracked down the shop who supposedly tuned it last and they said when it came in it had a kill tune on it with loads of boost so he said he turned it down and made it "safer".

Now that I have it all back together it is missing pretty bad. First I had a P0201 code which was Injector #1 circuit too low. So I went to switch #1 with #4 and when I did I found that I somehow very easily pulled one of the wires out of the pigtail to injector #1. So after fixing it and still switching injectors 1 and 4 around I never got the code again...
Immediately after it is still missing the same as it was. So I used Evoscan to clear the code and let it cycle again to find that I had a P0302 which is cylinder #2 misfire. I cleared the code to see if the injector code would come back and then I got a P0303 code for cylinder #3 misfire... then after clearing the code again I got a P0300 multiple cylinder misfire FML!!!

Since then I have gone over many threads saying to check plug gap and I did they were a little close about 22 so i gapped them to 25. Then I Replaced both coils and wires because they looked original and the car has 150k on it... and still the same miss. After clearing the codes a few more times I came up with another cylinder 2 miss independently from yet another P0300 multiple cylinder miss. My timing seems pretty far out at anywhere from 10 to 20 while all this is going on. Another thread pointed me to the infamous P0300 code diable thread so I have thought about that but I haven't even driven it more than 1/4 mile so I do believe it is a real miss.

To top all of this off I am having a heck of a time getting ECUflash to even connect to the car. I have been in contact with Tactrix support and they have been trying to help me figure it out... but at this point ill take all the help I can get. I know there are threads out there with info on this but I honestly cant seem to find the unicorn that I've been looking for. Can someone PLEASE help or at least steer me in the right direction?? I have a few problems and help with any of them would be much appreciated.

Also this is the last message I got while trying to connect about an hour ago...[21:53:39.783] Logging to file C:/Users/Chris/AppData/Roaming/OpenECU/EcuFlash/logs/ecuflash_log_20220131t215339.txt

[21:53:39.783] EcuFlash Version 1.44.4799

[21:53:39.783] OS Version Windows 10

[21:53:39.783] Kernel Type winnt

[21:53:39.783] Kernel Version 10.0.19043

[21:53:39.783] CPU x86_64

[21:53:39.783] Product Name Windows 10

[21:53:39.783] Product Type windows

[21:53:39.783] Product Version 10

[21:53:39.783] Qt Version 5.6.0

[21:53:39.783] Qwt Version 6.1.2

[21:53:39.783] QwtPlot3D Version 0.2.6

[21:53:39.783] Boost Version 1.60

[21:53:39.783] FTDI Library Version 3.02.11

[21:53:39.783] Openport J2534 Library Version 1.02.4798

[21:53:39.799] 67 memory models read.

[21:53:39.799] scanning for metadata models in D:/TUNING/OpenECU/EcuFlash/rommetadata

[21:53:39.877] 745 ROM metadata models scanned.

[21:53:39.877] checksum module "subarudbw" loaded.

[21:53:39.877] checksum module "subarudiesel" loaded.

[21:53:39.877] checksum module "subaruhitachi" loaded.

[21:53:39.877] checksum module "mitsucan" loaded.

[21:53:39.877] checksum module "mitsuh8" loaded.

[21:53:39.877] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.

[21:53:39.877] patch module "Mitsu CAN RAM Parameter Logging" loaded.

[21:53:39.877] using metadata XML ID read_evo9 from file D:/TUNING/OpenECU/EcuFlash/rommetadata/read templates/read_evo9.xml

[21:53:39.940] flashing tool "wrx02" loaded.

[21:53:39.940] flashing tool "wrx04" loaded.

[21:53:39.940] flashing tool "sti04" loaded.

[21:53:39.940] flashing tool "sti05" loaded.

[21:53:39.940] flashing tool "mitsucan" loaded.

[21:53:39.940] flashing tool "mitsukernel" loaded.

[21:53:39.940] flashing tool "mitsukernelocp" loaded.

[21:53:39.940] flashing tool "mitsubootloader" loaded.

[21:53:39.940] flashing tool "shbootmode" loaded.

[21:53:39.940] flashing tool "shaudmode" loaded.

[21:53:39.940] flashing tool "subarucan" loaded.

[21:53:39.940] flashing tool "subarucand" loaded.

[21:53:39.940] flashing tool "subarubrz" loaded.

[21:53:39.940] flashing tool "subaruhitachi" loaded.

[21:53:39.955] interface open

[21:53:39.955] FTDI Driver Version 2.12.12

[21:53:39.955] characteristics set to 0,8,1

[21:53:39.987] Using interface OpenPort 1.3 Universal TX2VEFFXa055f42dd3f3378e693ee8a8e8736be9ac5e4ba6

[21:53:39.987] interface close

[21:53:40.050] interface open

[21:53:40.050] FTDI Driver Version 2.12.12

[21:53:40.050] characteristics set to 0,8,1

[21:53:40.065] Using interface OpenPort 1.3 Universal TX2VEFFXa055f42dd3f3378e693ee8a8e8736be9ac5e4ba6

[21:53:40.065] interface close

[21:53:40.128] interface open

[21:53:40.128] FTDI Driver Version 2.12.12

[21:53:40.128] characteristics set to 0,8,1

[21:53:40.158] Using interface OpenPort 1.3 Universal TX2VEFFXa055f42dd3f3378e693ee8a8e8736be9ac5e4ba6

[21:53:40.158] interface close

[21:53:40.221] interface open

[21:53:40.221] FTDI Driver Version 2.12.12

[21:53:40.221] characteristics set to 0,8,1

[21:53:40.236] Using interface OpenPort 1.3 Universal TX2VEFFXa055f42dd3f3378e693ee8a8e8736be9ac5e4ba6

[21:53:40.236] interface close

[21:53:40.315] interface open

[21:53:40.315] FTDI Driver Version 2.12.12

[21:53:40.315] characteristics set to 0,8,1

[21:53:40.346] Using interface OpenPort 1.3 Universal TX2VEFFXa055f42dd3f3378e693ee8a8e8736be9ac5e4ba6

[21:53:40.346] interface close

[21:53:40.409] interface open

[21:53:40.409] FTDI Driver Version 2.12.12

[21:53:40.409] characteristics set to 0,8,1

[21:53:40.424] Using interface OpenPort 1.3 Universal TX2VEFFXa055f42dd3f3378e693ee8a8e8736be9ac5e4ba6

[21:53:40.424] interface close

 

Some tuners lock the ECU after they tune it. That might be happening. If so there used to be a tool called "ECU unlocker". Could brick the ECU but worked with my Evo 9. I used it to unlock and duplicate a tune for my spare ECU.

 

But wouldn't tactrix support have told me that it was bricked?? Or would you be able to tell by the code I posted?

 

What do you mean "brick" the ECU?

 

Just to give ya a quick response to this:

@b00st junkie A bricked ECU has been corrupted and becomes un-readable. There are ways to un-brick them in some cases

 

I was afraid that's what it meant but didn't want to believe it. So you're saying I can brick it if I'm not careful.. or it may already be bricked from the previous tuner?

 

based on your log, your tactrix isn't even attempting to connect to the car. Your problem is more likely I.T. related and nothing to do with the car. If it starts, throws codes, and lets you clear them, your ECU is most likely not bricked.

You need to get a timing light on the motor and verify that the timing the ECU is showing matches what you see with the timing light. Being a fresh build, you might want to just double check that the cam angle sensor isn't installed 180 degrees off.

 

I will check it with a light. But I never removed the CAS from the first time so it shouldn't have changed.

 

A Bricked ECU no longer functions, ie as useful as a brick. Since your car runs ECU at this point is not a brick.
I would expect a locked ECU to not be recognized by ECU Flash nor readable, or programable.
This is why they would lock it.
I always put a battery charger on my Evo when programing. Low battery will not help and could cause problems.
Have you connected the white plastic connector? On mine I have two plugs black and white. Main one is black but I think there is a secondary connector with only a few wires. Both need to be connected with engine off and key in run position.

You could also try running the application in compatibility mode. Windows 10 did not exist when ECUflash was written. I think the last time I used it I was on Windows XP.

 

I have a brand new battery and it seems to be charging fine. I have connected the white connector as well as the OBD2 connector. My white connector only came with 1 wire in it (not sure if thats how its supposed to be). How do I switch it to compatability mode? Tactrix support said that my software was up to date and shouldn't cause any issues...

 

Put a battery charger on it while reading. 9's are picky about voltage. You've selected evo 9 in the drop down menu before trying to read? Have you tried evoscan?

 

Charger voltage is higher than battery voltage even when the battery is new. Otherwise the battery would not charge. So if you have a battery tender or something like that might help. Don't put a huge amp booster charge on it. Only 1-5amp slow or trickle charge.

Sounds like you have the right connectors, I don't remember how many wires are on mine. If you have only one and only one pin in the connector likely that is right.

How to switch it to compatibility mode in windows 10. Right click the application icon and read the drop down list. One of the options is to run in compatibility mode. This is a windows setting not Tactrix setting. If they say you don't need to do that, I would believe them. They know more than I do. But if you can't get it to work, might be worth a try.

 

Hey read through this and decided to chyme in, you said the head was refreshed with the 272 cams. Make sure the cam position sensors are not switched. The intake and exhaust cam sensors are different and have different part numbers. They look identical and an unfamiliar tech could switch them not knowing. Also make sure the exhaust cam position trigger wheel is not installed 180* off. The way you can tell this easily is pull #1 plug, set TDC make sure its on the compression stroke, hence pull the plug, then pull the exhaust cam position sensor out of the hole. Look inside, you should be able to see through to the back side of the trigger wheel. If the hole is immediately blocked by the trigger wheel then it is installed 180* the wrong way. This is another mistake that an inexperienced tech can make. Just some simple things to check. Also make sure the coils and wires are in the correct holes and wired correctly. Post up if you get it figured out. Best of luck.

 

First off thanks to all for the responses and the help. I tried to switch it to compatability mode and it didn't do anything.
So Tactrix support said:
"I don't know that I see any signs coming back from the ECU. An easy check would be to try with the Openport connected to your laptop, but unplugged at the OBD2 port. If the log result the same, then I would next scrutinize the connection of the OBD2 socket. If it's worn out a bit and not making good contact, an OBD2 extension cable sometimes helps. They tend to have oversized pins which take up some slack. The thing to check after that is to make sure you're getting an ~18 volt signal on the wire that is going to the car's 12 pin diagnostic port. The moment you initiate a read or write, there is a short burst of voltage putting the ECU in programming mode. With a decent meter you can verify you're getting that.
Also, I doubt you need an older version. We are in frequent contact with EvoScan around this hardware and if there was an issue preventing his hardware from working with the software, he would for sure be bugging us daily to fix it. There is no issue with our current software."

So today I was able to put a pin in the back of the signal wire on the wiring harness of my OBD2 port and used a meter to check the voltage. It never hit 18v but it did spike to at least 14v (it was a decent meter so hopefully it registered correctly fast enough). After about 3 attempts it dropped down to 11v so my testing was done. I am going to email them again and give them my results. It seems like I may need to find someone with a trickle charger and use it. I will continue to post results. Any insight is still appreciated.

 

So I had to buy another timing light yesterday because a friend of mine has mine and he is 700 miles south. From what I can see (because its hard to get a decent angle on it) the timing is doing what my datalog's say its doing. Also when I said the cylinder head was new I meant that it had been rebuilt before I bought the car and it had been running for some time (how long I don't know) but the car drove fine for me for the few days I had it before it went down. I never did anything to the CAS on either side. With all my testing I am starting to think that the false knock P0300 may be my problem although from what I see people are saying its more prominent in Evo8's and not "normally" in Evo 9's. I just have to fix the communication between my computer and the ECU.