©2019 Open Acoustic Devices

Aug 31

AM is not responding - charging issue?

15 comments

Hi, when I use new batteries and connect AM to PC, no LED is flashing. It seems like no responding. When I last configured it the battery (in the app) showed me still low voltage (I used new batteries). After one week in the field this unit did not record any recordings. What I can do?

Hi, Can you confirm which hardware and firmware version you are using? Does the battery voltage show <3.6V in the Configuration App even when the batteries are in place? Can you post a screenshot of this?

Hi, I am using probably the newest firmware. The config app is also the updated version. However I cannot confirm it because the app and the device don't communicate each other. How I wrote the LED don't flash. Result is that I can't connect the AM with PC.

Ah, okay, I misunderstood the problem. If you put the batteries and an SD card into the AudioMoth and put the switch to DEFAULT does the red LED start flashing and does a recording appear on the SD card?

Ok, I tried it. So the redlight didn't flashing. It looks like problem in power supply. On the SD card is nothing recorded.

What happens if you do the same without the batteries insert and with the device powered by the USB cable. Where did this AudioMoth come from? Is is a GroupGets Round 7 device?

It comes from second or third round. Firmware was updated by myself. Did you think that I should update the firmware?

Yes, I think it's worth trying that. If you remove the batteries, hold the paperclip on the contacts and then plug in the USB cable, the processor should come up in bootloader mode and talk to the flash application. If you open the Devices control panel you should see it appear there as a serial device.

Ok, I try it tomorrow because I am out of my home. I let you know result.

I applied your advance. However nothing change. The LED is not flashing and I cannot see the device via PC.

It looks like this AudioMoth has some sort of hardware fault. Is there any corrosion around the battery terminals or on the top surface around the contacts?

 

I attach a picture however there is lost something? I cleared the surface of battery connectors.

That's fine as long as the steel spring battery clip is on the inside. There isn't normally anything here as it is held in place by the centre rivet.

Please it is ok that there are some scratches on the gold contacts in the left lower corner?

Yes, I think that's fine. There seems to be quite a lot of corrosion in some of the holes in the PCB. That's more likely to be the problem. The version 1.1.0 use a slightly different design whereby the holes are covered over by the solder mask.

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.