To see this working, head to your live site.

USB request for device descriptor failed

If I plug the Audiomoth into my PC USB with the switch set to USB/OFF then the Audiomoth enumerates and the green LED stays on and the Config app recognises the Audiomoth.

But if I do the same thing with batteries inserted in the Audiomoth, then the green LED goes out after a few seconds and the Config app does not recognise the Audiomoth and Windows device manager displays an error saying the device is unknown because the device descriptor request failed.

This makes it impossible for me to configure the Audiomoth, because I can only configure it with the batteries out. But without the batteries the configuration is lost when I disconnect the USB cable.

I am using Config app version 1.2.2

The Audiomoth has firmware version 1.2.1

I am running Windows 10 64-bit.

I have verified that the Audiomoth records if the switch is moved to the DEFAULT position with the batteries inserted and USB not connected.

Please advise.

Thanks,

Nigel

3 comments

3 Comments

Share Your ThoughtsSign up to leave a comment.

Pierre

Sep 07, 2019

I'll jump into this thread, as I noticed a similar behaviour.

Usually I power my AudioMoths on NiMH rechargeable batteries. Connecting to PC, setting time and configuration just go as expected. With 3 fully charged batteries, both utility tools see 3.9 or 4.0 V.

On my 2 Round 5 AudioMoth's with new Alkaline batteries inserted, when connecting to PC, the green LED lights steady for a couple seconds, then goes off and Windows 7 alerts on "Unknown Device". No way to connect and configure the AudioMoth. I decided not to worry about that as 2600 mAh NiMH give enough autonomy for my usage.

Now I received the Round 7 AudioMoth's. Connecting to the same Windows 7 laptop, setting time and configuring, all go fine, also when powerd on new Alkalines. Voltage displays at 4.8 V.

So my guess is that on Round 5 devices there is some sort of an antagony effect when powering on both USB (rated 5 V, I've not measured) and batteries (4.8V) that make the PC expect someting else than it sees.

I hope this can contribute understanding this issue.

See you

Pierre

Alex Rogers

Aug 31, 2019

Hi Nigel, Can you confirm where this AudioMoth came from? Is it a GroupGets Round 7 device? Do you have access to another computer to try it on?

nigel.evans

Aug 31, 2019

Replying to

Hi Alex

Thanks for your quick response. I got the Audiomoth quite a long time ago, but due to circumstances this is the first time I've tried to configure it with the batteries inserted. My recollection is that I got it from Group Gets round 5, but I may be wrong - I'm not in the office, so I can't get at the paper work to check right now.

Anyway, I followed your suggestion and tried it on another computer - sure enough it works fine on that computer. So I'm thinking (as I expect you were) that it's a driver issue on the other computer. Some years ago I did some development work with EMF32 and I had an old but then current version of the SiLabs driver installed. When I tried to uninstall the old driver recently my PC said it couldn't because it couldn't find something or other. But I did install the current SiLabs driver, which appeared to work OK. But I guess something is mangled under the bonnet. I have searched but can't find any instructions to manually uninstall the old SiLabs driver, so I'm stuck with it on the other computer for now. I have seen some posts that suggest the SiLabs drivers prior to version 6.7 don't work under Windows 10.

Thanks again for your help - much appreciated ;)

Kind regards,

Nigel

USB request for device descriptor failed

Before posting, be sure to check the FAQ.