search

Enser45 / nmodbus

Automatically exported from code.google.com/p/nmodbus
0 stars 0 forks source link

Wrong Transaction Id returned by ModbusTcpSlave #39

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Create a ModbusTcpSlave
2. With a Modbus Master send a ReadHoldingRegister Request to the Slave
with TransactionId = 0

What is the expected output? What do you see instead?
The ModbusTcpSlave should return a response with transactionId=0 but 
returns transactionId=1 this produces an error on the ModbusMaster.

What version of the product are you using? On what operating system?
NModbus 1.8.0.0, VS2008 C# WinXP

Please provide any additional information below.
See the Wireshark Dump in the Attachment.

Original issue reported on code.google.com by m...@hesotech.de on 9 Oct 2008 at 10:28

Attachments:

GoogleCodeExporter commented 8 years ago 
I was (erroneously) assuming 0 was not a valid transaction ID. Will fix 
shortly, 
thanks for the detailed bug report!

Scott

Original comment by sja...@gmail.com on 9 Oct 2008 at 1:49

GoogleCodeExporter commented 8 years ago 
Fixed in the trunk. Apologies for the delay.

Original comment by sja...@gmail.com on 24 Nov 2008 at 2:46