©2019 Open Acoustic Devices

Sep 24, 2018

Simple AudioMoth Switch Repair


Edited: Sep 24, 2018

The projecting switch-tab on the current AudioMoth circuit boards is extremely vulnerable and easily broken.


Should this occur, it is much easier to perform transplant surgery on the switch than to try to remove it from the board and solder in a new surface mounted component.


The switch is held together by a simple spring clip, which is easy to remove with tweezers. Replace the broken slider assembly with a new one taken from a new switch and snap the clip back in place and the job is done.


The clip has two projections on the base that engage in small holes in the circuit board to relieve stress on the solder joints so you need to tip the spring gently over the edge of the board when removing in order to avoid damage. The component is pretty small so you need either good eyesight or a strong pair of reading glasses but otherwise it's dead easy!


Removal and replacement of the battery clip from the circuit board is straightforward as it is only secured by the two soldered pins and a spot of hot-melt glue on the opposite corner - you just need to take care not to damage any components when releasing the glue.


I've had to repair two broken switches - the first time I replaced the entire switch and managed to rip off three of the solder pads from the board in the process, leading to a very tricky board repair before I could fit a new switch. Replacing the switch slider, as described above, was very much easier.


The switch you need is a Nidec Copal CSS-1310TB - available from Farnell (order code 2854772) at £1.98 +VAT for a pack of 5 (plus a handling charge of £3.95 +VAT for orders under £20).




Oct 21, 2018

Had my first casualty this weekend, switch snapped off. But managed to change mode with a nail-file. Still got nice recordings though.

Nov 2, 2018

Thanks for this. I'll pin this post as it seems very useful.

Got the Audiomoth recently. After you tests only, the switch-tab is Broken (doesn't look i did anything to break it !!!!)... Not a disaster as i can, as previously written use a needle to change the functions, but this should be to update....

Aug 20

Hi Eric,

Thanks for the message. Sorry to hear that the switch broke so easily, was this AudioMoth version 1.0.0?


Is there a New Version ? I got this one.. amonth agao or so... It si 1.0.0. Has Davidlee wrote, is it true it can be reapaired easily even for someone with no electronic or DIY habilities ? Would like to know as i am thinking buying a new one... maybe even more (so to build up an ambisonc system !!!!

Aug 20

Nice ambisonic system sounds cool, will you be synching the clocks up for this? We are now on AudioMoth1.1.0 (below) which has an indented switch to prevent damage. The switch mechanism is quite easy to replace and cheap to buy from Digikey, I can even manage it without ungluing the PCB from the battery connector. There is a GroupGets round starting at the end of the month, so keep a look out on for the new version https://groupgets.com/manufacturers/open-acoustic-devices/products/audiomoth.


Thanks : yes such a design may solve the problem... Thanks for the good job...

many thanks... i will dig it up. Regarding the Ambisonic idea, this is for now just an idea, as ambisonic systems, or mics are quite expensive. I just thought for now that starting all recordings at same time may do the job .... maybe not ?

Thank you all I recently did this repair and it worked!

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.