A suite of client's and server's to test and emulate MODBUS implementations. A MODBUS interface is defined in JSON and can be used to simulate both server and client ends of the communication. Leveraged by the pymodbus library it fully supports any RTU, ASCII and TCP/IP combinations you may need in your project.

First install a python3 distribution of your choice, winpython works well for windows users, linux/mac users can use what ships with their OS. Then you need to install some dependencies:

python -m pip install pyserial pymodbus

Finally you can run the CLI server:

python mbtserver.py --profile Test_Simple.json

Now you can run the CLI client counterpart, downloading the dataset from the server:

python mbtclient.py --profile Test_Simple.json

Before you can use MBTester you need a modbus profile. This is a .json file which defines all the registers your device or integration needs. The simple test files in the repo has a set of holding registers as shown below. Each register has an address, a textual description, data type and value. You can also choose to define word-order, byte-order and read/write access for each register if you want to. Please check the other examples for reference.

You can now load the profile in a CLI server.

python mbtserver.py --profile Test_Simple.json

Alternatively, you can load it in mbtserver.py for a GUI server where you can monitor writes, change registers on the fly etc.

python qmbtserver.py

With the server running you can start a client. Choose the profile you wrote (Must be in the same folder) and the appropriate settings, and connect to the server. You can now monitor the registers in real-time or double-click one to write a new value.

python qmbtclient.py

The actual usage of this application depends upon what you want to accomplish with it. But generally speaking you first want to write a profile to define your interface, then test it by loading up in both server and client applications simultaniously.

Each application comes with both GUI and commandline interfaces. The former gives you visual feedback and real-time control over the running process, while the latter are lightweight and versatile in their own right. The GUI counterparts are named the same but has a Q prepended as they are implemented in Qt.

A simple MODBUS server. You can use this to emulate your own device or some device you need to integrate. The GUI monitors any register changed in real-time, and allows changing registers at your convenience. You can also enable debug-level logging to see the lowlevel traffic from your clients.

A simple MODBUS client. You can use this to interrogate your device, write values to your server, monitor register changes in real-time and/or log values to disk in CSV format. You can also enable debug-level logging to see the lowlevel traffic to your server.

A simple MODBUS proxy/forwarder. Basically it is a server (With any communication interface) and a client (Also with any communication interface) in one program. Any read and write requests to the server is forwarded to a remote server by the client. You can use this to bridge tcp and serial systems etc. You can also use it to monitor the traffic between devices for testing purposes.