Peter M. Groen / libmodbus

- 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

- Update the NEWS file

- Add test files to examples directory in libmodbus-dev.
- Add MIGRATION file to libmodbus-dev.
- Define the compatibility level to 6.
- Add MIGRATION to EXTRA_DIST in Makefile.am
- Add README to  EXTRA_DIST in tests/Makefile.am
- Add unit-test.h as dependency in tests/Makefile.am

The test is now outside of check_crc16 and directly included in
receive_msg().

- The coil and registers are wrote by the master and not assigned by the
  slave anymore
- The data used to write are the ones in unit-test.h
- The read test is done after the write test

- rename test-master-random => random-test-master
- fix memset
- update README
- add the files to configure.ac and wscript

I don't know how to manage many versions.

- 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

- cleanup in autogen.sh (only 2 lines now!)
- remove the version redundancy in configure.ac

execution.

http://code.google.com/p/waf/

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.

The results are really interesting!
- bench-bandwidth-slave.c
- bench-bandwidth-master.c