eCtune

I have had this problem since before the update an I just can't seem to get it to work anymore. If i open old datalogging files where I had it working before it will not show the trail now.Any suggestions?

yo have to play through the log, with map trace trail on (in the tuner options you will see a small box go around map trace trail icon in the menu) as you play through it the trace will show up on the maps.

map trail show you where on the map the ecu read

Here's a question.Does it need to be enabled before the log is made for it to work?.I can't get it to work on any new logs but if I look at my logs from march it works fine.I swore I had it enabled last time I made a log too but I can try and see if that's the problem Here's a snapshot of a new log I made on the 26th of this month.No trails Here's a snapshot of a old log from back in march on the 31st.It works fine on this log Here's my settings for both logs Here's the settings under the tuner options tab here's the settings under the options tab

Map trace should always show work Overlay options is how it stores the afr and which conditions

calvin wrote:Map trace should always show work Overlay options is how it stores the afr and which conditions

I think I just solved my problem...Late last month my vss stoped working right so the ecu isn't getting any gear information.Would that cause the problem since in my overlay conditions 0 gear isn't selected? edit: tried that.Still didnt work for the newer logs.

correct... fix vss first.. i'll debug with your log now post cal too pls

something is wrong with your driver your logging interval see data grid is 459mSec. Normally it's 14-25mSec. If i enable parse datalog on load i do see the map trail. But something is really wrong.. eCtune is getting data from ecu way to slow

Im using a xenocron usb cable and driver,could that be an issue? I thought the issues I was having with some of the old logs was just because some of them are back from feburary and march so they are 4-5 updates old. Problem solved for now.I went out and made a new log and it worked fine.It still won't play on some of the old logs but it doesn't really matter as long as it works now Heres a new log I made yesterday with it working.The interval on it is usually between 18-30ms.Here's the cal im on too.

those are better intervals. With moates hardware i get 14-20 ms.. more frames per second more data more to analyze