MG-Rover.org Forums banner

Rover streetwise imobilise stuck on

1 reading
1.7K views 19 replies 4 participants last post by  Handyman2018  
#1 · (Edited)
Hi all. I have a post face-lift Rover Streetwise 103SE 1.4 16v 2004 14K4F engine, 3 button Pektron fob. The immobiliser has suddenly stuck on. When I turn on ignition it no longer beeps warning immobiliser is on & the fob won't turn it off. I have tested the fob signal by using a cloning fob & it's good. I removed the bcu & there is no water damage & I checked the 5 relays in situ & they all registered correct resistance. When I lock the car with the key with a door still open the horn no longer sounds either. The central locking packed up on the drivers door a while ago but works on the key, locking & unlocking, although i think this may be the wiring that goes through body to door as it was intermittent to start with. The last time i used the car it was bump started, although the engine was turned off for 5 mins, then immobiliser turned off again and engine started ok, so I'm hoping jump starting it hasn't messed up the coding? I am thinking of getting an eka code but don't know if this will work? Last option is new ecu, bcu & fob (all matching) unless anyone has any other advice? Thanks
 
#11 ·
I take it is the obd to usb lead? Will I need software with it or just this download? I have had a good read of that link you sent and while there is a wizard available with it to delete the immobiliser function it's the "writing the firmware and map back to the ecu in the normal way" part that I do not understand, way too technical for me.
 
#8 ·
Oh ok. I have pc but no laptop. The cars parked right by my window tho can get pc by the car. I might try it, I can make it any worse than it is at the moment, unless the ekc actually works? I haven't bought the ekc yet as unsure if it will even work?
 
#14 ·
Hello. Thanks for your reply. The battery has been deteriorating lately but wasn't totally flat, it turned the engine a few times but didn't start hence bumping it. The horn is working and I did check the 5 relays on the bcu in situ & they all gave correct resistance reading. When I press the immobiliser the immobiliser light on the dash does flicker like its receiving but not a matching code so you may well be right in saying it is mismatched. I have disconnected the battery & left it off a couple of times, maybe I'll try it a few more times. As for the loom to the tailgate, I have had issues, firstly the boot unlock went, then about 2 weeks ago the rear wiper packed up, the loom is all intact but there must be broken wires, havent had chance to look at it yet. I have emailed Paul at Technozen but no reply yet. I may just get the ekc, don't really like the idea of messing around with the emobiliser coding in the ecu, may do more harm than good, and, like you say, it's not good as far as insurance goes, or having the car stolen!!!
 
#15 ·
You’re acting as if any thief couldn’t literally turn up with the software and do the exact same thing … I don’t think mg/rovers are too far up car thieves hit lists …. I don’t think trying to berate someone for posting useful information is too good like you are the high and mighty you’ve posted a load of crap and not sorted the OP’s problem my solution will literally solve the issue the op is having , everyone knows the immobilisers are a load of crap on these cars hence why someone built software to disable them ….
 
#16 · (Edited)
I am sorry if you can't cope with someone disagreeing with your opinion, but my opinion remains that an immobiliser bypass is neither the best, not the most appropriate solution.

Whilst most MG and Rover cars are now of an age where 'taking and driving away' are perhaps not an issue at present, it is possible that that may change over the next few years as they become older and rarer, and some models in particular may begin to command a premium (either in their own right, or for parts).

In addition, the recent value of scrap metal has seen a number of people have cars swiped by passing 'itinerant metal dealers' and immediately scrapped and crushed - someone had a nearly mint condition Rover 200 BRM taken from his driveway a couple of years ago, only for the police to trace it (via a certificate of destruction) to a fairly local scrapyard where it was found already cubed. Someone else had a similar experience with two SORNed Monogram painted ZSs a few months later, so they are certainly not immune from the attention of thieves.

I would like to know in what way I have posted "a load of crap" ?. After having had experience of the R3 200 series for 27 years, and the Pektron equipped cars for nearly 20 years, I am aware (from the problems handyman has posted) that the immobiliser is not the only issue here, and some of what has been posted (no beeping from the SCU immobiliser warning, and no siren sounding when locking with a door open) indicates at least the possibility of an issue with the Pektron SCU, or a wiring issue that may cause faults within the SCU. It seems therefore, wise to rectify or discount such possibilities to avoid further issues developing. If there are faults within the SCU or the wider wiring looms that will cause SCU problems to develop, performing an immobiliser bypass is absolutely not going to sort any of those problems at all. It seems to me that the problem with the immobiliser is most likely SCU related, and sorting out the SCU would in turn sort the immobiliser problem without resorting to the immobiliser disable (which I would regard as a 'bodge' at best).

In fact, the immobiliser function in the engine ECU (and indeed, the MEMS ecus in general) very rarely suffer any faults - immobiliser function problems are almost always traceable back to a problem with the remote fob (frequently a flat fob battery), the exciter coil around the ignition barrel, or with the alarm/immobiliser disarm function in the security control unit. Very few people on this forum over the years have actually needed to disable the immobiliser function, and those who have done so have mostly disabled it for personal convenience or for specialist applications such as motorsport. The earlier Lucas 5as is relatively trouble free, but the Pektron SCU quite commonly gives problems (see Pektron SCU), particularly where the car battery has been allowed to become mainly or fully discharged. SCU 'memory loss' or corruption is well known to those of us who have frequented these forums for the last 20 years, and various people have tried a variety of (what might seem odd) ways to rectify them, but they do often seem to work.
 
#17 ·
How is turning the immobiliser off a botch job ? It’s a simple way of not having to spend hours tracing a problem with an outdated system that isn’t worth a bean, I could literally turn up to anybody’s mems rover with my laptop and an obd connector and turn it off regardless so it’s not really the best in security is it and you have said yourself how they are stolen for scrap anyway regardless of the over twenty year old security system , it’s each to there own and if the OP doesn’t want to mess around and throw the money cannon at it or read your copy paste rubbish about outdated tech then that’s his/her choice they don’t need people like you berating them like you know the ins and outs of the Tin can and string equivalent to car security
 
#19 ·
Hi Andrew.
Sorry I didn't get back to you via email. I have now received the EKA code, free of charge, and got the car started!!
As Paul at Technozen has not replied, despite my sending him several emails, I have it booked in at a place in Darlaston to provide and code match me a new fob and reprogram the bcu (if it's been corrupted) for less than £100 so all good now!!
Thanks for your help.
 
#18 ·
You clearly have very little understanding of the Pektron SCU and the issues that occur with it. It is pretty clear to me that there are issues with Pektron unit in this case, and I strongly believe that it is the Pektron unit that is behind the immobiliser problem. The Pektron unit is not difficult to diagnose and repair/reset for someone with the kind of knowledge that Paul Brown does (technozen -already suggested to the OP by Roverlike) and that I feel confident will solve the immobiliser issue. Disabling the immobiliser function absolutely will not solve any problem with the SCU. The Pektron SCU controls all the main electrical functions either directly or indirectly, so failure to solve SCU faults has potential for further faults developing that may render any number of electrical functions inoperative.

As far as the possibility of the immobilser code having been corrupted/forgotten, it is a very easy job with suitable diagnostic equipment to rematch the SCU with the MEMS unit, and yes, it does make the idea of disabling the immobiliser look like a back-street garage bodge job.

If the car is subsequently involved in a crash where there is a death or serious injury, it is likely to be gone over with a fine toothcomb and some insurance companies will use something such as disabling the immobiliser without informing them as a convenient excuse to void the policy and refuse to pay anything out - potentially leaving the now uninsured driver with a large injury compensation bill and no way to pay it, as well as being prosecuted for driving with invalid insurance. And before you start, yes that sort of thing has happened.