PT vs Tiny Tuner; Spark mg/cyl not the same...?

[agrazela]

Screen shot of my Good Fuel Spark (GFS) table on PowrTuner:

Now, same table looking at Eddie's Tiny Tuner on the Web:

On both shots, starting at 80 mg/cyl, the mg/cyl increments by 40 up to 560.

But then the last three rows in PT say: 600, 640, 680 mg/cyl

The same last three rows in Tiny Tuner say: 680, 800, 920 mg/cyl

Which mg/cyl numbers are accurate? 600, 640, 680? Or 680, 800, 920?

 

[Trannyman95]

Maybe something in the spreadsheet in the program is wrong. They both have 16 lines of data and look at the tiny tuner. It jumps up from 560 to 680 instead of to 600-640-680, so the last three rows likely have the wrong number and the PT is correct. Both tables appear identical also

 

[agrazela]

I should update this...

According to Eddie Blattner, who made the TinyTuner as well as the famous "table modifier thingy," L36 .bin spark table progression is as shown in the PT window, L67 .bin as is shown in the TinyTuner window.

PT labels it wrong when opening an L67 .bin, and TinyTuner labels it wrong when opening an L36 .bin.

I dunno what HPT does ???

 

[Sabrewings]

I should update this...

According to Eddie Blattner, who made the TinyTuner as well as the famous "table modifier thingy," L36 .bin spark table progression is as shown in the PT window, L67 .bin as is shown in the TinyTuner window.

PT labels it wrong when opening an L67 .bin, and TinyTuner labels it wrong when opening an L36 .bin.

I dunno what HPT does ???

If that's true, all the more reason to base a F/I build off the L67 bin.

 

[Scimmia]

Looks like HPT labels it the same way that TinyTuner does, with either file.

One thing to note, though, in stock form, the last few rows seem to always be the same, anyway, so it doesn't really matter.