NefMoto

Will a m3.8.3 (06a906018cg) file work on a m5.92 (8d0907557p)ecu?

I've read on here that it'l flash. But not sure if the hardware is exactly the same.

No.

You can flash even a jpg on it. But as long as interupt vectors and memory map does not match hardware pin cfg or given cpu and external specific layout, nothing will start.

And depending on boot loader, the ecu is then bricked, factory or tool reflashable.
Desoldering may work, if bootloader doesn't store information in eep.

Thanks for the info. Too bad it wouldn't work. It would've gotten rid of my LDP cel and speed limiter. Would still need to find the rev-limiter calculation though.

Was hoping the info in ecuconnections stating that they had the same hardware was correct.

http://www.ecuconnections.com/forum/viewtopic.php?f=2&t=4192&start=0 (http://www.ecuconnections.com/forum/viewtopic.php?f=2&t=4192&start=0)

Ricekikr is nice to see that this info still is useful for someone. But if you read carefully although boards and MCP are the same programming and operation are something different. If you compare Bosch part numbers (M3.8.3 - 06A906018CG / M5.9.2 - 8D0907557P) you will notice that are different families. Inclusive 8D0907557P doesn't have internal CAN Bus IC that 06A906018CG has. Maybe an 8D0907559xx ECU could work, but I not sure.
Your best bet will be find an M3.8.3 ecu from an Euro MK4 VW Golf GTI or Euro 8L Audi A3 and married it to your car. Pinout are very very similar. Also those are flashable through OBD2 port too.

I have done this. The ecu worked, the car started. It only started for a moment as the immobilizer killed it, further testing would have required me to write the eeprom, which I didn't have time for.

Hi DD. I test it too having some weird boost (N75) control issues.

Thanks for the info  ;D

I neither have the need for n75 (just use the ecu as a base for my piggyback) or immo delete (cluster-key married).

With an unmarried key and m5.9.2, the immo just continously blinks.

Always wondered why the 3.8.2 clemens file has code for can-bus.

Removing the immo from the ecu will not stop the cluster light from blinking :(

DD what ECUs (OEM & Test ones) & Cluster are you working with?

3.8.3 (06A906018CG) didn't work on my 5.9.2 (8d0907557P). This is with the immobilizer married to the cluster

With the 3.8.3
Engine starts then shuts off after roughly 2 secs.
Immo blinks
Can't connect via generic obd reader (didn't try vagcom)

With the 5.9.2
Engine starts
Immo light stays on around 3 secs then turns off (with an un-married key, the immo would just keep blinking)
Generic obd reader connects (didn't try vagcom)

Ricekikr as I comment before M383 & M592 shares same basic board and hardware but boot rom, program and binaries can differ. If you see Bosch part number you can notice that many M592 8D0907557x / 8D0907558x ECUs are Bosch 0261204xxx coding while M383 06A906018xx (double letter code not one) ECUs are Bosch 0261206xxx coding.

If both ECUs comes from the same family (same hardware same firmware) you can do a cross-flash. That is why I suggest use a whole new ECU. When I was comparing ECUs (hardware / firmware / software) I notice that just some 8D0907559x ECUs are 0261206xxx Bosch family and could accept and function properlly with a M383 dump.

About immo, from my research seems to me that almost all 8D0907557x & 8D0907558x ECUs 0261204xx Bosch family lacks of CAN Bus IC in it board, then it should work with non CAN clusters, xxx919xxx ones. Seems to me that you can match an Immo II ECU with an Immo III cluster but not an Immo III ECU with an Immo II cluster. Just my idea.

Free and non-brick was worth a try. ;D

Would you happen to know how a 3.82 or 3.83 calculates rev limit (and possibly speed limit).

I really want to re connect my vss just to get the moving idle map back.

Cut the vss to remove speed limiter and rpm limter (no speed limiter, 10200 rev limit, but mines set lower than 1020)

Basically these ECUs calculates engine RPM limit based in some variables. I am not totally sure, but Crankshaft, camshaft and VSS should be the main ones.

Could you expound on that a bit?

Would changing the linearization from crank/cam/vss remove the limits? Limiting it at the top end and just compensate the fuel/timing maps?

Edit: not the best solution, since it'd mess up the fuel injection timing

I think I found the Vmax for a 3.8.2 file. But couldn't find anything close to it on a 5.9.2 file. Searched by searching values beside it.



3.8.2 4x1 7e44 (using clemens maps)
3.8.3 4x1 73e8 (using pvl maps)
5.9.2 = ?

From the information that I have and my readings about M383 & M592, rpm value should be measured directly from crankshaft signal, then RPM limit seems to me, be calculated from crank and adapted with other variables like cam & vss. Those are my thoughts.
Then based on that altering RPM values or linearization should affect everything in ECU, as you said, that could mess up whole ECU behaviour.

Do you know which address on m592 are for vss signal multipilier? My theory is it limits the speed per gear (in turn limits rpm). So cutting the multiplier in half could, in theory double speed limit and rpm limit. Assuming it doesn't throw a code based on the wheel speed sensor.

Couldn't find anything similar on the m592 using the m382 or m383 map info. 4 1x1 maps on the m382/383

Let try to check if I find it.

Thanks  ;D

Just found it.

6DDA 1x1 16lohi

In the 3.82 damos it's two 1x1 maps (same values). On the 5.92 it's just one 1x1 map. Tested at low speeds with the values doubled. It halved the speeds seen by the ecu.

Haven't tried at high speed to see if it'l throw a code and has removed the speed limiter.