返回资讯中心
外部精选
软件工程
#开发者实时流

Show HN: Open-source AAS digital twin studio with live PLC data collection

Author, validate, serve and collect live values for AAS (Asset Administration Shell) — in one web app.

Hacker News 最新effectsno12026/10/19 · 27 天前30 分钟阅读

以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。

Author, validate, serve and collect live values for AAS (Asset Administration Shell) — in one web app. Upload one machine's AASX, see exactly which rules it breaks, and fix what can be fixed in one step.

This used to take three tools. VEXPLOR AAS Studio brings the work together and is built so that people new to AAS can follow along.

Not affiliated with, and not derived from, the tools above — it combines the same jobs in one place.

New here? Click "Start with a sample" on the start screen to open a fully filled equipment file and a process structure.

Docs: Usage · Install · Deployment & hosting · The 52 rules · Using it with Logic Studio — every document is also available in Korean.

AAS is in place as a standard. Putting it into a factory is still work left outside the specification.

A review of ten years of AAS research (IEEE Access, 2025) names integration with existing machines and systems as a key challenge holding back adoption. Several studies point to the effort of building an AAS by hand, and the open tools are split into editors, servers and libraries, so collecting field values means mapping it yourself in configuration files. VEXPLOR AAS Studio lets software take on that work, so an AAS does not end as a document but becomes operating data with live values from the machines on the floor.

There are real line deployments (Bosch Rexroth and others). They adopted AAS to end months of integration work whenever machines change — and they too report that creating the AAS itself is the first hurdle for many users. Evidence and sources: docs/background.md.

The receiving validator remains the only authority on acceptance. This tool is a pre-check.

Open & edit Load AASX (JSON or XML), browse it as a tree, edit values, elements, submodels and concept descriptions. Fill many values at once from a submodel value table or from a CSV equipment list

Lint 52 rules in three layers — package structure (L1), metamodel constraints (L2), submission business rules (L3)

Auto-fix Preview the fixable findings (19 rules), choose, apply at once. Every relocation is recorded

Report A printable HTML validation report

What to fill With the IDTA templates installed, every value row shows required · collected · optional, and "Show only what to fill" hides the rest

Undo & history One-step undo, and restore a submodel to an earlier point

Types and units Split a type file into units; when the type changes, review the differences line by line and pull only the lines you choose — values edited on site are never overwritten

Process bundles Company → line → process → equipment → part. Group machines into a process and export a submission bundle

Data collection Read live values from OPC UA · Modbus TCP · MQTT devices, and directly from S7 and MELSEC (MC protocol) PLCs — read only, a VEXPLOR extension binding not yet checked on real PLCs — addressed by the AID submodel inside the AAS. Each value shows whether it is live, stale or missing, and each machine gets a daily status bar (running · stopped · alarm). Add dozens of tags from one pattern

Standard API IDTA Part 2 REST API, so other systems can read the AAS held here

MES · ERP · CMMS integration A pull feed of every change and runtime event (CloudEvents), signed webhooks and MQTT, equipment / BOM / hierarchy / maintenance / document exports in JSON or CSV, ERP numbers kept next to the AASX, and server-side state, alarm, counter and threshold rules. A secure OPC UA server (accounts + encryption). See docs/integration.md

Accounts Admin / editor / viewer, with an audit trail of who changed what

English & Korean, light & dark The interface and everything the server writes — findings, rule descriptions, the validation report, bundle README, errors — come in English or Korean. If you never choose, the browser language decides (Korean browser → Korean, anything else → English). Light and dark themes

What's new in 2.3 – 2.10

Feature Release Detail

S7 and MC protocol, read directly 2.10.0 Siemens S7-300 / 400 / 1200 / 1500 (ISO-on-TCP) and MELSEC Q · L · iQ-R · iQ-F (MC protocol 3E binary) are read without a gateway — read only. Addresses are written as the engineering tool shows them (DB10.DBD4:REAL, D100, D10.3). AID 1.1 has no binding for either, so this is a VEXPLOR extension binding, marked by our binding IRI; other AID tools do not read these interfaces. Tested against test servers built from the published formats — not yet checked on real PLCs. The server reads them with COLLECT=on, and the remote collector from VEXPLOR Edge 1.2.0 — usage §8

Remote collector on Windows 2.10.0 Settings → Remote collectors → "+ Connect a collector" has a Linux and a Windows tab. The Windows tab gives one line for Command Prompt or PowerShell (run as administrator) that downloads, checks the hash, installs and starts the Windows service — it changes no execution policy. Needs VEXPLOR Edge 1.2.0 or later (Windows x64), whose service install is tested on GitHub's Windows runners; not yet on a factory PC — remote collector install

S7 and MC in the edge contract 2.10.0 The read list's protocol adds S7 and MC; the contract stays vexplor.edge/1. An edge older than 1.2.0 does not read such an interface, reports why (S7 is not read by this edge yet) and keeps reading the others — contract §4

AAS metamodel V3.0 · V3.1 · V3.2 2.9.0 Opens files of all three versions — an XML file by its namespace, a JSON file (no version marker) by the lowest version that holds its content — and remembers the version each file came in as. Download AASX writes that version unless you pick another; new equipment, samples and passport templates are V3.1, the version KOSMO asks for. Writing a lower version lists every field it leaves out, with its value, and refuses values it cannot express (assetKind Role or Batch, a missing entityType …) unless you tick "download with the values as they are". V3.1 · V3.2 output is checked against the official JSON schemas in the tests — the official validator aas-test-engines 1.0.3 checks V3.0 only. Usage §4-10

Product passport (DPP) templates and checks 2.9.0 "Start from a product passport (DPP) template" on the start screen opens one of eight IDTA templates as published (CC BY 4.0): DPP Part 1 metadata (IDTA 02099-1 1.0.2) and the seven parts of the battery passport (IDTA 02035-1 – 7). Rules DPP-1 – DPP-5 check the passport metadata: the seven mandatory items, granularity (Model · Item · Batch), lastUpdate in UTC, content specification ids, and granularity against the shell's assetKind. This supports writing and checking passport data; it is not a verdict on conformity with the EU DPP regulation

Checks follow the file's version 2.9.0 52 rules, up from 44. AASd-090 and AASd-120, removed in V3.1, apply to V3.0 files only; PKG-FILE-URI and the idShort pattern follow each version's official schema; new AASd-137 · AASd-138 for V3.2 and PKG-MM-VERSION for content the declared version cannot hold (a V3.2 Batch in a V3.0 file). Below V3.2, AASd-119/129 now also look inside Operation variables

Korean and spaced attachment names in V3.1 · V3.2 2.9.0 Those versions accept only URIs as attachment paths. Downloading as V3.1 or V3.2 percent-encodes such names in the model and in the package parts, relationships and content types, so the reference still finds the file; this tool shows the original name. V3.0 output is unchanged

Part 2 under /api/v3 2.9.0 Clients generated from the V3.1 · V3.2 OpenAPI call /api/v3/…; the same routes answer there as under /api/v3.0. Endpoints new in V3.2 ($recent-changes, $history, $signed, asynchronous packages) answer 404

XML files read as written 2.9.0 Comparing the official examples' XML with their JSON found four reading faults, V3.0 files included: Range min and max were read as false (both bounds lost), an empty <administration/> as an empty string, an OperationVariable value as a one-item list, and the V3.2 unit data specification was not recognised. A file uploaded as XML before 2.9.0 keeps what was read then — upload it again

Remote collector intake, faster and whole 2.8.1 A batch from a remote collector is one write to the database: the values of every file in it and the record that it arrived go in one transaction, so a batch is stored whole or not at all. Before, each value was its own write, which capped a 4-core test server near 11,500 values a second with the database half idle; the same server now takes about 50,000. The remote collector list reads each file once per request instead of once per collector, and approving one collector writes only that collector. PG_POOL_MAX sets the number of database connections (default 10) — install

Server status while the database is down 2.8.1 With the database stopped or overloaded, "Server status" answered after more than 10 seconds or not at all. It now answers within about 7 seconds and shows the store connection as failed

Security and login on collection links 2.8.0 "Create collection link" picks the OPC UA security mode (Sign · SignAndEncrypt) and policy, and "Login required" for OPC UA and MQTT. The user name and password never go into the equipment file — they stay in the server's credentials file and the factory PC's credentials.json, keyed by the endpoint. "Load from equipment" connects with the chosen security and login. An old MQTT link with a password in its address is left out of the remote collector list and rule AID-1 says so (MQTT login needs VEXPLOR Edge 1.1.0 or later)

Why a read failed is kept 2.8.0 Automatic collection and remote collectors store the reason with the value. The row keeps "Read failed — reason" after the screen is opened again, and Modbus and MQTT, which have no quality code, show it too

Units, Modbus order, read period 2.8.0 A unit on every tag row, byte and word order (ABCD · CDAB · BADC · DCBA) on Modbus rows and a read period per machine, all on the screen. Remote collectors read at that period, and "Edit link" opens filled in with the current link

Collector health and server status 2.8.0 Each row of the remote collector list carries the server's OK · Warning · Problem badge and its reason in one line (free disk space, failed sending, clock offset, read success rate, queue, silence, no equipment connected). "Show state" opens the factory PC (CPU, memory, disk, uptime, clock offset), the line to the server, response time, success rate and reconnects per equipment, and the last 24 hours (values sent by VEXPLOR Edge 1.1.0 or later). Admins see the server's own state in Settings (store connection, disk, batches of the last hour, version). Usage §8-8

One-click remote collector 2.7.0 Settings → Remote collectors → "+ Connect a collector" — check the server address and the read list, press one button, and you get one line to paste on the factory Linux PC. That line downloads, checks the hash, installs, registers and approves; the screen turns to "Receiving" the moment the PC connects. The same screen shows the last batch, values received and machine connections, and pauses, resumes or revokes. Admins turn remote collection on right there (servers with EDGE empty)

VEXPLOR Edge, its own open source 2.7.0 The remote collector now ships from its own repository waceinc/vexplor-edge (Apache-2.0) with its own version (1.0.0). The canonical contract vexplor.edge/1 lives there; this server receives it as is

Collect pane refreshes itself 2.7.0 With a file that has a collection link open, values come in every 10 s, and while a remote collector's values arrive the connection shows "Receiving"

Equipment reader libraries 2.7.0 The release packages add @aas/collector, @aas/fieldbus and @aas/opcua — the remote collector reads OPC UA, Modbus TCP and MQTT with exactly this server's code

Remote collector (VEXPLOR Edge) 2.3.0 One program on the factory PC reads PLCs and sends signed batches out over HTTPS — read only, outbound only. Linux x64 · arm64 (install); Windows will be covered later

Send changes only 2.4.0 OPC UA subscriptions wi

正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。

打开原文
去社区讨论 →