blueplasticsoulman wrote:
I wonder why there's even the option to disable the EKA.
While everything is working as it should, then all that is needed to turn the alarm off and reset the immobiliser is to unlock with the key. So in that respect it could be considered a good thing. Until a microswitch fails which probably isn't something that the designers even thought about when the system was new. I mean, a decent quality microswitch is good for millions of operations.
In theory :)
If you search for various Range P38 related things in Google Images, you'll probably come across this picture...
That's my photo - that was how I was getting my 96 started for a few weeks before finding Marty and his excellent rebuilt latches. Unlock with key, and then faff around entering the EKA by emulating the door latch microswitches.
That same rebuilt latch is now in my silver one and still working nicely.
Lol. That's proper A-Team thinking.
"I love it when a plan comes together"
For Reference, when the BeCM is in the alarmed state, it does not reply correctly to any diagnostic request for information, but instead replies to every diagnostic request with a default value.
It would have been easier if it simply did not reply at all, but it seems that the designers of the BeCM had other ideas.
Origionally the Nanocom was not set to detect this and interpreted the replys as valid data, resulting in incorrect settings as detailed in the User Guide for the BeCM, however we have updated it in later firmware to detect these incorrect replies and so come up with a communication failure message, which is an improvement that has not yet migrated to the user guide and this oversight will be addressed shortly.
As per the content of this thread, The BeCM can be taken out of the alarmed state by unlocking with a sychronised Key Fob, unlocking with a Key or otherwise convincing it that this has occurred in the event of failure of the Micro switches in the door lock.
Noting that if Key Fob syncronisation has been lost and the BeCM is in the alarmed state, having a failed Micro switch in the door lock prevents both re syncing the Key Fob and taking the BeCM out of its alarmed state.
Thanks for the update, that would explain why in the past I'd seen a BeCM with a build date of 2026 or something equally ridiculous. That was obviously before I updated the Nanocom firmware.
BBS-GUY wrote:
Noting that if Key Fob syncronisation has been lost and the BeCM is in the alarmed state, having a failed Micro switch in the door lock prevents both re syncing the Key Fob and taking the BeCM out of its alarmed state.
Don't I know it! Fortunately I've got a pretty good understanding of how it all works and was able to sort it. Even without the info that OB posted, I would have got there eventually. Unlike a friend who bought a P38 with a faulty door ajar switch. That caused the central locking to not work, the dash to constantly tell him that the door was open, the air suspension to not work (resulting in the previous owner spending a fortune on replacement compressor and valve block) but no interior lights on as the previous owner had removed all the bulbs. He was gobsmacked when I told him everything was down to one little microswitch and a refurbed latch from Marty cured all the problems.