Any possibility of adding a map trace option similar to what the power fc has?

Maybe just an extra log entry that listed the map sensor reading and the rpm cell being used for the calculation?

If something similar in functionality to this already exists I must have missed it.

This might make it a bit easier for people to tune their rteks on their own. I find it a bit hard to keep flipping between the view log and then the tune page to make changes.

 

and after reviewing the manual it appears as thought the T-Index values do exactly what I was looking for.

 

I'm not sure exactly what your saying, Oh, gotcha, t-index, I am going to try it out... hmm...

Well it might be easier to review the Logs on the PLViewer on the computer. You can download it here, but you have to have WinRAR(similar to winzip) to unpack it.

Download the Rtek one from here:
http://pocketlogger.com/index.php?pid=utilities

 

yeah I got pocket logger but cause I don't take my laptop out to the car it's hard to know what changes to make but the T-Index and F-Index log values should do the trick

 

So what are T-Index and F-index?

 

Sorry to double post, but also how are they displayed? I am going to check this out as soon as possible...

T = timing

F = fuel

hmmm....

 

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 L relates to the 13 cells from 0 to 4096 RPM. Values will be 0 to 12. The T-Indx RPM H relates to the 7 cells 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.

I don't know why I haven't even tried this...

 

I would have tested this today but I have been running down some huge boost leaks.

 

FWIW, I tried this and came to the conclusion that its just easier to tune/change perameters around boost, rpm and afr values. You could change the specific cells, but what if you step out of those values, then your in bad lands... It might help pinpoint the areas where a map needs work... If we had the web based map interface this could probably be more useful... and possibly an EGT sensor.
Anyway, I'll try it out more, once I get my boost controller installed and fuel pump rewired and other winter modifications.