dali/gateway
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add InfoLed configuration XML for KNX application

Browse Source 
- Introduced a new XML file `InfoLed.part.xml` to define the Info LED configuration for the KNX application.
- The file includes manufacturer data, application programs, and dynamic parameter blocks for configuring Info LEDs.
- Logic for showing/hiding default checkboxes and function tables based on user selections is implemented.
- Parameter blocks are structured to allow customization of Info LEDs with appropriate UI hints and layout.

Signed-off-by: Tony <tonylu@tony-cloud.com>
This commit is contained in:
Tony
2026-05-28 17:20:10 +08:00
parent 803348ea3a
commit 4c9f26a638
228 changed files with 2393 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files
components/gateway_knx/oam_knxprod/README.md
+11 -1
View File
@@ -21,6 +21,13 @@ The XML keeps the upstream router/coupler shape and absolute memory segment whil
The secure proxy capability is advertised with `CouplerCapabilities="SecurityProxy"` on `Hardware2Program` and `MaxSecurityProxyGroupKeyTableEntries` on the application program, matching the secure proxy-enabled ETS database shape.
The OpenKNX module dependencies needed by this producer source are vendored under `deps/` so generation does not require an external OpenKNX checkout:
- `deps/OGM-Common/` provides `Common.share.xml`, `Common.Router.share.xml`, `InfoLed.part.xml`, `Common.script.js`, `library.json`, and producer baggage assets.
- `deps/OFM-Network/` provides `Network.share.xml`, `Network.script.js`, `library.json`, and producer baggage assets.
Dependency strings are localized by `Gateway-Dependency-Translations.xml`. Dependency context-help documents are kept with the vendored modules in German plus translated English, Chinese, and Japanese help folders; the generated application uses the English help source as its default context help through OpenKNXproducer's legacy context-help baggage placeholder. OpenKNXproducer still emits that selected context-help baggage with its legacy `Help_de.zip` generated name, so keep the `Help_en.zip` source mapped to the `%FILE-HELP-de%` placeholder unless producer support for language-specific context-help baggage changes.
The runtime identity must stay synchronized with `gateway/components/gateway_knx/include/gateway_knx_internal.h` and the OAM router Kconfig defaults in `gateway/apps/gateway/main/Kconfig.projbuild`.
## Validation
@@ -28,7 +35,10 @@ The runtime identity must stay synchronized with `gateway/components/gateway_knx
Run a well-formed XML check from the repository root:
```sh
xmllint --noout gateway/components/gateway_knx/oam_knxprod/*.xml
xmllint --noout \
gateway/components/gateway_knx/oam_knxprod/*.xml \
gateway/components/gateway_knx/oam_knxprod/deps/OGM-Common/src/*.xml \
gateway/components/gateway_knx/oam_knxprod/deps/OFM-Network/src/*.xml
```
Then run OpenKNXproducer with `Gateway-OAM-IP-Router.xml` and import the generated product database into ETS. ETS validation should confirm the router imports as a secure-capable KNX/IP router, exposes 16 tunneling interfaces, and supports secure tunneling plus security proxy table download/verify.