• Welcome to The Truck Stop! We see you haven't REGISTERED yet.

    Your truck knowledge is missing!
    • Registration is FREE , all we need is your birthday and email. (We don't share ANY data with ANYONE)
    • We have tons of knowledge here for your diesel truck!
    • Post your own topics and reply to existing threads to help others out!
    • NO ADS! The site is fully functional and ad free!
    CLICK HERE TO REGISTER!

    Problems registering? Click here to contact us!

    Already registered, but need a PASSWORD RESET? CLICK HERE TO RESET YOUR PASSWORD!

Need Help With Timing

Bill's chip could be DESIRED'ing more initial advance - dunno why, just yet, but MEASURED must always display DESIRED within 1*, so your MEASURED is no problem - START always gets increased advance, even when ECT is at operating temperature, but will drop off to +8.5* (tuned) as ECT increases

My truck is still running v2.0 with D\M +8.5 and TDCO (selected) -1.5 - Bill upgraded that to v2.1, but the engine seemed to lose some performance, so went back to v2.0 - I've not had experience with further upgrades, as that's about the chronology where I lost primary interest in the 6.5 (CRD is much more interesting\challenging)

Increased timing (advance) moves power development upward into the horsepower band, which is good for hi-performance but reduces low-end power, which is torque: Diesels are low-rpm torque-monsters - gassers (patooie!) are hi-rpm horsepower monsters (well, some of them are, anyway!) - gasoline is a quick-energy fuel, highly inflammable and violent but short-term duration, excellent for hi-rpm - Diesel fuel is a slow-energy fuel, difficult to ignite but increased duration - that means, not a high-rpm fuel in a mechanically-injected system, which the 6.5 got one of: all the fuel is injected in one burst, event-timing determined by IP position and injector pop-pressure - increased advance moves the injection event forward in time, necessary to allow complete burn at higher rpm - too much advance and the fuel is injected before cylinder temps have risen to combustion temperature, which cools the cylinder and delays combustion in a Diesel engine - gassers (you know!) with too much advance, being spark-infested, just ping and rattle and try to sound like a Diesel - too little advance and the injection event continues after cyl pressure has dropped below combustion temperature, the flame goes out with resultant black smoke = reduced torque\power - Diesel fuel combustion duration (slow-burn) and mechanical injection (one burst) are the limiting factors in hi-rpm horsepower development - thus, my concern on the increased low-rpm advance, which would require the IP advanced position to be on the ragged edge of viable injection event timing

Comparing your analog clock\watch to the crankshaft and pistons in your engine, 12 being TDC 0* crankshaft with piston at the top of it's stroke, 6 is BDC 180* crank when piston is at the bottom, 3 (at 90*) being the maximum length of the lever the piston is pushing in order to rotate the crank - maximum torque would be developed at low rpm when maximum cylinder pressure pushes that lever when it is at maximum length in the arc between 2 o'clock and 4 o'clock - that is rather impractical, however, because cylinder pressure (and combustion temperature) drops at a non-linear rate as the piston drops, so we must needs start the injection\combustion event such that max cylinder pressure occurs much earlier at ~15*, which is between 12 (0*) and 1 (30*) - if the injection event is further advanced, max cyl pressure is also advanced, pushing on the lever earlier in the arc when it is even shorter, and as pressure begins falling off much sooner, we get reduced torque

To overcome this we would need more air volume in the cylinder, such that cylinder pressure increases more rapidly, resulting in cylinder temperature increasing more rapidly with point of combustion temperature occuring earlier and cylinder pressure remaining hi much longer = more Boost at lower rpm, which will require more exhaust energy derived from increased BTU (air and fuel) or smaller turbine, either of which increases low-rpm spool-up - 'course the smaller turbine then restricts output power at higher rpm where exhaust energy is normally high - hmmmm..........the GM-X series turbochargers seem to come to mind on reading that, right?

CRD gets around this with very hi pressures (how does 4500psi at idle and 19000psi at 70mph and 22000psi at fwot grab ya?), multiple injection events and variable fuel-rates during each event, beginning combustion with minimal fuel to start the flame, increasing fuel-rate as flame increases, ending event by maintaining flame with reduced fuel volume, thus extending the event and maintaining cylinder pressure passed the mechanically-injected 15* point of diminished return - CRD rules!!!!!!!!

Aside: for you guys that carried a slide rule on your belt, another in your shirt pocket, and kept another under your pillow for intimate emergencies (and you know who you are, Goldsberg and rj!), feel free to chime in with minutes and seconds of an arc and deci-millimeters of fuel rates - no problem - I quickly noticed, during my first seminars, the glassy eyes and sudden loss of attention of some of the attendees when they were being brutally assailed with hard-core theory - best to generalize, addressing the deep stuff only when specifically asked, eh.................
 
Last edited:
That is an awesome amount of info...course I am more confused now that before. I understand the principle of timing and compression ignition. Just still don't get Time set vs TDCO. What we really need is an idiots step by step, assume we know nothing) procedure to set timing with GMTDScan. I screwed up last weekend thinking a guys truck was set and All I think I did was read a stored value. I don't get what timeset does. What Bill H explained to me was that it changes the value in the Prom and we should not be messing with that but here guys are saying do that first then TDCO.
:mad2::dr:
 
As a matter of trivia: Stanadyne sent a proposal to GM for an electronically-controlled upgrade to the venerable DB2 injection pump, known as the smokeless IP - this would be accomplished by using a solenoid valve to initiate and control the pumping stage of the event, while retaining the mechanical injectors - this was necessary because of the increasing emissions restrictions, which would soon result in loss of GM's C.A.F.E. mileage-factor improving engine, the 6.2L Diesel - GMC quickly tested the DS4, then forced Stanadyne to release the system B4 R&D had solved some of the infant's problems - those OBD1 systems were primitive because the system was an un-developed new infant, with R&D being done by the customer\owners and service techs - result: thousands of DS4's were unnecessarily replaced in '94 and '95 because MrGoodwrench had little training (theory of operation specifics are still restricted\prohibited, to this day) and no experience required to solve the field problems

OBD1 was primitive - TIMESET defaults to fixed timing so the engine will run during the test - PCM then rotates (DESIRES) the camring\OPTIC SENSOR to the maximum retarded position, then to the maximum advanced position allowed by the internal dimensions of the advance-piston bore in the IP housing - comparing the min\max degrees allowed by those dimensions to crankshaft timing, PCM can accurately determine the position of the IP relative to TDC - max camring travel is 11* total - thus, if the IP is rotated and locked down at +8.5* BTDC, PCM will see a range of available timing from +8.5* min to +19.5* max - PCM then stores those numbers in memory, used to vary advance as required by rpm and load

TDCO is a fudge factor that allows a mechanical injection system running intial timing advance for better torque to also run at higher rpm for more horsepower development - it allows the pump rollers to be at a higher point on the camring ramps allowing injection pressure to be reached quicker, necessary to remain within the shorter window of the injection event at hi rpm - thus, idle quality and accelerator position sensitivity is maintained as normal - the mythical Optic Bump accomplishes the same thing mechanically, but drastically increases app sensitivity and messes with idle quality, as PCM has no information on that procedure

In the primitive OBD1 systems, TIMESET measures and stores IP position relative to TDC - TDCO LEARN uses that stored number to determine the TDCO fudge factor - however, it was soon noticed that TDCO also sets a fixed timing number, then spans the camring between min and max travel prior to LEARNING TDCO, thus duplicating some TIMESET function - however, if IP has been erratically replaced, meaning the replacement is not to near-exact original position, TDCO LEARN does not determine new IP position - thus, for reliability\repeatability, TIMESET is required and should always be done prior to TDCO LEARN in OBD1

Software was re-written for the not-quite-so-primitive-as-OBD1 OBD2 systems to combine TIMESET and TDCO LEARN functions, thus allowing the KO-KO footsie\fingersie thingy to initiate TDCO LEARN - however, that procedure is safe only if:
- the IP has not been rotated from oem, or\and
- IP rotation has been measured-off in exact dimension from oem position: 2.5mm = 5*, or\and
- replacement IP was dimensioned\measured and replaced to exact position of removed IP, in which case TDCO LEARN is not required, or\and
- CPS was replaced
- etc

The OBD2 KO-KO routine is always safe to perform if PCM has been scanned for as-found D\M timing and TDCO, which must be noted prior to any adjustments for comparison to as-left values

OBD2 TDCO LEARN combines TIMESET and TDCO, so TIMESET is not required

OBD2-specific TECH2 does retain OBD1 functions including TIMESET, as it is downward compatible with OBD1 systems by using the 16pin DLC-to-ALDL 12pin adaptor cable

OBD1 procedure is
- allow full warmup to operating temperature = 180deg min for reliability - if ambient is below 50*F, allow IAT to come up to ~85*F such that PCM is not calling for any advance
- the following timing procedures will be invalid if PCM is calling for advance, as idicated by DESIRED\MEASURED timing, no matter how slight
- take an initial scan, note the as-found values for D\M timing and TDCO
- rotate\adjust the IP: 2.5mm = 5*
- again observe ECT and IAT for normal temps
- do TIMESET, exit, observe that new D\M timing reflects new IP position
- do TDCO LEARN, exit, observe that new TDCO reflects new IP position
- if TDCO is not as desired, do TDCO LEARN, slowly rev engine to ~1200-1500rpm, exit when desired number is displayed

TDCO has a range of acceptable numbers for each position of the IP - increasing engine rpm causes PCM to attempt to advance timing as required by the increased rpm - numerical advance is locked to a preset value by the TIMESET and TDCO LEARN commands, but the DESIRED number actually does change, resulting in the changing TDCO values, allowing you to select a particular number within that range
 
Last edited:
So when the dust settles....the HP4 sets the timing at 10ish degrees and not 8.5 as the stock, or early chips do....right?
 
Dunno fer shure - enuff of you post those exact results with HP4, and we can safely assume that to be fact - if the rattle doesn't scare you in cold weather, it's prolly hurting nothing but my pride, for not knowing, eh.................
 
Rattle?

LOL


I'll get a sound clip of it when it gets colder out here....the HP4 really shakes the old IDI....the PD Jetta purs like a kitten....
 
What' s scary about that rattle is that it is the sound made by violent precup expansion into it's pocket in the head - the normal slight rattle cracks the precups over tens of thousands of miles, such that each should be replaced when any crack is longer than 1/4", or any crack traverses across the surface from the outside edge into the Ricardo port - I shudder to think what's happening to the 'cups when they can be heard screaming in agony at -1.5* TDCO, greatly moreso at -1.94* - first cool autumn morn of ~50*F at -1.94*, I quickly reset my PCM back to -1.5*, still loud but not quite as scary - yeah, I'm a wuss, but my engine (and me) is happier with the improved prognosis...................
 
LOL!

I understand your concern.....legitimately so....

I will get a sound clip for you at -40* C.....should be good for a laugh....engine is due for a rebuild anyways....
 
That'd be cool - you gonna rebuild it anyways soon? Been wanting to see a set of 'cups that had been run at -1.94* for a long while, see if my concerns are really legitimate
 
OK So if I set my TDCO about 6 months ago with GMTDScan and I recheck it now do I have to do a relearn to just see where it's at or just connect GMTDScan and read it ? That is the part confusing me. When you go to set Base time do you exit when the value reached is what you want or does it exit itself and whatever it reads is the value ? Same question with TDCO do you exit when you are at -1.94 or let it keep going until it exits and whatever it reads is what you have and need to physically move the pump to change value ???????:confused:
 
Just read it.

You stop the relearn - don't exit (that is a Tech II thing).

When you stop the relearn it will keep the value that it is stopped at.....hope that makes sense....
 
OK That's what I thought you told me last time but here is where I am lost. JD said (If I understood it right) that after every 50 keystarts it commands a relearn on it's own so does that mean whatever value I locked in will change anyway ?
SO Let me see if I got it right.
Connect GMTDScan
Command Time set and exit manually when Timeset value of base time(3.5 ?) is reached. If Timeset(or base time) can't reach 3.5 then manually move IP and repeat until 3.5 can be reached.
Then command TDCO relearn. When desired value of -1.94(or whatever you want it to be) is reeached manually exit TDCO relearn ?
Also if desired range or value of TDCO cannot be reached do you again move pump manually or should you not have to do that because base time was already set ?
Ughhh do I have this yet ?
My 3 yr old is laughing saying Daddy can't you set timing yet ?
:D
 
TIMESET will read +3.5* no matter where the IP is locked down - look closely and you'll see the numbers are varying across 3.5*: 2.5~3.5~4.5~3.5~2.5, etc - as the IP is advanced, the numbers become weighted in the positive direction: 3 ~ 3.5 ~ 5 and upwards - from oem Base of 3.5*, you can rotate the IP exactly 2.5mm, lock it down, do TIMESET, exit, and the result will be +8.5*, where TDCO LEARN will recalculate to around -1.5* - 2.5mm = 5* advance

Therefore, first thing you will do is monitor ECT\IAT, then Des\Meas and TDCO, note the displayed as-found numbers

If at operating temp above ~180*, do TIMESET, exit then observe the new result, comparing to as-found - if they do not match, you'll need to adjust the normal 2.5mm increment, such that you do not dial in more than +5* total advance:
D\M+3.5* + 2.5mm = D\M+8.5*
D\M+4.0* + Xmm = +8.5*
D\M+5.5* + Xmm = +8.5*
etc

Do TIMESET then TDCO LEARN after each increment to verify progress and prevent DTC

The procedure guarantees reliable results, every time - assume nothing, suspect every one, take names and kick butt.................
 
Last edited:
I have never seen my TDCO reset itself after hundreds of restarts....

In fact I will scan it today or tomorrow to see if it is still set at -1.94 and I will be surprised if it is anything but.....
 
If you were to replace the IP without doing TIMESET and TDCO LEARN, after a while you would hear the rattle change as PCM finally figgers out that the previously stored timing numbers are incorrect for the new IP setting - that is a function written in stone in order to keep IP timing in spec as the timing chainset wears - word up......................
 
Last edited:
I'll have a look at my HP4 at idle timing tomorrow IIRC it sits a little higher than 8.5 stock timing


Tim this going into it`s forth page soon & you are keeping us all in
suspence.... & it`s started to get chilly here Br,r,r,r,r, :thumbsup:
 
Last edited:
What a wealth of information. Thanks for all the info! I finally got this thing set and I could not have done it without all of your input. Once I cleared all the codes I still had to move the pump 3 times and now it is back where I started, as far as I can tell. Timing is 9.5 -9.5 with TDCO at -1.5. THANKS AGAIN!
 
Back
Top