Setting up the BODAQS Import Manager

BODAQS Import Manager is the desktop app for getting logger sessions off the logger and into your library. It watches log sources (folders on your computer or loggers on WiFi), imports and processes the logs, and writes the results into a library directory.

More info

This page covers initial setup: install the app, create or adopt a workspace, create your first library and source, configure the bike profile, and run a first import.

A more complete description can be found in the BODAQS Import Manager user guide. For details of how the BODAQS workspace is organised, see the folder and file structure appendix.

Current platform

The packaged app is currently Windows-first; a macOS version is available but not fully tested.

Download and install the BODAQS Import Manager

Most users should download the latest BODAQS Import Manager installer release to their computer as a .exe file and then run it.

Go to the releases page in the BODAQS GitHub repository here and download the latest BODAQS Import Manager installer.

Run the installer and follow the prompts. Launch the Import Manager when prompted to do so.

Create the first library and source

1. Choose a Libraries root. This is the workspace root for managed libraries and shared profiles.
2. Enter a Library name for your first library or accept the default. Separation of libraries is for convenience: you can put all your runs in one library, or use different libraries for different riders, bikes, test programs etc. It’s up to you.
3. Choose whether the library should generate data.syn.bike exports. Enable this if you intend to view processed sessions to data.syn.bike.
4. Choose a Sources root. This is where source folders and local import workflow folders are created. Accept the default unless you have a particular reason to do otherwise.
5. Choose a Source name or accept the default. Suggested naming should reflect what the type of source and what it will be used for. For example, I have a source named Ben-Stevo-Local for import of data from my Stumpjumper Evo from a local folder (see below).
6. Choose a Source type. For a first setup, Local archive folder is the simplest option. The Import Manager can watch local archive folders and automatically process log files you copy there.

WiFi sources

You can set up a Wi-Fi logger import source to download directly from your logger. Details can be found in the BODAQS Import Manager user guide

7. Choose the target library for the source. For initial setup, your one source should target your one library.
8. Optionally enable Auto-name sessions on import and enter a Session base name. By default, your imported logs will retain their date-time file names from logger. If you would like your logs to be sequentially numbered from a common base name (‘Ben 001’ etc) you can specify that here.
9. Choose whether the source should attach a draft setup note on import. We recommend you do this. Setup templates are explained below.
10. Select Create Initial Library + Source.

Already have a workspace?

If the source and library folders already exist, use Use Existing Workspace instead of creating a fresh setup. This rebuilds this computer’s local app settings from the shared folders without overwriting logs, libraries, bike profiles, preprocess profiles, or notes.

The manager creates a source folder, a library folder, and shared profile folders. If the source and library roots are under the same data folder, the layout is typically:

<data-or-workspace-root>/
  sources/
    <source>/
      import_source.json
      notes/
      fit/
      inbox/
      done/
      failed/
      staging/
  bike_profiles/
  preprocess_profiles/
  event_schemas/
  libraries/
    <library>/
      library_definition.json
      runs/
      library/
      syn/

Your setup may keep the sources root and libraries root in different places. The appendix has the full path reference.

Multiple sources, multiple libraries

The Import Manager supports multiple sources and source types. Those features can direct log data for different bikes, riders, or test programs into different libraries, or process them with different shared bike and preprocess profiles.

Configure the bike profile

After the first source is created, the Import Manager asks whether to open the bike-profile editor. Choose Yes for a new setup.

If you skip this step, you can open it later from the Manager tab by right-clicking the source and selecting Edit bike.

The bike profile tells preprocessing how to interpret suspension and bike geometry data. It is worth entering these values before your first import.

Bike details

Provide the basic information about your bike. Geometry information is important, especially wheel travel, suspension travel, and head angle.

Rear wheel LUT

The rear wheel lookup table maps rear sensor travel to rear wheel travel. The sensor may measure shock movement directly, linkage rotation, or some indirect linear or rotational quantity.

At minimum, the LUT needs two rows: one representing zero travel and one representing full travel. If you do not specify additional points, the rear travel curve is treated as a straight line.

The LUT input units can be millimetres or degrees. Choose the unit that matches your sensor: linear sensors in mm, rotational sensors in degrees.

Obtaining suspension curves

Some ways to get suspension curve data for your bike:

• Search for an existing curve for the bike.
• Find your bike in the Linkage X3 library, if you or someone you know has access to Linkage X3 software, and read the values from the motion curve.
• Find a manufacturer-published graph of the leverage curve and read values from the graph.
• Measure your bike and calculate the curve yourself.

If nothing else is available, use two LUT points and assume a linear relationship. This is not perfect, but you need something.

What about the front wheel?

By convention, wheel travel is measured vertically. The fork moves in a straight line, but it does not move vertically with respect to the bike. That is why the steering head angle is required.

Editing bike profiles directly

Bike profiles are JSON files under the shared bike_profiles/ folder. Direct editing is possible, but use care: a shared profile can be used by more than one import source.

Configure draft setup notes

You can automatically attach a draft setup note when logs are processed. Use the note profile to choose the fields you want and the default value for each field.

Remember to edit your setup notes

Draft notes are meant to be reviewed after import. They are useful for standard or baseline setup values, but they may not exactly match the setup used for a particular session. The note carries information about its status - draft or edited - so downstream software can keep track of which notes need attention.

Unlike bike profiles, note templates and presets are source-local. They live in the source notes/ folder.

Run a first import

For a local archive source:

1. Copy a completed .zip session archive or supported logger file, such as a .bdq log, into the source inbox/ folder.
2. Go to the Manager tab.
3. Make sure the source is enabled.
4. Select Import Now.
5. If the run-description prompt appears, enter a useful run name or leave it blank to use the default.
6. Watch the status log until the import completes.

On success, the input moves to done/ and processed artifacts appear under the target library’s runs/ folder. If data.syn.bike export is enabled, export files are also written under the library syn/ folder.

For a Wi-Fi logger source, use Check Logger and Request Upload Mode from the source context menu before selecting Import Now.

Next steps

• Use the Import Manager user guide for watch mode, Wi-Fi logger details, shared profile assignment, reprocessing, naming, exports, and troubleshooting.
• Use the folder and file structure appendix when you need exact paths or want to understand what is safe to edit manually.