Hi , This is my first time using the ECU Master PRO. I’m having trouble with the trigger setup. I started with the Primary at 50 degrees (same as Black), cranked with a timing light and ended up at 102 degrees. I’m using the Secondary trigger as the Primary Teeth Window 3 to 10. After those settings are in I can see all cylinders and all secondary teeth are numbered on the scope. Still doesn’t want to run. I can’t find a Lock ign Timing function like on the Black so I just zeroed the table in the cranking section when I checked with the timing light.
I can’t upload attachments, saying I’m a new user, how can I get around this?
Could you please post a scope file from cranking and the corresponding project file.
You should be able to add attachments as I’ve increased your Trust Level.
Thank you, I knew the Lock would be there somewhere.
Hopefully Scope is attached.
scope_2024_1228_1956.emuproscp (3.4 KB)
The scope looks correct to me. The spark for cylinder 1 is triggered at 50 degrees on the scope.
Could you please post a screenshot of the primary trigger setup in BLACK?
I had been trying 50 degrees and 102 (and a few in between), will check again tomorrow with the timing light at 50 just to make sure and with the timing lock on this time.
This is the last S54 on Black that I did.
Thank you for the screenshot.
BLACK uses two parameters to describe the first cylinder TDC - First Trigger Tooth and Trigger Angle. After conversion, you should enter: 87 degrees into EMU PRO “Trigger Setup First TDC Angle”.
87 = 6*(360/60) + 51
I found something interesting in your scope: the maximum compression of the engine for cylinder 1 is at about 87 degrees. The red lines have lengths corresponding to the time between the teeth. Longer lines indicate a slower engine speed. So the TDC is very close to 87 degrees.
(My recommendation is below the screenshot.)
I recommend:
- using 87 as the first cylinder TDC.
- if the engine will not start, you can try to activate the Trigger / Secondary / Invert Engine Phase
That’s perfect. It needed the Invert engine phase to start.
I have carried on and calibrated the VANOS intake which looked like it worked fine and applied the new figures into the control.
The exhaust however, it died and it now doesn’t have the sync, the exhaust cam has moved outside of the Secondary Window (3-10) the cam moves around 9 teeth retard so now is sitting at tooth 115 instead of 3.
Can you help on this please?
attached is a scope
scope_2024_1230_1432cam moved outside window.emuproscp (3.5 KB)
of the cam sitting full retard.
You can change the Trigger Secondary Pattern to “N-1” or “Longer than factor 2.0”.
It will detect the highlighted edge. You probably need to change the phase again.
hi, I have noticed you have started measure time between the teeth in the trigger scope, so my dumb question would be, can we hope for something like cylinder contribution or individual power? kinda way to see missfire on ecumaster, maybe it was already implemented?
Hi, sorry for the late reply, that worked well on the N-1, thank you for your help. I have now configured the VVT using the VVT tuner and seemed to work and all the figures were inputted automatically.
I started tuning and completed the 2000rpm row fine but, as soon as the rpm increases the cams seem to wander about. After a fair bit of going back and fourth I zeroed the cam targets and increased the rpm without load and the cams still wander.
I have attached a log file with the cam targets zeroed and I increased rpm, then with a steady lower rpm I added intake degrees then back to zero, then the same with the exhaust.
Would you be able to cast your eye over the log and base map settings please and see if anything is out of place? Or should I be looking at a mechanical fault?
BMW-S54-EK-001.emupro (24.6 KB)
2025_0116_1814_vvt test.emuprolog (231.4 KB)
Hi @Kamuto,
Thank you for the interesting suggestion.
We did some misfire detection research in the past by calculating the energy for each individual cylinder. However, we ran into issues when the car was driving uphill or downhill, so this feature never made it into the final EMU PRO firmware. Achieving OEM-level misfire detection is quite challenging.
We could add back these cylinder energy channels into the firmware. We will not call anything “misfire detection”, as it’s not perfect. But you will be able to at least compare each cylinder’s energy and spot potential misfires.
1 Like
@Maciej.Ordowski_ECUMASTER could you please analyze @Gareth logs.
Thank you
it does not need to be oem level for sure, that’s really hard, but, measuring crank acceleration between ignition events would really benefit the users, with the condition that those values can be assigned to the individual cylinders
Thank you @Jan_Matlag_ECUMASTER
Hi @Gareth
At first I suggest to change ‘Signal edge’ to Rising on Intake camshaft. Then please increase logging frequency to 100 Hz on Position, Target and Duty cycle channels. Afterwards you need to run VVT Tuner on this camshaft again.
Test both camshafts again and provide the log file with VVT Tuner procedure and similar test as in your previous log. Also screenshot from VVT Tuner would be helpful.
Thank you, attached are two screen shots of the vvt tuner after it has completed. I did it a couple of times. And the log file, towards the end it has the tables zeroed and increased rpm with the cams moving away from target.
2025_0122_1103_VVTtuner_end of log zeroed.emuprolog (5.6 MB)
I see there a problem with synchronization. Please look at Primary Unexpected missing teeth channel, it keeps increasing when you see a noise in VVT position, which in fact is a wrong reading of position, not camshafts move.
Please provide a current project file and a scope file at idle.
If possible, try to save another scope in a moment when the problem shows up, i.e while reving the engine like before. You would see there some anomaly in primary or secondary trigger. Probably you would need to repeat it several times until you get one.
BMW-S54-EK-002.emupro (24.6 KB)
scope_2025_0122_1247_idle.emuproscp (3.0 KB)
scope_2025_0122_1248_higher rpm.emuproscp (2.9 KB)
Thank you for the files.
It seems some crank teeth are missing at higher rpm. Perhaps VR signal is too weak. Turn off Pulldown in Primary Sensor configuration and try again. You may check other Filter options too.