6 bolt problems

97_3clipse · #1 04-13-2005, 10:30 PM

as most of you might know i recently had a 6 botl motor installed by EclipseRST (jake)....
everything was running fine ,till tonight....
as i was driving home from work the car was running excelent, the about half way home (20min drive) i notice a CEL....i pay no attention because the car is running fine, then about 30 sec later i accelerate to make a light(3000rpm) the car starts shaking and accelerates for crap....almost as if im not firing on all cylinders...it just keeps getting worse as i get home , pulled over acouple times to turn the car off. when the car is restarted it seems to run better, but after 30 seconds of driving the vibrations slowly come back till the car is riding rough as it was before....

im going to pull the Check engin light with a scan tool tommorow , but bose anyone have any sugestions, you 2 cents will be helpful...

-Jake-

TsiTalon9587 · #2 04-13-2005, 10:42 PM

I am willing to bet that you got a the random misfire CEL. This will cause your car to go into limp mode. Thus, doing what you explained. Your 1g cas is at fault here, and the only way to fix it, at least the right way, is through DSMlink. There is a baro wire mod that you can do which will yeild the same results, but it's not reccomended. That info can be found on Magnus's website. You don't happen to have DSMlink, do you?

97_3clipse · #3 04-13-2005, 10:45 PM

its not a random misfire , its constantly shaking, i have had random misfires before, they make a sound ...but this dosent make a sound and shakes worse than random misfires

gthompson97 · #4 04-13-2005, 10:55 PM

you might get 1 random misfire which will cause it to go into limp mode which probaby causes all the vibrations. that's why it runs good for awhile and then all of a sudden goes into limp mode cause of a misfire and then vibrates.

kjewer1 · #5 04-14-2005, 02:22 AM

I dont know why you would say its not a random misfire, when you dont yet know what it is. Why should we bother replying again?

Random misfire will seriously ruin the way the car feels. No power at all, very rough running, etc. The only way I could reset it was to power cycle the ECU AND clear the RM DTC through the pocket logger. Always fun trying to do this at 75 on the highway. It would always come back after about 2 minutes. Too much steady state driving will bring it on sooner.

DSMlink is the best way to get rid of it. It simply removes that check for the random misfire from the ECUs programming. PRoblem solved.

The baro wire mod works, but its not the cleanest solution. BAsically you add resistance to the baro wire going to the ECU. The ECU thinks you are something over 5 or 6 thousand feet altitude, where it would expect to see some misfiring from the thin air perhaps, and stops looking for random misfires. NAturally changing the baro signal also changes the ECU perception of the airflow into the motor. You have to add back in about 30% airflow with an AFC or similar device. Its a hack solution, but I ran it for a year or two alright. When I got up to the 50 trim I Decided it was time to stop lying to the ECU in so many different ways, and that was the deciding factor in finally buying DSMlink. Best purchase I ever made, for so many reasons...

97_3clipse · #6 04-14-2005, 07:08 AM

ill have o get DSMlink, but i heard a 97 ECU solves the misfireing problem too....?

97_3clipse · #7 04-14-2005, 10:13 PM

also looking at my CAS....a peice of the mounting bracket is broke...

bighauns · #8 04-15-2005, 11:57 AM

That happened to me after my 6 bolt swap...it was a couple wires in the ignition coil crossing or one not grounding properly or something like that. seriously, that is exactly what happened, every single thing you said.

kjewer1 · #9 04-15-2005, 11:59 AM

Quote:

Originally Posted by 97_3clipse

ill have o get DSMlink, but i heard a 97 ECU solves the misfireing problem too....?

I wish. Being the cheap bastard that I am I would probably have tried a non-eprom 97 ecu

There are only two poeple that I know of that didnt get the RM CEL issue, and one of them at least had a 97 ecu. But its certainly not common to not get the problem.

CBURKE · #10 04-15-2005, 03:47 PM

Ok, well haveing this prob before and jake is the one that told me what to do. You will need to run a ground wire from a plug that is by the coil (don't know what it's called someone help here) to the fire wall. Then disconect you batt. This is someting that is known to happen with the 6 bolt swap. Something about the plug not getting the correct ground. I did this and have not had a prob sence.

You will know if you car does this. You can drive but then it starts to shake. If you let the RPM drop it will go away for a sec then come back. Does this sound like it?

97_3clipse · #11 04-16-2005, 07:53 PM

well today i pulled the codes and here they are:

DTC (codes)

P0300
Random/Multiple
Cylinder
Misfire Detected

P1400
Manfacturer Contrl.
Auxiliary emissions
Controls

DTC Pending(codes)

No Faults Detected.

thats exactually how it read...

TsiTalon9587 · #12 04-16-2005, 08:30 PM

Quote:

Originally Posted by 97_3clipse

well today i pulled the codes and here they are:

DTC (codes)

P0300
Random/Multiple
Cylinder
Misfire Detected

Hmm

Quote:

Originally Posted by 97_3clipse

P1400
Manfacturer Contrl.
Auxiliary emissions
Controls

Did Jake remove some emmisions lines?

EclipseRST · #13 04-16-2005, 09:05 PM

No I didnt... The reason that came up is because of the misfire. When a misfire happens on a 2g the 1st and 4th plug wires (coil on the left) do not get spark. There for fuel is going thru those cylinders unburned and tripping the front and rear O2 sensor saying hey something is up. So they start throwing codes. Since there is a lot of fuel passing the cat the rear O2 sensor is seeing it as if there wasnt a cat even in the exhaust system.

TsiTalon9587 · #14 04-17-2005, 11:46 AM

Quote:

Originally Posted by EclipseRST

No I didnt... The reason that came up is because of the misfire. When a misfire happens on a 2g the 1st and 4th plug wires (coil on the left) do not get spark. There for fuel is going thru those cylinders unburned and tripping the front and rear O2 sensor saying hey something is up. So they start throwing codes. Since there is a lot of fuel passing the cat the rear O2 sensor is seeing it as if there wasnt a cat even in the exhaust system.

Good call on that. As soon as I saw you say that the 2 cylinders weren't getting spark, it clicked and I knew exactly what you were going to say next. Thank you for clearing that up though.

POST REPLY TO THIS THREAD