TDCO limits are +2.50* to -2.50*, as I stated
Also, as I stated, DTC limit is ~ -2.20* for OBD2, less for OBD1
The consensus of moderator opinion, Buddy, is that you need to
a - commit the posted DS4 timing procedure to memory - it is correct in scope and intent, performed with a new TECH2 - the details are fuzzy, but, iirc, GMTDScan Tech duplicated TECH2 function, per Stefan's corrections and updates
b - study it till you get it right - it is correct
c - the problem is you not understanding Diesel technology vs gasser (patooie!) operation, not understanding Diesel injection function, not understanding DS4 timing procedure, all while also trying to learn GMTDScan, and trying to learn that and an afermarket chip - the resulting responses are confusing to all, because you use them to cast doubt on posted information - it is your input that is differing from standard DS4 timing procedures
The 6.5 runs well if the IP is correctly timed - if we determine that GMTDScan Tech functions differently than I've already posted, we can add that to the sticky thread in a separate GMTDScan response, incl differences, if any, encountered with the ENGH chip - same can be done for any other scantool or tune, long as the data is correctly posted - you know: correct decimal placing, correct value signing (+\-), etc and etc.....................
Remember, folks: I am dyslexic, and easily confused..........
Also, as I stated, DTC limit is ~ -2.20* for OBD2, less for OBD1
The consensus of moderator opinion, Buddy, is that you need to
a - commit the posted DS4 timing procedure to memory - it is correct in scope and intent, performed with a new TECH2 - the details are fuzzy, but, iirc, GMTDScan Tech duplicated TECH2 function, per Stefan's corrections and updates
b - study it till you get it right - it is correct
c - the problem is you not understanding Diesel technology vs gasser (patooie!) operation, not understanding Diesel injection function, not understanding DS4 timing procedure, all while also trying to learn GMTDScan, and trying to learn that and an afermarket chip - the resulting responses are confusing to all, because you use them to cast doubt on posted information - it is your input that is differing from standard DS4 timing procedures
The 6.5 runs well if the IP is correctly timed - if we determine that GMTDScan Tech functions differently than I've already posted, we can add that to the sticky thread in a separate GMTDScan response, incl differences, if any, encountered with the ENGH chip - same can be done for any other scantool or tune, long as the data is correctly posted - you know: correct decimal placing, correct value signing (+\-), etc and etc.....................
Remember, folks: I am dyslexic, and easily confused..........
Last edited: