adccommunitymod (AutomationDirect) asked a question.
DoMore and BRX reloading due to modbus TCP request. !LOL (not LOL)
Created Date: March 04,2019
Created By: svshow
**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****
Hi. Long story short but when i make a request to read 200 holding registers - PLC reloading. Tried to increase watchdog timeout - no luck. Tried to do the same with BRX - it is reloading after received request. Played with PAC - it does not respond, but at least continue to work properly...
Created Date: March 04,2019
Created by: svshow
Hi. Long story short but when i make a request to read 200 holding registers - PLC reloading. Tried to increase watchdog timeout - no luck. Tried to do the same with BRX - it is reloading after received request. Played with PAC - it does not respond, but at least continue to work properly...
Created Date: March 04,2019
Created by: BobO
There was a bug in the Do-more Modbus/TCP server implementation where an invalid request would result in a buffer overrun. It has been fixed, but not shipped (should be later this month). Pretty sure the maximum valid number of holding registers in a single request is 125.
Created Date: March 12,2019
Created by: Hans Rose
Looks like BobO is correct about number of registers per request.
In Do-More Designer 2.3, the MRX (Modbus Read instruction) throws an error message when trying to have it read more that 125 registers:
... P7 Number of Modbus Discrete Inputs Too many registers for Modbus Function Code 4 (175); valid range is 1 to 125 ...
Created Date: March 19,2019
Created by: svshow
;) Its not about DoMore request. The invalid request should be sent from another device or even application to DoMore PLC, and only in this case (so far) you will see "funny result ".