ignition firing at half speed?? (and car not running with 1.1.81 FW)

[DButters]

I will try your setup out tonight and see - but so long as I have the firing order (1,2,0) repeated it should not matter if ignchmax is 2 or 5, according to what I have read?

[rob@vems.co.uk]

With h[2]=10 20 00 02 01 00 21 11 and Ign channel max = 5
It will fire: 00, 01 (No spark), 02 (No spark), 00, 20, 10

[DButters]

Well,
I tried Robs setup, to no avail, I still have ignition that doesnt fire each coil the second time until 360 degrees later.

I am beginning to think this is a firmware bug ,so I will go to 1.0.73 and see what happens.......

This may be obvious but I have spent so many weeks on this I am going nuts - could anyone tell me approx the time between sparks for a 6 cylinder at approx 190 RPM? I get a consistent 1-2-3-1-2-3 spark order with about 200-300ms between each spark on my VEMS driven coils, and from my factory distributor setup I get twice as many sparks in the same time.

[DButters]

looking at the release notes, does this look like something I need to change in my config?


#  tooth_wheel_twidth1=18 # normal tooth width in quarterdegrees. decimal 24 quarterdegree that is 6 degrees (for 60-2 wheel)
# tooth_wheel_twidth2=00 # upper byte of normal tooth width

right now I have 00 and 00 for these according to your setup?

also are the release notes about the h[1] field accurate?
thanks again!

[rob@vems.co.uk]

Those twidth values are not used at the moment, tend to zero out things that aren't used (things that are used but disabled get set to 255 (0xFF))

[DButters]

Thanks rob, is that also true for the h[1] table? the release notes say it needs to be filled, or is that only the case when a camsync is used?

[rob@vems.co.uk]

Yes h[1] table needs to be setup for all 1.1.xx 

I'd spend at least a few minutes trying 1.0.73 with a 60-2 wheel

[DButters]

OK Some progress!!
down graded to 1.0.73, and ign appears to fire at correct speed.... cant get her running though as the downgrade has made a mess of my tables.
I will spend some time bringing them into line manually and then hopefully get it running on wasted spark.

so the question is, what in my setup or the 1.1.18 firmware caused me to tear my hair out for the last month?

[rob@vems.co.uk]

To be honest - I have no idea!
I have a number of cars running on 1.1.18 without a single problem.

But I'd not use it for missing tooth because 1.0.73 works perfectly well.

[DButters]

Hi again all,
I got curious with the new updates and tried updating form 1.0.78rc2 to 1.1.81.
Again I get no start - this time I checked the trigger log using the V3 function in latest vemstune - showed up perfect 58-2.

looking at some other peoples problems - http://195.159.109.134/vemsuk/forum/index.php/topic,1398.0.html

- I have updated the tooth width (which did not come through correctly in the upgrade) to 6
- I have updated the tooth reference table to 00 40 20

- It appears that I may also need to do the following:
  - invert my ignition outputs (pin 33, 34, 35 to 35, 34, 33)
  - change the number of ignition outputs to 6 instead of 3, and repeat the cycles in the ignition output and reference tooth tables?

If anyone cold confirm this it would be greatly appreciated, I have had the same issue trying to upgrade to an 1.1.xx firmware.

[mattias]

- invert my ignition outputs (pin 33, 34, 35 to 35, 34, 33)

Depends, if you're using regular passive coils with these ignition outputs like you are (wasted spark coil, right?). Then you should NOT invert the driver output, leave that disabled unless you want stuff to cook/fry.

  - change the number of ignition outputs to 6 instead of 3, and repeat the cycles in the ignition output and reference tooth tables?

Exactly. Do it.

[DButters]

- invert my ignition outputs (pin 33, 34, 35 to 35, 34, 33)

Depends, if you're using regular passive coils with these ignition outputs like you are (wasted spark coil, right?). Then you should NOT invert the driver output, leave that disabled unless you want stuff to cook/fry.

-- Sorry I meant reverse the order, not invert the output level which definitely would cook the coils. would reversing the order be correct? I would then set the outputs as pin 35, 34, 33, 35, 34, 33

And yes to confirm this is just a wasted spark setup, standard M30 BMW 60-2 trigger wheel with cherry hall effect sensor.

[mattias]

Yes, all tables are traversed in reverse due to letting programmers decide how things work in the beginning.

I can't tell you the order of your outputs, I have to know how the coils are wired and how your reference tooth table looks like to have a clue.

Regardless. If your ref tooth table is top to bottom : "0, 40, 20, 0, 40, 20 "
And your ign output table is "35, 34, 33, 35, 34, 33"
and the strobe light says that cyl 1+6 (which ever output that corresponds to) fires at TDC, then that output is in the right place in the ign output table. The other two outputs can only have two different patterns to get the correct firing order, either make adequate marks on the pulley to determine that or just try to fire up the engine, it will only run with the correct order and backfire/run bad with the other.

[DButters]

Yes, all tables are traversed in reverse due to letting programmers decide how things work in the beginning.

I should have understood that being a programmer myself 

I hit the motor with a timing light and cylinder 1 was 120 degrees out, so thanks for the assistance, this has SOLVED it for anyone who might have similar issues:
- filling in new tooth reference table (00, 40, 20)
- changing order of ignition outputs (33, 34, 35 to 35, 33, 34)

now 1.1.81 firmware is running, looking forward to setting up the new acceleration system (which has previously been giving me problems with my combo of big injectors and ali flywheel)