Production Counter Drops After a Restart? Separate Reset, Retention, and Reporting
- PLC Play Ground
- 0
- Posted on
A production count can disappear because it was reset, not retained as expected, or replaced by another system after reconnecting. Record where the authoritative total lives before changing memory settings. The controller, HMI, and reporting database may each hold a different copy.
Original ownership example; retention and restoration rules are controller-specific.
What is happening?
Retention describes specific storage behavior under defined restart or transfer conditions. Application initialization and synchronization can still overwrite retained values. A useful design defines total ownership, shift or batch reset rules, and reconciliation after interruption rather than relying on a tag's retentive label alone.
Check these five things
-
Identify the authoritative count and every copied or displayed version.
-
Cross-reference reset, startup, recipe, and synchronization writers.
-
Read the controller's retention behavior for power loss, download, memory restore, and other relevant events.
-
Define how count continuity and reporting are reconciled after interruption.
-
Test restart scenarios with a known count in an approved nonproduction environment.
Worked example
A retained PLC count survives restart, but the reconnecting HMI writes its own default value back into the tag. The observed loss is real, yet changing PLC retention would not fix the writeback path.
Quick diagnostic reference
| Possible cause | Evidence |
|---|---|
| Explicit reset | Program or operator event |
| Storage behavior | Platform retention rules |
| External overwrite | Communication write history |
The mistake to avoid
Making every tag retentive can preserve stale commands or invalid sequence states. Apply retention according to each value's purpose.
How to verify the fix
Demonstrate count continuity or the explicitly required reset behavior across the tested interruption cases, with reporting reconciled to the same definition.
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 data design and initialization considerations. The examples and diagnostic tables above are original teaching material; they do not replace the product manual.
