Refactor DALI component: remove Modbus bridge support, update documentation, and enhance bridge model handling

This commit is contained in:
Tony
2026-05-04 01:19:24 +08:00
parent 307c480aa0
commit 402d6a451b
11 changed files with 76 additions and 388 deletions
+3 -7
View File
@@ -1,6 +1,6 @@
# ESP32-S3 Bridge Example
This ESP-IDF example wires `dali_cpp` into a standalone application and demonstrates how to register strongly typed Modbus and BACnet bridge models.
This ESP-IDF example wires `dali_cpp` into a standalone application and demonstrates how to register strongly typed bridge and BACnet models. Modbus runtime support now lives in the native gateway project.
## Environment
@@ -21,13 +21,9 @@ idf.py build
- `DaliBridgeEngine` resolving model bindings.
- `BridgeProvisioningStore` loading and saving model/config state in NVS.
- `DaliModbusBridge` mapping Modbus TCP holding-register writes to DALI operations.
- `DaliBacnetBridge` mapping BACnet property writes to DALI brightness percentage updates.
- A simple Modbus TCP listener supporting write-single-register (`0x06`) and write-multiple-registers (`0x10`).
- Placeholder DALI gateway callbacks where you can connect your UART transport.
## Modbus Mapping Notes
## Modbus Notes
- The example listens on port `1502` by default.
- Holding register `0` maps to bridge register `40001`.
- The default config is stored to NVS on first boot and reused on later boots.
The gateway implementation in `gateway/components/gateway_modbus` owns Modbus TCP, generated DALI point tables, and provisioned Modbus overrides. Use `gateway/apps/gateway` to exercise Modbus behavior.