Can anybody direct me and others to an exact way to fill in these tables in regards to any trigger.
I.e a universal way to choose the right numbers that go in the cells.
h[1] is the trigger tooth pattern
h[2] is the corresponding ignition patten
The best explanation is an example or two.
A four cylinder engine with a 36-1 trigger, will trigger every 18 (36/2) teeth so the 18 is converted to Hex: 12
h[1]=00 12 00 12 .. .. .. .. every 18 teeth
h[2]=20 40 30 10 .. .. .. .. firing order 1, 3, 4, 2
(Remember that the count starts from the highest point and counts down)
A six cylinder engine with a 36-1 trigger, will trigger every 12 (36/3) teeth so conver 12 to hex: 0C
h[1]=00 18 0C 00 18 0C .. .. firing on teeth 12, 24, 0 (we go back to zero on count of 36)
h[2]=60 30 50 20 40 10 .. .. firing order 1,4,2,5,3,6
What I dont understand is the filtering functions.
Stupid hex has no business being in the user interface.
it should just be teeth.
What are the numbers representing in the h[2] table? , 20 40 30 10
h[2] is the coil outputs as defined in the pin out chart:
(http://www.vems.co.uk/VEMSUserManual/ECConnectorsOut.png)
where do i find this tables?
h[1] and h[2]
For which engine?
A 2.0l cosworth engine. With no cam sync an 18-1 trigger wheel. Hall sensor gt etc
I've never heard of an 18tooth trigger, but going from my example above:
QuoteA four cylinder engine with a 36-1 trigger, will trigger every 18 (36/2) teeth so the 18 is converted to Hex: 12
h[1]=00 12 00 12 .. .. .. .. every 18 teeth
h[2]=20 40 30 10 .. .. .. .. firing order 1, 3, 4, 2
(Remember that the count starts from the highest point and counts down)
18-1 will trigger every 9 (18/2) - in hex 9 is still 9.
So thats teeth 9, 12, 1B, 24, 2D, 36, 3F, 48...
In the first instance try:
h[1]=00 09 00 09 00 09 00 09
h[2]=20 40 30 10 20 40 30 10you could also try:
h[1]=48 3F 36 2D 24 1B 12 09
h[2]=20 40 30 10 20 40 30 10]
sorry but i dont understand where i should put those values in ???
Its a 18-1 wheel because it was a 36-1 wheel an the hall sensor couldnt read the tooth when they was so close to each other so i took a grinder an cutted evry another tooth. if you see :)
I use 1.0.73final firmware.
Some other questions.
What is this meens and what should i have in her:
Angular width of tooth?
Angular width of missing tooth?
Crank min, period (usec)?
Afterstart durations, number of engine cycles?
MAT dependent retard? its stands enable to me. Will it says that the ignition will retards when the inlet air temp becomes too high?
And when i drive in normal speed around 2k rpm, the car starts to cut when i dont have more than 5-20% throttle angel. With no boost. What can be the failure? It comes only when i drive easily. When i have 100% throttle the it doesent happend. Or if i are above 2,5rpm with little boost.
1.0.73 doesn't use h[1]
Angular width of tooth and missing tooth:
http://195.159.109.134/vemsuk/forum/index.php/topic,574.msg5909.html#msg5909
Crank min period:
http://195.159.109.134/vemsuk/forum/index.php/topic,75.msg598.html#msg598
Afterstart Enrichment:
http://195.159.109.134/vemsuk/forum/index.php?topic=36.0
MAT dependent retard:
http://195.159.109.134/vemsuk/forum/index.php/topic,345.msg3426.html#msg3426
All of these links - were found using the Search function
http://195.159.109.134/vemsuk/forum/index.php?action=search
are firmware 1.0.73 made for multitooth wheels? Wich firmware can i upgrade to get a better firmware.
Quote from: [email protected] on May 19, 2009, 12:15:50 AM
1.0.73 doesn't use h[1] ...
Which firmware versions use and don't use h[1]? Can't find the info in the GenBoard/UnderDevelopment/FirmwareChanges (http://www.vems.hu/wiki/index.php?page=GenBoard%2FUnderDevelopment%2FFirmwareChanges) wiki.
Genearlly 1.0.x firmwares don't use h1 table (reference tooth table) and 1.1.x use.