-
Address check in single register / coil responses added According to Modbus standard the address of single register / coils request and response must match Co-authored-by: Heinrich Gsponer <heinrich.gsponer@siemens.com>
-
It converts float values depending on what order they come in. This patch was modified from rm5248 [1] [1] https://github.com/synexxus/libmodbus/commit/a511768e7fe7ec52d7bae1d9ae04e33f87a59627
-
This native libmodbus error code is defined but not used.
-
Thank you @peternewman.
-
Sorry for the two PRs, I did one then realized I should check the other
-
While handling MODBUS_FC_WRITE_AND_READ_REGISTERS, both address offsets must be checked, i.e. the read and the write address must be within the mapping range. At the moment, only the read address was considered, it looks like a simple copy and paste error, so let's fix it. Signed-off-by: Michael Heimpold <mhei@heimpold.de>
-
Thank you @qqq89513
-
Thanks to @peternewman
-
Fix for #542
-
Fix #513
-
Add Embox RTOS to the list of supported OSes
-
There is a small typo in tests/bandwidth-client.c. Should read `response` rather than `reponse`.
-
When compiling with gcc and option -Wconversion it fixes the warning message warning: conversion from ‘X’ {aka ‘x’} to ‘Y’ {aka ‘y’} may change value Signed-off-by: José Bollo <jose.bollo@iot.bzh>
-
In case resulting value should be negative it is incorrect to use '+' operator to construct it from pieces, because highest bytes will result in negative number after bitwise shift while others will stay positive. Replacing addition with '|' should solve the issue.
-
Since SPDX release 3.0 LGPL-2.1+ became LGPL-2.1-or-later. Hence replace the deprecated identifiers.
-
I can't believe I committed that copy/paste mistake. Sorry Maor Vermucht and Or Peles, excepted naming your original patch was OK. Thank you Karl Palsson for your review.