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

Knock Window Graph

Started by billman, July 23, 2012, 09:29:20 AM

Previous topic - Next topic

billman

A forum member pointed out that when doing a log and viewing the knock sensors in graph then some peaks coincide with other event i.e. Lean condition, clutch chatter ect.

I read that the knock sensor do not work (VEMS fw does not support them) but what is that what it reads?

I checked on my older logs with bad trigger event and the spikes in knock coincide with the trigger event or the clutch chatter I get on low RPM.


billman


Kamuto

what shows individual power?
Vems installer in Lithuania
[email protected]

GintsK

Quote from: Kamuto on July 28, 2012, 12:05:53 AM
what shows individual power?
trigger relative delay/advance in microseconds.

billman

can someone comment on this? Why do these apparent "knock" regions appear in regions where it is lean?

mattias

Engines may not respond like you think, they are not designed alike.

In your case, maybe lean = hot = knock.

The lambda sensor will usually show leaner thanks to incomplete combustion when it knocks, it usually gets "nervous".

Your engine might never knock at such low revs, there is perhaps not enough volumetric efficiency ("torque") down there so in your case you can push the advance beyond peak torque ignition advance, which is hard on the piston, wrist pin, rod and rod bearings. You need to hook the engine/car to a dyno in case you can't realise this while driving the car. However, do this at 4000-5000 rpm and you will probably hear knock before this happens - unless the engine has a super low compression ratio to run on shit quality fuel or massive boost with shitty fuel. :)

billman

The graph above is not from my car. Is just an example that made me wornder as to what does it show on the knock graph when according to all sources the VEMS knock function does not work.

Joof

I know this is old but I would love for knock implementation; I feel a bit misled - it worked when I bought it (although I understand fairly poorly?) subsequently yanked from new releases with hints that it would be back better relatively quickly and is still not around...

More to the point though, I have my knock sensors wired in and they are interpreted - I have two gauges on my vems screen and they go all over the place in relation to engine events.  At one point I was firing on 1 bank (of 2 due to water on the plugs) and that knock sensor showed no activity at all.

It is not that the unit is not seeing the knock sensor signals, it is just not doing anything with them/interpreting when there are actually knock events. 

peter_jensen

Hi

A lot of people cant get the knock code to work but there is good news.
In October/November the developer team will look at the knock code and hopefully make it work.
It will be more simple then it is today so don’t expect any fancy stuff. 

Thank you
/Peter

Joof

Peter,

This is very good news. Thank you for the update!

fphil

Quote from: peter_jensen link=topic=1992.msg20100#msg20100
It will be more simple then it is today
/quote]great, lets start with the basic

Denmark

Bttt


Anyone Got a working setup ?
With newest firmware
working on the boxer