By some reason, I've got lots of 0 bytes files and some correct wav files:
Unit is 24410E085728D5E5 v. 1.0.0 with firmware 1.8.0
SD card (SanDisk Extreme 64Gb U3 A2 XC V30) is far from beeing full. This is the configuration:
Device ID : 24410E085728D5E5
Firmware : AudioMoth-Firmware-Basic (1.8.0)
Time zone : UTC
Sample rate (Hz) : 96000
Gain : Medium
Sleep duration (s) : 1500
Recording duration (s) : 300
Active recording periods : 1
Recording period 1 : 04:00 - 20:00 (UTC)
Earliest recording time : ---------- --:--:--
Latest recording time : ---------- --:--:--
Filter : -
Trigger type : -
Threshold setting : -
Minimum trigger duration (s) : -
Enable LED : Yes
Enable low-voltage cut-off : Yes
Enable battery level indication : Yes
Always require acoustic chime : No
Use daily folder for WAV files : No
Disable 48Hz DC blocking filter : No
Enable energy saver mode : No
Enable low gain range : No
Enable magnetic switch : No
Enable GPS time setting : No
Any idea on why could this be happening? Are 64Gb SDs not reliable?
OK, then I take as lesson learned that we have to check batteries with a tester prior configuration and not rely on the "BAT 4.6V" reported by the config app, in particular for lithium batteries. Thanks a lot.
Thanks for your many advises and expert opinion. I think I could have mistaken the batteries (or some of them) and put used ones instead of new ones. But my concern is: considering the configuration app was reporting "BAT 4.6V" (which I understand is acceptable), how could I have detected that the batteries were actually not good before the deployment?
The 64GB SD cards are reliable. We've made many months of continuous recording on them. Files that have 0kB length are generally caused by an SD card write error preventing the file from being closed. This occurs rarely with a genuine SD card error, more often with a full SD card, and sometimes when the battery is low. Always reformat the SD cards, rather than deleting files, as sometimes deleting files doesn't free up the space. The operating system just hides the files, rather than removing them from the file allocation table. In this case, I'd suspect that the battery was running down. If you check the header information of the file which was closed correctly, but is a bit shorter than expected, it will likely say that the file was cut short due to a low battery voltage. The same for the other short files that were written. You can see the header comment in on a Mac through the finder. Otherwise, open them with an audio application such as Audacity will allow you to see the information.