What HQ VISU Designer Is: Product Positioning and End-to-End Flow

HQ VISU Designer (HQ VISU PowerPoint) is a visualization page-authoring and export tool that runs inside Microsoft PowerPoint. Its goal is not to make ordinary slides, but to turn PPT pages into runnable HQ VISU screen packages. After install, an HQ VISU tab appears in the PowerPoint ribbon. It has four parts: the PowerPoint plugin (the editing entry), the Behavior Browser (visual configuration of components, behaviors, scripts, properties), the template and page editor (configures input, keypad, table and other templates), and the exporter (exports the PPT to an HTML + SVG + JS + JSON + IMG screen package).

Overview

Overview: What HQ VISU Designer Is: Product Positioning and End-to-End Flow

HQ VISU Designer is a screen-authoring and export tool that lives inside PowerPoint. You design pages in PowerPoint as usual, bind data and behaviors to the shapes, then export one screen package and run it in HQControl. This section explains what it is, who uses it, the value it gives, and the full path from drawing to going live.

What it is and what it gives you

HQ VISU Designer (HQ VISU PowerPoint) is a visualization page-authoring and export tool that runs inside Microsoft PowerPoint. Its goal is not to make ordinary slides, but to turn PPT pages into runnable HQ VISU screen packages. After install, an HQ VISU tab appears in the PowerPoint ribbon. It has four parts: the PowerPoint plugin (the editing entry), the Behavior Browser (visual configuration of components, behaviors, scripts, properties), the template and page editor (configures input, keypad, table and other templates), and the exporter (exports the PPT to an HTML + SVG + JS + JSON + IMG screen package).

It is for end users, field implementers, configuration/commissioning staff, and acceptance/training staff. The value: you build industrial screens with the PowerPoint you already know, wire shapes to PLC tags and interactions by dragging and filling fields, and never have to write a whole front end; draw a device once, save it as a template, and reuse it many times.

In the product line it only owns the "page design and screen-asset delivery" stage: HQ VISU Designer handles screens, templates, interactions, and export packaging; HQ Scan handles IO / tag / point-list data prep before binding; HQControl handles running pages, navigation, permissions, licensing, and deployment.

How to use it: the four-step flow and what you fill in the editor

The overall flow is four steps, mapping to groups on the HQ VISU tab:

1) Draw the page in PowerPoint and set the export size with Page Settings (e.g. 16:9 Wide 960x540, Full HD 1920x1080). 2) Open the Behavior Browser, drag a behavior from the right-hand catalog onto a component node on the left to bind it, then double-click that behavior to open its editor and fill the fields; add logic in Page Script / Global Script when needed. 3) Use Export HTML to export the whole PPT as one screen package. 4) Hand the screen package to HQControl to run.

The fields you actually fill in a behavior editor (each behavior uses what it needs):

  • Definition: the prep area; read tags, define variables, do intermediate math (e.g. var running = ReadTagInteger(...))
  • Condition / Value / Text: returns the result the behavior actually uses (condition, value to write, text to show)
  • Fill / Border / Visibility: fill color, stroke color, show/hide (visual behaviors such as Script Color)
  • Tag Expression / Default / Invert / BitNr / Action: read or write a tag or a single bit (Write Tag, Write Tag Bit)
  • Variable / Value: write a runtime variable on click (Set Variable on Click; do not quote the variable name)
  • target: keypad needs a target input template on the current page; Open Diagnosis takes PLC / ID / DiagnosisControl / GroupRightIndex
// Definition (prep)
var running = ReadTagInteger("PLC1.PUMP.RUN", 0);
var alarm = ReadTagBoolean("PLC1.PUMP.ALARM", false);

// Condition (output; State Color etc. use it for true/false)
running === 1 && !alarm

When to use it

Use HQ VISU Designer when you need a set of industrial monitoring screens that run on HQControl and animate from live PLC data. Two typical scenarios:

  • Build a device-status screen: draw the pump/valve shapes, bind State Color or Blink Color, read the run/alarm tags in Definition, and watch live state on HQControl after export.
  • Build an operator area with input and a keypad: insert an input template bound to a runtime variable or PLC tag, then add a keypad template pointing at that input so the field can write values directly.

A few boundaries to know before you start

These are the common traps; knowing them up front saves rework:

  • You can only bind a behavior by dragging it onto a component node on the left; double-clicking an item in the right-hand catalog does not bind; it only shows: Drag a behavior onto a component node to bind it.
  • The publish unit is "1 PPT = 1 screen package"; when you change global script, global JSON, shared styles, or navigation structure you must re-export the whole package; Current Page is only for page-level changes.
  • Whether a tag write succeeds is decided by the host (HQControl); it may apply permission checks, a confirm dialog, reason input, or async writes, so never assume "called means succeeded".
  • For cross-package navigation use screen-code (qtedit.openScreen(...)) and for same-package use qtedit.openPage(...); do not use relative disk paths like ../../xxx.html as the official jump rule.