How-to
How to reset a startup bit after two minutes in Vijeo Designer
Short answer
Set the bit with a startup action that writes 1, never a toggle. Clear it with a periodic action at a 2-minute frequency whose Condition is that bit at 1: the reset runs once, then blocks itself until the next startup.
On this page
Two actions and one condition do it. A startup action sets the internal bit to 1 the moment the application runs; a periodic action with a frequency of 2 minutes writes 0 to the same bit; and that periodic action's Condition is the bit itself, true while the message shows and false the instant the reset has cleared it. One effective reset per startup, no script, no controller. On a panel whose only partners are fixed Modbus cards, that combination is the whole answer.
What the configuration looks like #
The set must be an explicit write of 1. The toggle operation is the first trap: it inverts whatever it finds, so after a restart that retained a 1 it writes 0 and the message never appears. An explicit set produces the same result every run regardless of the variable's previous state.
The ungated periodic reset is the second trap. With no condition, it clears the bit every cycle forever, which works but keeps re-clearing a bit you may set deliberately later. The interlock turns it into a single-shot: while the bit is 1 the reset is permitted; the moment it writes 0, its own Condition goes false and later cycles are blocked. The action stays scheduled in the project — only its operation is gated. If another action sets the bit again, the next cycle clears it once, which is exactly the behavior you want from a startup flag that has one writer.
Configure the set and the reset #
- In the project's variable list, create an internal Boolean variable named for its job, and set the message object's visibility to it: 1 shows the message, 0 hides it. Write both states to the variable by hand and confirm the message follows before any timing exists.
- Create a new Global Action. Set Trigger Type to "Event" and Trigger Event to "On Startup". Its operation writes 1 to the variable — an explicit set, not a toggle.
- Search the project for any other action or script writing the same variable and remove it. Two writers produce faults that look like timer faults.
- Restart the runtime. The variable must read 1 and the message must be on screen. Fix visibility or wrong-screen problems here, before the reset exists.
- Create the second Global Action. Set Trigger Type to "Periodic" and its Frequency to 2 with the unit set to minutes. Read the value and the unit back on screen; do not assume either.
- Set that action's operation to write 0 to the same variable — a reset, likewise not a toggle.
- Enable the interlock on this action and set its Condition to the variable being equal to 1. The condition belongs on the action itself, not on the message object's visibility animation.
- Restart and watch the variable: 1 at startup, 0 at the first periodic execution, message gone, no further writes.
Enter the period in the right unit #
The frequency field takes a number and a unit, and 2 means whatever the selected unit says. The common slip is entering 2 with seconds selected, which removes the message after two seconds instead of two minutes. A countdown variable is the same trap in another shape: a counter decremented once per second counts executions, not minutes.
| Frequency entry | Interval produced | Verdict for a two-minute message |
|---|---|---|
| 2, unit minutes | 120 s | Correct — pair it with the interlock |
| 2, unit seconds | 2 s | Reject — unit slip, 60:1 too fast |
| 1 s periodic decrementing a counter set to 2 | 2 s after two decrements | Reject — counts executions, not minutes |
| 1 s periodic decrementing a counter set to 120 | 120 s after 120 decrements | Only for a deliberate scripted countdown |
The direct periodic reset needs no counter at all, which is why it is the arrangement to build first.
Timing a startup message on an HMIGTO at two minutes #
Inputs: the requirement is a message on the main screen for the first 2 minutes of the application run, on a Magelis HMIGTO running Vijeo Designer V6.2.3 SP3.1 that talks directly to non-programmable Modbus cards. The frequency is 2 minutes, and the conversion is 60 s per minute. The action and condition mechanism is documented for Vijeo Designer across versions, so the service pack is not the deciding factor.
Rule in words: a periodic action executes once per frequency interval, and the reset lands at the first execution scheduled after the startup set; the interlock makes every later execution inert.
Arithmetic: 2 min × 60 s/min = 120 s. The expected first 1-to-0 transition is therefore 120 s after the startup action fires, and scheduler alignment can place it anywhere inside the first full period.
Measurement: restart the runtime, timestamp the moment the startup set executes, and timestamp the first transition of the variable to 0.
Decision: accept the timing when the first transition lands between 120 s and 240 s after the set, then repeat one restart to confirm the transition keeps the same relationship to startup. Earlier than 120 s means something else wrote the variable — most often the frequency unit left in seconds, otherwise a competing writer. Later than 240 s means the Condition never became true: wrong polarity, wrong variable, or the wrong operation on the reset action.
Where the timing lives, and what it is not #
With fixed-table Modbus cards there is nowhere to put a timer except the panel, so the delay lives in these two actions. If a programmable controller were in the project, the cleaner split would be the panel writing the bit at startup and a controller timer clearing it; making the bit an external variable is the mapping covered in adding a Modbus RTU driver and external variables in Vijeo Designer.
The 2 minutes are application minutes. Actions execute once the runtime is operational, so panel boot time before that point sits outside the interval. If the real requirement is "communication established" rather than "application started," the right signal is a heartbeat or the communication control word, not this bit. And if any machine behavior is meant to wait on this message, that interlock belongs in the controller or hardwired — a display timer is not a safety function.
Questions asked
Can I reuse the same bit for another message later?
Not cleanly. Any action that sets the bit again re-arms the periodic reset, and the next cycle clears it within one period, taking the second message with it. Give each timed message its own internal bit and its own pair of actions.
Should the set action trigger on entering the main screen instead?
No. A screen-entry event fires every time an operator returns to that screen, so the message would reappear on each visit. The On Startup event fires once per application run, which is what a startup message needs.
Is a script needed for the delay?
No. The startup set, the periodic reset and the condition do it with actions alone. A scripted countdown only earns its place when the delay must change at runtime; then decrement a counter from 120 on a 1 s frequency and check where its first tick falls.
Can I test the logic without waiting two minutes each time?
Yes. Temporarily set the frequency to 5 s and confirm the full sequence: set at startup, reset at the first execution, no further writes while the bit stays 0. Then return the frequency to 2 minutes and do the timing measurement once against the real period.