PID Scaling

[Beerman]

Is there away scale a PID to display RAW HEX value.

[2002_z28_six_speed]

Usage? Example input and output?

[Beerman]

I've created a file for my 97 Camaro and for example I defined and scaled PID 11E3 Low Res Signal RPM as follows


*PRN- - Parameter Reference Numbers
#Parameter.......................PRN..SLOT........ ..Units................System..............Descrip tion
#------------------------- ---- ------------ ---------------- ---------------- -------------------------------------------------------------
LT1.11E3_LO_RES_SIG_RPM..11E3.UNM-16-922.rpm..................Conditions.........."LOW RESOLUTION SIGNAL RPM"


#Units.......... Low............. High............. Fmt Op Factor....... Offset
#------------ ------------- ------------- ---- - ------------- -------------
#Low Resolution Signal RPM
*UNM-16-922
rpm...............0.0 .............65535.00....... .2.. / -1456.333333. 45.0


Now my question is if I wanted the response from PID 11E3 to give me a value in the range of $0000 to $FFFF how would I do that?

[2002_z28_six_speed]

I think this would be possible but EFI Live doesn't support PIDs in HEX? Nor does it support defining multiple variables/results per pid...

So maybe you will have to convert the number in multiple PIDs?
http://www.webelfin.com/webelfindesign/dechex.html

You could have a PID for each of the 4 places in the hex number. I am thinking about it.

Ugh. Maybe it would be easier to export the log into excel and run the dec to hex command in there for that whole column but excel doesn't suport math on hex numbers.

[Beerman]

I can define multiple variables/results per pid

LT1.119D_BARO_kPa 119D UNM-08-43 kPa Conditions "Barometric Pressure kPa"
LT1.119D_BARO_inHg 119D UNM-08-43 inHg Conditions "Barometric Pressure inHg"
LT1.119D_BARO_VOLT 119D UNM-08-42 V Conditions "Barometric Pressure Volts"


I'm thinking of trying


LT1.FC01_CURRENT_PCM_CALID ........ FC01 PKT-32-902 . ........CALID..... "PCM Calibration ID"

*PKT-32-902
1 LT1.HEX1
2 LT1.HEX2
3 LT1.HEX3
4 LT1.HEX4

LT1.HEX1............8001 . SED-08-80....... . ................. Internal ............. "HEX1"

VAL .......... CODE ....... DESCRIPTION
*SED-08-80
0 ............. 00 ............. 00
1 ............. 01 ............. 01
xxx ........... xx ............ xx
255 .......... FF ............ FF

LT1.HEX2 / 8002 AND SO ON
will this work???

[joecar]

If this is V4 related, do you want this moved to the V4 subsection...?

[Beerman]

No it's J1850 VPW I'm using a V1 Interface and Lc-1's
I started with V5 then V6 and currently V7. Way back when (V6 beta) the idea was you could make your own file for any VPW vehicle.
I got tired of waiting for MXscan and I had played with the idea for a long time.
in the sae generic file I changed VINCONFIG to
VINCONFIG
#VIN Config file
#---------- --------------
# 1996 LT1
........... GM_LT1.txt
# 1997 LT1
........... GM_LT1.txt
where GM_LT1.txt are my lt1's PIDs so I do not load EFILIVES gm_enhanced.prn file.
I made a template in excel that helps me scale the HEX values

[Beerman]

IT WORKS
while playing with that I scaled my TAP Cells to give TPS % instead of cell numbers, now I'm thinking I could do the same for FTC maybe use MAP and RPM boundries and names instead of cell numbers

Also it would be nice if I use J2190 mode $3C along with mode $22 so I could show Trans TAP Cells