Changes by last author:
Changed:
|
Q1 I read I need to configure ign_dualout but I cant find where?? |
|
=> start to document what you know, eg.
* ignition firing sequence * What ignition option did you choose when ordering? * ECU serialnr * webshop oid |
| EGT |
| EGT - the standard EGT sensor is used (from WebShop) |
|
* how do you connect EGT ?
** EGT connector ? ** terminal rails ? ** is the connection solid ? |
|
** 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 |
|
* 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. |
| 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). |
| ignition outputs |
|
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!!! |
|
* 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 |
| * 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 al work well with keyboard command mdnxx. but when I crank the engine nothing happens even the spark advance in megatune stays red ad the background en says -1.7 degrees |
| 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). |
| Q2 What is wrong please see my 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) |
|
The input triggers: original 60-2 wheel (BMW e34 ’90)
Camsync: [Hall-Effect Vane sensor] |
|
Camsync: [Hall-Effect Vane sensor] |
| Q Can someone confirm that I understand it correctly and that this is the correct way to connect the inductor. |
| This is the correct way to connect the inductor (inductive pullup). Make sure the output you use have power-IGBT-output (not logiclevel). |