Accessing logs and configuration

The BODAQS logger has a small web interface for downloading log files and editing configuration. You start it from the logger menu, then connect to it from a browser on the same WiFi network.

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, WiFi and the web server are stopped so sampling has priority.

You will need:

• A configured WiFi network that the logger can join.
• A phone, tablet, or computer connected to the same network.
• The logger powered on and not logging.

Starting the web interface

1. Open the logger main menu from the idle screen.
2. Select the WiFi menu item.
3. Wait while the display shows WiFi: CONNECTING.
4. When the connection succeeds, the display changes to WiFi: ON.
5. Note the network name and IP address shown on the idle screen.

Open a browser on the same network and enter the logger IP address, for example:

http://192.168.1.42/

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

http://192.168.1.42/files

Finding the logger

The logger’s idle screen shows the WiFi network and IP address while WiFi is on. If the page does not load, check that your computer or phone is on the same network as the logger.

Every web page shows, in the header:

• The name of the connected data logger
• the connected network and IP address
• navigation links for Files, General, and Sensors

The logger name is editable from the General configuration page.

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.

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.

Download logs

Select one or more files with the checkboxes, then choose Download selected or Download ZIP. Note fip files are uncompressed - this is just a file handling convenience.

Manage the SD card

Use folder links and breadcrumbs to navigate. 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 the CSV

Keep the .CSV file and its .json metadata file together. The JSON metadata file tells the analysis software what the CSV columns mean and tells it if the logger dropped any samples. It isn’t essential to have it (the software can use defaults for column definitions) but it is preferred. If you move or copy logs manually, copy the CSV and JSON together.

Uploading files

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.

Deleting files

Tick one or more files and select Delete selected. 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 a restart is required, restart the logger to ensure the change has taken effect.

The General page includes:

• Logger name: the human-readable alias shown in the web page title bar.
• Sample rate: the logging sample rate in Hz.
• Log format: the output CSV format. In addition to its native format, the logger can produce data for analysis on data.syn.bike.
• Omit log metadata JSON: disables generation of the JSON metadata file.
• Timestamp mode: controls whether the logger generates human-readable time or fast integer timestamps. Generally leave this set to ‘fast’.
• Timezone: your timezone code. Used by the logger when it sets its clock.
• Auto-sleep idle: idle time before the logger goes to sleep.
• Wi-Fi idle timeout: idle time before WiFi is stopped.

Metadata is recommended

Leave Omit log metadata JSON unchecked unless you have a specific reason to disable metadata. If you have the metadata file, then log files generated for data.syn.bike can be processed by BODAQS.

Network and time settings

The general configuration page also includes network and time settings:

• Whether WiFi should be enabled automatically when the logger is awake (recommended: OFF).
• Whether WiFi may be auto-enabled to set the real-time clock (recommended: ON.
• NTP servers used for time sync.
• Up to five WiFi network slots.
• Optional minimum RSSI and BSSID pinning for each network.
• Optional static IP settings.

The logger tries configured networks in priority order, with preference for the most recently connected network if it is available.

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.

After saving network settings, you will need to stop and restart WiFi from the logger menu before the new connection settings are used.

Sensor configuration

Open Sensors from the navigation bar to edit the logger’s configured sensors. The page lists existing sensors first, followed by a New sensor block at the bottom for configuration of additional sensors.

Sensor information is organized as follows:

Basic

The Basic information section contains:

• The sensor name. Generally the name should describe the physical sensor, e.g. Miran 78mm linear pot.
• The sensor type, selected from the types supported by the logger.
• How it is connected to the logger: either the analog input it is connected to, or its I2C bus and address.
• Whether it is muted (disabled) at startup. Muted sensors can be enabled on the logger if required.

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

Restart after add/delete

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

Output

The Output section controls what the logger writes for that sensor. In addition to the raw sensor output, the logger can scale the outputs linearly into real-world units, or apply a non-linear transformation specified either as a lookup table (LUT) or by a polynomial.

• Output mode: controls what, if any, transformations will be applied to the raw output. Options are Raw, Linear, LUT or Poly.
• Include raw column: for non-raw output modes, the raw output can additionally be included.
• Sensor full travel: the full travel range, in real-world units (e.g. mm), used for linear scaling.
• Units label: the units shown for linear output.
• Output transform: the selected polynomial or lookup-table transform, where applicable.

Transform files

Transforms are defined in a data file. These files must be placed in the config/<sensor name> directory before they can be assigned to a sensor.

Applying transforms on the logger

It is generally preferable to do non-linear transformations (e.g. translating shock travel into wheel travel) in the analysis software. This approach means that the logger configuration does not need to change when the logger is moved from bike to bike, and zero-point calibration is unnecessary. For the time being the logger firmware supports transformations when the log is captured, but this functionality may be removed in the future.

Usage

The Usage section describes what the sensor is actually measuring. These fields are written into the JSON metadata file and help the analysis software choose the correct data, even if sensor names change. It also assists the logger to write the correct data when an alternative output format is chosen, e.g. for analysis on data.syn.bike.

Usage is described in terms of:

• End: which end of the bike is being measured: front or rear.
• Primary domain: which part of the bike is being measured, for example wheel or suspension.
• Primary quantity: what physical quantity is being measured, for example disp for displacement.

Calibration

The Calibration section contains information required to translate raw sensor readings (e.g. ‘counts’ from the logger’s analog-to-digital converter) into physically meaningful units.

The calibration parameters available depend on the type of sensor, but for linear-motion sensors (e.g. linear potentiometers) they are:

• Sensor count at zero and full travel - the sensor output at the extremes of sensor travel. This information is used along with sensor full travel to translate raw output to displacement in mm.

• Installed zero count - the sensor output when the installed sensor is at its zero position (e.g. sensor is installed and bike suspension is topped out).

Generally the on-device calibration workflow will set these fields, but the web page is useful for inspection.

Wrapping

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

Removing a sensor

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

Transform files are left in place

Deleting a sensor from the web page does not delete transform files or transform folders from the SD card. If you no longer need those files, remove them manually from the Files page.