LiDAR / laser rangefinder UART decoder
Paste a hex dump or connect a module over WebSerial (Chrome / Edge). The page finds the protocol and baud rate, decodes every frame and flags checksum errors. Everything runs in your browser; nothing is uploaded.
WebSerial: checking...
-
No data yet.
Protocol candidates
| Profile | Explains | Frames | Bad | Baud | Same bytes, pick by model |
|---|
| # | Check | Frame | Type | Distance (m) | Strength | Temp | Note |
|---|
Supported modules
| Vendor | Modules | Frame | Default baud |
|---|---|---|---|
| Benewake | TFmini, TFmini-S, TFmini Plus, TF-Luna, TF02-Pro, TF03 (9-byte cm / mm, string and Pixhawk modes) | 59 59 DL DH SL SH TL TH SUM | 115200 |
| LightWare | SF30/D binary protocol; SF10 / SF11 ASCII serial | AA flags.. ID data CRC16 / 22.48 m\r\n | 115200 |
| Chengdu JRT | phase-shift laser distance sensors (U81 / U85 / M88 class) | AA 00 00 22 00 03 d d d d q q SUM | 19200 |
| Nooploop | TOFSense, TOFSense-F (UART active and query output) | 57 00 .. 16 bytes | 921600 |
| DFRobot | SEN0366 infrared laser distance sensor 50 / 80 m and the identical 80 m modules | 80 06 83 ASCII CS | 9600 |
| ERDI | LRF50H...LRF1500H, LRF22VB, LRF50VB, LR1000E2...LR2000E4, LRF1200A1, LRF3000A1, SPD1200 | 5C lo hi chk / 55 AA fn .. SUM | 460800 / 115200 |
Each profile is built from the vendor's public manual; sources and frame tables are in PROTOCOLS.md. Same bytes can mean different units on different models (an ERDI 5C 02 11 EC is 43.54 m on an H-series module and 4.354 m on a VB module), so confirm the model before trusting the number.