So do you mean that the M57's crank sensor and flywheel are the same with the Td5's and the signal has the same waveform while the rpm input is matching the driver demand(TPS input)? even if you let the TPS there connected to the Td5 ECM it doesnt mean that at a certain throttle position the M57 will deliver the same torque... also the Td5 ECM needs ECT, FT, MAP/IAT, MAF correct inputs to not go to default and what about the TPS input? this is more complicated than it appears believe me. I can make any conversion myself to make a D2 to run with any engine and botch up all the warnings and management but that doesnt mean it's ok... so how would you make the EMS warning light to come on if there's some M57 engine misbehaviour or lack of fuelling as long as the warning it's managed by the Td5 ECM but the engine is not throttled by the Td5 TPS? I dont say it can't be done but i declare that if somewone claims that it's perfect it's just a false impression. I'll watch this thread with interest to see the outcome.
good luck with that, i'll wait to see that interface's description especially for the instrument pack's management
i can write a whole novel about that but i'd like to see an explanation just about one of the elements: how would the Td5 ECM read and 'consider' it's ok the input from a 4 bar MAP sensor while it is "calibrated" in the fuel map for a 2.5 bar sensor with a different voltage curve? ... and so on with all the other sensors and once an input is not like expected the Td5 ECM it goes to default and sends that message to the SLABS which goes to it's own default with "wrong engine data" code and bring up the 3 amigos