EasyModbusTCP.NET icon indicating copy to clipboard operation
EasyModbusTCP.NET copied to clipboard

Modbus TCP, Modbus UDP and Modbus RTU client/server library for .NET implementations

Results 69 EasyModbusTCP.NET issues
Sort by recently updated
recently updated
newest added

Every time the Available() method is called the program uses about another 100k or RAM.

When the slave machine continuously receives incorrect response and CRC check fails, the stack overflow will occur in an infinite loop ` if (receivedUnitIdentifier != this.unitIdentifier) data = new byte[2100];...

Based on the specification described in this [link](https://modbus.org/docs/MB-TCP-Security-v21_2018-07-24.pdf), I have tried to implement the features that will provide a security-focused variant of the Modbus/TCP protocol by utilizing the Transport Layer...

Hi! I've been using the library in a project. I'm connecting to Modbus RTU flow meters. First I designed the app for one type of them. Now I'm adding a...

If connected with TCP/IP, the connection aborted if there is no poll for sometime with server. It end up with below exception: At this line: stream.Write(data, 0, data.Length-2); System.Net.Sockets.SocketException :...

Using an empty constructor to generate a ModbusClient, then setting its properties. Setting `ModbusClient.Parity = Parity.None;` before calling `.Connect()` results in the internal serialport still creating with `Parity.Even`

我将ModbusClient 用于多线程环境的时候,调用ModbusClient 的ReadHoldingRegisters 方法时,获取到的值有时候是错误的。 (en:When I use ModbusClient in a multi-threaded environment, I sometimes get the wrong value by calling ModbusClient's ReadHoldingRegisters method.) 错误的(The wrong): ![image](https://user-images.githubusercontent.com/56746942/150936684-06558880-e5da-4348-b3cf-dbbd8f466d65.png) ![image](https://user-images.githubusercontent.com/56746942/150936723-90cbab48-3e85-4c88-ad95-c7e288b422c1.png) ![image](https://user-images.githubusercontent.com/56746942/150936815-589fef6c-c021-41d9-8b9c-0219977b72f8.png) 正确的(The correct):...

![QQ图片20220125133440](https://user-images.githubusercontent.com/56746942/150917624-99797630-fde8-4239-aa34-c446dcc6ebd4.png) 上面的图片是Visual Studio2019 Debug 调试运行时抛出的异常。出现的位置是EasyModbusTCP.NET项目的ModbusClient.cs的ReadHoldingRegisters 方法 注意:这个 BUG是偶尔发生的,按照以下说明操作可以大概率重现。 情景重现: 我的程序是具有掉线重连功能的,每隔一秒会检查是否断开连接,如果断开连接则调用 Connect() 重新连接。 ![image](https://user-images.githubusercontent.com/56746942/150918051-68e05976-12dc-4eb1-9f06-240fbb375669.png) 当我启动我的程序,然后再`立刻`启动ModBus Tcp Server 监听端口,最后抛出了异常。 en: Visual Studio2019 Debug debuts an exception thrown at runtime. The location where...

我用的EasyModbusTCP.NET v5.6 当TCP服务器断开连接时,客户端并不能获取到反馈,依然能够读取和写入(显然这是错误的)。 不过,我查看EasyModbusTCP.NET 项目的 ModbusClient.cs 源代码后, 将Connected的代码改为以下代码即可得到正确的反馈。 ``` c# public bool Connected { get{ if (serialport != null) { return (serialport.IsOpen); } if (udpFlag & tcpClient != null) return...

public short[] localArray defined in EasyModbus.ModbusServer.HoldingRegisters, which is not suitable defined as a short[] type because sometimes we need to write a value bigger than 32767 (UInt16) to a single...