Haltech Auotune update!!!!!!!!!!!!!
Compliments Claudio.
E-8
http://www.tuningtechnology.com/Down...1_s2v11B32.zip
E-11
http://www.tuningtechnology.com/Down...1_s2v11B32.zip
The above firmware does not support 'Autotune' as of yet.
1. Overall Ignition trim
2. On-board datalogging can be activated by going over a certain RPM
3. Added dig out - alternator control
4. Added a user definable hysteresis on the RPM parameter of the decel cut
5. decel cut now looks at the throttle deadband to determine if off throttle
instead of the hard-fixed 0.2%
6. FuelTmpSensorCal, GasPrsSensorCal, SuspensionTrvlSensorCal,
ExtMapSensorCal, OilPrsSensorCal and closedLoopBoostMap2 have been shifted
by a word because they overlapped with the CLBC start duty map
7. CAN comms for AIM Dash
8. Digital inputs can be set on the analogue inputs
9. Closed loop O2 has a 3D map it can target
10. Variable Cam Timing
11. Add Subaru MY06 Trigger Type (with VCT)
12. Coolant correction maps (2d & 3d) was:
0 - 200 (raw) = 0 - 100% correction
is now
0 - 250 (raw) = 0 - 250% correction
resolution has changed from 0.5% to 1% because of this. Changed was
made because it was felt 100% correction was not enough
13. Fuel pump can be inverted
14. Detail 2 of engine data is being used for VCT
15. added support for late model Toyota 36 -2 motronic with 3 pulses on the
cam (for VCT)
16 .add a new o2 heater output O2 Heater Control. outputs a 16Hz 50 duty
cycle signal until RPM reaches 4500 or TPS is greater than 75%
17. Added a Thermofan output that will out put a duty cycle from 0% to 100%
between two coolant temp values set in the front-end.
18. The stepper position/duty cycle of the idle control will now slowly
decrease between the post start position/duty cycle to the start
position/duty cycle of a time span of 15sec. stops the RPM dropping
rapidly because of the sudden change of positions
19. Intercooler spray input. can work like a normal input or as a momentary
switch. when set to momentary switch the ECU turns the input into an
interrupt. this is because the pulse sent to turn it on or off will most
likely be less then the 200ms sample rate of the dig input function
20. intercooler water spray output (Adv) that looks at load, rpm, tps
coolant & air temp also only works when the input is set to on.
21. intercooler water spray armed output is used when the intercooler spray
input is on. used to turn on the little light on the dash. needed because
the input can be a momentary switch.
22. the point below the target boost level where control starts to happen is
now a settable value
23. Added Ford PIP Trigger
24. Made the air con delay adjustable in the front-end under air con aux
output setup page.
25. Also added this to when the air con output is inverted because it didn't
have the part that checks idle.
26. Oddfire on STD & M24
27. New throttle pumps, completely async. Those 4 maps are gone. TPU for
fuelling had to be re-written to support the async fuel pulses add a little
mini map for the injection times.
28. same air con delay in stepper motor for BAC, the delay from pressing the
button till when the A/C actually kicks in.
29. Cosworth trigger type
30. added a proportional component into the O2 control.
31. added a delay in the O2 controller in the time between when the
controller falls into the boundaries of being able to control till when it
actually starts control.
32. Gave the O2 controller its own operating temp value. Does not use the
one in main setup anymore.
33. min position/duty for idle control now has the aircon offset
position/duty added to it as well when aircon is turned on.
34. Added a second target boost map for closed loop boost control. This map
is selectable in the auxiliary output setup page for closed loop boost
control or alternatively with the map selection digital input.
35. Added the Mazda B trigger. Uses all the same code as Subaru trigger
except for the trigger interrupt function
36. Allowed the use of the Generic 3D RPM/LOAD Map to the oil metering pump.
can now select between the normal 2D oil metering map and the 3D Gen
RPM/LOAD map. Front-end will block the user from trying to use the Gen 3D
map as both oil metering pump and Generic PWM output.
37. There are now two post start maps, one for above operating temp and one
for below operating temp
38. Added a fix for fuel pumps so that any spike in RPM on start up does not
shorten the fuel pump prime
39. stopped BAC from working at 0000 RPM
40. added 6 more values to the engine data protocol specifically so that the
aim dash can display calibrated values for coolant & air temp, manifold,
fuel & oil pressure and AFR. This meant adding a new function that converts
raw values from temp sensors into calibrated values. The other pressure
values used the same as the convert map sensor to calibrated value function
in closed loop boost control.
E-8
http://www.tuningtechnology.com/Down...1_s2v11B32.zip
E-11
http://www.tuningtechnology.com/Down...1_s2v11B32.zip
The above firmware does not support 'Autotune' as of yet.
1. Overall Ignition trim
2. On-board datalogging can be activated by going over a certain RPM
3. Added dig out - alternator control
4. Added a user definable hysteresis on the RPM parameter of the decel cut
5. decel cut now looks at the throttle deadband to determine if off throttle
instead of the hard-fixed 0.2%
6. FuelTmpSensorCal, GasPrsSensorCal, SuspensionTrvlSensorCal,
ExtMapSensorCal, OilPrsSensorCal and closedLoopBoostMap2 have been shifted
by a word because they overlapped with the CLBC start duty map
7. CAN comms for AIM Dash
8. Digital inputs can be set on the analogue inputs
9. Closed loop O2 has a 3D map it can target
10. Variable Cam Timing
11. Add Subaru MY06 Trigger Type (with VCT)
12. Coolant correction maps (2d & 3d) was:
0 - 200 (raw) = 0 - 100% correction
is now
0 - 250 (raw) = 0 - 250% correction
resolution has changed from 0.5% to 1% because of this. Changed was
made because it was felt 100% correction was not enough
13. Fuel pump can be inverted
14. Detail 2 of engine data is being used for VCT
15. added support for late model Toyota 36 -2 motronic with 3 pulses on the
cam (for VCT)
16 .add a new o2 heater output O2 Heater Control. outputs a 16Hz 50 duty
cycle signal until RPM reaches 4500 or TPS is greater than 75%
17. Added a Thermofan output that will out put a duty cycle from 0% to 100%
between two coolant temp values set in the front-end.
18. The stepper position/duty cycle of the idle control will now slowly
decrease between the post start position/duty cycle to the start
position/duty cycle of a time span of 15sec. stops the RPM dropping
rapidly because of the sudden change of positions
19. Intercooler spray input. can work like a normal input or as a momentary
switch. when set to momentary switch the ECU turns the input into an
interrupt. this is because the pulse sent to turn it on or off will most
likely be less then the 200ms sample rate of the dig input function
20. intercooler water spray output (Adv) that looks at load, rpm, tps
coolant & air temp also only works when the input is set to on.
21. intercooler water spray armed output is used when the intercooler spray
input is on. used to turn on the little light on the dash. needed because
the input can be a momentary switch.
22. the point below the target boost level where control starts to happen is
now a settable value
23. Added Ford PIP Trigger
24. Made the air con delay adjustable in the front-end under air con aux
output setup page.
25. Also added this to when the air con output is inverted because it didn't
have the part that checks idle.
26. Oddfire on STD & M24
27. New throttle pumps, completely async. Those 4 maps are gone. TPU for
fuelling had to be re-written to support the async fuel pulses add a little
mini map for the injection times.
28. same air con delay in stepper motor for BAC, the delay from pressing the
button till when the A/C actually kicks in.
29. Cosworth trigger type
30. added a proportional component into the O2 control.
31. added a delay in the O2 controller in the time between when the
controller falls into the boundaries of being able to control till when it
actually starts control.
32. Gave the O2 controller its own operating temp value. Does not use the
one in main setup anymore.
33. min position/duty for idle control now has the aircon offset
position/duty added to it as well when aircon is turned on.
34. Added a second target boost map for closed loop boost control. This map
is selectable in the auxiliary output setup page for closed loop boost
control or alternatively with the map selection digital input.
35. Added the Mazda B trigger. Uses all the same code as Subaru trigger
except for the trigger interrupt function
36. Allowed the use of the Generic 3D RPM/LOAD Map to the oil metering pump.
can now select between the normal 2D oil metering map and the 3D Gen
RPM/LOAD map. Front-end will block the user from trying to use the Gen 3D
map as both oil metering pump and Generic PWM output.
37. There are now two post start maps, one for above operating temp and one
for below operating temp
38. Added a fix for fuel pumps so that any spike in RPM on start up does not
shorten the fuel pump prime
39. stopped BAC from working at 0000 RPM
40. added 6 more values to the engine data protocol specifically so that the
aim dash can display calibrated values for coolant & air temp, manifold,
fuel & oil pressure and AFR. This meant adding a new function that converts
raw values from temp sensors into calibrated values. The other pressure
values used the same as the convert map sensor to calibrated value function
in closed loop boost control.
The software I downloaded has a section for target afr. Does this mean that the autotune function works.
I assumed that there was an autotune function and never bother to ask haltech nor the distributer if this function actually works.
? Any info. Sucks if this does not actually come to be.
I assumed that there was an autotune function and never bother to ask haltech nor the distributer if this function actually works.
? Any info. Sucks if this does not actually come to be.
Joined: Feb 2006
Posts: 2,897
Likes: 2
From: Renton/Bellevue/Seattle WA
Just wondering, if anything new has happened with this? I am about to install my e11v2, and want to make sure I have the best firmware and such.
Thanks
~Tweak
Thanks
~Tweak
We did an auto-tune (more like auto AFR) for Wolf3d.. at the start of it all, it was only log based then became realtime.
i'd love to attach a g-force meter on the car then pipe that data into my software and have a go at the timing map;
i'd love to attach a g-force meter on the car then pipe that data into my software and have a go at the timing map;
The quick tune feature works but I'm still not a huge fan. Even if you want to use it you will need a dyno. You'll have to hold the engine in a given load cell long enough for the ECU to make it's calculations for the proper a/f ratio. This can't be done properly on the street. The quick tune feature won't do anything a compentent tuner can't. It will only make it happen a little faster.
Other than the quick tune feature there isn't much in the 1.82 firmware that's all that attractive. And there are some real bugs in the beta version. I'd recommend sticking with 1.71 until the 1.82 goes to full release.
Launch control works better than the old haltech 2 step, but the bug of it coming on when its not supposed to makes it unusable.
It also did a pretty good job of blowing the guts out of my cat converter right onto the track.
Ive found that some of the bugs (such as the nonfunctional boost control) where due to incompatible firmware.
It also did a pretty good job of blowing the guts out of my cat converter right onto the track.
Ive found that some of the bugs (such as the nonfunctional boost control) where due to incompatible firmware.
The quick tune feature works but I'm still not a huge fan. Even if you want to use it you will need a dyno. You'll have to hold the engine in a given load cell long enough for the ECU to make it's calculations for the proper a/f ratio. This can't be done properly on the street. The quick tune feature won't do anything a compentent tuner can't. It will only make it happen a little faster.
Other than the quick tune feature there isn't much in the 1.82 firmware that's all that attractive. And there are some real bugs in the beta version. I'd recommend sticking with 1.71 until the 1.82 goes to full release.
Other than the quick tune feature there isn't much in the 1.82 firmware that's all that attractive. And there are some real bugs in the beta version. I'd recommend sticking with 1.71 until the 1.82 goes to full release.
Joined: Feb 2006
Posts: 2,897
Likes: 2
From: Renton/Bellevue/Seattle WA
Eeek, all this talking about bugs and things blowing me up really makes me nervous. I got the e11v2 so I could do a lot of the cool things such as launch control, 2 step, and boost control.
Haltech has a few things to do still.
Like allow you to tag aux inputs and outputs. Have the program display what map you are on. Have A/F ratio's displayed in lambda or A/F. Datalogging should also be work on .(Like double click on the datalog sends you to the bar to program?) Also there is so many hang ups thats its not funny. Maybe its just me or vista
Still waiting for the new software version!
Like allow you to tag aux inputs and outputs. Have the program display what map you are on. Have A/F ratio's displayed in lambda or A/F. Datalogging should also be work on .(Like double click on the datalog sends you to the bar to program?) Also there is so many hang ups thats its not funny. Maybe its just me or vista

Still waiting for the new software version!
The quick tune feature works but I'm still not a huge fan. Even if you want to use it you will need a dyno. You'll have to hold the engine in a given load cell long enough for the ECU to make it's calculations for the proper a/f ratio. This can't be done properly on the street. The quick tune feature won't do anything a compentent tuner can't. It will only make it happen a little faster.
Other than the quick tune feature there isn't much in the 1.82 firmware that's all that attractive. And there are some real bugs in the beta version. I'd recommend sticking with 1.71 until the 1.82 goes to full release.
Other than the quick tune feature there isn't much in the 1.82 firmware that's all that attractive. And there are some real bugs in the beta version. I'd recommend sticking with 1.71 until the 1.82 goes to full release.
I think it could be a wonderful feature given Haltech allows the tuner to set the load-holding (time needed at X load to make a change). Now what i'd like to see is someone let us attach an accelerometer to help dial in the timing map (maybe split timing too?);
just the overall idea is exciting and doesn't really need to be Haltech only. Once they create the foundation (rules for making an adjustment) you could almost apply it to any ECU given you knew the parameters (coolant,afr,iat,ve/map,etc).
Yeah and after you've destroyed 4 or 5 engines you might have a pretty good base timing map.
I think it could be a wonderful feature given Haltech allows the tuner to set the load-holding (time needed at X load to make a change). Now what i'd like to see is someone let us attach an accelerometer to help dial in the timing map (maybe split timing too?);
just the overall idea is exciting and doesn't really need to be Haltech only. Once they create the foundation (rules for making an adjustment) you could almost apply it to any ECU given you knew the parameters (coolant,afr,iat,ve/map,etc).
just the overall idea is exciting and doesn't really need to be Haltech only. Once they create the foundation (rules for making an adjustment) you could almost apply it to any ECU given you knew the parameters (coolant,afr,iat,ve/map,etc).
That's what I was thinking. In an engine that is knock limited, and absolutely intolerant of knock, you can't utilize power production to setup a timing map. It'll make more power, or pull more g's out of the accelerometer, right up to the point it breaks.





