Prev: Petrol Starvation
Next: cabin/pollen filters
From: DTS on 17 Jun 2010 04:07 Hello Thanks for any advice in advance Car is a Nissan Micra 1.0 litre 1999 on an S reg used as a cheap runabout. I got in the car last Friday and tried to start the car and the car started for 2 seconds then stopped with the check engine light flashing on the dash which after digging round the internet discovered it was a NATS problem. After repeated retries I gave up and tried the other key with the same problem. I called my Auto-Electrician guy who took a look and promptly discovered the immobiliser had lost its codes for the keys. He reprogrammed it with the key codes and we were back in business. The electrician also checked all fuses and relays and said they were sound and couldnt see a problem with rusty fuses that sometimes causes problems with the NATS according to him He was unsure as to why the immobiliser lost the key codes and Im a bit wary now and question if it could happen again. Fortunately this time it was on the driveway but what about if it happens again! Can anyone explain why this would have happened ? The only thing that has been done recently is the battery was changed in March but this is 3 monthes ago surely that cant have affected it ??? Hope someone can shed light on this or has come across something like this before? Damian
From: Mrcheerful on 17 Jun 2010 04:15 DTS wrote: > Hello > Thanks for any advice in advance > Car is a Nissan Micra 1.0 litre 1999 on an S reg used as a cheap > runabout. > I got in the car last Friday and tried to start the car and the car > started for 2 seconds then stopped with the check engine light > flashing on the dash which after digging round the internet discovered > it was a NATS problem. After repeated retries I gave up and tried the > other key with the same problem. > I called my Auto-Electrician guy who took a look and promptly > discovered the immobiliser had lost its codes for the keys. He > reprogrammed it with the key codes and we were back in business. > The electrician also checked all fuses and relays and said they were > sound and couldn�t see a problem with rusty fuses that sometimes > causes problems with the NATS according to him > He was unsure as to why the immobiliser lost the key codes and I�m a > bit wary now and question if it could happen again. > Fortunately this time it was on the driveway but what about if it > happens again! > Can anyone explain why this would have happened ? > The only thing that has been done recently is the battery was changed > in March but this is 3 monthes ago surely that cant have affected > it ??? > > Hope someone can shed light on this or has come across something like > this before? > > Damian strong electric/mahnetic fields can mess up immobilisers on anything, which is why I don't put my phone in the same pocket as keys. On yours you can re-program the keys for yourself if it happens again. which type of system have you got? separate key fob or buttons in the key?
From: DTS on 17 Jun 2010 04:28 On 17 June, 09:15, "Mrcheerful" <nbk...(a)hotmail.co.uk> wrote: > DTS wrote: > > Hello > > Thanks for any advice in advance > > Car is a Nissan Micra 1.0 litre 1999 on an S reg used as a cheap > > runabout. > > I got in the car last Friday and tried to start the car and the car > > started for 2 seconds then stopped with the check engine light > > flashing on the dash which after digging round the internet discovered > > it was a NATS problem. After repeated retries I gave up and tried the > > other key with the same problem. > > I called my Auto-Electrician guy who took a look and promptly > > discovered the immobiliser had lost its codes for the keys. He > > reprogrammed it with the key codes and we were back in business. > > The electrician also checked all fuses and relays and said they were > > sound and couldnt see a problem with rusty fuses that sometimes > > causes problems with the NATS according to him > > He was unsure as to why the immobiliser lost the key codes and Im a > > bit wary now and question if it could happen again. > > Fortunately this time it was on the driveway but what about if it > > happens again! > > Can anyone explain why this would have happened ? > > The only thing that has been done recently is the battery was changed > > in March but this is 3 monthes ago surely that cant have affected > > it ??? > > > Hope someone can shed light on this or has come across something like > > this before? > > > Damian > > strong electric/mahnetic fields can mess up immobilisers on anything, which > is why I don't put my phone in the same pocket as keys. On yours you can > re-program the keys for yourself if it happens again. which type of system > have you got? separate key fob or buttons in the key?- Hide quoted text - > > - Show quoted text - Thanks for your reply The only keys i have black NATS ones with a red chip in them as its the pikey version of the car. He recoded it using a plug in coding device and also said Nissan would have charged a packet to do the same thing. It only cost me 60 Quid to have them reset . Could a microwave cause the keys to screw up ????
From: Tim Downie on 17 Jun 2010 12:46 DTS wrote: > On 17 June, 09:15, "Mrcheerful" <nbk...(a)hotmail.co.uk> wrote: >> DTS wrote: >>> Hello >>> Thanks for any advice in advance >>> Car is a Nissan Micra 1.0 litre 1999 on an S reg used as a cheap >>> runabout. >>> I got in the car last Friday and tried to start the car and the car >>> started for 2 seconds then stopped with the check engine light >>> flashing on the dash which after digging round the internet >>> discovered it was a NATS problem. After repeated retries I gave up >>> and tried the other key with the same problem. >>> I called my Auto-Electrician guy who took a look and promptly >>> discovered the immobiliser had lost its codes for the keys. He >>> reprogrammed it with the key codes and we were back in business. >>> The electrician also checked all fuses and relays and said they were >>> sound and couldn't see a problem with rusty fuses that sometimes >>> causes problems with the NATS according to him >>> He was unsure as to why the immobiliser lost the key codes and I'm a >>> bit wary now and question if it could happen again. >>> Fortunately this time it was on the driveway but what about if it >>> happens again! >>> Can anyone explain why this would have happened ? >>> The only thing that has been done recently is the battery was >>> changed in March but this is 3 monthes ago surely that cant have >>> affected >>> it ??? >> >>> Hope someone can shed light on this or has come across something >>> like this before? >> >>> Damian >> >> strong electric/mahnetic fields can mess up immobilisers on >> anything, which is why I don't put my phone in the same pocket as >> keys. On yours you can re-program the keys for yourself if it >> happens again. which type of system have you got? separate key fob >> or buttons in the key?- Hide quoted text - >> >> - Show quoted text - > > Thanks for your reply > The only keys i have black NATS ones with a red chip in them as its > the pikey version of the car. > He recoded it using a plug in coding device and also said Nissan would > have charged a packet to do the same thing. > It only cost me 60 Quid to have them reset . > Could a microwave cause the keys to screw up ???? As I understand it, the memory in the key is non-volatile, it's just an RFID chip. It is the car that has to be taught to recognise and accept the key as being the right key. If your old key still works I think you can forget any microwave/mobile phone damage to your key. I would have thought though that the immobiliser system in the car would also have non-volatile memory as otherwise every Nissan owner in the country would have to be getting their systems reprogrammed every time they had a flat battery so I'm not convinced that the battery is at fault either. You didn't have a problem when the battery was changed which would support the "non-volatile" memory theory. This doesn't help you alas. It's possible I suppose that the immobiliser's memory might not be entirely non-volatile, i.e., it might lose its memory if it loses power for a long time. I suppose this could occur if the immobilser's power supply or earth was faulty. Lastly, RF interference can sometimes cause a temporary loss of function (although not usually wipe an immobiliser system's memory). Got any neighbours with new aerials (CB) or a taxi driver living next door? Tim
From: bill on 17 Jun 2010 16:45
DTS <damian.tomlinson(a)googlemail.com> wrote: >Hello >Thanks for any advice in advance >Car is a Nissan Micra 1.0 litre 1999 on an S reg used as a cheap >runabout. >I got in the car last Friday and tried to start the car and the car >started for 2 seconds then stopped with the check engine light >flashing on the dash which after digging round the internet discovered >it was a NATS problem. After repeated retries I gave up and tried the >other key with the same problem. > I called my Auto-Electrician guy who took a look and promptly >discovered the immobiliser had lost its codes for the keys. He >reprogrammed it with the key codes and we were back in business. > The electrician also checked all fuses and relays and said they were >sound and couldn�t see a problem with rusty fuses that sometimes >causes problems with the NATS according to him > He was unsure as to why the immobiliser lost the key codes and I�m a >bit wary now and question if it could happen again. >Fortunately this time it was on the driveway but what about if it >happens again! >Can anyone explain why this would have happened ? >The only thing that has been done recently is the battery was changed >in March but this is 3 monthes ago surely that cant have affected >it ??? > >Hope someone can shed light on this or has come across something like >this before? > >Damian Wife's Micra had a very similar sounding problem. Sometimes had problem starting but after leaving it for a minute or so would eventually start and run fine. Slowly got worse but would start eventually. Then after a year or so it started cutting out on the road. Felt like fuel running out, so I blamed the fuel pump but tests showed that this was fine. Changed the fuel filter - no change. Next to get the blame was the temperature sensor because after unplugging this and plugging it back in it started behaving. I changed the connector and all was fine for a few months until the problem came back worse than ever. Unfortunately, each time it was taken to the garage it performed fine and there were never any fault codes on several checks. Main dealer was stumped and was suggesting a new ECU for around a grand! Independent mechanic was also stumped but suggested the crank sensor on the grounds that unplugging it gave the same symptoms. Changed the crank sensor and all was ok again for about 9 months. Back came the problem. Started looking around the internet for a replacement ECU. Found one on eBay were the owner said main dealer insisted it was the problem so he changed it only to have the problem return. He traced the problem to a relay and was therefore selling his working ECU. I emailed him and asked which relay. He very kindly told me. Pulled said relay from Wife's car and tested it in my lab at work. I discovered that every now and then on operating the relay the contacts, whilst clicking and closing (ie it appeared to be working) showed a resistance of a few hundred ohms. Found the problem!! This relay is in the relay box beside the battery. It is the immobiliser relay which supplies the injectors. There are two blue relays near the front of the box. One is the immobiliser the other is the radiator fan control. I cannot remember which is which. I swapped them over and ordered a new relay. In the meantime the car would now start instantly on turning the key. New relay arrived and I fitted it and have not had a single problem since. It was autumn and the car was used as a run around so I wasn't too worried about overheating with the dodgy relay contolling the fan for a couple of days until the new one arrived, just kept an eye on the temperature guage but didn't have a problem. This was more than a year ago so I am convinced that it is now fixed. Definitely worth checking this relay especially if there are no fault codes to read. Bill |