_________ \__ __/ ) ( | | | | | | | | )_(
## ### ## ## ## ## ## ###
_ / \ / _ \ / ___ \ /_/ \_\
___ ( _`\ | (_(_) | _) | | (_)
_____ | __ \ | | \/ | | __ | |_\ \ \____/
IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now. Visit Preferences to set your user name Summary of change: '''Knock Sensing''' BMW M102/M106 engines (similar to M30 + turbo) are factory equipped with two knock sensors. I'm trying to utilize them... - Unfortunately at the moment there's only support for one sensor at-a-time in firmware. I'd definitely like to utilize both of them in the future, but for now I need to stick with the second one which is located between cyl. 5-6. It is the well-known place of knock, more than the first sensor location, since cyl.6 is the hottest one. '''PLAN''' '''How to set up the characteristic knock frequency?''' Bore is 92mm, so r=46mm. '''1. Theory''' The expected knocking frequency is around 900/(pi*r) = 900/(3.14*46) = 6.2kHz See TPIC8101 datasheet (using 4 MHz crystal; for reference, 0x29 = decimal 41 = appr 7 kHz) '''2. Experience''' * record the knock-sensor output with notebook soundcard while knock sensor is connected (with a 50k series resistor) to the microphone input of a laptop. * recommended: '''cling the block with a wrench''' when engine not running. Record the sound from the knock-sensor with your notebook sound input ** Tried it and seems pretty useless. Check this record: https://quasar.dynaweb.hu/~lezsi/bmw/knock-hit-on-block-test.mp3 I couldn't get my resonance frequency in spectral view or freq analysis either. https://quasar.dynaweb.hu/~lezsi/bmw/knock/knock-hitting1.jpg" https://quasar.dynaweb.hu/~lezsi/bmw/knock/knock-hitting2.jpg" '''counterrecommended:''' * adjust the ignition advance (usually upto 36 degrees in 4..5 steps) at idle until slight knock happens. * This is very hard without WideBand closed-loop EGO control, because the engine will want to stop before any knocking, and adjusting the fuel manually at the same time ignadv is adjusted is hard. * note that the MAP should be low, 25..40 kPa (max 55kPa), otherwise the engine is endangered. RPM also low (<1500 RPM). * play back the sound after the engine stopped. You'll be surprised how well the ping sound can be heard without the loud exhaust sounds. * just read the characteristic frequency from the FFT diagram. ** I was going to play high and raised ignition advance gradually on boost to get signals just like real life situations. A snippet from slight knock: https://quasar.dynaweb.hu/~lezsi/bmw/knock/slight-knock1.jpg https://quasar.dynaweb.hu/~lezsi/bmw/knock/slight-knock2.jpg I think frequency analysis didn't justify expectations rather amplitude changes shows quite a difference! I've marked the knocking area with gray background. The long "needles" in the waveform view are the "pings". This is a shot of a bit heavier knock (still couldn't be heard by naked ear): https://quasar.dynaweb.hu/~lezsi/bmw/knock/middle-knock1.jpg Unfortunately it is clipped because of excessive volume. This is a compilation of three records, one with no knock, second with slight knock and third with heavier knock: https://quasar.dynaweb.hu/~lezsi/bmw/knock_record.mp3 After listening to it a few times I can recognize very slight knock (high pitch "pings") even where amplitude or spectral analysis doesn't show. Interestingly only left channel (knock sensor 2) hears slight knock -it should be a rear cylinder- and it is not reported by sensor 1. - It is clear that distinguishing sensors with cam-sync is a must for large engine blocks. (BMW uses two sensors even on 4cyl engines) - Second observation is HUGE amplitude changes over rev-range. I think calibration of noise (in best case by one-time learning) is necessary on several (4-8?) points of revolutions. It seems much more consequent to base sensing on amplitude deviances from a set of tight (noise amplitude) reference values. Even frequency calibration seems unrelevant compared to those big amplitude differences. I have to point out that all these experiments were slight knock without making any damage to my engine, and were -in fact- undetectable from the cabin. ---- '''Config''' From TPIC8101 datasheet config value 39 stands for 6.37kHz, which is probably close to current typical knock freqency. * from global.h: uint8_t knock_conf; // knock, config. bit0 o FF means knock2... ?? o FD means knock1... (DEFAULT!) # Overall System Settings # Knock selection knock_conf = FF # enable knock-detection, will use Channel2! knock_sampling_window = e2 # ??? # Use knock sensing in this RPM range # FF for both means no knock sensing/control??? knock_minrpm = 05 # FF=No minimum RPM. 0x01=100rpm knock_maxrpm = FF # FF=No maximum RPM knock1_frequency = 27 # dec 39, 6.37kHz knock1_gain = 40 # ??? knock1_integrator = 14 # ??? knock2_frequency = 27 # dec 39, 6.37kHz knock2_gain = 40 # ??? knock2_integrator = 14 # ??? # Trigger level knock_threshold = 50 # ??? knock_noise_scale = 10 # ??? # Ignition effects # # Knock getting louder knock_max_retard = 50 # 20 degreees, 0x01=0.25 crank degrees. knock_default_retard = 10 # *0.25 crank degrees. knock_retard_step = 08 # 3.2 degrees knock_retard_delay = 10 # 0x01=15ms Retard delay. # Knock getting softer knock_advance_step = 02 # *0.25 crank degrees. knock_advance_delay = 10 # 0x01=15ms I'm '''totally lost''' with these config values. Couldn't find any usable info for those ??? values. Any idea? See lcd_display.c for the displayed knock values. Most importantly: lcd_knock_diff ("d:...") and you'll see that increasing gain increases this. We like to set gain so above d:100 means knock. There are no sharp limits here. Optional: Add document to category: Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.