It is already in help. If you go to Fn 1 it will show.
1 Like
Ah thank u. Exactly what i was looking for 
1 Like
Hi,
I have an EMU Black in an Audi TT with a de-stroked R36 VR (2.8 crank), with a GT3584RS turbo, and water/air intercooler. The car runs E10 fuel. Its my daily driver car and it is a hoot to drive with around 450hp.
I normally tune Haltech ecu’s, and have a couple of suggestions I’d love to see you bring over to the EMU Black software.
Fuel correction for Air Temp needs another axis for MAP.
The AutoTune map doesnt update in realtime. I have to close it and open it again to see the recorded values. Other than that its pretty great.
I’d love to see a long term knock table RPM/MAP that records knock number and correction. Its a faster method to review the data rather than playing back the log on scope view and watching the load point move in the ignition table.
Haltech records a long term fuel trim and long term knock trim tables in the ECU, and apply them constantly based on constraints put in place. You can also apply them to the base table, reset and have it continue perfecting the map. While no substitute for dyno tuning, its great for sorting out the low end tune of a car.
Cheers,
Ian
6 Likes
Please add a wheel slip table to the center diff control. Also a pump bleed button would be great. This would be a huge help.
See below for the Haltech Attesa Wheel Slip Table.
Hi
With newer V2 or V3 Firmware it is possible to get at a TT MK2 Oiltemperature over OEM Sensor. With same Firmware at a Audi S3 8L this does not work. Could that be implemented? Use of OEM Sensor is always a pleasure.
We read this data from CAN stream (PQ35).
I’m not sure how it is connected in 8L model.
I will add Atessa option to diff control as well as bleed switch.
1 Like
Why do you need MAP for this table ? Normmaly IAT correction is calculated by the internal fueling algorith. Do you want to alter this only with the high load/ boost ?
The autotune tables are generated when you select Tools / Autotune and press ok.
I can add a shortcut for that to regenerate with the last set parameters.
But I can see that the tables refresh immediately. Can you give me more details.
I’d love to see a long term knock table RPM/MAP that records knock number and correction. Its a faster method to review the data rather than playing back the log on scope view and watching the load point move in the ignition table.
Thats good idea to make it in the same way as autotune. I added this idea to to do list.
Haltech records a long term fuel trim and long term knock trim tables in the ECU, and apply them constantly based on constraints put in place. You can also apply them to the base table, reset and have it continue perfecting the map. While no substitute for dyno tuning, its great for sorting out the low end tune of a car.
We have such functionality in EMU PRO. In Black there is not enough memory resurces for that 
2 Likes
Here’s how Haltech does the Attesa bleed mode which is nice.
“When pressed in software, ECU checks for 0 engine RPM, then pulses AWD solenoid 1s on, 2s off for 15 seconds. Pump pressure switch and pump output should work as normal. After 15 seconds, bleed mode disables and button must be clicked again to repeat the process.”
Is there a reason coolant fan PWM output is limited to 100hz but PWM1 and PWM2 are not? I need a minimum of 110hz to turn on my brushless fans. Can this be added to the drop down?
2 Likes
Yes, there is a software limitation. You can use PWM table and higher PWM frequency to control CFan.
You can use Coolant fan settings to define min temeprature and CAN - BUS as an output.
Then you can create function that activates PWM table when the Coolant fan is active.
That give you the full functionality of coolant fan.
Yes. And then make your PWM table that the higher load and higher CLT the higer DC
Hi Jadzwin_ECUMASTER.
To follow up on your follow up…
My thoughts on the fuel correction for Air Temp vs Map is as follows. While I understand the ECU fueling algorithm does account for air temp, I feel it needs some adjustment.
My reasoning is that should I setup an autotune to log and suggest corrections to my base map and I drive into work in the morning in 25 degree air temps, my low speed/cruise load points are normally round 55-65. However later in the day when ambient temps kick up 5-10 degrees, without changing anything, the ECU wants to suggest 65 to 70.
Yes, I have the engine up to temp before starting the logging/autotune session. I am using a water to air intercooler. My intake air temps in the morning are around 27-30 degrees max, and in the middle of the day driving in traffic etc, they are around 38-40 degrees c. Air temp sensor is pre throttle body, and silicon rubber isolated from the intake so it doesnt heatsoak.
What this means is that I have a choice with the current tuning options. I can tune it in the middle of the day, and have it run a little rich in the mornings. Or if I tune it in the mornings and have dead spots before it transitions into boost.
Regarding the Autotune map, having a button on the toolbar to re-fresh/recalc what it has learned would be great. Something next to the Help button would be idea.
Really looking forward to seeing what you can do with the knock table.
Use IAT correctioon )
why not using ego correction?
1 Like
Already have IAT correction in place, but it compensates too much for when map >100kpa.
Already using Lambda correction. But relying on O2 correction to fix this is like running someone else’s base map and crossing your fingers that the car will drive nicely. Lambda corrections are for minor adjustments, not for correcting big holes or fat spots in the base VE map.
If it happens on low load, that could be cause by the sensor heat soak. Try to play with the charge temp table.
1 Like
(This is an automatic translation by Google)
My vehicle also has a turbocharged engine, but the IAT change range is large so I thought it would be impossible to make any corrections.
In my case, I added AmbientTemp and placed it in a location not affected by the engine or sunlight, and am currently testing it with corrections over a narrow range.