Skip to content

Releases: Apollo3zehn/FluentModbus

v4.0.0-preview.5

28 Jul 10:11
Compare
Choose a tag to compare

Bugs Fixed

  • Fixed a bug that caused Modbus RTU frames to be detected incorrectly under certain circumstances (#75 ). Thanks @iberisoft !

v4.0.0-preview.4

20 Jun 14:27
Compare
Choose a tag to compare
v4.0.0-preview.4 Pre-release
Pre-release

Bugs Fixed

  • Modbus TCP client async read operations are correctly timing out now.

v4.0.0-preview.3

25 May 11:17
Compare
Choose a tag to compare

Features

  • The previously private protected method TransceiveFrame has been made overridable.

Bugs Fixed

  • Connect fails if port is not specified (#69)

v4.0.0-preview.2

19 Oct 08:08
Compare
Choose a tag to compare
v4.0.0-preview.2 Pre-release
Pre-release

Features

  • The Modbus RTU client and server can now use Parity.None in combination with a single stop-bit.

v3.2.1

19 Oct 08:09
Compare
Choose a tag to compare

Features

  • The Modbus RTU client and server can now use Parity.None in combination with a single stop-bit.

v4.0.0-preview.1

21 Sep 14:16
Compare
Choose a tag to compare
v4.0.0-preview.1 Pre-release
Pre-release

Features

  • The Modbus RTU server now supports multiple units which can be created using the constructor or by invoking the server.AddUnit() method (#53). Thanks, @aviatrix.
  • There are new methods to set and get mid-little-endian data.

Breaking Changes

v3.2.0

14 Sep 15:05
Compare
Choose a tag to compare

Features

  • The client now offers an overload to connect to the server using a simple string like 192.168.0.1:502 instead of parsing an IPAddress or Endpoint first.

v3.1.1

23 Jun 08:50
Compare
Choose a tag to compare

Bugs Fixed

  • Async Modbus RTU client did not respect the read and write timeouts.

v3.1.0

13 Apr 11:06
2eb0a8a
Compare
Choose a tag to compare

Features

  • The client now offers an additional async API to communicate to the server.

v3.0.1

25 Mar 09:42
Compare
Choose a tag to compare

Features

  • The server implementations now provide notifications when holding registers or coil data changes.

Breaking Changes

  • Originally, the server relied on natively allocated buffers. With .NET Core's Span support this is not needed anymore. Thus, the four Get...Ptr properties have been removed.
  • Additionally, the buffers are not cleared anymore when the server is stopped or started. This allows preparing the server data before it gets started. The method to clear the buffers manually is still present.
  • See this list for API changes: https://www.fuget.org/packages/FluentModbus/3.0.1/lib/netstandard2.1/diff/2.4.2/