Standalone TD5 / imobiliser bypass options?

Quote:

---

Originally Posted by sierrafery

No "conflicts" with Hawkeye. In the BCU - Programming - Alarm there are only two options "fitted" and "not fitted"(or something very close to these)

---

Thank you SF, what options will i find under Passive and EKA .

oh! - by conflicts i was meaning if I set the Immobiliser to “NOT FITTED” must i change the Passive settings too?

Quote:

---

Originally Posted by onebob

Thank you SF, what options will i find under Passive and EKA .

oh! - by conflicts i was meaning if I set the Immobiliser to “NOT FITTED” must i change the Passive settings too?

---

Hawkeye has the menu same as testbook, IIRC in the same order too, see the BCU's description in the WSM(RAVE), it is a table there with all the options but once the alarm is set to "not fitted" with Hawkeye all the immobilisation protocols are disabled automatically even though better disabe everything just to be sure... just don't do anything in the EKA section with hawkeye cos i dont know why but it locks the ECM.

Quote:

---

Originally Posted by sierrafery

Hawkeye has the menu same as testbook, IIRC in the same order too, see the BCU's description in the WSM(RAVE), it is a table there with all the options but once the alarm is set to "not fitted" with Hawkeye all the immobilisation protocols are disabled automatically even though better disabe everything just to be sure... just don't do anything in the EKA section with hawkeye cos i dont know why but it locks the ECM.

---

Thank you for your always excellent advice - I have found the BCU description in RAVE and because there is no option listed to change the EKA code I have no need to in go there now. When you say doing anything in the EKA section locks the ECM - does it [brick 🧱] the vehicle? My ECM is the early MSB one.

Quote:

---

Originally Posted by onebob

Thank you for your always excellent advice - I have found the BCU description in RAVE and because there is no option listed to change the EKA code I have no need to in go there now. When you say doing anything in the EKA section locks the ECM - does it [brick 🧱] the vehicle? My ECM is the early MSB one.

---

I'd reckon it'd brick the BCM. I don't think the ECU has anything to do with security, other than receiving the "good to go" code from the BCU.

I chickened out of doing the test. Mr Ferry sorta freaked me out and I've got work to do today.

Quote:

---

Originally Posted by onebob

Thank you for your always excellent advice - I have found the BCU description in RAVE and because there is no option listed to change the EKA code I have no need to in go there now. When you say doing anything in the EKA section locks the ECM - does it [brick 🧱] the vehicle? My ECM is the early MSB one.

---

Only nanocom can change the EKA code, hawkeye can only set to "EKA" or "no EKA" and i tried "no EKA" twice on mine and other vehicle and both times the engine didnt start on this setting but once reset to EKA it came back to life so i dont know what is the utility of this other than neglect it.

Imobiliser removal in ECU just removes the need for BCU confirmation.
Mapping it out makles it exactly like the factory ECUs used when moving vehicles around the plant back in the day - no interrogation of BCU and just starts.

Quote:

---

Originally Posted by Tombie

Imobiliser removal in ECU just removes the need for BCU confirmation.
Mapping it out makles it exactly like the factory ECUs used when moving vehicles around the plant back in the day - no interrogation of BCU and just starts.

---

Yes, simple as that as long as the alarm is disabled and if it is disabled no need for any security device otherwise the alarm will yell and hazards will be on with a running engine...so that's the big utility of that emulaor. [bawl]

Quote:

---

Originally Posted by Tombie

Imobiliser removal in ECU just removes the need for BCU confirmation.
Mapping it out makles it exactly like the factory ECUs used when moving vehicles around the plant back in the day - no interrogation of BCU and just starts.

---

Is this something that can be done with the nanocom options or is it a matter of re-flashing the ecu?

Quote:

---

Originally Posted by Discosux

Is this something that can be done with the nanocom options or is it a matter of re-flashing the ecu?

---

It seems that you missed the point... you can disable the alarm/immobiliser with nanocom in the BCU and the ECM will addapt itself to that setting... believe it or not, eventually spend some money for a useless pack of crap which needs to be sync'd with the ECM but once the alarm is set to "not fitted" the ECM needs no code if you see what i mean.... maybe not

Quote:

---

Originally Posted by sierrafery

It seems that you missed the point... you can disable the alarm/immobiliser with nanocom in the BCU and the ECM will addapt itself to that setting... believe it or not, eventually spend some money for a useless pack of crap which needs to be sync'd with the ECM but once the alarm is set to "not fitted" the ECM needs no code if you see what i mean.... maybe not

---

Hi mate, I understand where you're coming from. Maybe there are differences between ECU's and stuff. So do, some don't?

Have a look at this link
Td5 Standalone Harness / Loom

I have no idea who these guy's are or their level of knowledge,
but according to them it's either a "black box" to send the code or an ECU re-flash to delete the code requirement