SCADA Things
← Articles
LangEN한국어
SCADA Basics/3 min read/— views

Try a Live Operational State Tutorial

A short hands-on walkthrough that turns one temperature signal into alarm state, switch action, HMI feedback, and an event log using the StateX tutorial.

StateXTutorialHMIAlarmsControlOperational State

Why this tutorial exists

Many SCADA and HMI examples explain concepts with screenshots or diagrams. That is useful, but it is easier to understand operational state when you can touch a small live example.

The StateX tutorial is designed as that first-touch example. It keeps the full app on hold and starts with one simple story:

  • a temperature signal,
  • a low/high alarm band,
  • a heater switch,
  • an HMI-style screen,
  • and a plain-English event log.

You do not need to configure a PLC, create tags, or sign in before the idea makes sense.

The scenario

The tutorial behaves like a small water-heater control screen. A temperature value moves over time. StateX interprets that value against the alarm thresholds and decides what the operational state should be.

In plain language:

  • If the temperature is too low, the heater switch turns ON.
  • If the temperature is inside the safe band, the system keeps watching.
  • If the temperature is too high, the heater switch turns OFF and the screen shows the high-state condition.

This is intentionally small. The point is not the heater. The point is the pattern: signal → state → action → event.

What to try first

Open the tutorial and walk through the checklist:

  1. Turn on the device.
  2. Connect the LAN cable.
  3. Start the StateX Edge Agent.
  4. Connect to StateX.

As each step is checked, the HMI changes from setup mode into a live control screen. When the checklist is complete, the StateX display shows the live signal, operational state, heater switch, and event text together.

Try it here: Start the live StateX tutorial.

What this teaches

The example compresses several common SCADA ideas into one page:

  • Tag naming: the raw value becomes a readable temperature signal.
  • Alarm interpretation: thresholds become meaningful low, normal, and high states.
  • Control state: the switch output is shown as a result of the interpreted state.
  • Operator feedback: the HMI explains the current condition without requiring a tag table.
  • Event logging: the tutorial writes plain-language events that describe what changed.

That is the practical difference between collecting values and presenting operational intelligence.

How this maps to real projects

In a real SCADA, HMI, or industrial data project, the same pattern appears with larger equipment:

  • A pump has pressure, flow, permissives, faults, and command feedback.
  • A conveyor has speed, running feedback, jam detection, and manual/auto state.
  • A tank has level, valve position, fill mode, drain mode, and alarm state.
  • A production cell has machine state, process state, alarm state, and recipe or batch context.

The details change, but the useful question stays the same:

What state should this signal help someone understand?

When to customize

After the tutorial makes sense, customization belongs in the StateX app. That is where a team can map real devices, define tags, tune rules, and build a more specific operational view.

For a first visit, though, the better path is simple:

  1. Read the concept.
  2. Try the tutorial.
  3. Understand the signal-to-state pattern.
  4. Customize later if the pattern matches your equipment.

Start with the live example: StateX Tutorial.