top of page

Support Forum

Public·1076 members

Unexpected recording failure on five AudioMoths after first scheduled recording period

Hi everyone,


I'm hoping someone can help me troubleshoot an issue we experienced during a recent deployment.


We deployed five AudioMoths (all running AudioMoth-Firmware-Basic v1.12.1) that were all programmed with the same configuration. According to the CONFIG.TXT files, the settings were:

  • Sample rate: 48,000 Hz

  • Sleep duration: 5 s

  • Recording duration: 55 s

  • Active recording periods: 1

  • Recording period 1: 00:00–00:00 (UTC)

  • First recording date: 2026-07-10

  • Last recording date: 2026-07-24


After retrieving the units, every recorder only contained data from the first scheduled recording date (July 10). None of them recorded on any subsequent days, despite the configuration indicating they should have continued through July 24.


Another detail that seems important is that all five units stopped recording at different times, but they all stopped during approximately the same window on the first night. For example:

  • One recorder stopped around 12:04 AM

  • Another stopped around 12:20 AM

  • The others also stopped somewhere between 12:00 AM and 12:20 AM


One recorder produced 21 WAV files, beginning at 20260710_000000.WAV and ending at 20260710_002000.WAV. The first WAV file is the expected 55 seconds long, but the final WAV file is only about 25.6 seconds, suggesting that recording was interrupted rather than ending normally.


Because all five units stopped recording suddenly, but each at slightly different times, it doesn't seem like a scheduled stop. It also seems unlikely that all five experienced battery failure within just 4–20 minutes of beginning to record, especially since they were expected to operate for about two weeks.


Has anyone seen this behavior before or have suggestions on what might cause multiple AudioMoths to stop recording shortly after the start of the first scheduled recording period? Also, does the CONFIG.TXT shown above indicate anything unusual or point toward a possible configuration issue?


Any suggestions or ideas on what to investigate next would be greatly appreciated.

162 Views

Hi, Do you know what the LED were doing when the devices were recovered? Can you use the 'Summarise AudioMoth Files' option under the 'Process' menu of the Config App to generate a SUMMARY.CSV file that will show what the AudioMoth recorded. The reason for the short file will be described in the WAV header and will likely reveal what was happening. What make and model of battery and SD card are you using? Alex


Edited

Support Forum

©2026 Open Acoustic Devices

bottom of page