-
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
-
It is easier to install on rpm based systems with a spec file. I don't want to update the file to each beta until the 2.0 release so I already use the 2.0 name in the spec file.
-
- concat the content of INSTALL at the end of README - re-add the --force option to autogen.sh
-
libmodbus does not link with c++ code.
-
Pahole tool by Arnaldo Carvalho de Melo has been used to found this problem.
-
- change autoreconf option to not overwrite INSTALL file - add verbose flag
-
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
