Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncements
Discussion Groups
By Brand
BMWChevroletDodgeFordGMHondaLexusMercedes-BenzNissanPeugeotToyotaVolkswagenOther Brands
By Topic
4x4 CarsRVsDrivingMaintenance & RepairCar AudioCollectible Cars
Country Specific
Australian ForumsUK Forums
ArticlesAuto InsuranceBuyingCars & TechnologyMaintenanceMiscellaneousSafety
DMV Resources
Related Topics
MotorcyclesBoatsMore Topics ...

Car Forum / Ford / Ford Falcon / February 2005

Tip: Looking for answers? Try searching our database.

BA starting problem - immobiliser?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
kkerrison@ozemail.com.au - 26 Jan 2005 08:01 GMT
Three times my RCV has failed to start - first time it came good after
15 minutes. Second time Not until NRMA came and fiddled with the fuses.
Third time I removed and replaced fuses 20 and 24 and fiddled with a
few others and it came good.

But it seems unlikely that it is the fusese - more likely some sort of
dry joint nearby.

Has anyone any ideas?

Sometimes the word CODE appears on the screen during the fault and the
remote locking is inoperative
col - 26 Jan 2005 11:58 GMT
i have had a similar problem in the smart lock immobiliser of my EB2 for
some time it indicates a fault code from the ignition code recognition, from
10 seconds to 30 minutes delay mostly a few minutes. Tried many things
including fuses ect but seems a bad joint in the smart lock unit, it is
mainly on sunny days when car left in carpark and heats up but some times
when cool. The most successful fix about 70% is to kick the crap out of the
fwd centre counsole drivers side where the module is, seems to work but will
have to pull unit and fix or replace soon as is a pain in the arse. you
would have to relate this info to the BA via manual. although prob could be
at the door/boot units, ignition locks as immobliser gets signal from them i
believe

col

> Three times my RCV has failed to start - first time it came good after
> 15 minutes. Second time Not until NRMA came and fiddled with the fuses.
[quoted text clipped - 8 lines]
> Sometimes the word CODE appears on the screen during the fault and the
> remote locking is inoperative
kkerrison@ozemail.com.au - 27 Jan 2005 06:47 GMT
'The most successful fix about 70% is to kick the crap out of the
fwd centre counsole drivers side where the module is'
I know how you feel!  Thanks.
Noddy - 06 Feb 2005 21:58 GMT
> Has anyone any ideas?

There was a problem with the BA's engine management system coding that
forced it to shut down if it thought things weren't right (particulalry if
it was hot), and there was/is a dealer flashrom upgrade that apparently
addresses the problem.

It may be worth contacting a dealer and asking to have it done if it hasn't
been already.

--
Regards,
Noddy.
Kieron - 07 Feb 2005 00:44 GMT
>> Has anyone any ideas?
>
[quoted text clipped - 5 lines]
>It may be worth contacting a dealer and asking to have it done if it hasn't
>been already.

IIRC, that was for the turbo only.
kkerrison@ozemail.com.au - 07 Feb 2005 08:34 GMT
Damn!  I'll mention it to the dealer anyway.
kkerrison@ozemail.com.au - 09 Feb 2005 08:39 GMT
I faxed the story about this problem to the dealer's service manager.
He replied that they had had several similar cases and the cause was a
connector 'not fully home on body electrics module'.  We will follow up
this fix and report the result.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.