31 lines
1.8 KiB
Markdown
31 lines
1.8 KiB
Markdown
# ModbusMQTT
|
|
|
|
This repository is a workspace for developing ModbusMQTT and the crates developed in the course of the project.
|
|
|
|
View the appropriate READMEs in each package directory for details about each.
|
|
|
|
## [`modbus-mqtt`](./modbus-mqtt)
|
|
|
|
[](https://hub.docker.com/r/bjeanes/modbus-mqtt)
|
|
[](https://crates.io/crates/modbus-mqtt)
|
|
[](https://docs.rs/modbus-mqtt/latest/modbus_mqtt/)
|
|
|
|
|
|
ModbusMQTT is a bridge between Modbus devices and MQTT. It aims to allow the operator to generically expose any compatible Modbus device as though its API were MQTT.
|
|
|
|
## [`sungrow-winets`](./sungrow-winets)
|
|
|
|
|
|
|
|
|
|
|
|
This is a barebones API client for reading and writing settings for Sungrow solar and hybrid inverters equipped with a WiNet-S communications module. Its only known use is `tokio_modbus-winets` (see below).
|
|
|
|
## [`tokio_modbus-winets`](./tokio_modbus-winets)
|
|
|
|
|
|
|
|
|
|
|
|
This wraps `sungrow-winets` client in the appropriate traits from [`tokio-modbus`](https://crates.io/crates/tokio-modbus) to allow accessing the Modbus registers which the Sungrow WiNet-S dongle exposes. The reason for this is simply that Sungrow's TCP Modbus support is buggy and inconsistent (though improving).
|