- MoTeC
- .ld
.ld · MoTeC
Open MoTeC .ld files without installing i2
A MoTeC .ld file is a binary container holding the session header, the channel definitions and the samples. Wild Telemetry decodes it directly, with no i2 install and no MoTeC hardware attached, and recovers the logger's own exact lap boundaries from the internal beacon channel.
- Format at a glance
Format at a glance
| Extension | .ld (optional .ldx sidecar) |
|---|---|
| Vendor | MoTeC |
| Type | Binary, reverse-engineered format |
| Lap boundaries | Exact, from the beacon (internal) channel |
| Agreement with i2 | ±0.3 s after Running Lap Time refinement |
| Altitude | GPS Altitude channel, where logged |
Where do the lap boundaries come from?
The pulses on the beacon (internal) channel are exactly the lap markers MoTeC i2 displays, including the first start/finish crossing that the Lap Number channel misses, and without the spurious logger-stop event. That channel is the source, not a reconstruction.
The boundaries are then refined against Running Lap Time resets, which lands each cut within ±0.3 s of what i2 reports. Because they are exact they enter as the top rung of lap splitting: nothing downstream has to guess.
- The product
- FUJI
What you get when you open a session.
What it does not do
- Nothing writes .ld: the application reads, and never modifies your original files.
- An unknown format revision raises a typed error pointing at the CSV export route, rather than silently mis-decoding.
Have .ld files?
Tell us which logger you run and we will say whether we can open your files before you install anything. Answered by hand.