Author Topic: Knock sensing  (Read 14457 times)

Offline GintsK

  • Hero Member
  • *****
  • Posts: 1257
  • BHP: 50
Re: Knock sensing
« Reply #15 on: March 30, 2011, 02:26:31 pm »
Sorry? Have you 1.1.85 compiled with knock alternative?

In any case for >1.1.88 you must chose what to log in those separate channels: individual power or knock noise. There are drop-down menu for this choice. Might be it is individual power what you see in your logs???

Offline BigD

  • Full Member
  • ***
  • Posts: 111
  • BHP: 6
Re: Knock sensing
« Reply #16 on: March 30, 2011, 02:31:16 pm »
The log you see there is from 1.1.77. The fields are from Knock->Knock0..5. Knock 6-7 have nothing as expected. But 0-5 have reasonable values and the knock chan is 85, which should alternate between input 0 and 1. But if my 2nd input is disconnected, how is this possible?

Offline AVP

  • Hero Member
  • *****
  • Posts: 743
  • BHP: 11
Re: Knock sensing
« Reply #17 on: March 31, 2011, 08:21:45 am »
i hope knock sensing becomes usable and easily configurable, because that will close the gap of IAT ignition retard to ignition retard due to low octane in fuel. It seems that there are a lot of fuel stations out there that supply rotten fuel for 98 octane and VEMS has no way of knowing this other than the knock sensors. I believe that even those are not enough, especially when 1 is used for 2 or 3 cylinders, but at least now they are just sitting there doing nothing.

Offline GintsK

  • Hero Member
  • *****
  • Posts: 1257
  • BHP: 50
Re: Knock sensing
« Reply #18 on: March 31, 2011, 08:26:43 am »
The log you see there is from 1.1.77. The fields are from Knock->Knock0..5. Knock 6-7 have nothing as expected. But 0-5 have reasonable values and the knock chan is 85, which should alternate between input 0 and 1. But if my 2nd input is disconnected, how is this possible?
I think you do not see knock but individual power there.