smitty

I have an fc with a haltech e8 that I got so annoyed with I just pushed it to the back of the garage. I am starting to remember why. I think my problem is with my ignition trigger. I am unable to get the timing zeroed. I do get a steady rpm reading during cranking but with the timing light the timing seems to jump around. With the filters set at zero I was getting trigger counts with the car not running or even cranking.I turned the filters up to 2 that did seem to clear up the false triggers. My ignition settings are Distributer mode-falling-falling-constant charge-constant charge. How do you turn on the toggle for the trailing?
Is There a formula to make sense of the trigger data log ?
Any help would be appreciated I am at the end of my knowledge.
Dave Smith

C. Ludwig

iTrader: (27)

Log trigger at last home. It should be 12 at all times. If it is not, you have a trigger issue. If it is, you have issues else where.

If trigger at last home is 12 consistently, ensure that the timing is zeroed. Once that is done, any other issues would be fuel and ignition calibration only.

smitty

thanks for the info on the trigger. I'll double check it tomorrow. Is it possible for the program to get corrupted ? I loaded one of Claudio's maps and made the needed changes. The timing zeroed right up and the crazy rich condition I couldn't seem to remedy is gone. I compared his program to mine before I loaded it and other than some minor mapping differences they looked the same. At this point I am just glad I am heading in the right direction.
Dave

bumpstart

yes e8 has an occasional bug where it can corrupt the fuel maps and put big bands of useless info in them

thinks it is a bug that occurs during jumping whilst cranking with very low battery , or when a transfer or shutdown is interrupted

easily fixed in seconds by just rebooting a master saved copy of your tune


the other bug that comes is when you build your base map from a different firmware version than the one on your machine
this can lock out some choices and make some features unusable

build from the initial base map that comes in the setup files for your firmware version.. to that you can import any haltech fuel or ig map
though you must double check it has scaled correctly across your x and Y axis
( especially if you are using custom scales )


setting up the timing itself isnt so hard.. make sure you have the timing locked
( -5 for FC pulley ,, although you can remark the pulley for a 10 BTDC and use 10 BTDC as your locked value )
.. each trigger tooth number pushes the timing mark around 30 degrees
and trigger angle numbers are the 30 degrees between tooth events.. and to give the ecu a chance to advance the ignition timing,, are set in a window between 60 and 90 degrees

so 10 tooth 60 ( 360 ) .. is the same as an 9 tooth 90 ( 360 ) etc


so by manipulating the numbers,, with timing locked at -5 ( for FC pulley ) you get the timing mark to align with the pin , without having to constantly redrop the CAS

smitty

Things are making so much more sense now. I am sure I have cranked with a low battery. I must have saved the corrupted file to my laptop and just kept reloading it. I have upgraded the firmware and upgraded to Halwin 1.89 from 1.62 so should I start from scratch to avoid any conflicts? At this point it really is not much of a problem. The only question I still have left is setting the toggle for the trailing. Does that just happen when you select distributer mode or am I missing something?
thanks again
Dave

bumpstart

select distributor mode for s4 coil toggle..

open the 1.89 base file and load the base map, name it,, then import the fuel and ig maps from what ever copy just got you up and running .. then build from there

smitty

Thanks for all of the help so far. I created a new program using my default from 1.89. I imported the maps. My only choice was import E 11 maps that's ok ?
I am now trying to get my no load tuning sorted out. My o2 numbers show way lean. My ear doesn't agree with what I am seeing. Looking at the end of injection map starts out at 320 and goes up from there well past 360. Is there any reason this map should exceed 270 ?
Thanks Dave