Bristlemouth-enabled Spotter systems contain additional log files with content depending on the connected Bristlemouth modules.
This guide only covers SD card data related to the Bristlemouth control system and connected modules for Bristlemouth-enabled Spotter 3 systems.
➡️ For a complete description of Spotter 3 system logging, see Spotter 3 SD Card Data Guide.
➡️ For a complete description of Legacy Spotter system logging, see Spotter SD Card Data Guide (Legacy).
<aside>
Table of Contents
</aside>
Files are split into numbered "log sessions" to limit the maximum size of individual files and minimize the damage of any file corruption.
Log Session ID will increment on every system boot, as well as when any individual file in the session exceeds 1GB. All files with the same Log Session ID are concurrent.
bm/ directoryFiles in the bm/ directory contain data useful for Sofar Support to track system health and diagnose issues, as well as any data from custom Bristlemouth applications. Data in the bm/ directory is organized into sub-directories by Bristlemouth Node ID. The files within each subdirectory are fully managed by the corresponding Bristlemouth Module.
log/ directoryBristlemouth-enabled systems will also log to the log/ directory. The additional Bristlemouth-related files in the log/ directory are:
SENS_IND.csv : Individual sensor readings from Bristlemouth sensors.SENS_AGG.csv : Aggregated samples from Bristlemouth sensors.BRIDGE_CFG.log : A record of the Bristlemouth system physical configuration and settings.BRIDGE_SYS.log : Debug system output from the Bristlemouth controller.BRIDGE.log : Debug system output from the main Spotter controller related to Bristlemouth tasks.BM_DFU.csv : A record of Bristlemouth firmware updates.The Bristlemouth-related files in the log/ directory use the same file rotation management and indexing pattern as other Spotter SD card files, as described in Overview.
SENS_IND.csvThis file contains individual sensor readings from supported Bristlemouth module types.
The first 6 columns are common among all module types. Subsequent columns depend on the specific Bristlemouth module type, and are not labeled in the common CSV file header. In the table views below, these flexible columns are labeled as “Data Column 1”, “Data Column 2”, etc., but these column names will not appear in the CSV header.