©2019 Open Acoustic Devices

Feb 26, 2018

Belize project


Hi, This is specifically for the team who worked out in Belize. I am doing a similar project in Costa Rica and will be using the information I collect on spider monkeys to correlate this to gunshots. I would be interested to learn more about your work out there? have you published? If not is it possible to see your reports and to know more about your analysis of the gun shots, your algorithms.....Potentially I do not need to create a training database since you may already have one if you are happy to share this? Best wishes. Jenna

Feb 26, 2018

Hi Jenna,

Just incase you haven't seen yet, we published a recent Methods in Ecology and Evolution paper covering this project in a bit more detail. The Belize project is still ongoing, the Open Acoustic Devices team will be there next month to continue the work, so unfortunately the code won't be ready for release until later this year. If you have any more questions that the paper doesn't answer let me know.

Thanks Andy

Feb 26, 2018

Thanks Andy I look forward to reading it, Are you able to provide us with anything resembling a training database of the gun shots or even the raw audio files?

Aug 23, 2018

Hi Andy, I was wondering if you could share some of the details about how you modified your AudioMoths for the Belize deployments. Specifically - you modified your audio-moths to use d-cell batteries right? Did you have to use 3 batteries? How many Ah did that provide and for your consumption rate, how long a deployment period did you get? Was the power consumption consistent across our survey period...ie. did the consumption estimate from the app hold up for your long deployment period? How did you like your waterproofing solution after retrieving your devices? Sorry to pepper you with these questions...and please point me elsewhere if you have published these details elsewhere. Very excited to hear more. Matthew

Aug 24, 2018

Hi Matthew, We used 6V lantern batteries for the Belize deployment, they are 26Ah which gave us about 400 days deployment period. For this deployment we changed the firmware quite significantly, changing the processor clock frequency and the way AudioMoth deals with audio samples to save energy. We also use the time setter app for all of our detection deployments, with recording schedules hardcoded into the firmware. Water proofing worked well, we used a coupling drain pipe (see image below). For this you need a separate PCB to be manufactured, this connects the PCB to the battery terminals. Andy


Aug 24, 2018

Thanks Andy! Next round (if and when round 6 happens)...could we order audio moths with the extra power connection PCB soldered on?

New Posts
  • Hi, in all my recordings there's a "clicking" noise (26-28kHz). This is an issue that I had before with some recordings but now the noise is louder and it is present in all recordings. The batteries are Energizer AA (new) and the SD card is the SanDisk Extreme 32GB. Is there Anything I can do to make the "clicking" noise disappear?
  • Amazing work! https://www.openacousticdevices.info/mmoth Clearly it is early days, but obviously so many questions pop into mind ... - Off board Lithium ion battery, with a onboad connecter? (So you can choose any size LiOn? or LiPo? like - https://hobbyking.com/en_us/turnigy-2000mah-1s-1c-lipoly-w-2-pin-jst-ph-connector.html ?) - Any Battery life / runtime estimates vs AM1.1? - Cost? Double side so more expensive? - etc, etc, etc ... Anything else to share with us yet??
  • Hi, I'm attempting to modify the basic firmware, and I'm progressing quite well however there are a couple of sneaky scenarios which require a lower level debugging capability. Can you please advise how you debug the firmware, on the device? I've modified the firmware to call 'AudioMoth_setupSWOForPrint' at the end of AudioMoth_initialise() and added a couple of debug statements such as printf("Debugging enabled"); Throughout the code, being executed. These changes, along with my other alterations were then successfully flashed to the AudioMoth device. I've then connected my J-Link debug probe https://www.segger.com/products/debug-probes/j-link/ , which appears to support the EFM32WG980F256 chip. https://www.segger.com/downloads/supported-devices.php 1. PC -> USB -> AudioMoth USB plug (normal USB connection for an AudioMoth) 2. PC -> USB -> JLink Debug Probe -> SWD via Dupont Connectors -> AudioMoth Debug pads Here's a couple of photos to highlight what I'm doing. Sure, those connections are soldered a little rough but have been verified to be fine. As a simple dump, here's what I'm using. I'm expecting you're doing something similar when modifying the firmware. JLinkExe SEGGER J-Link Commander V6.52c (Compiled Oct 11 2019 15:44:58) DLL version V6.52c, compiled Oct 11 2019 15:44:50 .... Type "connect" to establish a target connection, '?' for help J-Link> connect Please specify device / core. <Default>: EFM32WG980F256 Type '?' for selection dialog Device> Please specify target interface: J) JTAG (Default) S) SWD T) cJTAG TIF> S Specify target interface speed [kHz]. <Default>: 4000 kHz Speed> Device "EFM32WG980F256" selected. Connecting to target via SWD Found SW-DP with ID 0x2BA01477 Scanning AP map to find all available APs AP[1]: Stopped AP scan as end of AP map has been reached AP[0]: AHB-AP (IDR: 0x24770011) Iterating through AP map to find AHB-AP to use AP[0]: Core found AP[0]: AHB-AP ROM base: 0xE00FF000 CPUID register: 0x410FC241. Implementer code: 0x41 (ARM) Found Cortex-M4 r0p1, Little endian. FPUnit: 6 code (BP) slots and 2 literal slots CoreSight components: ROMTbl[0] @ E00FF000 ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7 ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM ROMTbl[0][4]: E0040000, CID: B105900D, PID: 003BB923 TPIU-Lite ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM Cortex-M4 identified. J-Link> SWORead 0 bytes read (0 bytes in host buffer) J-Link> SWOView Receiving SWO data @ 4000 kHz. Data from stimulus port 0: ----------------------------------------------- Occasionally I'll get SWO output, but its all garbled and meaningless. On other hardware I would think this was a mismatch of the receiving clock (4000 kHz), but maybe I'm attacking this incorrectly. I appreciate this is getting down into the lower levels of core programming on the device but I suspect other users may wish to also understand these debugging aspects when modifying the firmware to suit their needs also. Without a device level debugging capability the only way to check out changes is to flash the device with extra LED flashes to highlight state changes, or log to the microSD via the AudioMoth_appendFile operation. Which SWO debug probe do you use to validate changes to the base firmware? What code changes do you make to enable debugging? Are there Simplicity Studio changes which you utilise to support debugging on the device? Are you debugging the code off the device instead, on a PC using a 32-bit ARM emulator or 32-bit x86 target toolchain? Are you implementing Unit Testing on your version of the firmware?
Before posting, be sure to check the FAQ.