Integrating solar panels with batteries to AudioMoth

Installed new Simplicity IDE (SV4.1.12.1) and updated per instructions on WIKI https://github.com/OpenAcousticDevices/AudioMoth-Project/wiki/AudioMoth Studio Packages installed are: GNU ARM Toolchain (v4.9.2015.q3) GNU ARM Toolchain (v7.2.2017.q4) 32 bit MCU SDK - 5.7.3.0 32 bit MCU SDK - 5.8.4.0 Trying to import AudioMoth-Project I get error: "SDK of the build configuration cannot be resolved." Specifically it doesn't like the line in .cproject: value="${StudioSdkPathFromID:com.silabs.sdk.stack.super:1.1.0._1914564505}"/>

Hi, I have purchased an AudioMoth to detect the ultrasonic sound emitted by bats. And I would like to know how can I detect i) count number of bats ii) bats' flying direction. I am doing a project to contextualize bat data through different actuators of Arduino. Using LEDs, speakers, motors, etc to visualize bat data. For example, if frequency = 45kHz, LED will light up; if more bats, the motor will spin faster, etc. How can I do that? And can I transfer the data live, and wireless, using a raspberry pi and upload it to the cloud? Again, how can I achieve that? Finally, is there any guide to manipulating the bat ultrasonic wav. file to human audible sound or visualize through spectrogram? Any tutorial for that? I am trying to use Adobe Audition. Many Thanks!

Hello, we deployed AMs with 64GB cards (formatted to FAT32 with a Mac) and 3 x eneloop 1900mAh AA batteries. Calculated they should last ~8-9 weeks at our recording schedule. Have just found that the first 8 we retrieved all ceased recording within a day of each other, 4 weeks after deployment. The cards only have 19GB of data each, so probably not a card issue. Individual testing of AA batteries pre- and post-deployment showed average voltage of 1.34 each prior, and now each AM had at least one battery with voltage as low as 0.06-0.21V (but others up to 1.14V). Stumped, as a colleague had the same set- up with a slightly longer daily recording schedule and longer deployment, with no issues. Am I right in thinking: 1) there is some critical minimum threshold in battery voltage, below which the AMs won’t work, despite our calculations they should have lasted twice as long? 2) if we decrease the amount of data collected per day they would last longer, and 3) does ticking or unticking the ‘enable low battery cut-off’ box in the configuration app make any difference to this? 4) is there a large error around the mAh drawdown prediction on the app that could explain our predicted vs actual data collection period?