Lookup tables for calculations

SPOOLD U · Post by **SPOOLD U** » Sat Dec 13, 2008 2:42 am

I am loving the lookup table feature in ScannerPro, since I have some sensors that are non-linear. However when trying to set up parameters on Tunerpro it's a bitch because I can only do linear calcs in TunerPro. I would like to be able to use a lookup table for value interpretation in Tunerpro as well.

Six_Shooter · Post by **Six_Shooter** » Sat Dec 13, 2008 7:07 am

TP RT does have the ability to use look up tables, look in the editing datastream menu.

SPOOLD U · Post by **SPOOLD U** » Sat Dec 13, 2008 7:27 am

I'm not talking about for datalogging I'm talking about for bin editing.

Six_Shooter · Post by **Six_Shooter** » Sat Dec 13, 2008 11:10 am

SPOOLD U wrote:I'm not talking about for datalogging I'm talking about for bin editing.

You mentioned how you like the look up tables in Scanner Pro, that's a datalogging only program so I thought that would be what you were talking about.

I don't understand the need for look up tables for editing the bin.

Essentially the tables that are there are look up tables, they just convert the binary to hex, or floating point or integer.

Maybe explaining exactly what you are looking to do might help.

The tables are user defined to be saved in the xdf files, number of rows and columns. This only works if that's how the bin is set up though. As an example look at the upper VE table for AUJP and then look at the upper VE table for S_AUJP. The difference to be able to use the extended upp VE table is in the bin file.

Maybe a better example would be the non-linear WBO2 tables used in $59, I think S_AUJP has some of the same WBO2 tables as well. But again, the code needs to be there in the bin file to make use of any of the tables.

SPOOLD U · Post by **SPOOLD U** » Sat Dec 13, 2008 2:11 pm

for variable interpretation. Example, I want to edit a single byte 0-255 on it's proper scaling for a limitation for something, say a temperature to turn a fan on or off. The coolant temp sensor has a S curve rather than linear scaling. So to properly scale the calculated value of this bin location, I require a lookup table. The logger can do this, so that I can properly log the values, I just want to be able to edit the value without physically referencing an outside source to calculate what number to fill in the blank.

Post by **Mangus** » Sat Dec 20, 2008 5:04 pm

Yeah, this is something I've thought about, and has been requested once before. I don't think it will make the initial V5 release, but it's on my list for the V5 series. It's good to know that more than just myself and one other person wants it.

Six_Shooter · Post by **Six_Shooter** » Sat Dec 20, 2008 8:58 pm

Maybe a little explaination on how this is used or why?

I'm still not following how this would be used.

Not a GM need?

Post by **Mangus** » Sat Dec 20, 2008 9:06 pm

For instance, GM OBDI computers have a cylinder select to choose between 4 cyl, 6 cyl, 8 cyl, etc. The values are $80, $C0, and $00 respectively.

Instead of relying on the user to enter the right (rather arbitrary) value of 80, C0, or 00, why not have a lookup table (AKA an "enumeration") instead, where you can assign a string or description to the value:

"8 Cylinders" maps under the covers to $00
"6 Cylinders" maps under the covers to $C0
"4 Cylinders" maps under the covers to $80

The user would select one of those three (in this example) from a drop list.

Six_Shooter · Post by **Six_Shooter** » Sun Dec 21, 2008 7:17 am

Mangus wrote:For instance, GM OBDI computers have a cylinder select to choose between 4 cyl, 6 cyl, 8 cyl, etc. The values are $80, $C0, and $00 respectively.

Instead of relying on the user to enter the right (rather arbitrary) value of 80, C0, or 00, why not have a lookup table (AKA an "enumeration") instead, where you can assign a string or description to the value:

"8 Cylinders" maps under the covers to $00
"6 Cylinders" maps under the covers to $C0
"4 Cylinders" maps under the covers to $80

The user would select one of those three (in this example) from a drop list.

Ahhh.

BTW good example, I had been trying to find a calculation for that, but there doesn't seem to be one.

I see where you're coming from now. I guess I just take it forgranted that I've learned to deal with stuff like that. *shrug*

It would make it nicer for beginners to use something like that, in instances where hex is the only input variable, not many people have found or read your introduction to hex, which BTW THANK YOU for writing and publishing that, it has helped me greatly understand how to manipulate and tune.

ToBeFrank · Post by **ToBeFrank** » Thu Feb 19, 2009 8:51 am

I also want this feature!

SPOOLD U · Post by **SPOOLD U** » Tue Apr 14, 2009 5:39 pm

Mangus wrote:For instance, GM OBDI computers have a cylinder select to choose between 4 cyl, 6 cyl, 8 cyl, etc. The values are $80, $C0, and $00 respectively.

Instead of relying on the user to enter the right (rather arbitrary) value of 80, C0, or 00, why not have a lookup table (AKA an "enumeration") instead, where you can assign a string or description to the value:

"8 Cylinders" maps under the covers to $00
"6 Cylinders" maps under the covers to $C0
"4 Cylinders" maps under the covers to $80

The user would select one of those three (in this example) from a drop list.

While that would be an awesome similar feature, I was more wanting to do it for interpreting sensors that have non-linear outputs. Having both would be pretty sweet.