IdMtnGirl Posted June 23, 2017 Share Posted June 23, 2017 Hello all, we recently went through our 95 Subaru legacy 2.2L, redid the head gaskets and replaced several other seals, got it all put back together and now we have no spark. we checked the coil pack, Crank sensor, Ignitor, Fuses, Cam sensor, Timing (4 times..), and still nothing. but we dont have a code reader and would like to check the ECM, before going all the way through the wiring. any help would be greatly appreciated, we are at our wits end here. Thanks in advance! Link to comment Share on other sites More sharing options...
Mike104 Posted June 23, 2017 Share Posted June 23, 2017 Timing marks aligned? Link to comment Share on other sites More sharing options...
IdMtnGirl Posted June 23, 2017 Author Share Posted June 23, 2017 Yes, we checked four times and its all where it's supposed to be. Link to comment Share on other sites More sharing options...
GeneralDisorder Posted June 24, 2017 Share Posted June 24, 2017 An inexpensive code reader is in order. Spend $75 or so and get one that does live data, etc. GD 1 Link to comment Share on other sites More sharing options...
Subaru Scott Posted June 24, 2017 Share Posted June 24, 2017 Many times on cars of that age, the latching tab on the coil pack connector will break. I have a ziptie holding mine together. 1 Link to comment Share on other sites More sharing options...
IdMtnGirl Posted June 24, 2017 Author Share Posted June 24, 2017 Well, many thanks to all of you! We finally discovered what we did wrong... This is going to sound funny I hope, as I am still laughing at myself for it. We installed the Cam pullys wrong. The right one is on Drivers side.... I can chalk it up to a loooong day... we read on this site that the number 1 thing was that we did something in the wrong order or put something in the wrong spot.... we of course only realized our mistake after going through ALL the wiring, but hey. I really appreciate this site and all of your help. we will be swapping the Pully's to the right position tomorrow morning. Thanks again! Link to comment Share on other sites More sharing options...
Mike104 Posted June 24, 2017 Share Posted June 24, 2017 Thanks for letting us know what the problem was. And hey we have all made mistakes! 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now