Omega Owners Forum
Omega Help Area => Omega General Help => Topic started by: ianu on 21 April 2013, 10:39:38
-
Hi all,
Any help appreciated. Obviously last time car was used all appeared OK. Been parked for a day or so. This morning - engine spins but will not fire.
The only code present is the Cat code (0430) - I'm assuming that that wil not prevent it starting as I've had it a while anyway.
If there is a crank sensor problem, would you always expect the code to be present ? This is a fairly new sensor as well (GM part).
It's not battery as far as I can tell - it turns over at the same rate with or without a jump pack connected.
The crankshaft is turning along with everything else on that visible belt - my worry is that it seems to be turning rather 'easily' - almost as if there is no compression.
Is there a quick inspection I can do to check the cambelt is where I left it when I parked it up last time I used it ? or would it be pretty apparent if it'd gone walkies ??
Is there anything else that would give these symptoms ?
Cheers
Ian. :-[
-
OK - quick update :-\
Car finally started - but very reluctantly after a lengthy cranking with a booster pack connected to keep the battery company.
Initially misfiring - then settled down OK. Took it for a quick run and all seems OK. But I now have 0300 code - indicating a random multiple misfire. I'm sure it was 0340 when I first read it ?
Will this clear if it disappears as it seems to be Ok now. Should I be checking coil packs again ?
Cheers
Ian.
-
Fuel related? Fuel filter serviced?
Sounds crank sensor related otherwise. Often no code stored.
Difficult one :-\
-
Yep agreed most likely dodgy crank sensor ;)
-
Any chance it could have flooded? Has it been started for a few seconds just to shift it around the driveway? I find they can get upset after a couple of quick runs due to the rich mixture.
Failing that, crank sensor, I'd say. They don't always generate a code IME.
-
Any chance it could have flooded? Has it been started for a few seconds just to shift it around the driveway? I find they can get upset after a couple of quick runs due to the rich mixture.
Failing that, crank sensor, I'd say. They don't always generate a code IME.
I agree,seen that many times where someone has started and moved vehicle a few feet and then found next time out it won't go,OP also mentioned feeling that there was a lack of compression which ties in with that :y
-
Thanks all,
Yes I'm suspicious of the c/s even though it's less than 6 months old ?? Still no code other than 'random misfire detected' - but to make matters worse it seems to be OK now. :-[ :-[ so I have a possible intermittent fault.
I know what you mean about possibly flooding it - it wasn't me but SWMBO that originally tried to start it - so I don't have the exact millisecond by millisecond account of what precisely happened as the key was turned for the first time :(
I've had that happen to me when it hasn't caught as expected and I've released the key before it fired, only to have to coax it a couple of times to get it to come out to play again ::)
SO nothing conclusive yet - but it seems to have decied to play ball for now ???
Cheers
Ian.
-
Any chance it could have flooded? Has it been started for a few seconds just to shift it around the driveway? I find they can get upset after a couple of quick runs due to the rich mixture.
Failing that, crank sensor, I'd say. They don't always generate a code IME.
I agree,seen that many times where someone has started and moved vehicle a few feet and then found next time out it won't go,OP also mentioned feeling that there was a lack of compression which ties in with that :y
Agreed & apparently a very common call out at Christmas when a car gets moved to let Auntie's car of the drive & left again for a few days. :y