Trying to stabilize the CI build as the last build had only 20% coverage due to wrong detection

This commit is contained in:
2024-03-09 23:38:56 +01:00
parent 24f7cc74a7
commit 946614b86c
3 changed files with 14 additions and 3 deletions

View File

@@ -13,7 +13,7 @@ If you want to speak a custom type of protocol with the clients, you can impleme
**ModbusBaseClient**
This abstract base client contains all the basic methods and handlings required to communicate via Modbus Protocol.
The packages `AMWD.Protocols.Modbus.Serial` _(in progress)_ and `AMWD.Protocols.Modbus.Tcp` have specific derived implementations to match the communication types.
The packages `AMWD.Protocols.Modbus.Serial` _(in progress)_ and `AMWD.Protocols.Modbus.Tcp` _(in progress)_ have specific derived implementations to match the communication types.
### Enums
@@ -40,6 +40,11 @@ The different types handled by the Modbus Protocol.
- Holding Register
- Input Register
In addition, you'll find the `DeviceIdentification` there.
It is used for a "special" function called "Read Device Identification" (0x2B / 43) not supported by all devices.
The `ModbusDevice` is used for the server implementations in the derived packages.
### Protocols