Telemetry · Mathematics · AIIssue 01 — The LineNative on Mac · Windows

User guideI. Getting started

Import recordings

Bring logger recordings into the workspace. Lattiro keeps their original channel names, values, units and timestamps.

Where to find it

  • Start center → Import data
  • in Analysis: navigation File → Import data, or ⌘/Ctrl+I

Steps

  1. Prepare the file

    Supported: AiM .xrk, MoTeC .ld, aRacer .loga, Racelogic .vbo, and 2D as a complete .MES measurement folder or a .zip holding one complete measurement. Import one measurement at a time.

  2. Pick it

    Open a workspace and click Import data. Use Choose file for a recording file or ZIP, or Choose folder for a .MES folder.

  3. Check the format

    Format detection lists the matching readers with a confidence; if several match, pick one. 2D MES must be picked explicitly: its support is still being validated, and only the channel samples declared in the DDD are read, not companion files such as LAP or CAL.

  4. Start the import

    Click Start import. The stages run from Verifying source file to Import complete; Cancel import stops it.

  5. Add record info if you like

    While it runs, the Record info form takes the rider, vehicle, session type and name, event, weather, surface, air and track temperature, date, humidity and notes. Empty fields leave existing values unchanged.

  6. Open the recording

    When the import completes, the recording opens by itself. If you edited the form, choose Save info, or Skip for now.

Good to know

  • Your original data is kept

    Custom names, categories, marks and corrections are stored separately and never overwrite the imported file.

  • Notes by brand

    AiM: logger analog inputs are read as the physical values already converted in the file; no separate dashboard configuration is needed. MoTeC: the file's stored conversions are used; LDX formulas and corrections are not imported. aRacer: verified Logger formats. Racelogic: VBO keeps its header and data. 2D: an LDD file has no samples and cannot be imported on its own.

  • Laps from an AiM logger

    Until you calibrate the track, an AiM recording takes its laps from the logger's own start/finish crossings, if it recorded any. L1 is the first complete lap (lap 2 in AiM's own software); the out lap and in lap are not listed. The logger's split times can be added to lap tables as sectors (S1…). Once the track is calibrated, laps and sectors come from the calibration instead.

  • Supported record formats

    In Analysis, File → Supported record formats lists every format and the files each one needs.

  • Standard track identified

    If the trace matches a standard track, a Standard track identified card appears with Open track calibration and Not now.

  • If an import fails

    Several measurements in one source: pick one .MES folder at a time, or keep one measurement per ZIP. Unsupported value or calibration encoding: check the readings in the vendor software and keep the original file.