IMDTouchKnowledge BaseShop main store

Troubleshooting

HMI numeric input does not change FX2N timer preset

HMI and touchscreens Published 8 min read

Short answer

A numeric input works only when it writes the exact D register the timer or counter instruction reads as its preset. Open the device monitor, enter a known value, and watch that register: if it does not move, fix the link, driver or address; if it moves but the delay stays fixed, the rung still reads a K constant or another register — change the preset operand to the register, mind the timer's time base, then test two settings before production.

On this page
  1. Why does my HMI numeric input not change the FX2N timer?
  2. Which D register should the numeric input write?
  3. How do I prove the HMI write actually reaches the FX2N?
  4. How do I point the ladder at the register?
  5. Why does the delay come out wrong even though the register changes?
  6. How do I connect the HMI to the FX2N over serial or Modbus?
  7. Why does my entered preset vanish after a power cycle or restart?
  8. What do I check before the line runs again?
  9. Questions asked

Your Weintek panel is probably doing its job. A numeric input on an HMI is a transport object: it writes one number into one PLC device address and does nothing else, and the FX2N ladder decides what that number means. When the machine delay never moves, the usual cause is that the timer or counter instruction still reads a fixed K constant or a different register than the one the input writes. The fix is to prove the write first with the PLC programming software's device monitor, then repair whichever half is broken — the link, the address, or the rung. Every number below is worked for a 100 ms timer so you can check the arithmetic yourself.

Why does my HMI numeric input not change the FX2N timer? #

Because the input writes a D register while the ladder applies the preset somewhere else — with preset K30 in the rung, a new value of 50 in D100 changes nothing, because the timer instruction never reads D100. A numeric input has no awareness of timers: it writes the device address you configure, over the link you configured, and the PLC program alone decides what the value does. Sort your case by symptom before editing anything.

  • The HMI shows the new value but the machine delay does not move: the rung applies a fixed K constant or a different register as the preset.
  • The entry fails, errors or reverts immediately: wrong address or driver, or PLC logic overwrites the register.
  • The delay changes but to the wrong length: a time base or display scaling problem, not the link.
  • The HMI shows no live data anywhere: the communication link itself; fix that before touching any logic.

Which D register should the numeric input write? #

The exact register the timer or counter instruction uses as its preset — one spare data register per setpoint, never the counter's accumulated value and never a register already doing another job. FX data registers are addressed as D plus a number, the same D family as D8120, the serial-parameter register you meet when setting up a 485-BD board.

Choose a register that appears nowhere else: search the ladder for the number and check the existing HMI project for objects already mapped to it. Keep a written list of what each HMI-facing register means, its units and its limits — that list is what the next technician will need. One register holds one setpoint. The counter's accumulated (current) value is the counter instruction's own bookkeeping, so pointing an operator entry at it changes the count, not the target.

How do I prove the HMI write actually reaches the FX2N? #

Watch the register live in the device monitor of the PLC programming software while you enter a known value on the panel — enter 50, and the monitor must show 50 in that register, before you touch any ladder. This one test splits the fault in half, because it separates a communication problem from a logic problem with no guesswork. Open the device monitor on the D register you mapped, type 50 into the numeric input, and read the monitor. Then apply the table.

Device monitor shows What it proves The decision
Still 0 after the entry The write never arrives Link problem: driver, port, station number or serial settings — not ladder
50, delay still 3.0 s The write works; the logic ignores D100 Repoint the preset operand at D100
50, delay moves but wrong length Write and logic both work Fix units: time base and display scaling
50, then back to 0 moments later Something rewrites the register Find the every-scan or startup write and remove it

A note on simulation: the editor's simulator exercises your screens, not your serial link, so a pass in simulation proves nothing about the panel-to-PLC write. Testing HMI simulation against a live PLC explains the switch to real hardware, which is where this fault lives.

How do I point the ladder at the register? #

Replace the fixed constant in the preset operand with the register number — the rung that read K30 becomes a rung that reads D100 for the timer, or D101 for the counter, and nothing else about the instruction changes. In words: the rung keeps its drive contact and its timer or counter device, and only the preset operand changes from the constant to the register. FX-series timer and counter instructions accept a data register in that operand; the FX series programming manual documents the form.

You add no ladder to receive the HMI write: the HMI's PLC driver performs the transfer on its own, and the rung only consumes the value. While you are in the program, restrict the entry point so operators can change presets only in the machine's safe stopped state.

Why does the delay come out wrong even though the register changes? #

The register stores time-base units, not seconds — on a 100 ms timer, 50 in the register is 50 × 0.1 s = 5.0 s, so an operator who types 5 meaning five seconds gets 0.5 s. Work the example end to end:

  • The timer is T0 on the FX2N, in the 100 ms time-base class; the FX series programming manual's timer table gives the class for every timer number, and counters carry no time base at all.
  • Old logic: T0 preset K30 → 30 × 0.1 s = 3.0 s, fixed, which is why the machine never responded to the panel.
  • New logic: T0 preset D100; the numeric input writes D100 as a 16-bit integer with limits 0 to 600.
  • Operator needs 5.0 s: enters 50 → D100 = 50 → delay = 50 × 0.1 s = 5.0 s. Maximum entry 600 → 600 × 0.1 s = 60 s.
  • If the panel should read in seconds, give the object a display scale of 0.1 so an entry of 50 shows 5.0 while D100 still holds 50; the general method is in how to scale a PLC integer into an HMI display value.
  • Counter version: batch counter C0 with preset D101; an entry of 25 sets the done contact on the 25th pulse.

A delay that moves but lands at the wrong length is a units problem, not a comms problem — multiply the register value by the timer's time base, make the HMI display agree, then retest with two entries: 50 for 5.0 s and 100 for 10.0 s.

How do I connect the HMI to the FX2N over serial or Modbus? #

Match the driver to the physical port: the FX2N's built-in RS-422 programming port uses the vendor's Mitsubishi FX-series serial driver, an FX2N-485-BD board runs RS-485 with its serial parameters set in register D8120, and Modbus RTU is a driver choice — never new ladder code.

Before changing anything, write down the four facts that decide the setup: the HMI model and software, the PLC port in use, the driver selected in the HMI project, and the station number. The vendor publishes a connection guide per PLC family: the FX2N sits in the guide titled Mitsubishi FX0S/FX0N/FX1S/FX1N/FX2/FX3SA for the built-in port, and in Mitsubishi FX232/485BD for the RS-485 board, and those guides carry the cable pinouts and the D8120 setting value. Serial settings must match on both ends, and pin assignments vary between HMI models, so take them from the guide rather than from guesswork. If the device monitor proved the write never arrives, the fix lives here: correct driver, correct port, matching station and serial settings.

Why does my entered preset vanish after a power cycle or restart? #

Because ordinary data registers do not hold their value through power-off — unless the ladder writes the register at startup or the register sits in a latched range, the preset returns to 0 at the next power-up, and the HMI entry was never stored anywhere else. Two fixes exist.

Give each preset register a power-up default: one rung, executed once at startup, moves a sensible initial value into the register, and HMI entries overwrite it from there. Or place the setpoint in a latched D register so the FX2N's battery carries it through power loss — the right choice depends on whether an old value surviving a power loss is safe for your machine. The rung pattern and the trade-offs are in how to keep HMI-entered timer presets in PLC memory. One related trap: logic that rewrites the register every scan does the same damage while running — the entry lands, the next scan's write erases it, and the operator swears the panel is broken. A preset write belongs at power-up, not in the scan.

What do I check before the line runs again? #

Four checks: the register holds the entry, the instruction reads that register, two different entries produce the expected 5.0 s and 10.0 s delays, and the numeric input's limits reject out-of-range values before the machine ever sees them.

  • Time two real cycles with entries of 50 and 100 and confirm 5.0 s and 10.0 s on a stopwatch.
  • Power the panel and PLC down and back up and confirm the preset does what the retention choice promises: default restored, or value latched.
  • Enter 0 and 601 against the 0 to 600 limits and confirm the panel refuses them.
  • Keep preset edits locked to the machine's safe stopped state through an access or state condition on the entry.

Change presets only from a stopped state: an HMI preset write is an ordinary control write with no safety function, and a timing change must never be used to alter a guarded stop or a safety-related sequence.

The decisions, one per case: the monitor never moves, so fix the comms — driver, port, station number, D8120; the monitor moves but the delay stays fixed at 3.0 s, so repoint the preset operand from the K constant to the register; the delay moves but to the wrong length, so multiply by the time base and align the display scale; the preset vanishes, so add a power-up default rung or use a latched register.

Questions asked

Do all FX2N timers count in 100 ms steps?

No. The FX2N assigns a fixed time base by timer number, with 10 ms, 100 ms and 1 ms classes, so the same register value gives a delay ten times shorter on a 10 ms timer than on a 100 ms one. An entry of 50 is 0.5 s on a 10 ms timer and 5.0 s on a 100 ms timer. The timer table in the FX series programming manual lists the class for each timer number.

Why does my entry revert to the old number a second later?

Another writer is beating the HMI to the same address: an initialization or parameter block that runs every scan, or a second HMI object, recipe field or another panel mapped to the same register. The entry lands, the other write erases it, and the fastest repeating writer wins. Move any PLC write to a power-up-only rung and search the HMI project for other objects on that register.

What happens if the operator writes the counter's accumulated value instead?

The counter instruction compares its current count with the preset, so writing the current-value register does not set a target — it can force the count past the target so the done contact fires immediately, or drag the count back so parts get counted twice. Keep the operator entry on its own register as the preset and leave the accumulated value entirely to the counter instruction.

How wide should the numeric input's limits be?

Set them from the process, not from the register: the minimum and maximum are what the machine tolerates, as in the 0 to 600 example that allows 0 to 60 s in 0.1 s steps. Keep the upper limit at or below 32767, the maximum of a 16-bit signed integer, so an oversized entry cannot wrap to a negative value. Reject bad entries at the panel instead of clamping them in the ladder.

Keep reading

  • How-to

    How to Display a Time-Until-Closed Countdown on an HMI

    Display time until closed by computing the timer preset minus the accumulated value (.PRE - .ACC) in the PLC and binding the numeric display to that result. Clamp the value to zero when the done bit sets, keep the operator's duration in its own tag, and let the timer-done rung in the controller close the valve - never the panel.

    HMI and touchscreens

  • Explainer

    Why the compiled HMI project view is not for editing

    The compiled HMI project view in EcoStruxure Machine Expert HVAC is a debug window: it shows the Structured Text the HMI compiler generated from your authored project, and it cannot be used to develop the project. Create every function your procedures need in the authored project, compile clean, and confirm the generated view reflects the change after two consecutive builds.

    HMI and touchscreens

  • How-to

    Display large PLC array history on an HMI with a buffer page

    Put a display buffer in the PLC sized to one visible page (10 rows here) and let the HMI show only that. On each page change the PLC clamps a start index and copies the requested slice of four 5000-entry test arrays plus a timestamp array into five 10-element buffers, so 1000 exposed entries become 100 pages and 50 HMI-facing values instead of one object per tag.

    HMI and touchscreens

WinCC flexible IO field not editable on the panel