« previous next »
Pages: [1]

Author Topic: h[1] and h[2] explanation required  (Read 11060 times)

Offline gunni

  • Hero Member
  • *****
  • Posts: 1492
  • BHP: 37
h[1] and h[2] explanation required
« on: April 26, 2009, 06:09:04 pm »
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.
Logged

Offline rob@vems.co.uk

  • Hero Member
  • *****
  • Posts: 3115
  • BHP: 49
    • VEMS Forum
Re: h[1] and h[2] explanation required
« Reply #1 on: April 26, 2009, 06:30:19 pm »
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.

Logged

Offline gunni

  • Hero Member
  • *****
  • Posts: 1492
  • BHP: 37
Re: h[1] and h[2] explanation required
« Reply #2 on: April 27, 2009, 12:43:14 am »
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
Logged

Offline rob@vems.co.uk

  • Hero Member
  • *****
  • Posts: 3115
  • BHP: 49
    • VEMS Forum
Re: h[1] and h[2] explanation required
« Reply #3 on: April 27, 2009, 01:13:59 am »
h[2] is the coil outputs as defined in the pin out chart:
Logged

Offline SierraCos2wd

  • Jr. Member
  • **
  • Posts: 26
  • BHP: 1
Re: h[1] and h[2] explanation required
« Reply #4 on: May 17, 2009, 08:07:44 pm »
where do i find this tables?
Logged
Ford Sierra Cosworth<br />Powered by VEMS

Offline rob@vems.co.uk

  • Hero Member
  • *****
  • Posts: 3115
  • BHP: 49
    • VEMS Forum
Re: h[1] and h[2] explanation required
« Reply #5 on: May 18, 2009, 01:57:29 am »
Quote from: SierraCos2wd on May 17, 2009, 08:07:44 pm
where do i find this tables?

Which tables?
Logged

Offline SierraCos2wd

  • Jr. Member
  • **
  • Posts: 26
  • BHP: 1
Re: h[1] and h[2] explanation required
« Reply #6 on: May 18, 2009, 12:35:11 pm »
h[1] and h[2]
Logged
Ford Sierra Cosworth<br />Powered by VEMS

Offline rob@vems.co.uk

  • Hero Member
  • *****
  • Posts: 3115
  • BHP: 49
    • VEMS Forum
Re: h[1] and h[2] explanation required
« Reply #7 on: May 18, 2009, 05:02:46 pm »
For which engine?
Logged

Offline SierraCos2wd

  • Jr. Member
  • **
  • Posts: 26
  • BHP: 1
Re: h[1] and h[2] explanation required
« Reply #8 on: May 18, 2009, 06:41:40 pm »
A 2.0l cosworth engine. With no cam sync an 18-1 trigger wheel. Hall sensor gt etc
Logged
Ford Sierra Cosworth<br />Powered by VEMS

Offline rob@vems.co.uk

  • Hero Member
  • *****
  • Posts: 3115
  • BHP: 49
    • VEMS Forum
Re: h[1] and h[2] explanation required
« Reply #9 on: May 18, 2009, 08:02:34 pm »
I've never heard of an 18tooth trigger, but going from my example above:
Quote
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)

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 10

you could also try:
h[1]=48 3F 36 2D 24 1B 12 09
h[2]=20 40 30 10 20 40 30 10]

Logged

Offline SierraCos2wd

  • Jr. Member
  • **
  • Posts: 26
  • BHP: 1
Re: h[1] and h[2] explanation required
« Reply #10 on: May 18, 2009, 10:34:15 pm »
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.
Logged
Ford Sierra Cosworth<br />Powered by VEMS

Offline rob@vems.co.uk

  • Hero Member
  • *****
  • Posts: 3115
  • BHP: 49
    • VEMS Forum
Re: h[1] and h[2] explanation required
« Reply #11 on: May 19, 2009, 12:15:50 am »
Logged

Offline SierraCos2wd

  • Jr. Member
  • **
  • Posts: 26
  • BHP: 1
Re: h[1] and h[2] explanation required
« Reply #12 on: May 19, 2009, 12:45:37 am »
are firmware 1.0.73 made for multitooth wheels? Wich firmware can i upgrade to get a better firmware. 
Logged
Ford Sierra Cosworth<br />Powered by VEMS

Offline SamSpade

  • Jr. Member
  • **
  • Posts: 46
  • BHP: 5
Re: h[1] and h[2] explanation required
« Reply #13 on: July 02, 2009, 04:04:11 pm »
Quote from: rob@vems.co.uk 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 wiki.
Logged

Offline PeepPaadam

  • Sr. Member
  • ****
  • Posts: 250
  • BHP: 8
Re: h[1] and h[2] explanation required
« Reply #14 on: July 04, 2009, 12:46:25 am »
Genearlly 1.0.x firmwares don't use h1 table (reference tooth table) and 1.1.x use.
Logged
Pages: [1]
« previous next »