Modbus TCP Online Tool | Command Generation/Response Generation/Data Parsing All-in-One Tool
Modbus TCP online tool with three core functions: command generation, response data generation, and data parsing. Supports MBAP header processing, transaction ID management, and multiple data types (UINT16/INT16/UINT32/INT32/FLOAT32) with various byte orders (ABCD/DCBA/BADC/CDAB).
Modbus TCP Request Command Generator
Modbus TCP Response Generator
Data Type
Byte Order
Value(Decimal Value)
Modbus TCP Message Parser
Parse Rules Configuration
Start Position
Data Type
Raw Data
Byte Order
Ordered Data
Parse Result
Actions
No parsing rules configured. Please add rules to start parsing.
User Guide
Function Overview
Modbus TCP Tool is an integrated Modbus TCP protocol tool that provides three core functions: command generation, response data generation, and data parsing. It helps users quickly generate standard Modbus TCP commands, handle MBAP header information, simulate slave response data, and parse actual communication data.
Main Features:
- Command Generation: Supports common function codes, can quickly generate standard Modbus commands
- Response Data Generation: Supports simulating slave response data for testing and verification
- Data Parsing: Supports parsing multiple data types and byte orders, can quickly verify if data types and byte orders are correct
Command Generator User Guide
- Unit Identifier: Device address in TCP mode, included in MBAP header
- Transaction Identifier: Used to match requests and responses in TCP mode, range 0-65535
- Function Code: Supports standard function codes like 01/02/03/04/05/06/15/16
- Start Address: Starting address of registers to access
- Quantity: Amount of data to read or write
- TCP Command Examples:
- TCP Read Command: 00 01 00 00 00 06 01 03 00 00 00 02 (MBAP header+PDU)
- TCP Write Command: 00 01 00 00 00 06 01 06 00 00 00 01 (MBAP header+PDU)
- MBAP Header Description: Transaction ID(00 01) + Protocol ID(00 00) + Length(00 06) + Unit ID(01)
Response Data Generator User Guide
- Select function code matching the command
- Supports multiple data types: UINT16/INT16/UINT32/INT32/FLOAT32 etc.
- Supports multiple byte orders: ABCD/DCBA/BADC/CDAB
- TCP Transaction Identifier: Must match the transaction ID in the request command
- TCP Unit Identifier: Corresponds to the unit ID in the request command
- TCP Response Examples:
- TCP Read Response: 00 01 00 00 00 07 01 03 04 00 01 00 02 (MBAP header+response PDU)
- TCP Write Response: 00 01 00 00 00 06 01 06 00 00 00 01 (MBAP header+confirmation PDU)
- Note: Transaction ID in TCP response must match the request, length field is automatically calculated
Data Parser User Guide
- Supports inputting standard Modbus data frames for parsing
- Can configure multiple parsing rules, supports different data types and byte orders
- Built-in multiple data type conversions, supports signed/unsigned integers and floating-point numbers
- Flexible byte order configuration, adapts to different device data formats
- TCP Parsing Features:
- Automatically identify and parse MBAP header information (transaction ID, protocol ID, length, unit ID)
- TCP mode does not require checksum verification, relies on TCP protocol to ensure data integrity
- TCP frame format: MBAP header (7 bytes) + function code (1 byte) + data (n bytes)
- Validation points: MBAP header format correct, protocol ID is 0x0000, length field accurate
- TCP Parsing Example:
- Input: 00 01 00 00 00 07 01 03 04 00 01 00 02
- Parse: Transaction ID=1, Protocol ID=0, Length=7, Unit ID=1, Function Code=03, Data=00 01 00 02
- For parsing large amounts of data, it is recommended to use the file parsing function in the Modbus data parsing section of the Modbus debugging page, which supports batch data processing