timing on table doesn't match log file

S.Bretz · Post by **S.Bretz** » Wed Jan 07, 2015 5:40 pm

I started driving the car around a bit to tune the fuel table a little better and noticed that autotune was filling in an area pretty heavy so I turned on the datalogger today and noticed something strange with the spark advance recorded in the log file.

Look at the two high rpm spikes/protion of the log file. The timing shows its around 30 degrees around 13psi, but the spark table 1 shows the tracer point going between 16-20degrees. I checked all my other settings to make sure I don't have anything other settings ramping up timing (but I may have missed something) and I don't see why its recording timing that far advanced. When I left work today, I pulled up the timing calc window to make sure... the only things I see a reading other than zero was for the FFS, spark 1 and the base stock adv gauge.

I did notice that the timing seems to be right around the sum of adding spark table 1 and spark table 3 with the almost 1 degree retard from the flex fuel sensor reading. BUT I am not using dual tables at ALL. All the dual tables are turned off and the conjecture doesn't hold up in other areas of the rpm range/datalog file.

I'm using ts 2.6.04 with MLV 3.4.03 (both the lastest stable releases)
I attached the msq I had in this morning and the log file I recorded. I had to zip the mvl file.

Edit: Firmware MS3 1.3.3

S.Bretz · Post by **S.Bretz** » Sat Jan 10, 2015 10:51 am

After some more datalog reviewing, I see that the ignition load goes up to a max of 99.9kpa in the datalog.

Why is it not reading over that value? Max pressure as recorded at 194.4kpa.

Post by **jsmcortina** » Sat Jan 10, 2015 12:25 pm

Your Ignition Load is set to use the Alpha-N algorithm. So load = TPS%. Hence a max of 99.9% seems reasonable.

James

S.Bretz · Post by **S.Bretz** » Sat Jan 10, 2015 1:35 pm

I checked my MSQ...I'm set for speed density.

What would cause MLV to not show the correct value form the look-up table?

I double checked the y-axis on in MLV and it is set to MAP.

S.Bretz · Post by **S.Bretz** » Sat Jan 10, 2015 1:37 pm

Never mind...I found it what you are talking about James in another window.

I'm lucky I didn't blow some stuff up. I surprise it didn't hiss and spit back at me with that much timing.

whittlebeast · Post by **whittlebeast** » Fri Jan 16, 2015 5:29 am

Here is your reported Spark Advance map. This was done using the latest version of MegaLogViewerHD

http://www.nbs-stl.com/mlvhd/MLVHD%20Ti ... togram.PNG

Megasquirt Support Forum (MSEXTRA)

timing on table doesn't match log file

timing on table doesn't match log file

Re: timing on table doesn't match log file

Re: timing on table doesn't match log file

Re: timing on table doesn't match log file

Re: timing on table doesn't match log file

Re: timing on table doesn't match log file