Main result Workshop IPC i5 / 16 GB Backend tag budget 500k-1M tags Fits a regular production-line HQControl host. A 16 GB IPC is a practical starting point for 500k-1M tag projects; near the 1M mark, pair it with a dedicated database host. The real scale limit sits on the PLC side; confirm tag count × scan rate through field load tests.
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 reserved2M-tag configuration reference: about 13.1 GB memory / 25% CPU reservedUseful 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 GB32 GB: recommended for 1M-2M tag server deployments64 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.
Compatibility result Supported Reason and guidance Supported with version-specific limits PowerPoint 2016 / 32-bit Morph / smooth transition is not supported. Multi-state color and path animation have version-specific limits. Use move / scale / opacity combinations instead. 32-bit / 64-bit does not change export compatibility; it is shown only to confirm the installation environment.
Hide when not enabled 当某个交互在当前条件下不应允许操作时，Hide when not enabled 可以隐藏入口，避免用户误以为对象可操作。它适合权限不足、条件未满足或上下文未准备好的场景。
