Coolant temp filter problems

Just come back to Auto Tune after a long time away! Happy o see this got fixed! Thanks Justin!

Rob

We have updated the AutoTune so it now filters out coolant temperature below the value for each log file when there are multiple log files opened at once. This is available in v3.4.9 Good stuff. Using old log files and comparing the resulting maps, in a number of cells (both IAP and TPS) the resulting correction is a reduction in the order of 1% to 2%.

Re: Coolant temp filter problems

We have updated the AutoTune so it now filters out coolant temperature below the value for each log file when there are multiple log files opened at once. This is available in v3.4.9

Re: Coolant temp filter problems

Yeah, I definitely agree. That would be the best way for it to work. It doesn't matter if the temp drops lower after this time "in the same log file" as you know the engine is already warmed up. But of course it can't be assumed that each successive log file had a warmed up engine, so engine temp must again be reached for the next log file.

Re: Coolant temp filter problems

Not sure what you mean by keep the filter "always on". I'm assuming you mean as a future feature of the software as I haven't seen this option. I have seen that the original logbox (v1) had in the config file an option to delay logging until: a. time delay has lapsed b. engine is running c. engine coolant temp has reach predefined value Unfortunately on the logbox denso v2 it has a slight change to those options: a. time delay has lapsed b. engine is running c. predefined engine RPM has been reached The first one makes more sense as I'm not about to limit my revs just because engine isn't up to temp. Temperature is what makes the biggest difference as to whether I will want to use the data for tuning or not. I was referring to the autotune filtering, when temp is reached, even if it goes below threshold (time wise) it is no longer filtered. It would be easy to change this behavior or add an option for it. If multiple files are loaded, this should be the default or a low temp mark should be inserted at the beginning of a new file.

Re: Coolant temp filter problems

Currently when the threshold temperature is reached, the filter is disabled and every temperature (even lower than the threshold) is included. A simple fix would be to simply keep the filter "always on", maybe as a configurable option.

Re: Coolant temp filter problems

Does anyone have any answers to this problem. I have come across the same issue myself. Ideally you want large amounts of data to apply to the AT but when I select more than one log file at a time I end up with unfiltered data with low coolant temps despite my coolant temp filter set at the default 80 degrees. Autotune is obviously designed to be used with multiple logs at a time. You can't apply one log and then another and then another without flashing the ECU in between otherwise you're apply the logs in "series" instead of "parallel" and would end up with extreme overcompensations. The original post was over 6 months ago, surely other people have noticed this problem. Is there something I'm doing wrong? Is there an easy way around it without having to flash between every single ride until I'm happy with the tune?

Coolant temp filter problems

Hi, I am having problems with the minimum coolant temp filter. It only works if I open a single log file at a time. If I open multiple log files I get cell adjustments based off of very low coolant temps! Perhaps this is expected behavior, the tool simply concatenates the log files together, so you get the cold temps from the second log file? (as the first log file triggered the min coolant temp filter?) Still I commute to work and back again, so it would be useful to reset the filter at the start of the second log file. See this post for further details: http://www.zx-10r.net/forum/showpost.ph ... tcount=884 Rob

View Topic on the Woolich Racing Forums