# Actual cylinder cut lags far behind requested cut **URL:** \ **Category:** EMU PRO\ **Created:** [September 18, 2026, 5:38pm UTC](https://community.ecumaster.com/t/actual-cylinder-cut-lags-far-behind-requested-cut/6529 "2026-09-18T17:38:56Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![ScottSmith](https://avatars.discourse-cdn.com/v4/letter/s/cc9497/32.png) [@ScottSmith](https://community.ecumaster.com/u/ScottSmith)\ **Post date:** [September 18, 2026, 5:38pm UTC](https://community.ecumaster.com/t/actual-cylinder-cut-lags-far-behind-requested-cut/6529/1 "2026-09-18T17:38:56Z")
I’ve noticed both a high lag and an inconsistent lag between requested cylinder cut and actual cylinder cut (at least when going through the Vehicle Speed Limiter). First, my settings are pretty basic, a 1:1 mapping from “Trial Cut” to cylinder cut, with a 50% ramp per revolution: ![Screenshot 2026-09-18 093830](https://europe1.discourse-cdn.com/flex013/uploads/ecumaster/original/2X/a/a0191b42c5c74ed4d1a1bb2897da0ccda29398f0.png) But here’s a sample of it in action (I’m using cylinder cut for upshifts with a DCT; yes I should use more ignition retard and less cut, but this should work too): ![Screenshot 2026-09-18 103212](https://europe1.discourse-cdn.com/flex013/uploads/ecumaster/original/2X/e/eaf3eb1eca27a7fb92efb62b2cb15bb6d311c155.png) 1. The first peak seems 30ms delayed, ok not terrible but not great either. Not sure whether it’s relevant but RPM is around 5700, so let’s say 10ms per crank revolution or 20ms per cam revolution. Maybe the delay is related to that? Can we get cut updated more than once per cam revolution? 2. The second peak is less consistent. The rise is delayed about 8ms but the decay is delayed about 30ms. Is this related to where in the cam rotation it is? 3. If I utilize ignition timing instead, will it react more quickly / more consistently? Maybe I can hone in on this if I up the logging frequency of Trigger/Primary tooth cycle.