Free · runs in your browser
Drop a .ch10 or .c10 file. The checker reads every packet header, the TMATS setup record and the time channel, then tells you what the recording contains and whether anything is missing, damaged or cut short. Your browser reads the file on your computer: nothing is uploaded.
Read on this computer. Nothing is sent.
A synthetic 10-second recording made for this page, with one packet removed on purpose.
The report appears here: a verdict, the checks one by one, and every channel of the recording.
REPORT
The file from its first byte to its last, in 128 slices: each slice is coloured by the data types its bytes carry; a red tick marks a missing packet or a damaged area.
| Channel | Name (TMATS) | Data type | Packets | Data | Mean rate | Longest gap | Status |
|---|
This page checks the container. D.T.MUX Viewer opens the data itself: every channel on oscilloscope, video, map, instruments and bus decoders, on the recorded time, with exports to CSV, KMZ and Tacview. Free and unlimited with ETEP equipment; 30-day free trial for other manufacturers' recorders.
WHAT THE CHECKER READS
A Chapter 10 file is a sequence of packets, each with a header that says which channel it belongs to, how long it is and when it was recorded. Most damage shows in those headers, which is where the checker looks.
Sync pattern 0xEB25, header checksum, packet and data lengths, the per-channel sequence counter and the 10 MHz relative time counter. A damaged area is skipped and measured; a lost packet shows as a break in its channel's counter.
The first packet of the file describes the recording: program name, edition of the standard, and each channel with its number, type and name. The checker compares that list with the channels actually found.
Time packets give the absolute start and end of the recording and the source of the time — internal clock, IRIG, GPS. Each step is compared with the recorder clock, so a lost or reset time source shows up.
The page uses your browser's own file reader. The file is read in 8 MB blocks on your computer; no byte is sent to ETEP or anyone else, and only counters are kept in memory, whatever the size of the file.
It does not decode what the packets carry — samples, bus messages, video frames. That is the job of D.T.MUX Viewer.
FREQUENTLY ASKED
No. Your browser reads the file on your computer, with its own file reader, and no byte is sent to ETEP or to anyone else. You can see it for yourself: once the page has loaded, disconnect from the network — the checker still works.
Any file made of IRIG 106 Chapter 10 packets (Chapter 11 in the 2017 and later editions), from any recorder that follows the standard, whatever its extension. D.T.MUX .mux files are a different format: open them in D.T.MUX Viewer.
The page sets no limit. It reads the file block by block and keeps only counters in memory, so a recording of several tens of gigabytes is read like a small one; the time it takes depends on your disk, and the bar shows the progress.
Each channel numbers its packets from 0 to 255, then starts again. When a number is skipped, a packet the recorder wrote is not in the file: lost while recording, while copying, or removed by an editing tool. The first packet of each channel is not checked, so a file that starts in the middle of a recording is not reported.
No: it checks the packets that carry them, not their content. To plot the parameters, decode the buses, play the video and replay the flight, open the file in D.T.MUX Viewer.
Yes, with no registration and no limit on the number of files.
D.T.MUX Viewer replays every channel of a Chapter 10 recording on the recorded time: oscilloscope, video, map, instruments, bus decoders, 3D flight.
Download D.T.MUX Viewer →Type at least two letters. Enter opens the first result.
