( I'm viewing this via my phone )
F9 would be the Data tab in the V7 scantool, correct...?
And you're viewing the states/flags of the pid GM.VTD...
IIRC, there are some no-start reason flags in some of the pids GM.STATExx, these may or may not be helpful.
( I can look in the scantool when I get home to my PC )
Last edited by joecar; January 4th, 2016 at 07:12 AM.
From memory, if you are logging GM.VTD .... then VTD-VTD1 (Vehicle Theft Deterrent Fuel Control) will be "No" if VATS is active, and will be "Yes" if VATS has been disabled (patched).
Update, Hey Taz, the VTD appears to be the other way around..... I'm 50% certain of that..... hehe
The good news for me is, I have it running, but to do so I jury rigged another VZ style custom manual harness I have made for a customers Patrol, and used the same service #12633238 2010 model E38 with OS 12639270 and did all the mods required, vats patch, full flash etc and as soon as I checked the VTD-VTD1 it read no, which was kinda exciting, and as soon as I hit the key it fired up spluttered a bit, then lost injectors, and came up with P0690 from memory and the VTD1 also changed to yes.
I masked the engine relay code, and flashed that back in, and it now runs good enough for now, with VTD1 remaining on NO.....
I reckon I tried every combo and applicable mask I could find and could not get a murmur or VTD1 NO out of the 2014 OS 12656930.
I havent given up yet on the VF setup, and will work systematically through it and do process of elimination, but the big question is...
Has anyone done the OS conversion yet successfully in a vehicle and not on the bench????
Or is it just easier to use the (tried and proven) VE OS's....
I'm a bit concerned with the VF trans calibration matching the earlier VE OS, even though both are serv# '238's..... any clues???
Thanks for all your replies, and I hope what I'm writing is helpful to all.
Apologies if I wasn't clear in an earlier post - the 12656930 OS was VATS patched and run in our test vehicle in the road with an A6 trans & E85.Can't drive a bench.
. Only DTC's were a new O2 sensor code - to do with response rate of the O2 sensors, and the P0615 Start Relay test.
Thanks gmh308, I will persevere......
Update... problem solved.
After much stuffing around using a 2nd harness and then pinning (almost) everything out, and then doing process of elimination, it turned out to be a broken wire in the cam sensor lead. The crashed donor car took a hit on the front left, and although it didn't cut the harness, it busted the earth wire in the crash.
This was my bad, as I know that these engines will run with the cam sensor unplugged, so I "assumed" this sensor wouldn't be a problem..... wrong.... it will run with 3 wires unplugged but not just 1.... and this is enough to cut fuel and spark....
Thanks for the help guys, much appreciated
I have it all finished and running very nice now
Next step is to get the VF Body Control module to run the TUTD, has anyone done this yet??? and/or got the pinouts from BCM to use.
Or is it just easier to use the VE BCM
No CAM DTC Hooter?
Thanks for reporting back your finding.
No cam code at all gmh308, also it was the signal ground wire.
Weird. Normally if ECM sees no CAM with Crank, DTC pops up. Echoing Joecar, thanks for reporting back your finding. Great to know!
Posting Permissions
Reply With Quote