Problem scenario:
I can successfully test and read data from my MODBUS RTU device using the MODBUS Poll software. How can I copy a MODBUS query settings to your logger because I would like to export data to a database?
It is assumed that:
You can successfully read data from your MODBUS device using MODBUS Poll(fig. 1).
Solution:
1. Create a new configuration from the main window using the “Green Plus” button. (fig. 3). This example shows the connection settings for MODBUS RTU. If your device uses MODBUS TCP, look here
. First, copy the communication settings from MODBUS poll (Connection → Connect, fig. 1, 2):

Fig. 1: MODBUS Poll Connection Setup.

Fig. 2: MODBUS Poll Advanced Setup.

Fig. 3: MODBUS Data Logger Connection Setup.
2. Activate the “MODBUS RTU” plugin in the settings in both fields “Data query module” and “Parser module”. Please do not confuse it with “MODBUS RTU [Passive]” or “MODBUS RTU [Slave]” because they realize other functionality. We configure the MODBUS master station.

Fig. 4: Activating the MODBUS RTU plugin.
3. In the MODBUS RTU plugin settings, click the “Action → Add new request” button to add a new query request (fig. 6). Copy basic request settings from MODBUS poll (Setup → Read/Write Definition, fig. 5):
Note: The figure 6 is an example. It does not match the settings on figure 5.

Fig. 5: MODBUS poll: Basic MODBUS query settings.

Fig. 6: Logger: Basic MODBUS query settings.
4. Add only one response item by clicking the “Action → Add response item” button if it does not exist in the list (fig. 8).
Note: The figure 8 below is an example. It does not match response items on fig. 5 and 7. The correct definition for the “Signed 32 bit, big-endian” data type in MODBUS Poll:

Fig. 7: MODBUS Poll: Display.

Fig. 8: MODBUS response items.
How can I poll multiple MODBUS RTU devices?
MODBUS RTU allows you to connect up to 254 devices on one RS-485 bus. You may specify several addresses like 1,2,3,4,5 in the ” Device address” field (fig. 3).
Can I poll MODBUS TCP devices?
Yes, of course. The settings are almost identical. You should configure the TCP connection settings and select other parser type (MODBUS TCP instead of MODBUS RTU on step 2).