Accessing logger data and configuration

The BODAQS logger has a small web interface for downloading log files and editing configuration. You can connect through a normal Wi-Fi network, or put the logger into access-point mode and connect to it directly.

Before You Start

The web interface is intended for setup, file transfer, and checking the logger between runs. It is not used while the logger is actively recording.

Logging has priority

The logger will not start the web server while logging is active. If the web server is running and you start a log, Wi-Fi and the web server are stopped so sampling has priority.

You will need one of:

• Station mode: a configured Wi-Fi network that the logger can join, plus a phone, tablet, or computer on the same network.
• Access-point mode: a phone, tablet, or computer that can connect directly to the logger’s own Wi-Fi network.

The logger must be powered on and not logging.

Connection Modes

The logger can run its web interface in two network modes.

Mode	Use When	Notes
Station	You have a local Wi-Fi network that both the logger and your computer/phone can join.	Supports normal network workflows and NTP time sync.
Access point	You want to connect directly to the logger without a router.	Useful in the field. Does not provide internet/NTP time sync.

You can change the mode from the OLED menu under Settings -> WiFi mode, or from the General configuration page in the web interface.

Starting The Web Interface

1. Open the logger main menu from the idle screen.
2. Select the WiFi menu item.
3. Wait while the menu shows WiFi: STARTING.
4. When the web server is running, the menu shows WiFi: ON.
5. Close the menu and note the network/AP name and IP address shown on the idle screen.

In station mode, open a browser on the same network and enter the logger IP address, for example:

http://192.168.1.42/

In access-point mode, first connect your phone, tablet, or computer to the logger’s AP SSID, then open the IP address shown on the logger display. If the default ESP32 AP address is unchanged, this is typically:

http://192.168.4.1/

The root page redirects to the file browser. You can also go directly to:

http://<logger-ip>/files

Finding the logger

The idle screen alternates between network/AP name and IP address while Wi-Fi is running. If the page does not load, check that your computer or phone is on the same network or connected to the logger access point.

Every web page shows navigation links for Files, General, and Sensors.

Web editing locks

While logging is occurring or upload mode is active, configuration editing is disabled and manual file changes are blocked. The web page shows a warning when editing is disabled.

Files Page

The Files page is the home page of the web interface. It lets you browse the SD card, download log files, upload files, create folders, and remove files or folders when manual file changes are allowed.

The page also includes a Logger upload panel showing upload mode, network/IP, hostname, and importable session counts.

Typical files produced by the logger are:

• .CSV log files containing time-series data.
• .json log metadata files with column semantics, run statistics, and other metadata.
• .bdq compact binary log files when BODAQS compact binary output is selected.

Download logs

Select one or more files with the checkboxes, then choose Download selected or Download ZIP. ZIP downloads are for convenient packaging; the files are not intended to be compressed for analysis.

Manage the SD card

Use folder links and breadcrumbs to navigate. When allowed, you can create folders, upload files, delete selected files, or remove empty folders.

Downloading One Or More Files

To download logs:

1. Open the Files page.
2. Browse to the folder containing the log files.
3. Tick the files you want.
4. Select Download selected to download each file individually, or Download ZIP to package them together.

Keep metadata with logs

Keep each log file with its .json metadata file where one exists. The JSON metadata tells downstream software what the logged columns mean and whether the logger dropped samples.

Upload Mode

Upload mode is used by Import Manager and related session-transfer workflows. Enter it from the Files page or from the OLED main menu.

When upload mode is active:

• The upload workflow can enumerate and transfer completed sessions.
• Manual upload/create/delete actions are disabled.
• Configuration editing is disabled.
• Logging cannot start until upload mode is exited.

Uploading And Deleting Files Manually

The upload control is useful for restoring configuration files or putting supporting files onto the SD card. Choose one or more local files, then select Upload.

Tick one or more files and select Delete selected to remove files. For folders, use the folder remove action shown on the file list.

Deletion is permanent

Deleting from the web interface removes files from the logger SD card. Download anything you want to keep before deleting it.

General Configuration

Open General from the navigation bar to edit logger-wide settings. Changes are written to the logger configuration file when you press Save.

If a page reports that restart is required, restart the logger before relying on the changed live behavior.

The General section includes:

• Logger name: the human-readable logger alias.
• Sample rate: the logging sample rate in Hz.
• Log format: BODAQS CSV, syn.bike CSV, or BODAQS compact binary.
• Omit log metadata JSON: disables generation of the JSON metadata file.
• Timestamp mode: timestamp output policy.
• Timezone: timezone rule used when the logger sets its clock.
• Auto-sleep idle: idle time before sleep.
• Wi-Fi idle timeout: idle time before Wi-Fi is stopped.

Metadata is recommended

Leave Omit log metadata JSON unchecked unless you have a specific reason to disable metadata. Metadata is the best way for downstream tools to understand logger columns and run quality.

Network And Time Settings

The General configuration page also includes network and time settings:

• Whether Wi-Fi should be enabled automatically when the logger is awake.
• Wi-Fi mode: Station or Access point.
• Access-point SSID and password.
• Whether Wi-Fi may be auto-enabled for NTP if the RTC is invalid.
• NTP servers.
• HTTP time check URL.
• Up to five station-mode Wi-Fi network slots.
• Optional minimum RSSI and BSSID pinning for each station network.
• Optional static IP settings.

Station mode tries configured networks in priority order, with preference for the most recently connected suitable network.

Access-point credential changes are saved immediately, but they take effect the next time Wi-Fi is restarted.

Static IPs

Most users should use DHCP and leave static IP disabled. Static IP settings are useful only if you deliberately want the logger to use a fixed address on a known network.

Sensor Configuration

Open Sensors from the navigation bar to edit the logger’s configured sensors.

The Sensors page now shows:

• A summary table of configured sensors.
• Each sensor’s name, type, default state, and output mode.
• An Edit link for each sensor.
• A New sensor block for adding a sensor.

Selecting Edit opens the sensor detail page for that one sensor.

Restart after add/delete/type changes

If you add or delete a sensor, or change a sensor type, restart the logger before relying on the live logging output. The web page will remind you when a restart is needed.

Supported Sensor Types

The current firmware supports these user-facing sensor types:

• Analog Potentiometer: the ubiquitous potentiometer - usually linear - used for measuring suspension displacement.
• AS5600 String Pot (Analog) and AS5600 String Pot (I2C): multi-turn string potentiometer based on AS5600 12-bit encoder. Can be read as either an analog device or via I2C (recommended).
• AS5600 Angle (I2C): A simple AS5600 single-turn sensor.
• AS5048B Angle (I2C): Another single turn sensor, but using an AS5048B 14-bit encoder.
• DAN-F10N GPS (UART): A modern GPS module with inbuilt patch antenna.

Basic

The Basic section contains:

• The sensor name.
• The sensor type.
• Connection fields for that sensor, such as analog input, I2C bus/address, or UART parameters.
• Whether the sensor is muted by default.

Analog input selection is board-aware. On RC3 hardware, analog inputs may map to external ADC channels rather than ESP32 GPIO ADC pins.

Changing a sensor type reloads the available fields for that sensor. Adding, deleting, or changing sensor type saves the configuration, but the live sensor set is rebuilt on restart.

Output

The Output section controls what the logger writes for that sensor.

• Output mode: RAW or LINEAR.
• Include raw column: adds a raw-count column alongside the primary output.
• Sensor full travel: full sensor travel used for linear scaling where applicable.
• Installed range: installed travel/range in the sensor’s linear output units, used by the Sag Helper in percentage mode.

Transforms are downstream

Logger-side LUT and polynomial output modes are no longer supported. Complex transformations, such as shock-to-wheel lookup tables, are applied during import.

Usage And Signal Semantics

The Usage section describes what the sensor is measuring. These fields are written into metadata and help downstream software choose the correct data even if sensor names change.

Usage is described using:

• End: for example front or rear.
• Primary domain: for example wheel, suspension, or brake.
• Primary quantity: for example displacement, angular displacement, pressure, voltage, or similar quantity metadata.

The Sag Helper uses usage metadata. A sensor must be active and have primary_domain=suspension to appear in the Sag Helper screen.

GPS Sensors

The DAN-F10N GPS sensor is logged differently from fixed-rate scalar sensors. GPS data arrives asynchronously at the GPS update rate and may be invalid while the receiver is acquiring a fix. The logger writes GPS signal age and quality data to assist downstream tools.

Calibration

The Calibration section contains values used to translate raw sensor readings into physically meaningful units.

Calibration methods is read-only. It shows the effective calibration actions available for this sensor type. Calibration values below it remain editable where the sensor exposes them.

For linear displacement sensors, common fields include:

• Sensor count at zero travel.
• Sensor count at full travel.
• Installed zero count.

For rotary angle sensors, zero calibration may also set direction/polarity using the on-device Capture +move step. The firmware uses direction for rotary polarity and may still emit compatibility invert metadata for downstream tools.

Wrapping

Wrapping fields are shown only for sensors that can produce multi-turn or wrapped magnetic encoder counts. These settings describe how wrapped counts are unwrapped into continuous raw position.

Other Fields

Some sensor types expose additional fields in an Other section. These are type-specific advanced settings. Leave them at their defaults unless you have a specific setup reason to change them.

Removing A Sensor

The remove button is at the bottom of the sensor detail page. Removing a sensor removes it from the logger configuration only.

Supporting files are left in place

Deleting a sensor from the web page does not delete supporting files or folders from the SD card. If you no longer need those files, remove them manually from the Files page when manual file changes are allowed.