-
Reported by Allan Cornet.
-
Page 38 in the document Modbus_Application_Protocol_V1_1b.pdf: 6.17 23 (0x17) Read/Write Multiple registers This function code performs a combination of one read operation and one write operation in a single MODBUS transaction. The write operation is performed before the read. The unit test has been updated.
-
Contributed by Dominic Storey. - new function modbus_reply_exception - unit test
-
The goal of this rewriting is to avoid the timeouts on the receiving of exceptions and to be more robust on bad requests. Some devices use the exception MODBUS_EXCEPTION_ACKNOWLEDGE to response to some valid requests, so in this case, you'll really appreciate this change! - Slower! More system calls are used. - The code is cleaner and easier to understand. - Really faster when an exception occurs. - Fix unit test of bad request in RTU
-
Reported by Ivan Giuliani <giuliani.v@gmail.com> It was not possible to use libmodbus outside of projects without config.h file. The inclusion has been removed from the public header. Signed-off-by: Stéphane Raimbault <stephane.raimbault@gmail.com>
-
modbus_set_slave must be used to set the slave ID of the remote device to talk in master mode and to set the internal slave ID in slave mode. If you talk to several devices, you need to call modbus_set_slave each time the following requests must be sent to another device.
-
- more coherent - namespace - opaque and smaller context - usual wording
-
The ID used at init time will be the device ID of the caller and the server ID in request functions is the target to reach.
-
- MAJOR changes to the API (see MIGRATION) - New unit tests - Removed TODO list - Updated NEWS & MIGRATION files
-
- Major changes to unit-test-master/slave to add 4 tests - Use new functions to manipulate bits - Reduce memory usage (allocate only the required space and use uint[8|16]_t pointers)