Perhaps BBS has not spent as much time or effort in to this particular model,
are they still updating their information MOST days in 2020 like here?
 
I honestly don't think you have a Nanocom do you? I'm all ears - what model/ year/ software version do you have? Or perhaps no P38 to test it on

You also like to change people's words so that you can then claim they're wrong, don't you? Most does not equal All. My BecM is a v38 , in a 1998. I've EKA-disarmed a 1996, just a few weeks ago.... P38 was produced from 1994 -2002 - you do the maths - "Most" by anyone's definition.

According to the systems docs the ALARMED state can be exited using the EKA code, and yes, I've done it. Not so rare then...

Direct reproduction from the system docs:

FYI IMPORTANT NOTICE If the BECM goes into an ALARMED state you will notice that the reading
will be incorrect such as Language will become French and the date will be 1990 something. In
this state communication is not possible and can only be resolved by either inputting the EKA
code if it is accepted or by someone who can unlock the BECM for you with our specialist
software only available on the Faultmate MSV-2 system.

Although, for the avoidance of doubt I didn't just accept what was in the system docs. I've got off my arse, triggered multiple lockouts in my P38, desync'd remote etc, and concluded that you might not be as right as you think you are.
I tell you what you carry on, I have tried to help you and explain things. You dont have a clue what you are talking about. Bye.
 
Unproved if we're ignoring the fact that the BBS system documentation says it's not possible ?!

Missed a bit but to summarise: 3 different issues causing need for diagnostics.

1) Loss of engine sync. Not relevant to current discussion.
2) immobilised requiring EKA.
3) immobilised and BECM in alarmed state.

3 requires Faultmate or similar.

Opinion seems to be divided as to whether 2 requires EKA to be entered by diag or key before EKA and passive immobisation can be switched off? Wammers says it can be done with his model of Nanocom, presumably with diesel. You say it cannot with your model of Nanocom with GEMS? No-one else has tried different engine types or indeed Nanocom versions so we're looking at a sample size of 2?

How did you fool it into needing EKA?
 
Not really on the summary of 1,2 and 3, but I've now lost the will to live. System docs quoted above say that 3 can/ may be cleared by EKA. I have been in the 3rd state in the past, for sure (after I had a flat battery and was in a fairly advanced lockout , and cleared it via EKA disarm in the Nano - likewise the 96 GEMS I cleared a couple of months ago. The 2001 Thor clearance i did last week was more a case of stopping it asking for EKA each time the ignition was turned off.

Or if you just mean, how did i upset the security system.... lower the window, lock with the fob, pull the sill button (someone has just smashed the window), pop the hood, remove the battery negative (thief trying to turn the alarm off), press the fob button 5-10 times (desyncs the fob). Reconnecting after this then the car is very upset - according to the dash: Engine disabled. Keycode lockout, press remote or enter EKA. They fob is also now desync'd for good measure, I also looked at what would happen if the fob batteries were removed entirely. I dare say there are even funkier ways of challenging the security system but I'm not looking to blow anything up, mine is a working car.

Whether or not EKA is enabled in BeCM the EKA entry option is always open - indeed if you go in on the nano after tripping the alarm then you can see that imm and eka are flagged enable. After clearing with an EKA code the settings go back to whatever they had been originally.
 
Last edited:
All you have to do is lock with the fob and open with the key to activate immobiliser. The trick is knowing what to do and get the car started when the fob loses sync in the mean time and you don't have an EKA code.
 
Sure, I started with that method and then challenged the system a bit harder because I wanted to be sure that the fob was completely out of the picture. Now you're criticising me for being too thorough ?!

Did your car from Chorley have a passive coil on it? Do you have a nanocom now? or a P38? What's stopping you repeating this magical event? There's no way, unless you documented what you did at the time, and tested it, that you can conclude that something which the system docs says is not possible suddenly is. And you should not be insisting this to folks who might be thinking of buying a nanocom to allow them to do this - because at the end of the day, it seems you plan on taking this secret to the grave.

You're just ****ed off cos someone called bulls*** on something that you now can't remember how/ if you did

Since you had a pre-production unit for assessment, then presumably you told BBS about this "feature" you found. What did they have to say?
 
Sure, I started with that method and then challenged the system a bit harder because I wanted to be sure that the fob was completely out of the picture. Now you're criticising me for being too thorough ?!

Did your car from Chorley have a passive coil on it? Do you have a nanocom now? or a P38? What's stopping you repeating this magical event? There's no way, unless you documented what you did at the time, and tested it, that you can conclude that something which the system docs says is not possible suddenly is. And you should not be insisting this to folks who might be thinking of buying a nanocom to allow them to do this - because at the end of the day, it seems you plan on taking this secret to the grave.

You're just ****ed off cos someone called bulls*** on something that you now can't remember how/ if you did

Since you had a pre-production unit for assessment, then presumably you told BBS about this "feature" you found. What did they have to say?
I have never claimed to have a pre production unit what I said was I got mine before they were available to the general public. I am sure it's the same as everyone else's. It's not a feature it's knowing how to use it properly. Anyway keep trying you will get the hang of it one day.
 
Not really on the summary of 1,2 and 3, but I've now lost the will to live. System docs quoted above say that 3 can/ may be cleared by EKA. I have been in the 3rd state in the past, for sure (after I had a flat battery and was in a fairly advanced lockout , and cleared it via EKA disarm in the Nano - likewise the 96 GEMS I cleared a couple of months ago. The 2001 Thor clearance i did last week was more a case of stopping it asking for EKA each time the ignition was turned off.

Or if you just mean, how did i upset the security system.... lower the window, lock with the fob, pull the sill button (someone has just smashed the window), pop the hood, remove the battery negative (thief trying to turn the alarm off), press the fob button 5-10 times (desyncs the fob). Reconnecting after this then the car is very upset - according to the dash: Engine disabled. Keycode lockout, press remote or enter EKA. They fob is also now desync'd for good measure, I also looked at what would happen if the fob batteries were removed entirely. I dare say there are even funkier ways of challenging the security system but I'm not looking to blow anything up, mine is a working car.

Whether or not EKA is enabled in BeCM the EKA entry option is always open - indeed if you go in on the nano after tripping the alarm then you can see that imm and eka are flagged enable. After clearing with an EKA code the settings go back to whatever they had been originally.

There's a '98 GEMS parked in my back garden. Hmmmm!
 
Maybe the last post o_O

krjqRKqwCdzwn2Y4PMGmH2X-seFH0xmsfcQzvLf0lUL6C00C6jmMdFK1XBZBd4pnlOSxryTlFdKSQSSBV69BRgrEncEnUF7gA5slpLN2VHGNKCPEK3M
 

Similar threads