v5.3.2

Bugs Fixed

• Fixed #144: ModbusRtuServer Start functions handle IModbusRtuSerialPort inconsistently

v5.3.1

Bugs Fixed

• Fixed #141: Inconsistency in WriteMultipleCoilsAsync Function Signature

v5.3.0

Features

• Implement ModbusRtuOverTcpClient.cs (#99) Thanks @schotime!

v5.2.0

Features

• Make IsConnected an abstract member of ModbusClient (#115)

v5.1.0

Features

• Add option for raising event even if values of buffer have not changed (#96)
• support for WriteMultipleCoils (#111)

Bugs Fixed

• Fixed propagation of cancellationToken (#100)
• Fixed exception for malformed messages (#101)
• typo in ModbusClient docstring (#95)
• SampleServerClientTCP broken? (#102)

v5.0.3

• The Modbus TCP server now returns the received unit identifier even when its own unit identifier is set to zero (the default) (solves #93).
• The protected methods AddUnit() and RemoveUnit() have been made public.

v5.0.2

Bugs Fixed

• The Modbus RTU client did not correctly detect response frames (thanks @zhangchaoza, fixes #83)

v5.0.1

Bugs Fixed

• The Modbus server did not correctly detect request frames (thanks @jmsqlr, #75 (comment))

v5.0.0

Breaking Changes

• The previously introduced TCP client constructor overload was called Connect although it expected a totally externally managed TCP client which should already be connected. This constructor is now named Initialize and its signature has been adapted to better fit its purpose. The passed TCP client (or IModbusRtuSerialPort in case of the RTU client) is now not modified at all, i.e. configured timeouts or other things are not applied to these externally managed instances (#78).

Features

• Modbus TCP and RTU clients implement IDisposable so you can do the following now: using var client = new ModbusTcpClient(...) (#67)
• Modbus server base class has now a virtual Stop method so the actual server can be stopped using a base class reference (#79).

Bugs Fixed

• The Modbus server ignored the unit identifier and responded to all requests (#79).
• Modbus server side read timeout exception handling is more defined now:
  • The TCP server closes the connection.
  • The Modbus RTU server ignores the exception as there is only a single connection and if that one is closed, there would be no point in keeping the RTU server running.
• Modbus server did not properly handle asynchronous cancellation (#79).

See API changes on Fuget.org

Thanks @schotime and @LukasKarel for your PRs!

v4.1.0

Features

• Added a new constructor to the ModbusTcpClient which allows passing your own externally managed TcpClient.

Fuget API Diff

https://www.fuget.org/packages/FluentModbus/4.1.0/lib/netstandard2.1/diff/4.0.0/