HQ VISU MINGXU INDUSTRIAL SYSTEMS

Input HQControl scenario configuration

Choose the panel, station, or server role first. Panels browse and operate screens; HQControl tag services run on an IPC or server.

Choose field role Recommendation

Resource reference Tag-scale resource conversion

Measured sample: 367k tags use about 1.6 GB memory and about 3% CPU on an Intel Core Ultra 7 255H / 48 GB; used only as the conversion baseline.

1M-tag configuration reference: about 6.6 GB memory / 13% CPU reserved
2M-tag configuration reference: about 13.1 GB memory / 25% CPU reserved
Useful for host selection, server budgeting, and field load-test planning

Conversions include about a 1.5x safety margin; CPU percentages are relative to the reference machine (Ultra 7 255H, 16 cores); scale them up for less powerful hosts. Project scale is confirmed together with PLC scan cycle, history writes, alarms, trends, API concurrency, and field load tests.

Server scenario Server deployment guidance

Reserve room for runtime services, database, history data, alarms, trends, and third-party interfaces.

16 GB: fits a 500k-1M tag project budget; close to 1M tags, move the database to its own host or step up to 32 GB
32 GB: recommended for 1M-2M tag server deployments
64 GB: recommended for 2M-4M tag load-test and expansion planning

Production sizing is confirmed across PLC communication, scan cycle, history writes, alarms, trends, and concurrent access. Targets above 2M tags are conversion-based planning figures, confirmed by field load tests.

Connectivity measurement PLC connectivity, types, and import

Verified on: Intel Core Ultra 7 255H / 48 GB · Windows · Siemens S7-1500

PLC connection: S7-1500 connected (TCP + S7 handshake passed)
Data types: 13 / 13 passed (BOOL/INT/DINT/REAL/STRING/TIME/DTL, etc.)
Import speed: about 1,500 points / sec

PLC connectivity and import speed are independent measurements; read them separately from the resource conversion.

PLC collection PLC scale depends on the controller model

HQControl can connect multiple PLCs per project. A single PLC collection scale depends on CPU model, firmware, communication path, exposed variables, DB continuity, and scan cycle.

Symbolic addressing (OPC UA / 4840): follow the PLC OPC UA Server specification. In one S7-1515F-2 PN example, accessible variables are 100,000 and Siemens recommends about 2,000 monitored items for 1s sampling / publishing (a performance recommendation, not a hard limit; higher on newer firmware).
Controller classes differ widely: S7-1200 exposes about 1,000 accessible variables, while S7-1500 ranges from about 50,000 (1511/1513) and 100,000 (1515/1516) up to 200,000 (1517/1518), with monitored-item recommendations rising by model and firmware.
Absolute addressing (S7 TCP / 102): suited to continuous DB batch reads; block length, job data, timeout, and communication load follow the PLC specification.
Large projects can split scan cycles, IO Owners, and server resources by device, then confirm the final scale through field load tests.

The real scale limit sits on the PLC side: maximum tag count depends on PLC model, communication path, and tag count × scan rate. These are not HQControl collection limits; HQControl can collect from multiple PLCs in parallel, so evaluate PLC capacity and server resources separately.

Manual

实时值、Tag 质量和画面问题排查入口 | HQControl

实时问题按链路查，不要把单个 Bad Tag 当成整台设备故障。

迁移与 FAQ诊断

诊断

实时值、Tag 质量和画面问题排查入口

实时问题按链路查，不要把单个 Bad Tag 当成整台设备故障。

Tag bad / stale / unverified

设备连接正常但部分点异常时，先用 Tag 诊断和 Bad 检查复核。`unverified` 表示按需点尚未完成采集确认，不等于 good，也不等于 bad。

检查地址模式和数据类型
按需点没有订阅时不会常驻采集
删除 Bad 点前先按当前 tag_latest 复核

实时值不刷新

按设备连接、采集 Owner、IO Worker、Redis、WebSocket、页面订阅顺序检查。反向代理场景必须启用 WebSocket upgrade。

看系统状态里的 IO / Redis / WebSocket
看 activeHotTags 和订阅来源
看反向代理是否支持 WebSocket

画面空白或菜单打不开

先看画面文件页是否存在 `screens/assets/<screen-code>/index.html`，再看菜单目标路径和 `/settings` 里的公开主机名。

画面文件页能看到入口 HTML
菜单目标路径真实存在
公开主机名不是旧 IP