On the panel, 011 either never starts the ten-second cycle, pauses in the wrong state, or starts again immediately after cycle 500. Start here: this is a sequencing and reset problem built around latch 701, retentive timers 901/902, and counter 903. That is not a hardware fault.
Stop applying the wrong fixes
| Symptom or attempted fix | Why it does not solve the sequence |
|---|---|
| Replace the SLC 100 with a programmable relay | A replacement may modernize the machine, but it does not define the required start, pause, timing, counting, and stop behavior. |
| Change from an up-counter to a down-counter | Either direction can terminate 500 cycles. The real issue is generating exactly one count per complete on/off cycle. |
| Use ordinary non-retentive timers | A non-retentive timer loses its accumulated interval when the pause condition makes its rung false. The sequence then restarts that interval instead of resuming it. |
| Reset every element as soon as the counter reaches 500 | Resetting 903 immediately removes the terminal count from the programmer display and permits a maintained start input to initiate another batch. |
| Search only for a manual | The manual provides instruction syntax, but you still need a defined state sequence and a scan-by-scan test. |
Trace the actual sequence
Use 701 as the run-state latch. The start contact sets it, and counter 903 unlatches it after 500 completed cycles.
-
901measures the output-on interval with a preset of10.0seconds. - The done state of
901starts902, which measures the output-off interval with the same preset. -
011is energized while701is set and901is not done. - The completion of
902increments903once, then resets both timers for the next cycle. - The normally closed
002condition inhibits both timer rungs. Because the timers useRTO, their accumulated values remain available for the resume.
The source notation identifies the physical controls as 001 or 101 for start and 002 or 102 for pause. Use the address format accepted by the installed controller and programmer; do not mix both formats in one program.
Enter the timer-counter logic
- Latch
701from the start input. - Run
901while701is active and pause input002is off. - After
901completes, run902under the same pause condition. - Count the completion of
902with903. - Reset the timers at the end of each complete on/off cycle.
- Unlatch
701when903reaches 500.
Rung 1 -| |- 001 --------------------(L)- 701
Rung 2 -|/|- 002 -| |- 701 ----------(RTO)- 901 PRE = 10.0
Rung 3 -|/|- 002 -| |- 701 -| |- 901 -(RTO)- 902 PRE = 10.0
Rung 4 -| |- 902 --------------------(CTU)- 903 PRE = 500
Rung 5 -| |- 902 --------------------(RST)- 901
Rung 6 -| |- 902 --------------------(RST)- 902
Rung 7 -| |- 903 --------------------(U)- 701
Rung 8 -| |- 903 --------------------(RST)- 903
Rung 9 -| |- 701 -|/|- 901 ----------( )- 011
Read contacts 901, 902, and 903 here as their completion states. Confirm the exact entry and monitoring syntax on the 1745-PT1 before placing the sequence in service.
Make the pause action intentional
Closing pause input 002 makes its normally closed contacts false. Both timer rungs stop executing, but 701 stays latched and the retentive timer keeps its accumulated value.
- If you pause during the on interval,
901stops accumulating and011remains energized because rung 9 does not contain002. - If you pause during the off interval,
901remains done,902stops accumulating, and011remains off. - The counter does not advance until
902completes, so a partial interval is not recorded as a cycle.
This is a hold-state pause, not a force-output-off pause. If the load must de-energize whenever pause is pressed, add the pause condition to the output logic—but recognize that this changes the requested timing sequence. Decide which behavior the process requires before editing rung 9.
Verify every transition
- Release the start input after initiating the test. Confirm that
701latches. - Verify that
011energizes immediately and stays on while901accumulates toward10.0. - At the first timer completion, verify that
011turns off and902begins accumulating. - Operate pause once during each interval. Confirm that the active timer stops at its current value and resumes from that value when pause opens.
- At the completion of
902, verify one increment of903and the reset of both timers. - Confirm that the next cycle begins with
011on and that the counter does not increment on either the start or pause transition. - Test the terminal count with the start input released. When
903reaches its preset of500, verify that701unlatches and011remains off.
For a controlled bench test, temporarily use shorter presets or a lower terminal count, then restore 10.0, 10.0, and 500. Recheck the final values from the programmer before connecting the process load.
Prevent restart and display traps
Rungs 7 and 8 stop the run and immediately reset 903. If input 001 remains closed, rung 1 can latch 701 again on the next scan. Use a momentary start, require the operator to release start, or add a one-shot/start-inhibit arrangement supported by the installed controller.
Automatic counter reset also means the final value of 500 will not remain available for observation. If the terminal count must stay visible on the 1745-PT1, remove the automatic counter reset from the terminal event and reset 903 from a separate clear or new-batch command. Verify first that the handheld programmer can display the counter value in its monitor mode.
Test power interruption behavior separately. An RTO instruction provides retentive timing when its rung goes false, but the required restart policy also depends on the retained state of the run latch, timers, counter, and controller startup processing.
FAQ
Why does SLC 100 output 011 stay on during pause?
The pause contact 002 stops the timer rungs but is absent from the output rung. During the on interval, 701 remains latched and 901 remains not done, so 011 holds on.
Why does the timer resume instead of restarting?
Timers 901 and 902 use RTO. When pause makes their rungs false, they retain the accumulated interval until their reset rungs execute.
Why does the SLC 100 restart after cycle 500?
Counter 903 unlatches 701, but rung 8 immediately resets the counter. If start input 001 is still closed, rung 1 can latch 701 again on the following scan.
Why does the count of 500 disappear from the programmer?
Rung 8 resets 903 when its completion state becomes true. Use a separate clear command if the terminal count must remain visible after the sequence stops.
When should I stop troubleshooting and contact Allen-Bradley support?
Stop if the 1745-PT1 rejects the documented addresses or instructions, the controller state cannot be monitored, or the observed retention behavior differs from the scan sequence above. Record the controller identification, programmer messages, entered rungs, and live states of 701, 901, 902, and 903, then escalate through an official Allen-Bradley support channel.