For more data analysis options, I recommend using the Data Master. Ecumaster Data Master
Set the channel range on the graph log. This range is used for scatter plots
Hello everyone. I have following problem: I just upgraded to V3, and now the engine won’t start. To be honest, the engine didn’t idle particularly well in V2 (presumably due to the VVT settings), but at least it ran.
The vehicle is a TT 8J 3.2, which features the BHE engine from the previous generation. The wiring harness, including the sensors, remains the BUB version. The engine ran with a supercharger for a long time; currently, I am running it in naturally aspirated mode, though I plan to install a screw-type supercharger later on. The firing order and coils have been configured accordingly — As soon as I can, I will upload the projects and the logs (V2 and V3).
Is there a typical “beginner’s mistake” when switching to V3? What changes should I make to get the engine to start?
There is a big change to how spark and injection sequence is specified. Firing order needs to be entered correctly, then coils and injectors are assigned to cylinders rather than injection events
take a look for bub base map included with v3 software. The trigger settibgs should work with your engine
Hi. Unfortunately, I can’t get the engine to start
20260528_1907.emublog3 (369.6 KB)
20260528_1708____2.emublog3 (138.3 KB)
I used the project file ‘r32_bub_v3_work_in_progress’ from the download section once and generated log file 20260528_1907. Prior to that, I used the same project file, but with a modified VE table. The corresponding log file is named 20260528_1708____2. I calibrated the DBW system on both occasions. I am using a throttle body from a Porsche 997. I can almost rule out any mechanical damage, as I was driving with V2 just a few days ago. Is it normal for the MAP reading to remain unchanged during the starting process, even though the throttle body is opening—at times—fully?
I have another question: by monitoring which parameters can I perform a kind of fault diagnosis in the log section? I would like to rule out the possibility that a sensor, an ignition coil, or a spark plug—for example—is defective.
double check all input and outputs assignments, etc, might have changed from the original running map on V2.
Use the base map that is located in EMU_BLACK_V3 Base maps
AUDIA3_R32_BUB_FW_3_057_V1.emub3
In the log it looks like there is a spark and fuel.
Check your firing order and coils and injectors assignement.
Also if it works on v2 you can first start the car on V2, warmup the engine and then play with V3.
It will be easier to startup the engine and harder to flood it.
any news on this update for v2 firmware? be nice to finally have traction control switch back on clio 3rs… thanks
The firmware is ready. I hope it will be published tommorow
The new EMU BLACK V2 is available. CLIO RS TC switch added.
Please let me know if it works for you
Hi
Tested.
Traction control active on clio 3rs returns can switch 3 = off
Traction control deactivated on clio 3rs returns can switch 3 = on
default state on clio 3rs is traction control active - resets with every engine restart.
(attachments)
20260605_1825.emublog (15.7 KB)
It is TC off button then. Is that ok for you ? In V3 it works the same
Yes is TC off button.
Yes this will work. In Traction Control General - Activation Switch will need to be CAN SW3 inverted to work correctly?
Yes switch inverted.
Before trying the embedded software AUDIA3_R32_BUB_FW_3_057_V1.emub3, I was running the V2 version as you suggested. Unfortunately, I was unable to start the engine. I also tested the aforementioned version using my own VE table; the engine sounded a bit more powerful but still failed to start. I should also mention that since swapping the engine (about 8 months ago), I have driven with V2 only a few times and tried V3 in the interim. Since then, the ignition coil for cylinder 6 has melted twice (in both cases within 12 minutes). Visually, the wiring harness appears to be intact. Is it possible that the control unit was damaged by switching back and forth between V2 and V3 or is there another reason such as settings (dwell time) or something else?
3_057_eig_VE_Tabelle.emub3 (70.5 KB)
Project and log of ´burning coil 6th cylinder`
20260605_1255_zuendspule.emublog (1.2 MB)
Zuendspule_2.emub (145.9 KB)
Values in Custom corr 1 table affect Lambda target even with Custom 1 corr. condition set to Disable
I changed the Custom 1 corr. condition from Always active to Disable, expecting logged values of Lambda target to always equal Lambda target from table. Checking the logged data, I find the correction is still being applied. Obviously I can zero out the values in the Custom corr 1 table, but shouldn’t the Disable selection in the General dialog be sufficient? All other correction table entries are zero (except ethanol correction).
Your dwell time is too long, however it shouldnt be an issue for the RPM from the log.
Do you made harness by yourself (I assume it is not a pnp adapter, as the base map is not working for you)?. It is possible that the grounding is a problem and the coild doesnt turn off fully.
Another option is that the engine is working in wasted spark. You can try disable pairing coils in ignition output cranking.