Peter M. Groen / libmodbus

This allows to place the coils/registers at any virtual
start address, not only at address 0. This can be useful e.g.
when the server has to fulfill a specification in which
registers are expected at predefined locations.

Signed-off-by: Michael Heimpold <mhei@heimpold.de>

Signed-off-by: Michael Heimpold <mhei@heimpold.de>

This replaces the lengthy license text headers with a short
and standardized license tag. See http://spdx.org for details.

This is useful e.g. for license compliance tools which scan
through files and generate a report of the licenses used
in a project.

Signed-off-by: Michael Heimpold <mhei@heimpold.de>

Function modbus_receive_from has no implementation in the library and is not used anywhere.

Change API of function for libmodbus v3.2.0

- add byte timeout tests (TCP backend only)
- update and improve documentation
- long timeout values are now uint32_t so it changes the API
  to disable byte timeout

https://www.securecoding.cert.org/confluence/display/seccode/DCL37-C.+Do+not+declare+or+define+a+reserved+identifier
Not applied to libmodbus constants for now...

- update documentation
- 5 new tests
- updated NEWS file
- avoid include of time.h

The index variable shadowed a variable in the standard library causing
warnings. Renaming the 'index' variable to 'idx' resolves the issue.

It's strongly recommended to update your libmodbus library if you
use it in a slave/server application in a not trusted environment.

Debian package of libmodbus 3.0.4 already contains a patch to
mitigate the exploit but the patch isn't as strong than this one.

This regression comes from Visual Studio patches.

- change return argument from void to int
- update documentation

Thanks Tobias Doerffel.

Fix EXXX values defined in Microsoft C Runtime 10

Add macros in libmodbus.txt and:
- modbus_get_byte_from_bits.txt
- modbus_get_float.txt
- modbus_reply.txt
- modbus_reply_exception.txt
- modbus_set_bits_from_byte.txt
- modbus_set_bits_from_bytes.txt
- modbus_set_float.txt

The function name was confusing because the write operation is performed
before the read. Take care to swap the arguments in the migration process.

Avoid incompatibility with GPLv2 program. This change has been approved by
Tobias Doerffel, Florian octo Forster and Hannu Vuolasaho.

The two modes are complementary, MODBUS_ERROR_RECOVERY_LINK handles
errors at data link level (bad file descriptor, timeout, etc) and
MODBUS_ERROR_RECOVERY_PROTOCOL checks Modbus error (eg. invalid
function code or trame length).

This change introduces the use of the Sleep function for Windows.
Some duplicated code has been moved from backends to modbus core.
A new debug message is now available when a flush occurs.

The unit tests are now based on this error recovery code.

The following functions have been renamed:
- modbus_get_timeout_begin -> modbus_get_response_timeout
- modbus_set_timeout_begin -> modbus_set_response_timeout
- modbus_get_timeout_end -> modbus_get_byte_timeout
- modbus_set_timeout_end -> modbus_set_byte_timeout

The meaning of these timeout intervals is now clearer. The documentation
has been updated.

These new functions seem clearer than the recent modbus_receive_from
function IHMO. This change fixes the bandwidth-server-many-up program.

Split the original modbus_receive function in two functions to avoid
the strange -1 value to ignore the sockfd argument.

The arguments are surrounded by parentheses to be evaluated first.

The _modbus_receive_confirmation()_ function shall receive a
request via the socket of the context 'ctx'. This function must be
used for debugging purposes because the received response isn't
checked against the initial request. This function can be
convenient to receive request not handled by the library.

The _modbus_send_raw_request()_ function shall send a request via
the socket of the context 'ctx'. This function must be used for
debugging purposes because you have to take care to make a valid
request by hand. The function only adds to the message, the header
or CRC of the selected backend, so 'raw_req' must start and contain
at least a slave/unit identifier and a function code. This function
can be used to send request not handled by the library.

Reported by Allan Cornet.