Having thought about this further, I don't think that the problem has anything to do with how the escapement is triggered. After all, the 4 main rungs of this program were lifted directly from the old program, which worked fine for the last 5-6 months. I think the problem has more to do with how the sequence is being initiated.
The goal with this modification is to reduce cycle time to the absolute practical minimum. Therefore, I don't want the pin-feed sequence to take place between the time the START button (X0) is pushed, and when the driver (Y2) begins to extend. I want to utilize that "dead time" when the operator is loading/unloading the part. Hence my thought that the pin-feed sequence would be "demand-initiated": Is the machine on? Yes. Is there a pin in the nosepiece? No. Then, send one NOW. Typically, this would happen when the driver has retracted just far enough, after having pressed a pin, for X11 to become true. Thus, the period of time from when X11 just goes true, to the time that the operator has removed the completed part, loaded a new one, and pressed the START button, is available for the pin-feed sequence.
Another requirement is that the program must be "patient". This gets to what some of you were saying about the timers timing out before another cycle happens to reset them. This operation is only one of several that the operator performs in this work cell. The time between cycles of the program might be as little as a couple of seconds, to as much as several minutes (or even longer, if they don't shut the machine down), so the viability of the program cannot hinge on a new cycle being initiated at some minimum, regular interval.
All of that said, I don't know exactly why the pin-feed sequence is failing at start up, when it works fine otherwise, but I think that it might be because of how the sequence is being initiated. I should probably not be using an E-STOP button contact (X1) to start the cycle. The way it's set up, the E-STOP interrupts power to the MCR (and the PLC outputs), and a RESET button must be pushed to pull the relay back in. HOWEVER, the PLC sees the X1 contact closure immediately. So, there is a delay between the time that X1 goes true, and the output commons are activated. This is what I think is causing the problem at startup, since the timer is triggered when X1 goes true, but the escapement output is not enabled until a few seconds later. It also explains why manually cycling the driver "fixes" the problem, as X11 is reset by the driver shank interrupting the beam. Only, this time the output commons are activated, so the pin-feed sequence happens the way it should.
I think I need to change how the pin-feed sequence is initiated, perhaps with a separate RESET button cantact?
Paula