I'm logging the Boost and RPM index. Is the first cells in each index 0 or 1
trying to figure out witch cell to make changes to.

 

From the manual:

Table Indexes
The two table index parameters allow you to log the X and Y index into the respective map. This is useful to easily see where to make changes in a table. If the Fuel Table index is checked, you will see two additional parameters being logged, one for the RPM index and one for the boost index. These number relate directly to the rows and columns of the fuel table.

The Timing table index, when selected, will log either two or three parameters depending on the ECU:The load index of the timing table, and one or two RPM indexes. On the N332 ECU, the T-Indx RPM Lrelates to the 13 cells from 0 to 4096 RPM. Values will be 0 to 12. The T-Indx RPM H relates to the 7cells above 4096. Values will be 0 to 6. All other ECUs only have one T-Index RPM parameter representing the full range of the timing table columns.

http://www.pocketlogger.com/instruct...cketlogger.pdf

 

When looking at a log, (and I had my foot off the throttle at that time.) The Boost index will say zero and the graph line will be at the bottom of display. so would you make an adjustment to the cell for -24inHG or disreguard the zero. not sure which cell to adjust higher up in the boost map, not knowing where to start. on many log the MAP will say-15 or -18 inHG so which cell do you change. Been using the bargragh to make fuel changes. maybe the table display would make more sense.

 

Think of it like an x-y axis. I just started from 0,0 and counted the clicks.

0 rpm = 0-1096 rpm
0 boost= 24 in/hg and below

1 rpm = 1096-1500 rpm
1 boost = 24-6 in/hg

16 rpm = 6960 rpm and up
16 boost = 14.7psi and up

(not sure on the exact #s)

Start at the lowest boost/vac cell/map (0) and count each click moving up the range.
From there work your way from the lowest rpm (0) to the rpm logged.

Really hard to explain on a computer...

If you pick these buttons all the way to the bottom, that is cell 0,0.


logging boost and the boost index should show you the correlation between the boost/index.. logging rpm helps too.


Good Luck!

 

thanks Nick,