Sun, 06 Jun 2021 22:52:40 +0100 mjsousa optimization: normalize buffer when it becomes empty after data purge
Sun, 06 Jun 2021 22:40:06 +0100 mjsousa fix bug: frame data read from network was potentially being moved inside buffer (lb_normalize()) before it was processed by caller to read_frame()
Wed, 02 Jun 2021 11:09:57 +0100 mjsousa add parenthesis to #define'd constants so later multipications work correctly
Wed, 02 Jun 2021 09:23:13 +0100 mjsousa fix bug with receive buffer handling. Was causing data corruption during communication errors with long frames.
Mon, 22 Mar 2021 14:57:48 +0100 Edouard Tisserant Add KeepAlive support for all TCP sockets.
Mon, 01 Jun 2020 14:28:49 +0100 Mario de Sousa merge
Mon, 01 Jun 2020 14:27:56 +0100 Mario de Sousa correct version of --> Allow "" and NULL on TCP host and service (=> IP=INADDR_ANY, and port=0)
Mon, 01 Jun 2020 14:24:57 +0100 Mario de Sousa Undo changes inserted in previous commit (included 2 unrelated changes)
Mon, 01 Jun 2020 14:15:03 +0100 Mario de Sousa Allow "" and NULL on TCP host and service (=> IP=INADDR_ANY, and port=0)
Tue, 10 Dec 2019 16:07:49 +0000 Mario de Sousa merge
Tue, 10 Dec 2019 15:51:32 +0000 Mario de Sousa change hton() and ntoh() so we don't use (u8 *) to (u16 *) casts. Some compilers incorrectly change the pointer to force alignment with even addresses.
Tue, 10 Dec 2019 09:30:59 +0100 bmakuc Mario's fix for the pointer alignment problem. See changeset 4: 99009b24d401.
Wed, 27 Nov 2019 14:53:22 +0100 bmakuc Variables start_addr and count were read from query_packet using function mb_ntoh_safe. It looks like some compilers change the pointer alignment if the first byte starts at an odd address. Because mb_ntoh_safe uses pointers slave address and count (number of registers) were not read correctly from the buffer when several modbus slaves were present in network. In this temporary solution pointer aritmetics is replaced by simple 256 multiplication.
Mon, 11 Feb 2019 11:07:01 +0100 Edouard Tisserant Setting socket option so that TCP Modbus slave can re-use same port immediately after freeing it