-
- reduce the number of variables to store return values (status, query_ret and response_ret -> ret) - add some comments
-
modbus_check_response() crashes on an invalid exception code
-
The test is now outside of check_crc16 and directly included in receive_msg().
-
- s/datas/data/ - the warning is now an error - add some checks in modbus.c - add unit tests - remove the TODO item - minor 80 columns changes
-
execution.
-
MODBUS Messaging on TCP/IP Implementation Guide V1.0b. The transaction identifier is used to associate the future response with the request. So, at a time, on a TCP connection, this identifier must be unique. There are several manners to use the transaction identifier: - For example, it can be used as a simple "TCP sequence number" with a counter which is incremented at each request. - It can also be judiciously used as a smart index or pointer to identify a transaction context in order to memorize the current remote server and the pending MODBUS request.
-
It's slower to pass non aligned values.
-
- Reduce the max message length to 256 (PI_M300) - s/size/length/
-
- add some unit tests - add PRESET_MULTIPLE_REGISTERS support in manage_query()
-
- cleanups in offset/resp_length vars - cleanups in comments - add FORCE_MULTIPLE_COILS in manage_query
-
- Add some tests for force_single_coil
-
- Two statements on the same line
-
- remove a comment about perror (useless) - remove some printf - rename write_ret to ret
-
o illegal data value o illegal data address - Better naming of build_query_basis and build_response_basis - build_response_basis can be use by response_exception - Reduce variable declarations - Close 3 FIXME - Add a test in unit-test-master
