Modbus RTU Write Simulink Block error

6 views (last 30 days)
Marco
Marco on 30 Jan 2025
Commented: Marco on 3 Feb 2025
Hi community,
I am starting with the setup of a modbus RTU communication between my matlab simulink model and some surrounding devices. Using the new simulink block "modbus client read", I can read the register of my external device, which shows me, that I've created a stable communication. However, if I want to write a register on the device, using the block "modbus client write", I get the following error:
Error:An error occurred during simulation and the simulation was terminated
Caused by:
MATLAB System block 'untitled/Modbus Client Write/internalModbus' error occurred when invoking 'stepImpl' method of 'icomm.system.ModbusWrite'. The error was thrown from '
'C:\Program Files\MATLAB\R2024b\toolbox\icomm\modbus\modbus\modbusblks\+icomm\+system\ModbusWrite.p' at line 0'.
The Modbus server returned an invalid address error. Address + number of values to write is out of range.
The config of the write-block is pictured:
As aforementioned, it's the same connection as used for the reading process. The model is quite simple and broken down to the minimum, but I get the error anyway:
Now I am struggling how to proceed with this error. Maybe someone can help me out!
Best
Marco
  1 Comment
Marco
Marco on 30 Jan 2025
note: I am very sure, that the register number 55 is right, because with other software (comTestPro) I can easy write the register.

Sign in to comment.

Answers (1)

Pramil
Pramil on 3 Feb 2025
Edited: Pramil on 3 Feb 2025
Hi Marco,
I faced a similar issue in MATLAB R2024b.
The issue was with the input data type of the signal going into "Modbus Client Write" block which has to be "double" otherwise it will result in an error.
As seen in the following documentation as well, the "Data type" for the "Reg_x" input to the "Modbus Client Write" should be a "double":
Hope this resolves your issue.
  3 Comments
Pramil
Pramil on 3 Feb 2025
Hey Marco, can you try incementing the register address by one, so instead of using "55" try with "56" and let me know if you get the same error.
Marco
Marco on 3 Feb 2025
Finally, it works! Thanks!

Sign in to comment.

Products


Release

R2024b

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!