Okay so my 99 SI has a full CTR swap with a P72 ECU running on a PCT basemap. I've been having firing issues for over a month now. It will throw a CEL and attempt to start, but not turn over. If it does turn over it will run for about 30 seconds with no throttle response and eventually die. Since I bought the car I have not been able to connect to it with different types of code readers. I just put a new dizzy in it, I have been told everything to check from knock sensors to buying a completely different ECU. Please help. I'm really tired of driving my Dad's '93 Geo to work and school.

 

2 things got to see if there using a obd1 or a obd2 harness? Might have the wrong dizzy on. There can be many things wrong with it,but 1st things 1st check ur harnnes.

 

I had the same issue u had when i got my ek with the swap all kinds of wrong stuff.

 

There's a sticky on how to pull codes. Read that, and post the results.

 

It's running an OBD2, with the stock SI harness. The dizzy is matched with a Honda Type R. To retrieve the codes could I use the USB connection in the ECU?

 

Read
The
Stickies

 

Yes or use the paper clip(oldschool)and see how many times the engine light flashes and goggle it. Your obd port will not work,is the car chipped and who chipped it. Is the dizzy obd1 or Obd2. The reason i ask they had the wrong one on mine. Second is there any sensors off and due u have fuel and spark. If u were around the IE i can figure it out it took me like 2 days full days to get mine started plus now im having issues again with my cluster they did a shitty install on mine so ive had to rip apart the car 3times to fix things. Almost done with it gotta fix a couple more issues.

 

Okay. So the car is chipped on a PCT base map, I'm honestly not sure who chipped it, the guy that I bought it from had it built in Bakersfield, and yeah I've got a buddy who was gonna try the paper clip trick tomorrow. About the dizzy, when I replaced it I bought it for a Honda type r, so I'm assuming its the right one. I'm in the IE, (Yucaipa), if you could stop by and help that would be really cool. I have spark for sure, fuel may be the problem.

 

You can pull codes with a paperclip in less than 1 minute. I taught my wife how to do it. Why do you need to wait for your "buddy"?

 

I never learned how to do it, and I don't want to end up doing the wrong thing.

 

You can't do something wrong. Just read the FAQ about it, and follow it. It's dead simple.

 

Cool i work in riverside if u dont figure it out,ill come by this week after work and see what the issue is,bu 1st pull the codes to see it can be something simple or ur fuel pump out or bad injectors it can be anything.

 

Take your car to a shop. It is apparent you didn't even look at the link in the stickies otherwise you would have seen how simple it was to do. If that is beyond you then you are best served taking it to someone that can properly diagnose your issue.

To me it sounds like your timing or your basemap it messed up.

 

Thanks man. So I tried the paperclip trick after looking at the threads. I followed the directions and the CEL never started blinking just remained constant when the paperclip was in. I took it out and put it back in the two pin connector but nothing changed.