How do i find out what 'byte #' corresponds to my ac press output on a 93 da2
#1
Race Director
Thread Starter
How do i find out what 'byte #' corresponds to my ac press output on a 93 da2
I am currently datalogging my wideband o2 sensor thru the ac press.
Wideband o2 values show up in terms of ac pressure (when reading datalogs from datamaster).
I then have to convert it, using a linear conversion, to afr.
I am getting tired of converting it. Especially when i am being charged for my time on the dyno. This is an extra step and it slows me down.
I want to use datamasters 'custom data' function to have it show me afr. In order to do this, i need to know the 'byte #' in the code, that ac pressure is displayed on
Does anyone know what byte # is used for the a/c pressure?
Wideband o2 values show up in terms of ac pressure (when reading datalogs from datamaster).
I then have to convert it, using a linear conversion, to afr.
I am getting tired of converting it. Especially when i am being charged for my time on the dyno. This is an extra step and it slows me down.
I want to use datamasters 'custom data' function to have it show me afr. In order to do this, i need to know the 'byte #' in the code, that ac pressure is displayed on
Does anyone know what byte # is used for the a/c pressure?
#2
Burning Brakes
Try posting your question on GearHead EFI Forum, you will most likely get an answer there.
http://www.gearhead-efi.com/Fuel-Injection/forum.php?
http://www.gearhead-efi.com/Fuel-Injection/forum.php?
#3
Race Director
Maybe this will answer your question. From the DA2 .ADS file on the TunerPro web site.
http://www.tunerpro.net/download/datastreams/GM/DA2.ads
{
dwItemType =1;
strItemComments =<Comments>;
bSeparator =0;
bVisible =1;
dwUniqueID =1;
btByteNumber =20;
btMessageNumber =1;
dwItemSizeBits =8;
dwOperation =0;
dFactor =1.875000;
dOffset =-18.750000;
strItemTitle =A/C Pressure;
strUnitLabel =PSI;
dwAlarmHigh =255;
bAlarmHighENable =0;
dwAlarmLow =0;
bAlarmLowEnable =0;
iRangeHigh =255;
iRangeLow =0;
iLookupTableIndex =-1;
}
http://www.tunerpro.net/download/datastreams/GM/DA2.ads
{
dwItemType =1;
strItemComments =<Comments>;
bSeparator =0;
bVisible =1;
dwUniqueID =1;
btByteNumber =20;
btMessageNumber =1;
dwItemSizeBits =8;
dwOperation =0;
dFactor =1.875000;
dOffset =-18.750000;
strItemTitle =A/C Pressure;
strUnitLabel =PSI;
dwAlarmHigh =255;
bAlarmHighENable =0;
dwAlarmLow =0;
bAlarmLowEnable =0;
iRangeHigh =255;
iRangeLow =0;
iLookupTableIndex =-1;
}
#4
Race Director
Thread Starter
Maybe this will answer your question. From the DA2 .ADS file on the TunerPro web site.
http://www.tunerpro.net/download/datastreams/GM/DA2.ads
{
dwItemType =1;
strItemComments =<Comments>;
bSeparator =0;
bVisible =1;
dwUniqueID =1;
btByteNumber =20;
btMessageNumber =1;
dwItemSizeBits =8;
dwOperation =0;
dFactor =1.875000;
dOffset =-18.750000;
strItemTitle =A/C Pressure;
strUnitLabel =PSI;
dwAlarmHigh =255;
bAlarmHighENable =0;
dwAlarmLow =0;
bAlarmLowEnable =0;
iRangeHigh =255;
iRangeLow =0;
iLookupTableIndex =-1;
}
http://www.tunerpro.net/download/datastreams/GM/DA2.ads
{
dwItemType =1;
strItemComments =<Comments>;
bSeparator =0;
bVisible =1;
dwUniqueID =1;
btByteNumber =20;
btMessageNumber =1;
dwItemSizeBits =8;
dwOperation =0;
dFactor =1.875000;
dOffset =-18.750000;
strItemTitle =A/C Pressure;
strUnitLabel =PSI;
dwAlarmHigh =255;
bAlarmHighENable =0;
dwAlarmLow =0;
bAlarmLowEnable =0;
iRangeHigh =255;
iRangeLow =0;
iLookupTableIndex =-1;
}