What is the USB device you are trying to record to and I guess I am wondering: Why? Is it perhaps a means to transmit your data?

Thanks Alex, I guess it will have to be custom firmware for my project then. In any case the 1.3.1/1.4 combo is a great help for my other uses of AudioMoth.

Thanks Peter, Alex and co for the wonderful update to the firmware and configuration software. I have a request for consideration in future versions of the configuration App. I hope this may not require variation to the firmware. The delayed scheduled start and stop (First/Last recording date) function is already useful in giving us three levels of scheduling. I would find it even more useful if I could apply more start and stop dates. I am working with the µMoth for a long term on-animal deployment where ideally the µMoth will not be in contact with a user until final retrieval. A limit on battery size means I cannot record continuously and I'll have to have extended off periods if it is to make it through more than one season of sampling. The interface for this could be done by changing the first/last portion of the schedule tab to become a scrolling list where the user could add as many first and last lines as required. Alternatively this could be combined with the "Add recording period" section so that the list of recording periods is a combined Active days (dd/mm/yyyy to dd/mm/yyyy for hh:mm to hh:mm) and repeated for each successive date period. That way it would also be useful for those trying to track sunset or sunrise times through autumn or spring as they could just make a continuous stream of one week periods where the start and stop times are progressively incremented appropriate for the location. (I'm assuming there is no plan to incorporate an almanac into the firmware). Any ideas on how hard that would be?

I think Sandor is referring to the amplitude threshold recording in the Advanced settings. But you probably already worked this out.

Can you give some more details of what has happened? You say the batteries are fine: What voltage are they registering? Is the switch set to USB/Off? Was the AudioMoth housed in something while outside?

Pancho, You are most likely correct. The problem you are experiencing is probably much simpler than the idea I was trying to explore. The microphone will still be receiving the ultrasound (which we know it is sensitive to and the silicon wafer will thus be vibrating which causes a signal to be sent to the A/D converter which it then has to interpret. I'm no expert in the way a MEMS mic works but I imagine that it is sending a similar kind of analogue signal to the A/D converter as any other microphone. If the A/D converter is just taking samples from the analogue wave form then it is going to come up with a result of some sort and it probably looks a lot like your first sonogram. At that point the AudioMoth could introduce a filter based on what frequency it is sampling at, but it does not appear from your results to be doing this. (Maybe a filter could be programmed or maybe there is already filtering hardware on the board or A/D converter that is not being engaged? Commercial recorders like the SongMeter have hardware filters that are engaged by software or manually with dip-switches or jumpers) If there is no built-in hardware solution then you will have to try a pre-mic filter to solve your issue. Ultrasound is lousy at going around corners so any solid, non-resonant barrier that you can position between the mic and the bats should moderate the ultra-sound. Lower frequencies are much better at travelling through and around barriers so you should be able to detect lower frequency bird calls preferentially to the bats but it will take a bit of experimenting to find your frequency window. Another glimmer of hope for your study is the plans to build AudioMoth with a microphone port so you can use any old mic you like. Then you can select a mic that has poor high frequency response or even better, one that has a built in low-pass filter. Your problems are of particular interest to me because I'm trying to build an enclosure for a µMoth to be worn by a Koala. I'm really only interested in sounds below 3 kHz that are coming from inside the Koala so I'm making the enclosure sealed and experimenting with the best shapes and wall thicknesses to transfer the low frequency sounds while excluding all the high frequency sounds (like the sound of things rubbing on the case). I hope I don't have to sample at a rate higher than 8 kHz in order to post process the higher frequencies out of my recordings. AudioMoth mic does have an excellent low frequency response (certainly into infrasound) which is why I'm interested in it for my application but the high frequency response could become problematic.

I'm wondering how you have the audioMoth housed. Could it be secondary harmonics generated in the housing? (Like the rattle you get in a badly installed stereo when certain frequencies are hit). The frequency range of some of those recorded pulses is quite a high percentage for a bat (rat6.wav shows pulses ranging from 3 kHz to 5 kHz) which if it was a frequency division issue might translate to a 40% variation (say 28 to 40 kHz) which would not be normal for search phase calls (but I am not familiar with your pipistrelles). So maybe they are some other kind of bat call or not a bat and are a "real" noise. What gain settings are you applying to the Audio Moth?

Any update on a release date or specifications for the μMoth. We are keen to strap audio devices onto Koalas but we will need to know the power draw of the μMoth to determine if this is our best option. The regular audiomoth has great sensitivity for recording low (even subsonic) frequencies so we are hoping that this version will also and that it is released sooner rather than later.