The process of decoding converts the format that the serial devices use to communicate directly into meaningful messages to the human caretakers of the systems in question. Using a Modbus message decoder allows you to understand the messages moving through the Modbus network which can be instrumental in diagnosing problems and increasing efficiency.
When issues arise in a Modbus network implementation, the ability to decode the Modbus messages is imperative in addressing the situation in the correct manner. This is where a quality Modbus frame decoder like Serial Port Monitor can make the difference in allowing quick and precise identification of the problem that is impacting your network or devices.
Using Serial Port Monitor to Decode
When you need to decode Modbus data, Serial Port Monitor is an indispensable tool that can aid developers or network administrators troubleshoot their networks. It is available as a free Modbus decoder download so you can see how the product can help in your Modbus installation. Here are instructions on how to decode Modbus messages using this excellent software tool.
- First, you need to start a new monitoring session by launching Serial Port Monitor.
- Select “Session -> New session” from the main menu. Alternately you can choose “New” on the main toolbar or use the CTRL+N keyboard shortcut.
- The “New monitoring session” screen will be displayed where you can choose the serial port or ports that you wish to monitor.
- Choose your desired visualizers from among Table, Line, Dump or Terminal View. If you are using the tool as a Modbus RTU decoder, select Modbus and RTU. Modbus ASCII is also available if that is the protocol you are using.
- New session options can be checked to “Start monitoring now” and to “Start in new window”.
- Select your Capture options to choose which events to capture – Create/Close, Read/Write or Device Control.
- Click on the “Start monitoring” button after you have made all of your selections. You will see the data in all of the formats you have chosen in the monitoring window.
Modbus Analyzer enables you to further customize the way your monitored data is presented by modifying your session preferences. In order to access the configuration dialog, you select “Session -> Preferences” or use the shortcut CTRL+P. Here are the ways you can tailor the data view that your monitoring session displays.
- Customize the way each visualizer is displayed by expanding the “Windows” option in the left window panel. You can choose to display your data in different colors and control which columns are displayed when you are in Table View.
- Customize the timestamp format to display the actual date and time or time intervals from the start of the session or since the last record was sent. This control makes it easier to see the records in a way the way that makes the most sense for your monitoring situation.
- The representation of transmitted data can be customized by modifying the string length and scale of notation.
- The customizable send dialog lets you send text strings with or without their hexadecimal equivalents. You can also create aliases here to increase the transmission speed.
Understanding and Decoding the
Modbus Message Format
The Modbus protocol was designed to be used with serial devices and applications. At its most basic level, Modbus communication is binary and is conducted by sending a series of bits signifying zeroes and ones via voltages. A positive voltage indicates a zero and a negative voltage is a one. The binary data transmission is converted into hexadecimal with each block of 4 bits representing a Hex digit 0 through F.
Messages are the way that the Master and Slave devices in a Modbus network communicate with each other. Using a Modbus packet decoder lets us investigate these messages to understand what the devices are saying to each other and determine why network or interface problems are occurring.
The Modbus messages travel between Master and Slave and indicate the function or purpose of the request. Messages are returned to the Master from the Slave with the requested data or an indication that the function has been performed. Modbus messages are coded differently for the RTU and ASCII transmission modes of the protocol. This makes the two protocols incompatible with each other.
Modbus messages are called frames and there are two types involved in communication. The Protocol Data Unit (PDU) which contains a function code and data is one of the frame types. The other is the Application Data Unit (ADU) which holds address and error-checking information. The function code indicates the action that is being requested to be performed with the data that accompanies the message.
Modbus devices contain coils which perform discrete on/off operations and registers which hold data. Function codes can request actions such as writing to a coil or reading or writing to a device’s registers.
Modbus RTU uses binary coding and a cyclic redundancy check (CRC) to perform error-checking. The ASCII Modbus transmission mode uses the less efficient longitudinal redundancy check (LRC) and ASCII coding so is more readable that is RTU. The use of binary coding means that data can be moved more quickly and efficiently and is the reason that the RTU transmission mode is used when possible. Modbus ASCII is useful when modems are involved due to the way the messages are delimited.
The ability to decode Modbus messages is vital when trying to track down communication issues in a Modbus network implementation. Using an application like Serial Port Monitor lets you see exactly what is going on between devices and swiftly take corrective action if needed. If you work with serial devices and the Modbus protocol, you really need to try the tool and see how it can help you and your organization.
Additional Features of Serial Port Monitor
This professional-grade Modbus protocol decoder is packed with many other features that make it a great tool for monitoring any type of serial communication. Here are some highlights from the software application’s extensive feature list:
- All variations of COM ports are supported including physical and virtual ports as well as extension board ports and Bluetooth serial ports.
- Monitor any number of serial ports simultaneously in a single monitoring session.
- Any serial device or software application can be monitored.
- Monitor ports that are already opened by another application.
- Capture data in real-time and view it in multiple formats.
- Monitoring sessions can be customized.
- User-friendly interface that can be used with basic computer skills.
- Export monitored sessions to a file in various formats such as HTML, ASCII, Unicode, and CSV.
- All data can be easily copied to the clipboard.
- Redirect exports to multiple files and control the maximum file size.
- Stream filtering tools with convenient presets.
- Monitoring sessions can be compared in the tool.
- Resend data to a serial port to observe changes in its response.
- Supports any device that employs the RS232/RS422/RS485 interface.
In addition to being a robust Modbus decoder, there are numerous other ways that Serial Port Monitor can be used when working with serial interfaces and devices. Here are some of them:
Modbus Analyzer runs on the Windows operating system and requires that you have at least one serial port on your system. It is a great addition to the software toolbox of anyone who needs to work with serial devices.