News:

When asking for technical help at the very least let us know the version of firmware you are running.
Cliff's Calibration (Mapping) Guide is a MUST READ: http://www.vemssupport.com/forum/index.php/topic,97.0.html

Main Menu

Individual cylinder power information

Started by gunni, November 14, 2008, 04:43:06 PM

Previous topic - Next topic

gunni

Any more info on this feature from 1.1.12 ?
and how to make good use of it.

z0tya

Has anybody info about it?
On 1.1.8xs there is individual power gauge...Can I use it for missfire detection, cylinder to cylinder mixture balancing?

NOTORIOUS VR

Where are you guys getting this information of these unreleased firmwares?  I can't seem to find that part of the Wiki

gox

E30 2.7 - VEMS,KKK K27.2,Schrick,1bar

Kenny Watson

Wow that could indeed be very useful for misfire detection.

I believe that's how motronic 7+ detects misfires - it expects to see the tooth rate on the 60-2 accelerate a certain amount at the firing phase for each cylinder. if the tooth rate for those (maybe 3 or 4 teeth?) is too slow it knows the cylinder didn't fire.

I'm not sure you could trust it for tuning individual cylinder trims though as I don't think many motors have even enough compression across the cylinders for you to be able to trust that a certain cylinder making less power is solely fueling related.

But having a specified cylinder-to-cylinder tolerance for power and then flagging when a cylinder goes out of tolerance would essentially be misfire detection and would be super awesome. ;D

NOTORIOUS VR

Quote from: BMW 325i on October 29, 2010, 08:38:24 PM
This looks like the place:

http://www.vems.hu/wiki/index.php?page=GenBoard%2FUnderDevelopment%2FFirmwareChanges

Wow... I'm a dumb ass... I know about that page as I check it all the time.

I just thought this was a new feature, but I see now the OP stated FW ver. 1.1.12 which for some reason my brain thought was a much newer branch (then 1.1.8x even, I was reading it as 1.1.112) lol

lezsi

Fine stuff to have, but how to interpret these values (which I have in all of my existing logs)?

It seems to me that the value range is -512..512ms (which is easily bottomed around idle)