Troubleshooting
How to Keep HMI-Entered Timer Presets in PLC Memory
Short answer
The presets return to zero because the V-memory word they are written to falls outside the PLC's configured retentive range. Open the retentive ranges setup in the programming software, extend the V register range to cover the preset addresses, download the change to the PLC, and save the project.
On this page
Timer presets entered on an operator panel come back as zero after a power cycle because the PLC word they land in sits outside the PLC's configured retentive range. In the case examined here, an EA9-series panel writes timer presets to V-memory word V35 in a DL06 micro PLC: the write succeeds while power is on, and the word initializes to zero at restart because V35 is not inside the retentive V register range. The repair is made in the PLC, not in the panel object — extend the retentive V range in DirectSoft, download that change to the PLC, and save the project.
Confirm Where the Value Is Lost #
Do not open the numeric entry object or the timer instruction first. Establish whether the value ever reaches the word, and whether the loss happens at restart; the two failures have different fixes.
- Enter a recognizable, valid preset on the panel.
- With the system powered, view V35 in the PLC and confirm it holds exactly the entered value.
- Power-cycle the PLC and panel together, following the site's normal procedure. Do it with the machine idle: both controllers drop out, and these presets set machine timing.
- After restart, read V35 again before touching any HMI object or ladder logic.
If V35 already reads zero before the power cycle, the write path is at fault — the object's mapped address or the link — and no memory setting will repair a value that never arrives. Prove the panel's writes against a running controller first; the procedure for testing HMI simulation against a live PLC is the right pattern. If the word is correct before shutdown and zero after restart, it is a retention failure, and the rest of this article applies.
What the Retentive Range Controls #
The DL06 stores data in V-memory words, and whether a word survives a power cycle is set by the retentive ranges you configure in the programming software. The DL06 User Manual covers this in Chapter 3 (CPU Specifications and Operation), under "Setting Retentive Memory Ranges". That section makes you responsible for the boundary: words inside the configured range keep their values through power loss, and words outside it initialize to zero at startup.
Two consequences follow for this fault. A low address is not automatically a safe one — V35 clears because the configured boundary excludes it, not because of anything about V35 itself. And the panel has no vote: a numeric entry object writes a value, it cannot confer retention on the word it writes. The current boundaries are displayed in the memory map view of the programming software, and those displayed values — not a range copied from another project — are what this PLC is running.
Set the Range to Cover the Preset Words #
- In DirectSoft, open
PLC -> Setup -> Retentive Ranges. - Read the V register range shown and note both boundaries.
- Move the boundary so every word the panel writes — V35 plus any neighboring preset words — falls inside. Extend no further than the application needs.
- Leave the other memory-type ranges in the dialog untouched.
- If the software refuses the new endpoint, the ceiling is the CPU's V-memory size: smaller DL06 CPUs top out at V377 and mid-range variants at V1777. Relocate the preset words inside the documented map rather than forcing the range past it.
Download the Change and Save the Project #
Editing the dialog changes nothing in the controller until the setting is transferred. Skipping that transfer reproduces the original symptom exactly, which is why this fault survives so many HMI-side edits.
- Use the download control inside the retentive range dialog to write the setting to the PLC.
- Confirm the software reports the transfer completed.
- Save the project in the same session, so the offline copy records the range the PLC now holds. Keep archived copies current the way you would after any program change — how to back up a PLC program the right way covers that discipline.
Worked Example: Six Timer Presets at V35 to V40 #
Take a panel that writes six timer presets, one word each, to V35 through V40, on a PLC whose retentive range dialog shows the V register range ending at V34. Both the six-word allocation and the V34 endpoint are this example's inputs; your dialog supplies your own reading.
- Words the panel writes: V40 - V35 + 1 = 6 words.
- Range needed to cover them, beginning at V0: 40 - 0 + 1 = 41 words.
- Growth over the old range: 40 - 34 = 6 words — exactly the preset block, nothing more.
- Endpoint check: V40 sits at or below V377, the ceiling of the smallest documented variant, so the endpoint is legal on every DL06 CPU.
The decision: move the endpoint from V34 to V40, download the range, save the project, and the six presets come through the next restart. If every entry targets V35 alone, the endpoint only needs to reach V35, for 35 - 0 + 1 = 36 words.
Prove Retention With a Full Restart #
- Enter an ordinary operating preset, not a value chosen to make the test pass.
- Read V35 before shutdown and record the number.
- Power-cycle the PLC and panel per the site procedure.
- After startup, read the word again: it must hold the identical value, and the timer must run the entered time.
If the word retains its value but the timer misbehaves, the retention repair is done — look for startup logic that writes the word, or a timer referencing a different address. If the word clears again, one of three things is true: the range change was never downloaded, the range does not include the exact address, or the test read the wrong PLC.
What Not to Change #
- Re-entering presets after every startup. It restores the value until the next outage and teaches the crew to treat the fault as normal.
- Editing the numeric entry object for retention. The object cannot make a PLC word retentive; touch it only if the value never reaches the word.
- Rewriting the timer instruction. The timer reads whatever the word holds; retention is a memory property, not a ladder property.
- Widening retention across unrelated words as insurance. Cover the preset block and stop, so what survives a power-up stays predictable.
Questions asked
Will the presets survive if only the panel loses power, not the PLC?
Yes. A panel-only outage leaves the PLC running and the word untouched, so the values stay in place. The loss appears only when the PLC itself restarts and initializes the non-retentive words to zero. That difference is a quick way to separate a retention fault from a write fault before opening the programming software.
How much V-memory does this PLC have available for retained data?
The DL06 specification lists 7680 words of ladder memory and 7616 words of V-memory, of which 7488 words are user V-memory alongside a 128-word non-volatile user block. Added together, 7680 plus 7616 gives 15296 words of memory. Capacity is not the constraint here; the configured retentive boundary is.
How long does re-entering the preset after startup last as a stopgap?
It holds only until the next PLC power loss. The word is written correctly each time; it simply is not retained. On a machine that runs for weeks between outages, the stopgap can look like a fix, which is why this fault often surfaces long after commissioning. Complete the range change before the next planned shutdown.
Can a later program download undo the retention fix?
Yes. An older project copy still carries the previous retentive range, so downloading it reinstates the original loss. Save the project in the same session as the range change and treat that saved file as the master, so the version you download always matches the configuration the PLC is running.