-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Call for Testers
We really need testers because the libmodbus supports many platforms and backends. If you intend to test libmodbus, please add your name to the list:
-
<[email protected]>, Linux TCP/IP (IPv4 and PI) and USB serial
-
<[email protected]>, AT91SAM9G20 (IP and RTU) Linux 2.6.38-rc
-
<[email protected]>, Windows XP Pro 32 bits, MinGW/GCC (see Issue #9). I just ran unit tests to help someone.
-
<[email protected]>, Debian GNU/Linux. RTU. Mini ITX w/ PCI and USB Serial + ARM
-
<[email protected]>, LynxOS 4.2, LynxOS 5.0. TCP/IPv4 tests on x86 and MVME5500
-
<[email protected]>, ARM Linux (AT91SAM9G20 (IPv4 + RTU) Linux 2.6.36-rc6 libmodbus compiled using BusyBox 1.19.4
-
<[email protected]>, ARM v7 Linux (BeagleBone Black) (IPv4) Linux 2.8.6 libmodbus 3.1 compiled using gcc. Tested with a Modbus OPC Server and tests examples.
Try to compile the latest version and run the unit tests of the tests directory. Launch ./unit-test-server in a shell and ./unit-test-client in another, you can also specify argument to test other backends (run ./unit-test-client -h to show the accepted arguments, eg. ./unit-test-client rtu).
If you already use libmodbus for your project, it’s great to have some real test cases too.