Hey all,
Thanks for the help so far with MTRacing's Camaro project. Being Mike's faithful helper boy, I am trying to sort out some things I've experienced and read re: h[2].
1.0.73 was installed as downloaded from vems.hu site.
We are setting up for wasted spark first, later COP, and have outputs selected so that dual output can be set to the correct combinations per his engine, allowing simple changes to allow us to get COP working.
In simple terms, I believe that h[2] is just the ignition outputs, sorted by firing order, read from right to left. Correct me if I'm wrong.
What I've experienced is that when setting h[2] values with MegaTune 2.25 is that it generated h[2] values that don't correspond to the logical ignition outputs, values like 53 and 72 (iirc, sorry I don't have an example since both Mike and I are away on business travel at the moment).
What further confuses me is the MT page under Advanced...something like "h[2] outputs that must be set to 0." What I learned here is that (despite our current trigger problems) the first set of values must be set to "Ign" (vs Stepper), and the second set must all be 0. I really have no idea what all this is for...any insight is appreciated.
Does this have anything to do with bits 0:2 and bit 7? What do these define/do?
Also, I read here
http://www.vems.hu/wiki/index.php?page=MegaTune the following:
[VemsMT1.0.73] - Full package with firmware 1.0.73 both 12x12 and 16x14 table support. The vems.co.uk zip has an error in the vemsv3.ini for the ignition outputs (h23 = h22), fixed in this vems.se zip.USE WITH CAUTION
NOTE: if upgrading from 1.0.53 or older you will need to type this in by hand
Manttg20h00g21h00g22h00g23h00g24h00g25h00g26h00g27h00mcsbyeWe have not entered that string yet...is it necessary with 1.0.73 from the vems.hu site? Could that be why I don't see certain ignition LEDs fire when a simulated trigger input is applied?
Thanks, and thanks for your patience with a noob.
Ron
