Modbus RTU CRC-16 calculator
Enter the frame bytes before the CRC. Example: 01 03 00 00 00 0A.
Modbus RTU transmits the CRC low byte first, then the high byte.
Calculate a Modbus RTU CRC, convert 4xxxx register references and decode 32-bit Float values without installing anything. All calculations run locally in your browser.
Quick answer: Modbus RTU uses CRC-16/MODBUS: initial value 0xFFFF and reflected polynomial 0xA001, calculated over every byte from the slave ID to the last data byte. The 16-bit result is appended low byte first, so for 01 03 00 00 00 0A the CRC is 0xCDC5 and the frame ends C5 CD.
Enter the frame bytes before the CRC. Example: 01 03 00 00 00 0A.
Modbus RTU transmits the CRC low byte first, then the high byte.
Convert classic documentation references such as 40001 into a zero-based protocol offset.
Manufacturer conventions vary. Confirm whether the device manual uses 0-based offsets, 1-based offsets or 3xxxx/4xxxx references.
Enter four bytes exactly as they appear across two consecutive 16-bit registers. Select how the device stores the IEEE-754 Float32 value.
If the result is unrealistic, try the other three byte orders. See the Float32 & byte-order guide for the underlying concept.
A correct CRC proves the frame bytes were calculated consistently; it does not prove the serial wiring or slave configuration is correct. Likewise, a plausible Float32 result confirms only one possible interpretation of two registers. Use the tools together with the device manual and a live communication log.
To see the frames that actually went over the wire, including the CRC, ModbusBB 2.1 has a Traffic Monitor with the raw TX/RX hex of every request and response. The CLI can also build a frame without sending it: ModbusBB.CLI raw --rtu COM3 --unit 1 --fc 3 --data "00 00 00 0A" --dry-run prints 01 03 00 00 00 0A C5 CD. See the CLI reference.
For field faults, continue with the timeout checklist, RS-485 wiring guide and exception-code reference.
Low byte first. Modbus RTU appends the low-order CRC byte and then the high-order byte, the opposite of the big-endian order used for register values. For the request 01 03 00 00 00 0A the CRC is 0xCDC5, transmitted as C5 CD.
Subtract 40001 for holding registers (or 30001 for input registers): 40001 becomes address 0 and 40100 becomes 99. Confirm that the device manual uses this convention, because some vendors already list zero-based offsets.
No. All calculations run locally in your browser with JavaScript, and nothing you type is uploaded.
Poll several devices at once over TCP, UDP, RTU, ASCII or RTU-over-TCP. Read and write registers, decode Float32/64 and strings, inspect raw TX/RX frames, trend values and simulate devices from Windows or the command line.
Download the 64-bit Windows installer or portable ZIP with SHA-256 checksums. Free 30-day trial.
$10 one-time payment for a lifetime license on up to 3 PCs with free updates and 14-day refund guarantee.
View your active computers, deactivate an old PC to move your license, or check your key status.
Direct email channels for technical support, licensing/invoices, volume quotes, and SCADA engineering.
Modbus master, traffic monitor, scanner, logger and slave simulator for Android phones and tablets.
Complete overview of transports, 11 data types, byte orders, Device Tools, simulator, trends and CLI.
Instant browser tools: Modbus RTU CRC-16 calculator, 4xxxx address converter, and Float32 byte-order decoder.
Scriptable CLI reference for automated testing, JSON/CSV logging, device scans and CI pipelines.
Technical reference covering connections, workspaces (.mbws), data types, scaling, and troubleshooting.
Step-by-step illustrated manual with annotated screenshots and downloadable PDF.
Read Device Identification (FC43/14), Report Slave ID (FC17), Diagnostics (FC08), Mask Write (FC22) and raw requests.
Built-in register templates for popular energy meters, solar inverters, and variable-frequency drives.
Understand 0-based, 1-based and Modicon 4xxxx notation and fix off-by-one register errors.
Detailed breakdown of standard read/write function codes and diagnostic function codes.
How to decode 32-bit and 64-bit integers and floats across Big-Endian, Little-Endian and word-swapped devices.
Field guide to RS-485 2-wire daisy chains, A/B polarity swaps, 120 Ω termination and ground reference.
Step-by-step commissioning checklist for diagnosing TCP and serial RTU timeouts using raw hex frames.
What exception responses 01, 02, 03, 04, 05, 06, 0A and 0B mean in hex frames and how to resolve them.
Compare Modbus frame structures, serial vs Ethernet transports, and when to use RTU-over-TCP.
How to simulate multi-unit Modbus slaves with value generators and exception injection for FAT/SAT.
Side-by-side comparison of ModbusBB 2.1 and Modbus Poll for Windows commissioning engineers.
Meet the SCADA/SAS electrical engineer behind ModbusBB and explore other Max Energic tools.