I am having issues getting my r53 to start with the V3 beta. I have set everything up pretty similarly to the V2 map. I have tried everything. It tries to start, seems to be spraying fuel, and sparking it. Primary trigger is setup exactly as V2. I can provide maps to compare the two as well as starting logs for both maps. I may be overlooking something really dumb, so forgive as I’m still learning how this stuff works.
Post project, log and scope please
If it doesn’t allow you to upload it then try changing the data endings to .txt
R53 Map_V3.emub3 (66.7 KB)
20250408_1812.emublog3 (688.6 KB)
scope_202546_1740.emubscp3 (628 Bytes)
Good afternoon. And why is that so? It’s not a mistake, is it? firing order: 1-4-2-3; injector phase: 1-3-4-2
all is ok. firing order is just offseted by 1 cylinder.
1 Like
I’m pretty sure you are using a regular emu.
In case of PnP, it 's quite specific , for example the coil type should be “with built-in amplifier”.
I tried both emu, but I don’t know why their is a diff
Is there any advantage to disabling the cam sync after the engine has started?
You’ve added a 50us input delay in the new wizard. Does this replicate the V2 ‘Increase precision at high RPM’ option? And is the input delay affected by the input filter selected?
Disabling CAM is only useful when you have very noisy signal from CAM, especially on high revs.
It is beter not to enable this option.
Delay input is connected to all delays from the primary trigger sensor as well as output stages and spark generation. It doesnt matter at low RPM, however it can be notciable at high RPM (the ignition angle will retard a little proportional to RPM).
V3 has only high precision mode implemented.
1 Like
Thanks… So 50us is generic or specific to the R53?
It is not generic value. Hower even you put 0 there there is no problem as you compensate it with VE table.
1 Like