Ford 1.6 edc16c34 IMMO OFF possible ?

[popov]

Hello , have Ford EDC16C34 1.6hdi , is it possible to immo off, or what kind of emulator will work on it? Already tried Module initialization with IDS whtihout success. Red dot on cluster is ON.

[kiszka]

Hello , have Ford EDC16C34 1.6hdi , is it possible to immo off, or what kind of emulator will work on it? Already tried Module initialization with IDS whtihout success. Red dot on cluster is ON.
it shows in the eprom that you listened to stupid ideas
read eeprom dash

[xenon74]

hi immo off don't exist for this ecu
use forscan

[kiszka]

hi immo off don't exist for this ecu
use forscan
he had already used the forscan and had come to a dead end

[xenon74]

Bonjour, avez Ford EDC16C34 1.6hdi, est-il possible de désactiver l'immo, ou quel type d'émulateur fonctionnera dessus ? Déjà essayé l'initialisation du module avec IDS sans succès. Le point rouge sur le cluster est activé.
file E2P is bad size

[alonedark]

yes you can do inmo off whith emu FORD EUCD platform cars, from 2007 and up to 2016 (Ford Mondeo, Galaxy, S-MAX. Acts as a CANfilter between ECU and original BCM. Must store 8 bytes SYNC and 6 bytes ABS_ID into emulator AND / ORmodify ECU EEPROM.


no se puede decir tanto que no

[alonedark]

here the manual :

Configuration and jumpers (JMP):  JMP1: open to allow SYNC update, if short update is prohibited; JMP2: open for standalone mode (emulator acts as a BCM for ECU), short for standard mode; JMP3: open for default SYNC: 6666666666666666 , ABS_ID: 999999; if short – use custom SYNC and ABS_ID stored into emulator EEPROM. Common alignment methods: method 1 – modify default SYNC and ABS_ID into ECU EEPROM. Jumpers (solder bridges) must be: JMP1 short, JMP2 short, JMP3 open. Install emulator inside ECU and enjoy; method 2 – store necessary SYNC and ABS_ID into emulator. JMP1 must be open to allow EEPROM updates, JMP3 shorted (to use custom SYNC and ABS_ID stored into emulator EEPROM), MBcan or any suitable CAN logger must be attached to emulator CAN 1 (BCM / car) side:◦ Using MBcan: simply store necessary SYNC and ABS_ID;◦ Using CAN logger: speed 500kB, 11bit (short) id. To store necessary SYNC (ex: 0102030405060708)and ABS_ID (ex: 123456 = 313233343536 to ASCII) must send 2 frames:0x7FC 8 00 00 31 32 33 34 35 360x7FE 8 01 02 03 04 85 06 07 08Must use least significant 6 characters of ABS hardware serial number, in ASCII. Example: full ABS_ID 000075123456, use only 123456, converted to ASCII character codes: 313233343536.Emulator must respond with same data (ID's are 7FD for ABS_ID and 7FF for SYNC):0x7FF 7 01 02 03 04 05 06 07 080x7FD 8 00 00 31 32 33 34 35 36◦ Short JMP1 to prohibit SYNC updates. All configuration changes become active at next power-ON,  If JMP2 is open, original messages from BCM are completely dropped and own ones are sent (standalone mode, “no BCM”). If JMP2 is shorted, original messages issued by BCM are modified to comply with ECU demands

the emu must be intaleted in bcm and ecu can lines



sorpresa

[alonedark]

Popo here a picture of your emu