DMA pids for E38 auto VE

[swingtan]

Hi guys,

I came across this problem yesterday with a late 2007 VE. Here's a break down of what has happened...

• On Monday, I could log all the PCM DMA PID's without problems ( OS - 12619078, CAL - 12619077 ).
• On Tuesday morning, I logged the TCM, again no problems.
• On Tuesday evening, I tried to swap back to logging the PCM and could not validate the DMA PID's. All other PIDS seemed fine and worked as expected. Only the PID's in the E38 section were "invalid".
• I then tried connecting to an older E38 OS, ( OS - 12607218, CAL - 12607217 ) and this worked fine. All DMA PID's were valid.
• Swapped back to the 1261907 OS and no go with the DMA PID's

Here's a clip from the scan tool console.....

06:53:22.391: Disconnecting ...
06:53:22.441: CAN-VPW Bridge Deactived
06:53:22.441: Disconnected
06:54:01.898: Scanning for EFILive FlashScan V2 HAPI
06:54:01.908: Autodetect interface ...
06:54:02.058: CAN-VPW Bridge Actived
06:54:02.078: Current protocol set to: "ISO 15765 CAN"
06:54:02.139: Interface firmware version: 2.5.15
06:54:02.139: Connection to [FSV2] interface is OK
06:54:02.139: Autodetect PCM...
06:54:04.262: PCM not detected.
06:54:04.262: Autodetect ECM...
06:54:04.282: Connection to ECM is OK
06:54:04.282: Autodetect TCM...
06:54:04.312: Connection to TCM is OK
06:54:04.332: Current protocol: "ISO 15765 CAN"
06:54:04.382: Interface firmware model: FSV2
06:54:04.402: Interface firmware version: 2.5.15
06:54:04.422: Interface firmware date: Jan 07, 2008
06:54:04.442: FlashScan serial number: 003653XXXXXX
06:54:04.462: FlashScan license number: 003653XXXXXX
06:54:04.532: Request GM VIN...
06:54:04.662: VIN: 6G1EK54H98LXXXXXX
06:54:04.662: Request serial number...
06:54:04.792: Serial number: 86K172XXXXXX
06:54:04.792: Request hardware number...
06:54:04.792: Hardware: 0
06:54:04.892: Request GM operating system...
06:54:04.913: GM operating system: 12619078
06:54:04.913: Request GM NVM...
06:54:04.933: GM NVM: 12619077
06:54:04.933: Request GM Engine calibration...
06:54:04.963: Request GM Engine diagnostics...
06:54:04.983: Request GM Transmission calibration...
06:54:05.013: Request GM Transmission diagnostics...
06:54:05.043: Request GM Fuel system...
06:54:05.063: Request GM System...
06:54:05.083: Request GM Speedometer...
06:54:05.113: Request GM BCC...
06:54:05.153: GM BCC: YRPS
06:54:05.153: Request GM VAT/IGN Cycles...
06:54:05.183: GM VAT/IGN cycles: 0
06:54:05.183: Request GM oil life...
06:54:05.213: Oil life: 76
06:54:05.213: Query support for stream.01 scan mode...
06:54:05.503: Query support for stream.02 scan mode...
06:54:05.624: Calculating number of dynamic packet ID's...
06:54:06.325: Loading generic configuration file: sae_generic.txt
06:54:06.325: User defined calculated PIDs file: calc_pids.txt
06:54:06.325: Enhanced configuration file: gm_enhanced.prn
06:54:07.466: Request GM VIN...
06:54:07.596: VIN: 6G1EK54H98LXXXXXX
06:54:07.707: Request GM operating system...
06:54:07.727: GM operating system: 12619078
06:54:07.767: Validating PIDs...
06:54:07.887: Validating Modules...
06:54:07.957: Initialising PIDs...
06:54:08.458: Initialising Modules...
06:54:08.458: Ready.

06:54:29.388: Req Current DTCs...
06:54:29.418: Req Pending DTCs...
06:54:31.561: Autodetect interface ...
06:54:31.591: CAN-VPW Bridge Actived
06:54:31.621: Current protocol set to: "ISO 15765 CAN"
06:54:31.681: Interface firmware version: 2.5.15
06:54:31.681: Connection to [FSV2] interface is OK
06:54:31.681: Autodetect ECM...
06:54:31.711: Connection to ECM is OK
06:54:32.743: Request DTCs for "Engine Control Module (ECM)" ($11)...
06:54:34.785: Request DTCs for "Transmission Control Module (TCM)" ($18)...
06:58:10.185: Programming PID GM.ETCTP, into dynamic packet 0[0..1] offset: 0...
06:58:10.205: Programming PID SAE.FUELSYS, into dynamic packet 0[2..3] offset: 2...
06:58:10.235: Programming PID SAE.RPM, into dynamic packet 0[4..5] offset: 4...
06:58:10.265: Programming PID GM.HO2S11, into dynamic packet 1[0..0] offset: 0...
06:58:10.295: Programming PID GM.KR, into dynamic packet 1[1..1] offset: 1...
06:58:10.315: Programming PID SAE.ECT, into dynamic packet 1[2..2] offset: 2...
06:58:10.345: Programming PID SAE.IAT, into dynamic packet 1[3..3] offset: 3...
06:58:10.375: Programming PID SAE.LONGFT1, into dynamic packet 1[4..4] offset: 4...
06:58:10.406: Programming PID SAE.LONGFT2, into dynamic packet 1[5..5] offset: 5...
06:58:10.456: Programming PID SAE.MAP, into dynamic packet 2[0..0] offset: 0...
06:58:10.476: Programming PID SAE.SHRTFT1, into dynamic packet 2[1..1] offset: 1...
06:58:10.506: Programming PID SAE.SHRTFT2, into dynamic packet 2[2..2] offset: 2...
06:58:10.536: Programming PID SAE.SPARKADV, into dynamic packet 2[3..3] offset: 3...
06:58:10.566: Programming PID SAE.VSS, into dynamic packet 2[4..4] offset: 4...
06:58:10.606: Using scan mode: Dynamic

If there is anything else you want me to try, let me know.

Simon.

[swingtan]

I have an update to this.

I was looking through the log I did on Monday and now realise that the DAM PID's I thought were working, were not. For example, I logged {E38.AFRATIO_DMA} and it appeared to work. Looking at the log now shows that the AFR's were between 0.09:1 and 1.34:1, obviously this is not right. I was also logging {E38.OCTSCL_DMA} and it appears to have worked.

Simon.

[hymey]

Simon, Thanks for the info mate, I was getting worried I was on my own with the problems I have been getting.

I have only tried to log validate pids through my V2 scan that has been setup for beta testing.

I thought this is the reason I was unable to select the e38 pids. But turns out other beta testers have been logging the pids on pass through mode.

My car has a .....78 OS and I have installed the latest cal files. I have not tried logging other e38s so I have been unable to test it.

When I did set e38 commanded afr as a pid I got crazy readings on my map log. Like 0.09 as you were experiencing.

Ross or Blacky do you have answers as of yet?

For the mean time I have using my own calc pid LM1 afr/ 14.63. I set my PE table to 1 so basically I command afr of 14.63 through the entire map.

For safety I pull 5 deg timing. After a few logs and autotuning I set my PE table to where I want it and shes all sweet.

Its a bit of a pain but all I could manage for the time being.

I new the motor wouldn't detonate with 18 deg WOT at stoich as Nizpro have been running race engines lean for years for fuel economy reasons.

I have seen pics of a XR6 turbo engine at 15:1 running at full rpms for 10 minutes straight.

Not exactly ideal.It is a little crazy but Simon likes to prove his point and shake the status quo.

[swingtan]

Bump......

Any ideas on this one?

Simon

[GMPX]

Paul had the thought that perhaps these cars were validated prior to EFILive adding in DMA support for the OS's in question, therefore it does not try to relearn the supported PID's.
Has anyone having the trouble tried to force a PID revalidation?

Cheers,
Ross

[swingtan]

Is this the <SHIFT-F2> option in the Scan-Tool ? If so, I tried doing this a few times and it completed successfully. However, the DMA-PID's were still unavailable for this OS. I just had a look at the calibration files for the E38, are 12619078.cal and 12622142.cal meant to be the same ? I ran an MD5-SUM on them and they come up the same....

3f6a71896264434ee52a4bf2c011f7f3 *12619078.cal
3f6a71896264434ee52a4bf2c011f7f3 *12622142.cal

Is it possible that a file got overwritten ?

Just checked the March 8 update...... they are still the same...

08adc896c61d45cb0046559c3af3e5c2 *12619078.cal
08adc896c61d45cb0046559c3af3e5c2 *12622142.cal

[GMPX]

DMA PID's are not defined in the .cal files, they are only related to the tuning tool.
DMA PID's are defined in the gm_enhanced file.
This thread is getting confusing, there is two issues, one can't log any DMA's, the other appears to have bogus readings?
I'll point Paul to the thread to see what he thinks.

Cheers,
Ross

[hymey]

Hi guys,

I tried to validate dma pids with the updated gm_enhanced file. It didn't make any difference. When I replaced it the PC said that the file already existed. So I overwritten it with the new file.

I have no idea what the cause is. Swingtan has experienced similiar problems to me. Although no pids can be validated.

I used the shift plus F2 function. Still the same outcome.

[hymey]

Got the E38 pids to start working. I was able to validate them with the flashscan and cable connected to the laptop.
All other attempts previously had failed even though I was connected directly to the vehicle.

The only change I made was the updated gm_enhanced file for e38 pcm. I had given up and thought I would give it a try today and it worked. So maybe the updated file fixed the problem. Why it took several attempts still has me stuffed. The e38 can be stubborn though.

Thanks Ross and Paul for your help.

Regards

Joel

[swingtan]

Now this is interesting......

I just checked the gm_enhanced.prn file in my 7.5 directory and it was dated 17/09/2007, which seemed a little old. I then checked the file under the V7 directory and it was dated 14/12/2007. So it looks like the issue is that I've managed to mess up and update at some stage. What's the "correct" file we should be using for V7.5 ?

Simon.