_ __ | |/ / | ' / | < | . \ |_|\_\
______ | ___ \ | |_/ / | __/ | | \_|
__ __ \ \ / / \ 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: Hi I am working on a BMW 635 csi '79 http://www.vems.hu/files/MembersPage/Bvd/Vems%20klein.JPG ---- I am going full sequential ignition and injection in the future but for now wasted spark is OK. All hardware is ready now only camsync not. For now I want to run wasted spark using COPs. But the inject and ignition outputs are a mystery for me. => start to document what you know, eg. * ignition firing sequence * What ignition option did you choose when ordering? * ECU serialnr * webshop oid '''A1''' I asssume you are running the latest released firmware/megatune package ? If not, get it from [http://www.vems.se/UserFiles/File/VemsMT1.0.36.zip here] (unzip and run megatune) then if you take a look at settings -> ignition settings, you'll find the option "Dual output mode"; enable that. After that set up the ignition channels in settings -> Ignition outputs dual setting screen. - DB '''Verification of setting''' After setting it, you can verify by doing a ''Man mcd'' dump in TerminalProgram 9600,8n1 (exit MegaTune while doing this) that ign_out=72 (not 70, that is normal dummy-ignition). The mcd and mct are the standard canonical dump of firmware variables. The information as suggested on IssueReports is the recommended way to document settings, it allows easy reproduction of setup, quick review by experts (which '''increases your chance to catch config errors if your setup intentions and wiring is also documented''') and avoids any human error or MegaTune problem (using very old version that is incompatible with recent firmware, or MegaTune bug). You can use MegaTune screendump for spectacularity, but mcd, mct dump is also highly recommended. <code> global.h describes variables: uint8_t ign_out; // EDIS:0x0? dummy: 0x7? disable:0xff bit1: ign_dual_out bit0: invertout </code> ---- '''EGT''' '''Q''' In the beginning I tested the egt when vems was not yet installed everything was fine and I had a nice reading. But when Vems is installed it doesn’t work anymore most of the time it says 0 en than for a msec 150 C and 300 C en than 0 again. * I have 2 egt channels but only one sensor and both channels give the same readings ** you can connect a sensor to both inputs simultaneously * I tested the sensor with an multimeter designed for Thermo Koppel’s and works fine! ** what sensor do you use ? Is that surely shielded ? That is the + and - has no galvanic connection to shield (>1 M Ohm). The WebShop EGT sensor is this type '''A''' I use the egt sensor from the webshop ** normal DVM can meausre ** disconnect the EGT (both pins) and apply an alligator clip on the wires (or short with some other mean). Heat this shorted end to >+10C (with your fingers) to see if reading is > 0C '''New info:''' when the sensor is completely disconected megatune give the same readings (for a msec 150 C and 300 C en than 0 again). ---- '''Wiring''' ignition settings => ign_dualout enabled * ign_out=72 (0x70 would be standard, but bit1=1 enables ign_dual_out) ** uint8_t ign_out; // EDIS:0x0? dummy: 0x7? disable:0xff bit1: ign_dual_out bit0: invertout ** '''NOTE THAT ign_out=02 is BAD!!!''' You need to configure "dummy" ignition outputs (NOT EDIS!) * ignchmax=02 ** 02 would work (3 channels), but 05 is recommended (6 channels). This way the knock-retard '''ignition outputs. TODO: document firing sequence!!!''' '''Pair 1''' Coil 1 to pin 35 Coil 6 to pin 33 '''Pair 2''' Coil 2 to pin 11 Coil 5 to pin 12 '''Pair 3''' Coil 3 to pin 34 Coil 4 to pin 36 * h[2]=01 05 03 01 03 05 00 00 is bad for several reasons ** for recent firmware (since stepper outputs can also be used for logic-level-input ignition modules), 10, 50, 30, ... would be needed. See GenBoard/UnderDevelopment/FirmwareChanges. Not clear what firmware you are using. ** C B A C B A .. .. would be needed to fire in sequence A,B,C,A,B,C (for a full engine cycle of 2 crankrevolutions): to see what are real A,B,C values, '''document your ignition firing sequence'''. '''Ignition output testing''' when using the keyboard command mdnxx, I get a 2 nice sparks for all 3 pairs * do you mean "mdnxx" ? that does NOT sound right. Replace xx with 05, 04, 03, 02, 01, 00 respectively, that is: mdn05 mdn04 mdn03 mdn02 mdn01 mdn00 to fire the related channels in the h[2] ignition sequence table. I'm now testing the ignition coils and all work well with keyboard command mdnxx. But when I crank the engine nothing happens even the spark advance in megatune background stays red and says -1.7 degrees => this does NOT sound good for cranking advance (usually 5..10 degrees). Check knock_default_retard (set to 0) and idle_advance (set to 0 for now). '''A2''' I guess you dont see rpm while cranking either (or irratic rpm numbers) it seems you have your trigger tooth and another trigger tooth swapped in config. Since you have a 60-2 on a 6 cylinder, another trigger tooth should be 60 / 3 = 20 (14 hex) trigger tooth should be adjusted so that ign_tdc_delay is around 60 degrees. (6 is usually a good starting point) - DB '''Q3''' The rpm number is good now but stil no spark while cranking '''A3''' your ign_out is set to 0x02, that should be 0x72 (DUMMY ignition + ignition_dual_out) easily adjusted from megatune->ignition settings->ignition driver type: DUMMY. (verify config afterwards) - DB [\ MembersPage/Bvd/Config] ---- '''Primary trigger''' original 60-2 wheel (BMW e34 ’90) Is that VR ????? * For VR, use primary_trigger=01 ** configure rising edge! ** reason: the LM1815 based VR input circuit always detects falling edge, but sends the signal to the processor so the rising edge is timed perfectly, the falling edge is appr 40..60 usec delay => so you need to configure the processor to trig on rising edge, otherwise timing table at high RPM would have 1..2 degree cheat) Camsync: [http://www.cy-sensors.com/Vane%20Sensors.pdf Hall-Effect Vane sensor] Camsync sensor position with the info on GenBoard/Manual/InputTriggerCamSync I made the following drawing to figure out where the camsync must be placed http://www.vems.hu/files/MembersPage/Bvd/campuls.JPG So if i turn the crankshaft to 150 degrees before TDC of cilinder 1 the Hall sensor mounted on the camshaft should give a reset puls. Please correct me if I'm wrong ---- '''RPM GAUGE CONNECTION''' I want to connect the rpm gauge and followed the directions from this webstore page: [http://shop.vems.hu/catalog/product_info.php?cPath=1_15&products_id=102&osCsid=18a8bb622ab2c487b5d0491aa7cb902a inductor] I don't completely understand it so i made a drawing http://www.vems.hu/files/MembersPage/Bvd/Vemsrpm.JPG This is the correct way to connect the inductor (inductive pullup). Make sure the output you use have power-IGBT-output (not logiclevel). ------ '''See DocsPage bottom for file area to upload images.''' alternatively you can upload the pictures from your computer to another image hosting ("gallery") site like [http://tinypic.com , than copy and paste the url for the image into you wiki page. ----------------------------------------------------------------- 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.