Weird stuff happening since the real 7.3 release

[kp]

I knew I should have left everything well enough alone but decided to clear all the old pre release stuff and put in a fresh new 7.3. I copied the generic.txt file as instructed.

Now everytime I load PIDs into the flashscan cable for black box logging they never come out the same as going in. For example, I'm using the AC pressure sensor to log boost, ever since the 7.3 upgrade no matter what I do if I load the AC pressure voltage and log it comes back as AC pressure kpa/psi - that doesnt work since the calculated pid uses the voltage in a lookup table. I tried loading all new pids a dozen times and it wont 'hold' thr AC pressure sensor voltage, always reads back as the pressure pid. Also sometimes the calculated boost PID that I use doesnt 'stick either, comes back as air mass.

Its getting a little frustrating, does the same thing on fresh 7.3 installs on both my desktop and laptop. Worked 100% perfect before.

[Blacky]

The calculated PIDs problem is caused by the faulty sae_generic.txt that shipped with V7.3.0.

Please make absolutely certain that you have downloaded the sae_generic.txt updated file. AND that you have copied it into the correct location. You must restart EFILive once the file has been copied into the correct location.

Regards
Paul

[Blacky]

Also make sure that any of your own calculated PIDs do not use PRNs in the range $F500..$F5FF. Since that range is used by EFILive for its own calculated PIDs.

See comment in sae_generic.txt:

# Note: the PRN must be in the range $F000..$F6FF which is reserved for
# scan tools. Additionally, EFILive defined calculated PIDs will be in
# the range $F500..$F5FF

Regards
Paul

[kp]

I downloaded and copied that generic.txt file like 5 times exactly where is should be

I can get it to work but have to clear the log, select AC pressure switch volts and calc boost. Then 'preview' the log from flashscan, then 'save as' and it all comes up fine. If I save the BB logs direct there is no way I can get the AC pressure (GM.ACP) changed to the votage (GM.ACPS). If it didnt work fine before I wouldnt complain. Naturally logging from the laptop everything is fine, only when I load the GM.ACPS pid into the flashscan cable it always comes out as GM.ACP and then I'll get an error that since GM.ACP isnt a valid PID then calc boost pid wont work. But if I clear the log, select GM.ACPS and preview, then save as, it works.

All other PIDs, wideband and such, work just fine when programmed into the cable, just the GM.ACPS gets changed to GM.ACP for some reason and sometimes the calc boost pid gets changed into something completely unrealted and random. The address for the calc boost pid is $F500 and it has always worked fine.

I guess I'll clear everything out and try again..

[Blacky]

There is a problem logging either of GM.ACPS and GM.ACP with black-box logging. Both PIDs are defined with the same PRN. They are really the same PID just scaled differently, one is scaled for pressure the other is scaled for voltage. When logging via the PC, the PID name is used so EFILive can identify them apart.
When black-box logging, the PRN is used and since they are the same the PID using the same PRN, the value that is returned will be a "random" choice of the two. ("Random" = depending on the order of the PID names listed inside of the EFILive software.)

The {GM.ACPS} PID will be removed.

That means your calculated PID will need to be changed to use the raw({GM.ACP})/51 function - which will return the sensor's voltage in the range 0-5V.
Note, raw({GM.ACP}) will return a value in the range 0..255 which represents the sensor voltage range 0-5V. Divide by 51 to get the actual voltage.

About the calculated boost PID using PRN $F500. PRN's in the range $F500..$F5FF have always been reserved for use by EFILive in sae_generic.txt. $F500 is used by EFILive for the CALC.CYLAIR PID.
The PRN's used in sae_generic were renumbered starting at $F500 in the latest release. It would explain why it used to work - there may not have been a PID using $F500 previously.

You should use values from $F000..$F4FF for user defined calculated PID.

Regards
Paul

[kp]

Thanks Paul, I'll change everything around and see how it all works.

Kevin

[SSpdDmon]

I've noticed something weird with the scanner too. The 400rpm row cells are filling up when my whole run never goes below 550. I ended up with 28X cell counts in one of the cells because it was jumping in there while I was idling. But, playing back the dashboard, it never goes under 550 rpm. Any ideas?

Depending on how your rpm labels are set up it is probably because of the way EFILive "decides" which column to place the data in.

EFILive used to use the row/col labels as break points, now it uses the row/col labels as the center point of the data.

Assume the rpm labels are:
400, 800, 1200,...

The OLD way:
RPM values from 0-400 would be placed under the 400 col
RPM values from 401-800 would be placed under the 800 col
RPM values from 801-1200 would be placed under the 1200 col
etc
In this case rpm value of 500 would be placed in col 800.

The NEW way:
RPM values from 0-600 would be placed under the 400 col
RPM values from 601-1000 would be placed under the 800 col
RPM values from 1001-1400 would be placed under the 1200 col
etc
In this case rpm value of 500 would be placed in col 400.

Regards
Paul

[kp]

I'm a dumbass when it comes to these calculated PIDs :(

This is what I have, its coming out way off so I'm sure something isnt right here:

"Lookup(raw({GM.ACP})/15,0.02,-29.10,0.35,-25.00,0.77,etc etc)"

[Blacky]

I'm a dumbass when it comes to these calculated PIDs :(

This is what I have, its coming out way off so I'm sure something isnt right here:

"Lookup(raw({GM.ACP})/15,0.02,-29.10,0.35,-25.00,0.77,etc etc)"

To get the ACP voltage (0-5), you should divide by 51 instead of 15

Regards
Paul

[kp]

heh, well that what I get for trying to do this after 3am after a few beers. I could have swore that 15 was a 51 last night :oops: