______ | ___ \ | |_/ / | / | |\ \ \_| \_|
_ (_) | | | | | | (_)
__ __ \ \ / / \ \ /\ / / \ V V / \_/\_/
## ### ## ## ####
_______ ( ) | () () | | || || | | |(_)| | | | | | | ) ( | |/ \|
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: I want to test the knock detection function on a bench before on the car... Knock signal is from frequency generator and I can also use the ignition signal to make some noise. '''PREPARING''' 1) Genboad is Vems V3.6, firmware 1.1.90. I get the knock sub menu under the tool menu !!! weird ?? ok I download firmware 1.1.95. 2) Genboad is Vems V3.6, firmware 1.1.95. I get 2 Knock submenus in the Base Setup Menu. 3) Wiring As said on the sheet which came with the Vems V3.6 ECU, pin outs are * Knock1: EC18-1 (ch.0) * Knock2 : EC18-2 (ch5)pullup No second wire input, the second wire from the sensor has to go with the other sensor grounds. This is a quite different setting from the previous version as shown by Phat Bob/User guide, but alright. It is also said on the sheet that there is a pull up for Knock 2? Are we using Variable Reluctance accelerometer ? probably no, they are all piezo. * Voltmeter gives: EC18-1 : 2 - 1.8V, EC18-2 : 0V !! Thanks for an explanation. Anyway I would go for EC18-2. 4) Knock menus Knock detection is done by the TPIC8101 chip and by firmware for threshold and scale factors calculation. The TPIC8101 setup is given the "Knock Sampling" (why this name ??) submenu which options are quite clear except for the way the Genboard input is linked with the CH1 and CH2 inputs of the chip. This should be done through the knock_chan parameter. 'knock_chan' Some values of the knock_chan are related to the SD Card function. I do not see why... * Bob has put knock_chan = 0 for Knock 1, why not ? * I went through the firmware change history, I found with version 1.1.26: "Knock_chan = F0 disables knock Knock_chan=00 select knock channel 0 for all ignition entry Knock_chan=FF selects knock channel 1 for all ignition entries Knock_chan= AA selects knock channe1 for every other ignition entries … ) knock_threshold and knock_noise_scale They are with the Knock Action submenu. (why not to have sub menus "Knock set up" and "Knock action" I was not able to find definition for these parameters. 4) Output To observe the output of the knock detection function we possibly have * Knock Diff gauge * Knock Advance Adjust gauge * Adjust and Knock gauges for each cylinder ignition. * ADC input gauge related to "channels". * I input some DC or AC signal in EC18-1 and EC18-2 ( I used EC18-1 as a puldown), nothing is shown in any channel * I test EC18-16: CH1: the related gauge moves accordingly. * mcd on page 05 I probably should go first with Knock Diff and Knock gauges even if I do not understand what they are supposed to show. '''TESTING with Vems V3.6''' 1-Input : 2 Vpp sine wave at different frequencies on EC18-2, testing any combination of the parameters and channels and playing with knock_threshold and knock_noise_scale. -> NO OUTPUT ON ANY GAUGE 2) Input : an ignition signal Indeed I thought that there may be no detection if the noise is the same inside and outside of the window detection. -> NO OUTPUT ON ANY GAUGE '''TESTING with Vems V3.3''' Knock sensor input is EC18-1 for Knock 1 or EC18-3 for knock 2. I select channel 0, this is for Knock 1, I put Knock_chan=0. Whatever I did as above -> NO OUTPUT ON ANY GAUGE Then I looked the mcd page 05 I made firts the thing running: mlp04mll RPM:1002 kPa:129 La:13.4 EgoC:094 Clt:-40C Air:-40 Egt:0021 Tps:max * the EC18-1 not connected to any wire mlp05mllAdv:+13 dwell:362 S:021C L:09C3 D:005B 00 15 d: -128 R:00D9 ka:00 00 70 Or Adv:+13 dwell:362 S:021C L:09C2 D:0053 00 25 d: -122 R:00D9 ka:00 00 38 Bob seems to know what are D and R, I do not * EC18-1 wired whatever the signal Adv:+13 dwell:362 S:021C L:09C2 D:03F5 00 45 d: -?19 R:09E4 ka:00 00 05 '''HELP REQUIRED''' I do not see what else to do. Does someone know how to test the knock detection function on a bench? ---- We are just reworking the knock code. * The old code makes 2 measurements per ign event, one "windowed" where knock can happen, and another where knock should not happen. ** (hard to test because knock-signal must be synchronized to ignition). * The new code makes 1 measurement per ign event, and uses loadsite dependent lookup table to decide if the measured amplitude is knock (too high) or no-knock. ** (easy to test because knock-signal can be continuous, no syncronization needed). ** We had some weird side effects of the new code, so currently disabled, but we definitely want to enable it soon, before 2.0.0 The inputs are as [http://shop.vems.hu/catalog/assembled-controller-p-48.html in shop] * Knock signal: EC18/1 (knock1) * EC18/2 (knock2, only if dual-knock option selected). * Knock GND: EC18/17 (also used for RS232 GND, internally connected to EC36pin26). We'll get back to it soon, thanx ! ** Hint: the firmware change page should say that the knock function is disabled for 1.1.95 (if it is the case) 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.