I’m attempting to get my N/A Mini R50 running on the plug and play ECU. So far I have had to replace a faulty MAP sensor that was preventing the car from running. Now I can get the car to start and it’s obviously doing its cranking sequence but as soon as the idle sequence kicks in, the engine stops with a fuel cut initiated by the ECU. The fuel cut is because there is no fuel pressure registering in the ECU.
From what I have been able to glean, the 2002 N/A R50 is not equipped with a fuel pressure sensor. How do I get around the fuel cut issue if I don’t have a fuel pressure signal to use?
I would recommend upgrading to the latest stable firmware.
I see your fuel cut when you start. I dont think the fuel cut is because of no fuel pressure sensor. It seems you have modified your fuel cut settings? as it varies from the those in the base map on the website.
Increase your overrun fuel cut decay rate and try (experts can recommend a value… )
Check your throttle also please doesnt seem to move. maybe its open because of which the engine starts. Has it been calibrated it?
Thanks for the reply shyam
I have calibrated the throttle body and confirmed it is operating correctly. I don’t think the throttle should need to be operated at start, The log should show the cranking sequence working correctly. The engine starts reliably every time but stops when the fuel cut triggers.
I did try to modify the fuel cut lower limit but with no fuel pressure signal, it still triggered because the lowest value possible is 1kPa and I have 0kPa.
Thanks for the tip on the fuel cut decay, I’ll try it.
your fuel cut is an overrun not anything else and is disappearing i think on 1500 rpm and you can see injectors pulse is there and going lot higher when overrrun end going to 5ms which is quite a lot. is that stock car ? or something has been changed ?
The car is stock and I have only altered the lower pressure threshold on the fuel cut from 25 down to 1kPa but I’m sure I saved the value back to 25kPa.
I’m running the base map for the R50 as it was delivered on the ECU.
The engine starts and then stops soon after, the timing in the log is consistent.
I have only made it run longer by repeatedly jabbing the accelerator and eventually the car starts popping and emitting a very rich fuel smell from the exhaust.
Why does the fuel cut operate at all if it’s not responding to a threshold?
Overrun fuel cut is behaving exactly how should you off the throttle and above the rpm threshold… and is fuelncut dissaperaing once below 1600rpm exactly whats on map fuel is reinstated and i can see that and is still not running. Enable lambda without rpm and try to start it… this will gove more idea whats happening
I’ve contacted ECUMaster here in Australia and I’m going to get a remote session with them today. They think it’s just an unpopulated fuel map that’s the problem so fingers crossed
Quick update. Rama from ECUMaster Australia remotely connected in to my ECU yesterday and found out the MAP sensor settings were way out. After a bit of experimentation, we got the car running and idling. However, the VE map is still out of whack so I’m getting a wideband 02 sensor to fit today. Once it’s installed, Rama said he will be able to sort out the VE table.
