Modbus TCP Client developed for Windows 10 UWP platform

Supports reading/writing holding and input registers, as well as coils and discrete inputs.
The application has features for plotting data and logging to csv file. ModbusInspector can store multiple device configurations in roaming application memory, automatically synchronized across a users account. The tool is compatible with all devices running Windows 10, including the Internet-of-Things core.

ModbusInspector is available in the Windows App Store
*App is available for a 7-day free trial.                                                                           


Please contact BEDKO with any questions or requests for additonal features or changes.

Instruction video with details on configuration:


1.) How do I configure ModbusInspector?

First, input the target device IP and port number (usually 502 for Modbus TCP). Next, configure the starting address and range for each of the four types of registers you want to read. A Range of 0 means nothing is read (saving bandwidth). Finally, set the "Read Interval" to decide how often ModbusInspector should refresh the device registers.

Once you have configured the data you want to see, you can go to the view of each type of register/coil/input.  For Holding Registers, user can simply enter a new value into the text-box. ModbusInspector will then stop to update that field, until user input is complete, and the new value is send to the device.

If you want to give a descriptive name to registers, you can do that for all four types of data. These names are also used in the plot-view. Similarly, datatypes can be specified, allowing users to show data as HEX, signed/unsigned integer, or even decimal number. For decimal formats, the input value is scaled by the appropriate number.
With a decimal setting of "D3", a register integer value of 10 000 will show as 10.000.

2.) How to configure plotting and sampling maps?
The basic syntax is a comma separated list of values. Each item in the list consist of one letter (upper or lower caps) and a number. The letter refers to the source of data, and the number is the index:
I - Input register
H - Holding Register
D - Discrete Input
C - Coil

Spaces are ignored, so users have some freedom in how to format string for preferred readability.

Ex: Plot holding registers 1 and 2, followed by input registers 1 and 2
Map = H1,H2,I1,I2

3.) What does the "ColorMap" setting do?
This is a list of colors that ModbusInspector uses when plotting. The first color correspond to the first item in the map of signals to plot. If there are more signals to plot then colors, the app starts over from the first color.
Colormap is also comma separated values, and spaces are ignored. Accepted values are
r - Red
g - Grean
b - Blue
k - Black
c - Cyan
m - Magenta