___ / _ \ / /_\ \ | _ | | | | | \_| |_/
##### ## #### ## #####
#### ## ## ## ## ## ## ####
#### ### ## # ## # ## # ### ##
##### ## ## ## ## ## ## ## ##
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 ---- 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. '''Q1''' I read I need to configure ign_dualout but I cant find where?? '''A''' 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> ---- '''Wiring''' '''ignition wired outputs''' '''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 when using the keyboard command mdnxx, I get a 2 nice sparks for all 3 pairs ---- I'm now testing the ignition coils and al work well (thanks DB) for the 3 cell numbers. but when I crank the engine nothing happens even the spark advance in megatune stays red ad the background en says -1.7 degrees '''Q2''' What is wrong please see my config '''A''' 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) [\ MembersPage/Bvd/Config] ---- The input triggers: original 60-2 wheel (BMW e34 ’90) 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 ---- '''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.