randy4762

I don't know if I can properly explain what I want to try to do. When I tune other after market ecu's(such as Autronic), the software can correlate exactly the cell you need to adjust. What I am saying is that while running the engine or parsing a log file, if you go to the VE table for example, the cell will be highlighted from the same spot (rpm vs. map, etc..). So live tuning is even better because while running, the software will constantly update the cell it is using to make the calculation. So you can just use the throttle to stay at a particular site and tune it (easier said than done). Some call this steady state tuning. Even when using the log files, it makes it really easy to find a trouble spot. There is no guessing what cell you are in. Because the software uses interpolation, that is how the ecu comes up with the calculations for values that lie between mapped cells. Interpolation is why it is hard sometimes to adjust the proper cell.
Is this beyond the capabilities of TunerPro? Or, could a revision be made to have the software work like the aftermarket stuff? I have been able to rough in a tune on an Autronic(within5%) within 4 hours of dyno time, and all the fine tuning was done at the track with logging on a test and tune day. I seemed to notice that alot of the best ecu's are Aussie designed, anyone else notice this?
Thanks,
Randy

DENN_SHAH

iTrader: (1)

i don't run a MAF system so im not sure if TunerPro does it with them. but with a speed density setup you can use data tracing to see where in the VE tables its running at.

https://www.thirdgen.org/forums/diy-...tatracing.html

randy4762

Thanks for the info, I haven't been able to get the data tracing to work yet.
I will work on that today though. That link helps out alot.
Randy

DENN_SHAH

iTrader: (1)

without that link i would probably still be trying to get it to work right.
even after reading it, it still took me some time to figure out how to get it going.
i do have a small problem with it, every time i close TunerPro, i lose the association to an item. i know its something im doing wrong but it only takes a few seconds to fix it so it isn't a big deal for me.
if you don't know it yet, you can also use data tracing when working your timing tables too.

randy4762

I got it to work with one exception, the RPM will move but the MAP won't.
I think the problem is that the MAP columns are labeled as kpa, while the
MAP is output from the datalogs as volts! Is there any easy fix for this?

randy4762

I was thinking about editing the aldl def to change the output to kpa. I just don't know the conversion factor to use.

DENN_SHAH

iTrader: (1)

what ECM & mask are you running?

randy4762

7747 and $42

randy4762

I think this is what I wanted?

randy4762

Okay, I made all changes. Still no change in being stuck on the 30 kpa column. I then completely shut down TP and restarted it. Now, it is stuck in the 100 kpa column. Note that my rpm's do change with the log file is playedback.
Also I never did figure out why my coolant temp is reversed (starts out hot then gets cold). I researched the problem to no avail.

DENN_SHAH

iTrader: (1)

im pretty sure it has to do with the MAP being output in volts instead of kpa.
im not sure if what you posted from RBob would work for you, its from the 8D mask.
there isn't much to the 747_42 ads i tried, you may be able to find another ads file at
http://www.moates.net/info_pages.php?pages_id=14 or
on http://www.diy-efi.org/ that will work.

RBob

iTrader: (1)

The same MAP ADC to KPa conversion as used on $8D will work on $42.

The CTS conversion is difficult. It is the inverse (why your CTS reading is hot with a cold engine). It also needs to be a table lookup. The CTS ADC value to degrees C or F conversion ends up being an 'S' shaped curve.

RBob.

randy4762

Funny thing, it seems to work on the SA table just fine?

randy4762

Thanks RBob. I always like it when you chime in. Does anyone have a coolant temp look table they would be willing to share. I know it is alot of work to make one accurate. I finally figured out the data tracing problem.
The column values have to correspond to the range you are tracing.
For example, my rpm in the xdf was listed as "4" for 400 and so on.
I just relabeled all of them and bingo, I got that warm fuzzy feeling of accomplishment that you get. Although I can't thank everyone enough for the help.

Everyone, Randy

Mangus

Note to self: Make tracing work better and easier in next major release.

Check!

randy4762

Nobody should be unhappy with all of the work you have done. Everthing in life can be improved upon though. If nobody strives for more where would this world be, probably still using vacuum tubes and the Univac...LOL

Mangus

That's the idea. Tracing will be implemented more generically, making it much easier to set up (in fact, in most cases it will be automatic), etc.