RealPLC Agent v1.1.4

v1.1.4

The cloud connection is something an Agent keeps by itself now: the RealPLC cloud's address is built in, a paired Agent connects again when it starts, and its credential is renewed when it is used.

• The cloud dialog no longer starts with an empty 云端地址. The RealPLC entry was put in the list of saved addresses only once, when there was no list yet. A list that had lost it afterwards (its one entry deleted, the entry's address empty, or the file unreadable) started the dialog empty from then on, and installing again did not bring it back, because the list is kept with the user's settings. The entry is now put back every time the list is read.
• The RealPLC cloud's own entry cannot be typed over or deleted: the pairing code is the only thing to enter. An address for a LAN or a private deployment is still added with 新增.
• "Agent 启动时自动连接" starts ticked on the RealPLC entry, and an installation that is updated gets that tick once, on its first start with v1.1.4: an Agent that was paired without it connects by itself from then on. A PC whose startup settings were saved with auto-connect off is left alone, and a box that is unticked afterwards stays unticked.
• The startup settings' auto-connect box shows what is saved for the cloud connection in use. It showed a copy of its own, and pressing 应用 could switch auto-connect back on.
• A credential is renewed when it is used. Earlier versions stopped it thirty days after the pairing whatever the cloud said, so every Agent had to be paired again each month.
• A new entry gets wss://www.realplc.com/api/agent-gateway/agent/ws. An entry that already holds one of the RealPLC cloud's addresses keeps it, so an Agent that is paired stays paired and does not ask for a pairing code after the update.
• An address that an earlier version let be typed over the RealPLC entry is not lost: it becomes an entry of its own and stays the one in use.
• A job result the backend will not take is no longer sent for ever. One result written on 2026-09-02 was still being sent on 2026-10-10, 1942 times that day. The backend's "job not found" is final now, a result that is kept is sent again at growing intervals, and one still undelivered a day after it was written is set aside unsent.
• The logs AgentHost writes (cloud-bridge.log, http.log, agent-host.log) roll at 20 MB and keep five older files. They used to grow without limit.

v1.1.4 installs over v1.1.3, v1.1.2, v1.1.1 and v1.1.0. Saved connections and credentials are kept. The Agent's window, AgentHost and CloudBridge change.

Known limits: credentials are renewed once the RealPLC cloud runs the matching change, and until then the cloud still ends one thirty days after the pairing; the four TIA changes of v1.1.3 were run against an offline Openness stub only, because the build machine has no TIA Portal; on scaled displays labels and buttons are still magnified and look soft beside the text that is sharp; the installer is not code-signed.

Validation:

• Openness harness: 120/120, of which the saved cloud addresses: 107/107, CloudBridge authentication: 48/48, result acknowledgements: 33/33 and rolling logs: 12/12
• Release verification: 28/28; engineering regression: 10/10; HMI Runtime self-test, mapping, end-to-end and benchmark runs: PASS
• AgentHost started on what v1.1.3 leaves behind: PASS (the tick, the saved config, and a connection on that very start)
• UI responsiveness harness against a real AgentHost, real-launch and host-started launch tests: PASS
• Installed over v1.1.3 on a paired PC: every installed file is the built one, and the Agent was connected and authenticated seventeen seconds after AgentHost started, with nothing clicked

Installer SHA256:
C7926F9C583F9599D33EE626092114110513D05AE04483A71D156C2DBFE925A3