A screenshot taken after a fault often shows the recovery state, not the condition that caused it. A carefully chosen trace with pre-event history can preserve the missing sequence. Start with a diagnostic question so the capture includes the signals that can distinguish competing explanations.

Evidence-capture method; trace features and resource limits vary by platform.

What is happening?

A circular or pretrigger recording retains recent samples and preserves them around a defined event, where the platform supports it. Useful evidence depends on sampling rate, trigger logic, signal selection, and time alignment. Collecting hundreds of unrelated tags can consume resources without answering the root-cause question.

Check these five things

1. Write two or three plausible explanations and identify which signals would separate them.

2. Include the initiating request, relevant feedback, quality, mode, state, and fault indication rather than only the final alarm.

3. Choose a supported sampling interval and pre/post-event duration appropriate to the event speed and available resources.

4. Validate the trigger in simulation or a controlled test and confirm the trace is retained after the event.

5. Annotate captured data with operator observations and compare repeated events before concluding causation.

Worked example

A sequence fault is visible after a pressure-valid bit has recovered. A trace retaining the preceding interval shows whether validity dropped before the transition failed. That ordering is more informative than a healthy value observed several minutes later, although timing alone may not prove the ultimate cause.

Quick diagnostic reference

The mistake to avoid

A trace sampled too slowly can miss the same short event as an HMI. Match acquisition to the question and platform capability.

How to verify the fix

Demonstrate that a known test event produces a readable record with adequate timing resolution and all required signals before waiting for the real fault.

Field-work boundary: These are educational diagnostic guides. Use the exact equipment manuals and approved site procedures. Electrical testing and machinery changes belong to qualified, authorized personnel; control hazardous energy and validate affected functions before release.

Technical reference

Rockwell Automation: controller trending and diagnostic documentation. The examples and diagnostic tables above are original teaching material; they do not replace the product manual.

Continue troubleshooting

• 4–20 mA Signal Jumping Around? Separate Noise From a Real Process Change
• The Analog Value Looks Right—But Is It the Wrong Channel?
• How Modernizing Old Equipment Improved Productivity: Industrial Case Study