Detect changes
ThermalDIAG can continuously evaluate temperature rises, current curves, vibration metrics as well as digital and analog signals against project-specific rules. This makes trends, recurring deviations and gradual changes visible.
ThermalDIAG
Define workflows with rule lists – no programming knowledge required.
ThermalDIAG is a local on-premise system for industrial plants where thermal condition, electrical load, mechanical vibration and machine signals need to be monitored, evaluated and documented together.
ThermalDIAG runs locally on suitable Linux IPC hardware, complemented by ThermalDIAG Analytics on Windows. Deployment and integration are agreed for each project.
Benefits
ThermalDIAG can continuously evaluate temperature rises, current curves, vibration metrics as well as digital and analog signals against project-specific rules. This makes trends, recurring deviations and gradual changes visible.
An incident collects rule context, measurements, timestamps, actions and evidence so operators and technicians do not need to reconstruct events from separate sources.
Tickets, snapshots, work notes, measurements and reports support a structured workflow from the first alarm to the completed inspection.
ThermalDIAG Rules
Rules are a core ThermalDIAG function. In a rule list, you define conditions, combine signals and specify automatic responses. Conditions → Filters → Actions: the rule list determines how project-specific monitoring and auxiliary procedures behave.
Compare temperatures, current, flow, digital states or numeric variables with thresholds and reference values. Combine conditions with AND or OR; delta and temperature changes complement direct comparisons.
A schedule, previous incident and activation count within a time window define when a rule may trigger. All enabled filters must pass.
Document incidents, save snapshots, issue messages, control approved outputs or update values, text and display colours. Targets and permissions are configured for each project.
The run signal is active AND a camera temperature exceeds its threshold for longer than the configured minimum duration. A schedule restricts triggering to the intended operating hours. A rule configured for this purpose documents an incident, saves a snapshot and marks the display status red. Hysteresis can prevent frequent state changes near the threshold.
Further applications
ThermalDIAG rules connect measurements, states and approved reactions without classic program code. In addition to alarms, this supports project-specific test and auxiliary procedures that are not safety-related.
A prepared digital output can, for example, actuate a moving component. One or two limit switches provide position feedback while a numeric variable counts cycles and temperature, current or vibration is monitored. This keeps it traceable when and under which conditions a deviation occurs.
An anomaly is assessed in the next applicable rule evaluation cycle. Permitted actions are then executed through their action processors. Calculated numeric variables are available for subsequent rule evaluations. Evaluation and processing are separate sequences on a seconds timescale.
Technical scope:
ThermalDIAG supports supervised test and auxiliary sequences on the Linux IPC on a seconds timescale. Time-critical machine functions, emergency stops and protective interlocks are handled by the independent PLC or safety controller.
Physical outputs may only be enabled by qualified personnel after a project-specific review of the electrical, mechanical and safety-related conditions.
On narrow screens, scroll the tables sideways to read all columns.
This description explains the Rules functions of ThermalDIAG V1.402, dated 2026-11-14.
Each rule has a name, a severity of 1–10, a cooldown, an order and an enabled state. Conditions use AND (all must be true) or OR (at least one must be true). A rule list defines the required behaviour without classic program code.
Available sources depend on the configured devices and project variables.
| Source | Available values |
|---|---|
| AX8 thermal measurements | Spot temperature; Box minimum, maximum and average temperature. |
| Camera and Modbus I/O | Configured numeric measurements, digital states and supported rising/falling edges; counter-capable Modbus inputs also expose counter value and increment. |
| MQTT devices | Numeric and Boolean signals, including configured OpenMV and Shelly values; communication-lost status is also available. |
| OPC UA variables | Readable Boolean, Int32 and Double variables; String variables support text equality and inequality. |
| TUF-2000M flow meter channels | Configured Modbus channels for flow rate, velocity, net/positive/negative total volume, measurement volume, measurement-running and measurement-valid states. |
| Numeric variables | Project variables Num1–Num100, usable as values, references, thresholds and calculation results; an OpenMV-N6 camera result stored in NumX can be checked by another rule. |
| System variables | timer_sec (Unix seconds), local_minute_of_day (0–1439), local_day_of_week (1 = Monday, 7 = Sunday); CPU usage, CPU temperature and RAM usage. |
| Constants | Numeric thresholds and references, including a left-hand constant for Delta; text constants for OPC UA String comparisons. |
| Condition | Evaluation |
|---|---|
| Direct comparison | Compare compatible values with >, ≥, <, ≤, = or ≠; digital-state and OPC UA text comparisons use = or ≠. |
| Delta | Compare the absolute difference, abs(A − B), with a constant or NumX threshold using >, ≥, < or ≤. Supported sources include numeric variables, system variables, constants, measurements, counters and digital values as 0/1. |
| Temperature change | Detect a rise or fall in an AX8 Spot/Box over 1–899 seconds using live samples; no threshold time or hysteresis. |
| Digital edge | Detect a supported camera/Modbus rising or falling transition; the sampling interval is selected to suit the pulse duration. |
| Communication lost | For MQTT sources: direct =/≠ comparison with 0 (healthy) or 1 (stale/offline); no hysteresis. |
Filters decide whether true conditions may open or reactivate an incident. There is one filter of each type per rule. Disabled filters are ignored, and all enabled filters must pass. Evaluation order is Schedule → Previous incident window → Count window.
| Filter | Purpose |
|---|---|
| Schedule | Allow triggering on selected weekdays within daily local-time windows, using the project time zone. Unchecked weekdays are blocked while the filter is enabled. |
| Previous incident window | Require another rule in the same project to have opened/reactivated an incident, or not to have done so, within the selected time window of up to 24 hours. |
| Count window | Require a selected number of separate false-to-true condition activations within a time window. Continuously true conditions count once; the count resets after triggering. |
Condition stability and freshness: Threshold time requires a supported condition to stay true for a configured duration. A NumX duration is rounded down and frozen when the true candidate starts; NumX hysteresis is read again at each evaluation. Hysteresis is available only for supported numeric comparisons. MQTT and OPC UA sources use direct comparisons and Delta.
Evaluation uses fresh, valid readings. IPC CPU/RAM values have a freshness threshold of 15 seconds. Local time values use the project timezone. Project text variables serve the Set text action, while OPC UA String sources serve text conditions.
A calculation action can assign a value or calculate with +, −, ×, ÷, MOD and FMOD and store the result in NumX. Sources include constants, NumX, system variables, AX8 temperatures, compatible numeric/digital Modbus values and counters, numeric OPC UA values and numeric or Boolean MQTT signals. Boolean values use 0/1. System variables are read as sources; results are stored in numeric project variables.
MOD uses rounded integer magnitudes; FMOD uses unrounded magnitudes. A zero divisor is rejected. Constants support up to six decimal places. The final result is rounded to the target precision using ROUND_HALF_UP. Measurement operands are captured for the queued action job; an earlier calculation action can update a variable used by a later action.
The three execution modes of an action
The execution mode determines whether an action starts when the rule becomes active, while it remains active or when its active state ends.
Here, “active” means that the state monitored by the rule is present. This is separate from whether the rule is enabled in the settings.
A – When the rule becomes active
The action starts when the conditions are met, the filters allow activation and the rule changes from inactive to active.
The action is started once for that activation. While the rule remains continuously active, mode A does not start it again. If the active state later ends and the rule subsequently becomes active again, the action starts again.
Example: When an overtemperature alarm begins, save a snapshot and switch on an indicator light.
W – While the rule is active
The action can execute repeatedly while the rule remains active. This mode is suitable for operations that need to be repeated regularly during the monitored state.
Repetition in mode W continues while the rule is active. After the active state ends, this mode does not start any further repetitions.
Example: While the alarm is active, a calculation repeatedly updates a numeric variable.
C – When the active state of the rule ends
The action starts when a previously active rule returns to the inactive state, for example because the condition that caused the alarm is no longer met.
This is a single start associated with the end of that active state. The required closing action must be configured separately: mode C does not automatically undo the actions executed when the rule became active.
Example: When the overtemperature alarm ends, switch off the indicator light.
Different actions in the same rule can use different execution modes. Only the modes supported by an action can be selected for it.
The Mode column lists the available choices; it does not mean that all modes execute automatically at the same time.
| Action | Description | Mode |
|---|---|---|
| Create event | Record an event with an optional message and tags. | A |
| Send a notification to configured recipients. | A | |
| Voice | Speak a configured English, German or Italian message, with optional numeric placeholders and delay. | A, C |
| Snapshot | Save an image from a supported camera assigned to the selected location. | A |
| Set output | Switch a permitted camera, Modbus or MQTT/Shelly output ON/OFF, optionally after a delay. | A, C |
| Cancel pending output | Cancel a waiting output action for the selected target without forcing it OFF. | A, C |
| Set impulse | Generate a timed pulse or pulse sequence with duration, pause, repetition and optional delay. | A |
| Stop impulse | Request a running pulse sequence to finish after at most one further pulse and cancel older waiting work for the target. | A, C |
| Camera torch | Switch supported camera illumination ON/OFF, optionally after a delay. | A, C |
| Cancel pending torch | Cancel a waiting camera-light action without switching the light OFF. | A, C |
| Numeric calculation | Assign or calculate a value and store it in NumX; use numeric and Boolean MQTT signals as sources. | A, W, C |
| Reset DI counter | Reset a digital-input counter that supports and permits resetting. | A |
| OPC UA write | Write a configured, correctly typed constant to a permitted OPC UA variable. | A, C |
| Start OpenMV-N6 camera check | Start an inspection on the assigned OpenMV-N6 camera using configured result and send-time NumX variables. | A |
| Get OpenMV-N6 camera check status | Query the current OpenMV-N6 camera inspection and publish its validated result into the configured NumX variable. | A, W, C |
| Set text | Replace a project text variable with configured language-specific text values. | A, W, C |
| Set display colors | Change the foreground and/or background color of a selected display cell. | A, W, C |
| Start TUF-2000M flow meter measurement | Start a measurement session using a fresh meter-counter boundary reading and a configured maximum permitted delay. | A, C |
| Stop TUF-2000M flow meter measurement | Stop the measurement session using a fresh boundary reading and retain the measured volume and session status. | A, C |
OpenMV-N6 camera: The Start action begins the inspection; Get status subsequently retrieves the validated result.
TUF-2000M flow meter: The actions define the start and end of a software measurement session using the meter totalizer. Pump control and management of the device counter are configured separately.
Cooldown defines the wait before reactivation. Actions are processed individually in the configured order. Delayed jobs are scheduled; cancellation removes waiting jobs. Stop impulse ends the sequence in a controlled way according to its pulse parameters.
Device capabilities, write permissions, enabled runtime and licensing still apply. The Incidents view shows activations, filter blocking and action results.
Time Delta: Delta uses the absolute difference, abs(A − B), including timer_sec. With timer_sec and NumX, the result is abs(timer_sec − NumX) regardless of operand order.
MQTT calculation operands: Numeric signals and Boolean signals as 0/1 are supported. The fresh, valid reading is matched to its configured source and retained for the queued action job.
Measurement service
After technical consultation, you can commission a time-limited measurement with a documented evaluation. The measurement setup, duration and prerequisites are set out in an individual quotation.
Use and integration
ThermalDIAG is available as local software. Configuration, scope and delivery dates are set out in the individual quotation.
System requirements
ThermalDIAG runs locally on a suitable Linux industrial PC (IPC). The exact sizing depends on the number of cameras, measurement points, signals, recording duration and required integration.
Used environments include Ubuntu 22.04 with 4 GB RAM in WSL, on Linux PCs and on an OnLogic CL260, as well as the UniPi Edge E410 ARM64 platform.
ThermalDIAG
ThermalDIAG extends shared monitoring with liquid measurement, OPC UA, N6 inspection workflows and configurable displays.
Users assemble displays from measurements, digital states, text and images. Content updates automatically. The editor offers live preview and full-screen view; decimal places, text styles and colours are adjustable. Rules can change text and field colours.
The ultrasonic flow meter is integrated through Modbus RTU. Flow rate, velocity, totalizer values and measurement state are available for Visualization and rules. Displays also offer litres and l/min. Start/Stop measurements can be requested manually or through rules.
Multiple OPC UA connections can be configured per project. Selected Boolean, Int32, Double and String variables can be read and used in rules. Numeric and Boolean values support history; approved writable targets can be set manually or through rules.
Rule actions start a configured N6 inspection and explicitly request its result. Results can be assigned to numeric variables. The camera can be assigned to a location; a snapshot can retrieve the JPEG of the latest available inspection.
Each project provides 100 text variables and 100 image slots alongside numeric variables. Texts have separate German, English and Italian values. Rules can set texts; snapshots can update image slots. The same content can appear on multiple displays.
One capture can be archived, sent to an image slot or used for both purposes. Voice actions support Piper and browser speech, with up to ten ordered values. CPU usage, RAM usage and CPU temperature can also be used in rules and calculations.
A successful start begins measurement at zero; Stop retains the result. Measured volume and total volume since IPC start add validated amounts in both flow directions. The display identifies the measurement state; selected TUF fields can retain the last valid value in grey. The documented water tests illustrate data transfer and Start/Stop. Installation and calibration are defined for the application.
OPC UA data types and server profiles are matched to the installation. Analytics, backtesting and publishing use the feature profile agreed for each task.
Users assemble their own displays from measurements, states, text and images. Content updates automatically; fixed numbers and text can be added through manually maintained project variables. Target values, shift notes and work instructions can therefore appear alongside current data.
The grid fills the available full-screen area; font sizes adapt to the space and images retain their aspect ratio. 8–10 large values suit a clear hall display, while 40–60 smaller values suit a detailed workstation. These are layout examples; monitor size, text length and viewing distance determine the arrangement.
A basic PC with a current browser and a LAN or WLAN connection to the Linux IPC is enough at the hall monitor. ThermalDIAG acquires and processes data on the IPC; the display PC opens the selected view. Authorized users can also change text and values from another workstation.
Explore integrationInterface
The images illustrate the ThermalDIAG interface.
Shared signal context
Visualization separates temperature history, analog inputs, vibration, digital states and numeric variables into clear bands. CPU usage, memory usage and CPU temperature can also be viewed for the latest 15 minutes. Signal aliases and technical names remain visible together.
Thermal-camera ROIs and other temperature measurements show local thermal changes.
Current, voltage and other analog channels are grouped by compatible unit for meaningful comparison.
Velocity, acceleration, frequency, kurtosis and crest factor support mechanical condition monitoring.
Camera I/O and multiple Modbus gateways provide time-aligned inputs, outputs and relay states. DI counter values appear alongside the digital signals.
Banner QM30VT2 and Seneca T201DCH100-OPEN are supported reference configurations. Naming, units and scaling are verified for each project.
A shared cursor links the selected charts. The tooltip shows the nearest value for every visible curve, with a colour marker and an individual timestamp when sample times differ. The cursor shows the time difference from the marked position. Each series keeps its source visible.
In operation
Licence status and resumption
The licence page displays the current status in colour and warns when no more than 14 days remain.
Typical use areas
ThermalDIAG combines the sensors, signals and operating states suited to the measurement task.
Temperature, phase current, vibration metrics and machine state are viewed together so load-dependent or mechanical anomalies become easier to classify.
Thermal image data can be combined with current, switching or enable information for terminals, relays, load circuits and distributions.
ThermalDIAG supports combined views of temperature, signal state and measurements in plants with changing operating states.
When temperature rise, flow, enable or switching state must be interpreted together, ThermalDIAG keeps the relevant data in one history.
Not every project needs to become a permanent system immediately. ThermalDIAG can also be used as a time-limited measurement and diagnostics setup.
Incidents and tickets help turn an alarm into a traceable task with responsibility, measurements, notes, evidence and completion.
Project workflow
The following sequence describes project-specific setup after technical consultation and agreement on the order.