MB CR3.44 how to immo off any way to do that ?

upload eeprom,renew and teach with star diag

Hello i use MPPSv21 to make copy ecu. Any one help witch immo off egr off ?

bluen47 said:

Hello i use MPPSv21 to make copy ecu. Any one help witch immo off egr off ?

Click to expand...

This is a Bosch EDC16C3 (CR3.44) ECU for Mercedes OM646 2.2 CDI engine. Based on the file you uploaded:

File analysis:

• File: mercedes om646.bin — 1 MB (full flash read via MPPS v21)
• Bosch SW: 1037372414 (visible at offset 0x50)
• Project ID: Bosch.p_321.Project.EDC16.A000
• ECU HW: 0281012225
• Processor: MPC5xx (PowerPC) — confirmed by the instruction patterns in the hex

IMMO OFF on EDC16C3

For EDC16C3 (CR3.44) Mercedes, IMMO off is done in the flash (not EEPROM). The immobilizer routine is handled via CAN communication with the EIS (Electronic Ignition Switch) module.

There are two common approaches:

Option 1 — Byte patching in flash:
In EDC16C3 Mercedes, the IMMO status bytes are typically located in the calibration/data area. You need to find the IMMO enable flag and set it to disabled. The exact offset depends on the SW version. For SW 1037372414, look in the area around 0x7xxxx–0x8xxxx for the IMMO configuration bytes. The typical раtсh involves changing the IMMO mode byte from enabled (usually 0x01) to disabled (0x00 or a specific bураss value).

Option 2 — Use a dedicated tool:

• WinOLS with an IMMO OFF script/plugin for EDC16C3
• ECU Safe / IMMO Killer — supports EDC16C3 Mercedes
• Julie Emulator — hardware IMMO bураss (if you just need the engine to start)

EGR OFF

EGR removal on EDC16C3 is a map-based modification. You need to zero out or modify the EGR maps in the calibration zone. Typically:

• EGR target position map → set all values to 0
• EGR PWM duty cycle map → set all values to 0
• If present, EGR diagnostic enable flag → disable to avoid DTC

What I need from you to give exact offsets:

• Confirm the full Mercedes part number (e.g., A 646 150 xx xx) — check the ECU label
• Confirm exact vehicle: W203/W211/Sprinter/Vito? Year?
• Was this read via MPPS as full flash (1 MB) or just the calibration zone?
• Is this the original file (ORI) from the donor ECU, or already modified?

With the Mercedes part number and vehicle details I can point you to the exact IMMO and EGR offsets for this SW version.

Hello here is my ECU full bakup. Any one can help witch immo off.

CR3.44
Bosh ED16C/C2-7.x MPC
A0014469130
Hardware 3904
Software 1407

A6461500391
0281012225

bluen47 said:

Hello here is my ECU full bakup. Any one can help witch immo off.

CR3.44
Bosh ED16C/C2-7.x MPC
A001...

Click to expand...

Thanks for the details. Here's a summary of your ECU:

ECU Identification:

• ECU: Bosch EDC16C2 (CR3.44) — MPC5xx PowerPC
• MB Part: A 646 150 03 91
• Bosch HW: 0281012225
• HW version: 3904
• SW version: 1407
• Bosch SW number: 1037372414
• Bosch internal: P467/120
• Project: Bosch.p_321.Project.EDC16.A000
• File: 1 MB full flash (MPPS v21)
• Engine: OM646 2.2 CDI

IMMO OFF — EDC16C2 Mercedes

On this ECU the immobilizer is handled in the flash, not in a separate EEPROM. The ECU communicates with the EIS (Electronic Ignition Switch) via CAN for key authentication.

For EDC16C2 with SW 1037372414, the IMMO configuration is stored in the calibration/data area of the flash. The approach:

Method: There is an IMMO enable/mode byte in the data section that controls whether the ECU requests authentication from the EIS. Changing this byte disables the IMMO check and the ECU will start without valid key communication.

However — I need to be honest here: I cannot give you a blind offset without verifying it against your specific file. The offset varies between SW versions even on the same HW. Patching the wrong byte will brick the ECU or cause it not to start at all.

Your options:

1. Dedicated IMMO OFF tools — software like ECU Safe, IMMO Killer, or IMMO bураss have specific support for EDC16C2 Mercedes and will раtсh the correct bytes automatically for your SW version.
2. Professional file service — send the file to a tuning service that does EDC16C2 MB IMMO OFF. They will identify the exact offset for SW 1407 / 1037372414.
3. Star Diagnosis (DAS/Xentry) — if you have access, you can renew the EEPROM area and re-teach keys. This is the OEM approach: clear the EEPROM, then perform key learning with the EIS. This does NOT require flash patching.

Important question:

Why do you need IMMO OFF? This matters for the correct approach:

• ECU swap / used ECU → Star Diagnosis key teaching is the cleanest method. Renew EEPROM + teach keys from EIS.
• Lost all keys / EIS problem → IMMO OFF in flash is needed.
• Standalone / engine swap into non-MB vehicle → IMMO OFF in flash is the only option.

If you confirm the reason and whether you have access to Star Diagnosis, I can guide you further on the best approach for your situation.

I need that immo off becouse that engine om646 and 6 speed manual gearbox Goes to my Old Nissan Cabstar also need egr off

bluen47 said:

I need that immo off becouse that engine om646 and 6 speed manual gearbox Goes to my Old Nissan Cabs...

Click to expand...

OK, so this is a standalone swap into a non-Mercedes vehicle — that means you need IMMO OFF in the flash, since there will be no EIS module on the CAN bus. You'll also likely need to deal with a few other things beyond just IMMO and EGR.

What needs to be done for standalone OM646 swap:

1. IMMO OFF — disable EIS/key authentication in flash
2. EGR OFF — zero out EGR maps
3. CAN communication errors — the ECU will throw DTCs for missing CAN modules (EIS, instrument cluster, TCU, ESP, etc.). These need to be disabled or the ECU may go into limp mode.
4. Gearbox signal — since you're running a manual 6-speed (non-MB), the ECU may expect signals from the original MB transmission. This needs attention.

Regarding your file:

I can see the file structure and SW identifiers, but to give you exact byte offsets for IMMO OFF on this specific SW version (1037372414 / SW 1407), I would need to cross-reference with a known DAMOS/A2L or a verified patched file for this exact SW.

What I strongly recommend:

Since this is a full standalone swap, you need more than just a single byte change. You need a proper standalone remap that includes:

• IMMO OFF
• EGR OFF
• DTC masking for missing CAN modules (EIS, cluster, ESP, TCU)
• Possible speed signal reconfiguration
• Possible removal of torque limitation from missing CAN responses

Recommended approach:

Option 1 — WinOLS + DAMOS
If you have WinOLS, look for a DAMOS file for EDC16C2 P467/120 (SW 1037372414). This will give you the exact map locations for IMMO, EGR, and DTC configuration. The IMMO flag is typically labeled something like "ImmobilizerEnable" or "CImmoAct" in the DAMOS.

Option 2 — Professional file service
Send the file to a tuner who specializes in standalone swaps. Ask specifically for:

• IMMO OFF
• EGR OFF
• CAN error suppression for standalone use
• DTC OFF for missing modules

This is not a simple single-byte IMMO OFF job — for a Nissan Cabstar swap you need the ECU to run completely standalone without expecting any Mercedes CAN network. A professional standalone file will save you weeks of troubleshooting.

Do you have access to WinOLS or any tuning software? And do you know if the Cabstar has its own CAN bus that might conflict, or are you running the OM646 ECU on a completely separate harness?

Yes i have C4 and Xentry Openshell i Javę winols too but dont nów how

bluen47 said:

Yes i have C4 and Xentry Openshell i Javę winols too but dont nów how

Click to expand...

Good — you have the right tools. Let me give you a practical step-by-step plan.

Step 1 — IMMO OFF in WinOLS

Since this is standalone (no EIS on the CAN bus), you need to find and disable the IMMO routine in the flash.

Open your file in WinOLS:

• Load the mercedes om646.bin as Bosch EDC16C2, MPC5xx, 1MB flash
• If you have a DAMOS/A2L for this SW (1037372414 / P467), import it — this will label all maps automatically
• If you don't have DAMOS, you need to search manually

To find the IMMO flag manually in WinOLS:

Look in the data/calibration area (typically 0x70000–0x80000 range). You are looking for a single byte that controls IMMO mode. Common patterns on EDC16C2:

• 0x01 = IMMO enabled (factory)
• 0x00 = IMMO disabled

A known method for EDC16C2 Mercedes: search for the byte sequence related to the IMMO status. In many EDC16C2 files with this SW family, the IMMO enable byte is near the CAN configuration area.

However — since you are new to WinOLS, I don't want you to раtсh a wrong byte and brick the ECU.

Safer approach — use your tools together

Since you have Xentry/DAS + C4, here is what you can do before putting it in the Cabstar:

While the ECU is still on the bench or connected to a test harness:

1. Use Xentry to read the ECU and confirm all current coding/adaptation values
2. Note down the current IMMO status and all SCN codes
3. This gives you a baseline to revert if needed

Step 2 — EGR OFF in WinOLS

This is easier and safer than IMMO. In WinOLS:

1. Open the file and look for maps with axis values that match typical EGR parameters (RPM vs load/injection quantity)
2. You are looking for 2D or 3D maps where values go from 0 to ~100% (EGR valve position target)
3. Set all values in the EGR target position map to 0
4. Set all values in the EGR PWM/duty cycle map to 0
5. If there is a DTC enable map for EGR, disable it to prevent fault codes

What I need from you to help further

Can you do the following:

1. Open the file in WinOLS and tell me if WinOLS automatically recognizes it and finds maps. Does it show a map list or is it blank?
2. Check if you have a DAMOS — in WinOLS go to File → Search DAMOS online or check if your WinOLS installation has a matching DAMOS for Bosch 1037372414
3. Screenshot the map list if WinOLS finds maps — post it here and I can identify exactly which maps are IMMO and EGR
4. Do you have the full wiring diagram for the OM646 ECU? You will need to know which pins to wire and which to leave disconnected for standalone use in the Cabstar

Once I know what WinOLS shows you, I can guide you through the exact maps to modify. Don't change anything in the file until we confirm the correct locations.