PDA

View Full Version : OS 09381344 - Trying to perform Calc.MAFT



ticker
September 5th, 2023, 12:39 PM
Background:
This is a stock 2000 5.7 LS1 with a 4L60E in a '58 vette chassis. The only modifications are:
1) 3" exhaust
2) Modified intake tract
3) 5 wire MAF replaced the original 3 wire MAF (the aftermarket harness came wired for a 5 wire).

The MAF Sensor Calibration (B5001) was modified with the values from a stock 5 MAF sensor.

The car drives okay under 40% throttle, anything beyond that it starts to fall flat and break up as if it's running rich.

Is there more that I am overlooking with the few modifications I described above. I anticipated the car to run fairly well without the need of tuning.

All that being said, I'm now looking at what will be needed to perform the Calc.MAFT tuning process with this OS. I chose the Calc.MAFT as it disables the MAF, which I'm curious how that alone may change the behavior of the car. I assume that disabling the MAF will 'fail the tune' based on the MAF DTC and force the tune to use the VE instead ?

First thing the Calc.MAFT process mentions is the OS needs to support GM.VETABLE_DMA in units "g*k/Kpa". What I see with this Operating System is VETABLE_M which is in units 've'. Will VETABLE_M work in it's place ?

ticker
September 5th, 2023, 12:48 PM
Also looking for some insight as to why I'm not getting any data for EFILive V2 AD1 when trying to log INNOVATE LM2 analog WBO2 output into the EFILive analog 5V inputs. Testing voltage with a volt meter at the orange connector coming into the bottom of the EFILive V2 shows 5 volts. Nothing shows up in the datalog under AD1 ?

joecar
September 5th, 2023, 03:46 PM
Can you flash the original factory tune that goes with this engine/trans? Or you could flash in the stock 2002 F-car 12212156 factory tune.

joecar
September 5th, 2023, 03:47 PM
Have you got all the calc pids from the Calc.MAFT tutorial selected in the scantool?

joecar
September 5th, 2023, 03:49 PM
If you full flash OS 12212156 you will get the pid GM.VETABLE_DMA.

joecar
September 5th, 2023, 03:51 PM
Disabling the MAF requires that the DTC is not ignored in table C6001/6002.

joecar
September 5th, 2023, 03:52 PM
Do you have the LM2 ground connected to the ground pin on the orange connector?

ticker
September 5th, 2023, 09:18 PM
Also, I'm unsure on where to put the calc_pids.txt file with V8.

I assume it might get copied here ?
C:\Users\twada\Documents\EFILive\V8\User Defined PID\calc_pids.txt

I really appreciate the help in getting started with this !!

ticker
September 6th, 2023, 10:44 AM
Can you flash the original factory tune that goes with this engine/trans? Or you could flash in the stock 2002 F-car 12212156 factory tune.

I believe I have the original calibration with the 3 wire MAF settings. This is definitely worth a try for grins.


Have you got all the calc pids from the Calc.MAFT tutorial selected in the scantool?

I do not, there were several that were not available with the 09381344 OS


If you full flash OS 12212156 you will get the pid GM.VETABLE_DMA.

Thank you, I'll have to try and get my hands on this operating system.


Disabling the MAF requires that the DTC is not ignored in table C6001/6002.

Got it, thank you.


Do you have the LM2 ground connected to the ground pin on the orange connector?

I do have I do have Analog2 +/- (Brown/white and Dark Green) connected. Are you suggesting there should be a 3 ground wire ?

ticker
September 7th, 2023, 12:00 PM
Can you flash the original factory tune that goes with this engine/trans? Or you could flash in the stock 2002 F-car 12212156 factory tune.

I just loaded a PCM with a stock 12212156 OS from a 2002 corvette 4l60E using a benchtop harness. I still don't see GM.VETABLE_DMA or numerous Calc.MAFT PIDs from the tutorial. Although within the tutorial they are referenced as Calc.VET PIDs, which is a little confusing ?

Also, I'm still unsure on where to put the "calc_pids.txt" file with V8 and if the file name is still accurate for V8.
I assume it might get copied here ?
C:\Users\twada\Documents\EFILive\V8\User Defined PID\calc_pids.txt

I appreciate your continued assistance as I struggle through this.

ticker
September 7th, 2023, 09:07 PM
I've placed copies of calc_pids.txt in all of the following directories and I still do not see things such as CALC.VET, CALC.MAFT, CALC.SELBEN, etc that are defined within the calc_pids.txt file.

C:\Users\twada\Documents\EFILive\V8\Config

C:\Users\twada\Documents\EFILive\V8\Config\PIDs

C:\Users\twada\Documents\EFILive\V8

C:\Users\twada\Documents\EFILive\V8\User Defined PIDs

I am making an assumption that once I find the proper location for calc_pids.txt I will actually see the PIDS listed in the file within the Scan tool's Calculated PIDs section ? I'm also assuming this file is read when the scan took is launched.

ticker
September 10th, 2023, 08:53 PM
Finally figured out there is a section in the V2 handheld to turn on the A/D PIDs (A/D PIDs = YES/NO). This helped to start seeing the results in the datalog, however the values are whacked out and the calibration process does not seem to be working. AD1 readings will switch between 1325 and 4080 (the low and high voltage values I supplied) and AD2-AD3 are constant 1325, all regardless of the voltage value applied to the ADx pins. Seem there might be a hardware fault?! :-(

ticker
September 10th, 2023, 09:01 PM
It seems the TAQuickness cables are no longer available. Would the following cable work (in addition to an EFILive Serial cable and a NULL MODEM) to try reading the WB02 in through the serial port ? It kinda looks like there is only two wires on this listing. Other posts on here make it seem there should be 3 or even four wires ?

https://www.amazon.com/Innovate-Motorsports-3840-Program-Cable/dp/B004MDXVTI/?_encoding=UTF8&pd_rd_w=yItcX&content-id=amzn1.sym.5f7e0a27-49c0-47d3-80b2-fd9271d863ca%3Aamzn1.symc.e5c80209-769f-4ade-a325-2eaec14b8e0e&pf_rd_p=5f7e0a27-49c0-47d3-80b2-fd9271d863ca&pf_rd_r=DDRVB1XDR9YMDCM045AM&pd_rd_wg=1BRqG&pd_rd_r=32955a61-f4b0-4b32-ae53-63e48936e0bd&ref_=pd_gw_ci_mcx_mr_hp_atf_m

joecar
September 19th, 2023, 05:37 PM
I just loaded a PCM with a stock 12212156 OS from a 2002 corvette 4l60E using a benchtop harness. I still don't see GM.VETABLE_DMA or numerous Calc.MAFT PIDs from the tutorial. Although within the tutorial they are referenced as Calc.VET PIDs, which is a little confusing ?
You may have to do Info->Validate in the V7 scantool.



Also, I'm still unsure on where to put the "calc_pids.txt" file with V8 and if the file name is still accurate for V8.
I assume it might get copied here ?
C:\Users\twada\Documents\EFILive\V8\User Defined PID\calc_pids.txt
calc_pid.txt is fot V7 only.

V8 has a user interface that lets you define the calc pid using syntax that is different than V7.



I appreciate your continued assistance as I struggle through this.No worries.

joecar
September 19th, 2023, 05:43 PM
I've placed copies of calc_pids.txt in all of the following directories and I still do not see things such as CALC.VET, CALC.MAFT, CALC.SELBEN, etc that are defined within the calc_pids.txt file.

C:\Users\twada\Documents\EFILive\V8\Config

C:\Users\twada\Documents\EFILive\V8\Config\PIDs

C:\Users\twada\Documents\EFILive\V8

C:\Users\twada\Documents\EFILive\V8\User Defined PIDs

I am making an assumption that once I find the proper location for calc_pids.txt I will actually see the PIDS listed in the file within the Scan tool's Calculated PIDs section ? I'm also assuming this file is read when the scan took is launched.
V7 calc pids format is Not for V8

joecar
September 19th, 2023, 05:43 PM
Finally figured out there is a section in the V2 handheld to turn on the A/D PIDs (A/D PIDs = YES/NO). This helped to start seeing the results in the datalog, however the values are whacked out and the calibration process does not seem to be working. AD1 readings will switch between 1325 and 4080 (the low and high voltage values I supplied) and AD2-AD3 are constant 1325, all regardless of the voltage value applied to the ADx pins. Seem there might be a hardware fault?! :-(

Please post your log file.

joecar
September 19th, 2023, 05:46 PM
It seems the TAQuickness cables are no longer available. Would the following cable work (in addition to an EFILive Serial cable and a NULL MODEM) to try reading the WB02 in through the serial port ? It kinda looks like there is only two wires on this listing. Other posts on here make it seem there should be 3 or even four wires ?

https://www.amazon.com/Innovate-Motorsports-3840-Program-Cable/dp/B004MDXVTI/?_encoding=UTF8&pd_rd_w=yItcX&content-id=amzn1.sym.5f7e0a27-49c0-47d3-80b2-fd9271d863ca%3Aamzn1.symc.e5c80209-769f-4ade-a325-2eaec14b8e0e&pf_rd_p=5f7e0a27-49c0-47d3-80b2-fd9271d863ca&pf_rd_r=DDRVB1XDR9YMDCM045AM&pd_rd_wg=1BRqG&pd_rd_r=32955a61-f4b0-4b32-ae53-63e48936e0bd&ref_=pd_gw_ci_mcx_mr_hp_atf_m

Null midem cable may work... if it does not, then switch thevTx and Rx wires.

I think RS232 needs 3vwires to function.

ticker
September 20th, 2023, 02:48 AM
That's just it, the log shows 0 volts for every AFR WBO2 PID I could find. Which had me isolating the issue between the Innovate WBO2 and the FlashScan V2 equipment. I had it narrowed down to seeing the proper voltage coming out of the LM2, but never seeing any voltage in the A/D inputs on the Flashscan V2. I had made sure the A/D inputs were set to YES in the V2, made sure the OBDII was getting 12V from the vehicle, as I understand that is necessary for the A/D inputs to work. Still no voltage shown on the V2. I tried going through the calibration process on the V2 handheld and through the EFILive software, neither provided a readable value for the input Volts from the A/D inputs. whether you applied voltage or not, the value stuck at the last value used during the calibration process.

Unfortunately I had to return the equipment back to the owner and let them know my findings.

I wanted to provide an update even though my tuning process has taken a turn away from this.

BTW - It was great to get a response regarding the calc_pids.txt. I was going insane trying to copy that file to all kinds of locations to get it to work, lol.

markemac
April 12th, 2024, 07:40 AM
I have been dealing with the same issue, getting an A:F finally through the serial input, on the V2