If your car is broken, you need to fix it. Changing the idle RPM requires remapping and that is not something you can do with multiecuscan. If the idle RPM is too low, you clearly have a malfunction and you should fix that, not fiddle with the ECU.

And how is your dash display for fuel consumption now?

Would it be possible to support the M2.5 and/or M2.7 as used in the 348(G)T? I'm sorry, I don't have the manuals for it to all the registers, so I can't help there.

Startrek

05 on older motronics (M1.7 and M2.10.3) is nothing when the engine is not running. When you get the error with running engine, it means crank sensor. However, it's hard to get a running engine with that sensor broken, so I really wonder what use it is.

I don't know about the 147 sillyspeed, but on older 2.0 16V TS engines, it's often powered by the same relay(s) that also powers the injectors, coils and fuel pump. Use a multimeter to see if it gets power that way.

It would be nice to have a generic OBD (2) car to choose. Especially if it would also work with a KKL interface. I really don't want to put a gazillion apps on my diagnose laptop and have all sorts of interfaces laying around if I can do it all with just one interface and one application.

Am I correct in reading that this is about the crank position sensor Andrea?

The ECU may not update/store the odometer value real-time. This means that slight variations may occur. It could very well be that on certain cars the odometer can be adjusted (can someone verify this for the multiecuscan ECUs and possibly tell where/how to do that?) for wheel circumference. If you ...

If the errors are still there, you also can not remove them. What errors are you getting exactly?