I have an AM that seems not to be connecting to the app. With the switch at USB\off, on inserting the batteries, the LED will flash once then go off. If I put the sd card in first, then the same thing happens. If I switch to Custom, then the LEDs will flash but obviously I cant programme. The USB cables are good.
Is this a switch issue?
Hi Steve, Most USB communication problems turn out to be down to a USB charging cable being used that doesn't have any data lines inside it. You shouldn't need batteries or SD card to test the communication. Just put the AudioMoth switch into USB/OFF and plug the USB cable in. The Config App should automatically then connect to the AudioMoth and you'll see the current time on the device start to change - it will start at 00:00:00 1st Jan 1970. What operating system are you using? Alex
Thanks Alex - Using Windows 10.
The USB cable is good - it works with other AMs. Have tested as you suggest but not getting any LEDs coming on.
@Steve Lucas If you now put an SD card in, and switch to DEFAULT can you confirm that you get a RED LED flashing as it makes a recording. Then switch back to USB/OFF and you should get 10 rapid RED LED flashes to indicate that the battery voltage is low (as there aren't any fitted).
@Alex Rogers no lights.
It's strange that the batteries affect this. It might be worth trying to reflash the firmware. That will confirm that USB communication and the processor are working properly. The instructions are here - https://www.openacousticdevices.info/flashing.
That crossed my mine earlier. Trouble is when you get to step 4, connect and remove the batteries, there are no flashing LEDs so presumably you cannot get into programme mode and certainly you couldn't tell if programming had worked.
BTW - when in Command prompt and enter Flashe.exe, what I get is "no serial ports found" These AMs have been flashed earlier this year so in know it works.
@Steve Lucas The 'no serial ports found' means that there are no serial ports at that precise moment - there are no real physical ones and Windows hasn't created a virtual one yet as it hasn't found a virtual serial device (the AudioMoth) connected to a USB port.
The AudioMoth will go into boot loader mode whenever it powers up with the paper clip shorting out the two terminals. If you remove the batteries, hold the paper clip onto the contacts, and then plug in the USB cable (a bit tricky but possible for one person), it will power up and appear as a USB device to Windows. The flash application will then find the virtual serial port and allow you to query the serial number and reflash the firmware.
@Alex Rogers This hasn't worked. tried it on two different pcs and no luck. I did Flash an AM that I know works and I was able to Flash that.
I have updated to the latest version of AM on my Mac and now my computer isn't finding the AM. Any suggestions?
There shouldn't be any problem. Can you confirm exactly what doesn't work. Have you used this USB cable with AudioMoth before?
Yes & it was OK but I have tried a different cable now & it works. I guess the cable has been damaged in some way. Thanks.
I have updated to version 1.4.4 on windows using the clip to make the connection. Then, when I want to configure recording time using the configuration app, the time doesn't apperar in black (it's not counting), despite the audiomoth is already connected. Any idea on how can I fix this?
Hi, That sounds like a communication problem between the app and the device. The USB cable is fine if you managed to flash the new firmware. Did you need to use the paper-clip because the Flash App didn't recognise the device? If you start the Flash App with the AudioMoth in USB/OFF mode, does it find it and tell you the firmware version? Alex
Hi. I used the paper clip because the firmware version that I had was 1.2.0. When I start the Flash App with the AudioMoth in USB/OFF mode, it recognises the AudioMoth and tells me'Found AudioMoth with in flash mode with a serial bootloader'. I understood that as I put again the batteries in the device before flashing, the firmware was not flashed properly. I repeated the process and now it's working! Thank you Alex.
Great. Glad it's working now.