Hello,
Thank you for reaching out. Yes, with the latest firmwares (from 7.13), the output of the ubus call for the Modbus request has changed. Please note that shell commands and their output were never guaranteed to remain unchanged, and this is the reason for the issue you’re encountering.
As a more reliable and structured alternative for parsing Modbus data, we highly recommend using the API instead of the ubus commands. TRB140 API Modbus client documentation can be found here: https://developers.teltonika-networks.com/reference/trb140/7.13.2/v1.5/modbus
For more details and information on this change, you can refer to a few similar topics here:
Hello,
Unfortunately, ubus commands were always used internally and at your own risk, without a guarantee that shell commands or their output would remain unchanged. The latest 7.13.1 firmware release is an example where ubus command output has changed, and there is no way to revert this behavior.
Instead of ubus, we strongly recommend using API calls, which provide a more reliable and structured approach. You can find all necessary details for API Modbus calls here:
Modbus API Documen…
Hi,
I have some custom scripts using “ubus call modbus_client.rpc tcp.test” with RUT956.
In latest FW release (07.13.1) it seams to execute the commands but the results returns just an incremented number for each attempt.
I see in the FW change log that there are several modification to the Modbus Client.
Can you provide instructions on how to use the commands with the new firmware?
Example command below working in previous FW-release (up to 07.13):
ubus call modbus_client.rpc tcp.test ‘{“…
Best regards,