If this does not help, please provide the version that you using, a screen shot of the main screen, and a debug log for me to review.
With this information, I will be better able to help you. Thanks. Doug Lyons
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There was a regression for Modbus Function Code 15 (Hex 0x0F) in the most recent revision of this project, so you may be able to use version 8.21.2.7 and have this work. I plan to create a fix and upload it to SourceForge within a week or so. Thanks. Doug Lyons
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the quick response! Initially, I used v8.21.2.7. But there was another problem: the correct command to write a set of bit registers (the second and subsequent) is perceived as erroneous, while reading is successful
In the case that you show above, it may help if you choose the option for "Use Long Timeouts".
This changes the numbers from 100ms/500msto 250ms/1000ms. The two numbers represent the maximum time between characters and the maximum time before a message times out. These numbers are only approximations. Thanks. Doug Lyons
Balaji, Are you using "seperate set of registers for each station"?
Please review https://sourceforge.net/p/modrssim2/tickets/22/
If this does not help, please provide the version that you using, a screen shot of the main screen, and a debug log for me to review.
With this information, I will be better able to help you. Thanks. Doug Lyons
The program interprets the received bytes as bits
There was a regression for Modbus Function Code 15 (Hex 0x0F) in the most recent revision of this project, so you may be able to use version 8.21.2.7 and have this work. I plan to create a fix and upload it to SourceForge within a week or so. Thanks. Doug Lyons
Thanks for the quick response! Initially, I used v8.21.2.7. But there was another problem: the correct command to write a set of bit registers (the second and subsequent) is perceived as erroneous, while reading is successful
In the case that you show above, it may help if you choose the option for "Use Long Timeouts".
This changes the numbers from 100ms/500msto 250ms/1000ms. The two numbers represent the maximum time between characters and the maximum time before a message times out. These numbers are only approximations. Thanks. Doug Lyons
Please try the new version 8.21.2.9 that was just uploaded. Thanks.
I checked everything works! Thank you very much!
Reported as working now with new version 8.21.2.9, so closing