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.
=> 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 [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
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.
global.h describes variables: uint8_t ign_out; // EDIS:0x0? dummy: 0x7? disable:0xff bit1: ign_dual_out bit0: invertout
EGT - the standard EGT sensor is used (from WebShop)
- how do you connect EGT ?
- EGT connector ?
- terminal rails ?
- is the connection solid ?
- 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!
- For the webshop sensor, the + and - has no galvanic connection to shield (>1 M Ohm), that can be verified.
- when the sensor is completely disconected the EGT reading does not make much sense (usually 0). In megatune this particular one actually gives 0C for a msec (msec ? millisecond?) 150 C and 300 C and than 0 again (well, that is a bit weird, but the good test is to short the inputs: eg with an alligator clip). open inputs => meaningless.
- 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
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!)
- 02 would work (3 channels), but 05 is recommended (6 channels). This way the knock-retard
ignition outputs. TODO: document firing sequence!!!
Coil 1 to pin 35
Coil 6 to pin 33
Coil 2 to pin 11
Coil 5 to pin 12
Coil 3 to pin 34
Coil 4 to pin 36
- h=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 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
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: [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
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: [inductor]
I don't completely understand it so i made a drawing
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.