myfirstl322
Well-Known Member
Well it seems it wasn't obvious when you licked that condiment arris, also.
Go on, do the face
Go on, do the face
Sorry for saying thank you to someone who helped me I thought that this was a forum about asking for help and getting good advice not about trolling people for having their view .However, maybe I have just read the whole thing wrong so I will get my coat and leave this discussion.Well it seems it wasn't obvious when you licked that condiment arris, also.
myfirstl322
Well-Known Member
Oh don't pretend to be naive, that's so last year,
you have deliberately concluded that Wammsybaby is getting a raw deal so you thought you'd chip in with words of 'oh he helped me something rotten'....
au contraire, you are witnessing something quite extraordinary here, and it ain't help!
Last edited:
Not said he was getting a raw deal just he helped me how much plainer can I say it.
RangeRoller dt
Well-Sprung Member
Read from post one ( or the other threads that led us here) it will make sense.
Or go look for Keith
When you find nothing -
yes we know
myfirstl322
Well-Known Member
I'm sorry, it's nowt personal.
Unproved if we're ignoring the fact that the BBS system documentation says it's not possible ?!
What is not possible?
Really? OK, even I'm bored now
Ok carry on clueless one.
RangeRoller dt
Well-Sprung Member
I have seen many arguments (to a lesser degree) like this. Where he says ‘enough, do it yourself’
I read a lot of old posts - this is where i usually find the ‘why’ 6 months later, or he tells me when I need to know. (Such as diy later type lift pump function)
So I believe him although you do not need to believe me as it is sort of blind faith.
He has never led me astray.
There was a time when ‘ok carry on’ had not been invented and things usually got much more volatile
He must like you
I read a lot of old posts - this is where i usually find the ‘why’ 6 months later, or he tells me when I need to know. (Such as diy later type lift pump function)
So I believe him although you do not need to believe me as it is sort of blind faith.
He has never led me astray.
There was a time when ‘ok carry on’ had not been invented and things usually got much more volatile
He must like you
COTY voters?
RangeRoller dt
Well-Sprung Member
Shippers
Well-Known Member
Did they not make multiple crap films?...ooh err matron...
Are you incapable of answering a simple question? What apart from unlocking a locked BECM is it not possible to do with a Nanocom. Because you certainly don't need to unlock the BECM to disable the immobiliser or EKA code.
I agree, you don't need to unlock the BeCM to disable the EKA/ Immobiliser provide that the BeCM is not in an Alarmed state. You seem to think it's possible to disable them while in the Alarmed state. System docs say otherwise, and the tests I and others have done back that up (FYI Nanocom Evolution Mark 2, using v1.34 firmware). Are you really smarter than the engineers who designed this stuff?
This is getting really really boring. I'm not calling you a liar - you probably really thought the settings had updated, because you saw the confirmation at the time - it's easy to be seduced by that. BUT you need to go into a clean nanocom session and reconfirm - the settings will have been rolled back. Unfortunately no-one else has a Nanocom like yours, as you have told us countless times - maybe it even had pre-production functionality, I have no idea. BBSs business model is based on selling a different box of tricks with the enhanced functionality - so I guess it is in their interests to make sure the "Wammers option" was/ is not available in the production Nanocom Evolution, if in fact it ever existed. FYI, Firmware is now v. 1.35 - any idea what version you were using - aeons ago?
As I said before, if you can't replicate this on a production nanocom TODAY - then your claim is worthless. I will happily defer to you on most/ all other matters P38 - but in this case I respectfully ask you to reconsider your position.
Fortunately most P38s have a BeCM >=v36, so there's a perfectly useful "Disarm" facility in the Nano, if all else fails, where the user can just input the EKA code
This is getting really really boring. I'm not calling you a liar - you probably really thought the settings had updated, because you saw the confirmation at the time - it's easy to be seduced by that. BUT you need to go into a clean nanocom session and reconfirm - the settings will have been rolled back. Unfortunately no-one else has a Nanocom like yours, as you have told us countless times - maybe it even had pre-production functionality, I have no idea. BBSs business model is based on selling a different box of tricks with the enhanced functionality - so I guess it is in their interests to make sure the "Wammers option" was/ is not available in the production Nanocom Evolution, if in fact it ever existed. FYI, Firmware is now v. 1.35 - any idea what version you were using - aeons ago?
As I said before, if you can't replicate this on a production nanocom TODAY - then your claim is worthless. I will happily defer to you on most/ all other matters P38 - but in this case I respectfully ask you to reconsider your position.
Fortunately most P38s have a BeCM >=v36, so there's a perfectly useful "Disarm" facility in the Nano, if all else fails, where the user can just input the EKA code
Last edited:
Simple answer to your statement is that BECM is not in an alarmed state when the immobiliser is active. An alarmed state BECM needs a lot more than a Nanocom to sort it except in very rare cases. What is plain is that you don't have clue what you are doing. To disable an enabled immobiliser certain steps need to be taken with the BECM in diagnostic mode. Obviously you don't know what they are. I do. Not all BECMs are V 36 by any means. Try your methods with an early one and see how far you get.
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.
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.
Last edited:
