Pid Creation / Calculated pids

[joecar]

lookup()

Syntax: lookup(x,a1,a2,b1,b2,…,c1,c2)

Arguments:
x: a numeric expression
a1,a2,b1,b2,…c1,c2 is a list of pairs of values.

Return value: The value of the second value of the pair whose first value is less than or equal to x.

The list of value pairs must be sorted on the first value of each pair.

[Gelf VXR]

Hi Gelf VXR,

What does B5101 look like...

If it's 1-dimensional, you can create a calc pid using the lookup() function, and then a second calc pid to calculate the looked value divided by SPARKADV.

Here is an example (ignore the part about cal_link.txt): showthread.php?t=8142&highlight=lookup

Cheers
Joe

Unfortunately its a 3d map, Data = Spark, Row = RPM and Column = g/cyl

[Gelf VXR]

lookup()

Syntax: lookup(x,a1,a2,b1,b2,…,c1,c2)

Arguments:
x: a numeric expression
a1,a2,b1,b2,…c1,c2 is a list of pairs of values.

Return value: The value of the second value of the pair whose first value is less than or equal to x.

The list of value pairs must be sorted on the first value of each pair.

My head hurts lol

[redhardsupra]

yea but wouldn't it be nice if there was some DMA or automated lookup procedure that could look up values for ANY table?

[joecar]

x is the "lookup" index pid.

a1,a2 -> when you lookup a1, you get back a2
b1,b2 -> when you lookup b1, you get back b2
c1,c2 -> when you lookup c1, you get back c2
d1,d2
e1,e2
.....,....
x1,x2
.....,....

a1,b1,c1,d1,e1,f1,...x1,... must be in ascending order

lookup() compares x to each of a1,b1,c1,d1,... it stops when it finds the matching/exceeding value;


Example:

lookup({GM.RPM}, 1000,1, 2000,2, 3000,3, 4000,4, 5000,5, 6000,6)

if {GM.RPM} is 3000, then lookup returns 3.
if {GM.RPM} is 4500, then lookup returns 4 (or actually 4.5... I think it interpolates).

[jfpilla]

Are we saying that B5104, b5122 can be logged seperately from B5101? The C5 tables that correspond always log based on what condition exists.

[redhardsupra]

is the interpolation in the lookup function done using the same exact method that the ecu uses?

[Gelf VXR]

x is the "lookup" index pid.

a1,a2 -> when you lookup a1, you get back a2
b1,b2 -> when you lookup b1, you get back b2
c1,c2 -> when you lookup c1, you get back c2
d1,d2
e1,e2
.....,....
x1,x2
.....,....

a1,b1,c1,d1,e1,f1,...x1,... must be in ascending order

lookup() compares x to each of a1,b1,c1,d1,... it stops when it finds the matching/exceeding value;


Example:

lookup({GM.RPM}, 1000,1, 2000,2, 3000,3, 4000,4, 5000,5, 6000,6)

if {GM.RPM} is 3000, then lookup returns 3.
if {GM.RPM} is 4500, then lookup returns 4 (or actually 4.5... I think it interpolates).

Ok, got that, can it not look up a1, a2, a3? Where a1 is the Row, a2 is the column and a3 is the the cross reference value?

[joecar]

lookup() only works with 1-D data.

[redhardsupra]

feature request: lookup2d