Tuesday, February 19, 2013

British Bat Calls: A Guide to Species Identification

So, I finally went ahead and ordered this book - British Bat Calls
I've been aware of it for a while now. Of course, I realize that it only covers the bats of Britain. But, I learned that it contains a lot of great info on the subject of bat detecting and recording in general. I took a look at a few sample pages, and it looks very interesting. The information, and topics covered, should prove to be useful to me! I'm looking forward to it. A short review of this book will be posted here in the not-too-distant-future.


Saturday, February 16, 2013

BatBox Griffin Firmware Update v25

My apologies for not having posted this sooner, but: Just a quick update / Reminder - For Owners of The BatBox Griffin bat detector.

As per BatBox Ltd.'s Site - Firmware update v25 is available for download:

"Please download the latest v25 firmware update here which includes 2 files (0025.fug and FUG 25.doc) and follow the instructions from the Word document. This Firmware update includes Bug fixes to the timer operation when used in unattended mode and the log file data reporting.
Also the unit now reports the name of the last fug update implemented."


Not too much to say about this, really...
Some key points:

After the upgrade, the Griffin's 'Firmware' screen displays:
(lastfug 25)


And, an example of a typical log (doc/txt file), of an individual recording, is as follows:

Log Rec# xxx...60:
date=13-Feb-13
time=20:38:35
sample_rate=705600
temperature(C)=3.0
light=3.2
rec_length=00h 00m 2.00s

Happy bat detecting!

Friday, February 15, 2013

The Latest BCID Software! Part 2 Of 2

Review: BCID software (from Bat Call Identification, Inc.) Part 2 Of 2

I'm having a lot of fun with this software! Finally! After many years of simply recording bats...Having the ability to quickly identify them to species...Even though it's not 100% accurate...Is still an awesome thrill.

Here's a quick summary, from Part 1 of this review:
* The software is developed by  Bat Call Identification, Inc.
* By default, it analyzes zero-cross files (such as those produced by AnaBat, SM2BAT, etc.). But, it features a built-in utility that will convert .wav files to .zca (zero-cross) files.
* A single-license copy of the software currently sells for $979.

* The software is robust, fast, easy to install, and use.

A typical work-flow of the software is as follows:

1. After the program is launched, you may start by clicking the 'Add Folders To Project' button, on the lower left of the BCID Dialog box

2. Specifying the path (File Folder location) where the (.zca/zero-cross) files reside. You are given the opportunity to drill down to the drive letter and Folder name.

3. Once the Folder is selected, click on the 'Identify Calls' button, and you will see the script run.

It's basically a Microsoft Windows Script. Which, in layman's terms means: It will appear as though a "ghost" is (quickly) clicking on a few buttons, on the Analook window. Analook will launch, and program options will be automatically selected, etc. The script will finish as quickly as it started. And, the dialog box that pops up, will prompt you to "Click OK" - "When you see "Done" displayed below the box.
*Note: AnaBat software, is not required in order for BCID to work. The reason is that BCID includes AnaLook - In the form of an executable file (Analookw.exe) which resides in the software's default Folder (i.e. C:\Program Files\BCID...)

BCID, is of course, excellent when used with files produced by any zero-crossing detector. This ID software is a powerful application, aimed at bat survey Professionals. For example, it was designed to handle >5000 files at a time! I found it very useful, when handling (what I believed to be) "large quantities" of recordings.
One of the hurdles I faced, in the past, was having large numbers of individual recordings - Without any quick way of analyzing them. It was a manual process, comparing sonograms/bat calls to the characteristics of calls from known (confirmed) species. To do this, you must have access to recordings that were made with a "bat in the hand" as the expression goes. These can be in the form of pages from books, or electronic format, etc.

After leaving some detectors out, doing passive recording for the entire evening - The next day, I was left with many individual recordings. Most of which would turn out to not have recorded any bats. Before having BCID software available, there was no easy way to determine which recordings picked up bats. What I ended up doing, was to open large bunches of files using Audacity. Then, I could at least use the visual representations of the recorded sounds, to see if bat calls were recorded or not. It was fairly tedious and I'm sure that many weak bat calls were missed using this method.

With BCID software, all of that work is a thing of the past. You simply tell BCID where your (.zca) files are located, and a few seconds later, an MS Excel file is created. By default, the Excel file is placed in the root directory (where the original files reside).

In addition, BCID also has a page on their site, which shows some great Example bat calls: Very informative!
I'm very happy that they have provided these valuable sonograms. They can be used to help you ID bats that you've recorded. Regardless of the software used, in the creation of your sonograms, you'll find these to be a big help. The bats represented, are North American species, in this case.

As far as weaknesses are concerned, the one area that is far from perfect, is the 'WavtoZero' feature. Accessed by clicking on the Tab of the same name. Of course, as the name implies, it is designed to convert .wav files to .zca files. But, during testing/normal use, this feature doesn't work as well as one might like.
However, the end user is made aware of this, clicking on the WavtoZero tab will bring up this embedded text: "BETA Version: This converter is still being refined for optimal performance. There are many types of ".wav" files and all may not work correctly. Please email us an example if you encounter a bat call file that does not work."

As a bat detecting enthusiast, you can imagine how wonderful it is to have such an application, at my disposal. I believe that many bat detecting Professionals will find it indispensable.

Happy bat detecting!

Saturday, February 2, 2013

First Look At The Latest BCID Software! Part 1 Of 2

Review: BCID software (from Bat Call Identification, Inc.) Part 1 Of 2

I finally had an opportunity, to install and try BCID software - And, I'm happy to report that it was a success. Everything went very smoothly. The software installation and program execution proceeded flawlessly; and fairly quickly.

A temporary license for the software, was graciously provided to me by Bat Call Identification, Inc. As you may notice, from some of the screen captures; the license will expire on April 1st 2013. Plenty of time for me to test and review it. I have no affiliation with  Bat Call Identification, Inc. I obtained the (temporary) copy of this software, for the sole purpose of sharing my findings with fellow bat detecting enthusiasts.



So, I installed the latest version, 2.4n, from the BCID Website

You may download a Trial Version of BCID software, on this Page (Link is found in the small brown box, at the center of the page).

The software application itself is neither large, nor complicated. It installs via a single executable file, right after download. After installation completes, you have the option of automatically launching BCID.

Here is a screen shot showing the 'Species' Tab - (New York is selected, in my case):



Some key points, that became evident right away, were:

* Affordability - At just under $1000 US, the price of this software is lower than it's main competitor (SonoBat). A factor that will be attractive to both hobbyists and Professionals.
* How small the software file itself is - Very fast download and install process.
* The application is robust: It's able to handle many files, very quickly.
* The software is easy to use - I was able to use it, before even reading the Manual - Although I don't recommend this! It's always best to read the manual first!
* A bat call identifying software, to use with files from zero-crossing bat detectors (AnaBat, SM2Bat, etc.) is very useful.
* The ability to identify bats down to Species, using recorded calls would be a valuable asset to all those doing bat surveys, research, etc.

Alas, nothing is perfect...

- BCID currently doesn't have the ability to ID bats using (raw) .wav files. The .wav files must be converted first. It does have this ability, through a built-in feature.

By default - BCID analyzes all of the (zero cross) files in the specified Folder, and automatically produces a MS Excel file. Here is a small sample of the data produced by BCID - It is just a partial image that I took from the resulting Excel file (Excel lines/cells are not shown in this example):



It was very exciting, to be able to finally ID the bats frequenting the airspace above my back garden :)

Check back, for Part 2 Of 2 of this Review; when I will cover how the software works.
Of course, the next thing that comes to mind is: I wonder just how accurate this IDing software is? The fact is, that at the time of this writing: There isn't any software available that can be depended on, for completely accurate bat call identification. None of them are 100% accurate.
This topic will also be covered in the second part of this review.

Part 2 Of 2

Saturday, December 1, 2012

Review: The New AnaBat SD2 - Part 2 Of 2

Review: The New AnaBat SD2 - Part 2 Of 2
Here is an example of how the AnaBat SD2 creates a small Log File, to record the various processes that take place.

AnaBat SD2 - CF Bat Detector
Firmware Version: V4060g
Serial Number: SN XXXXX
------------------------
YYYY-MM-DD HH:MM:SS
2012-08-27 18:41:14   ------------ BOOT MODE ------------
2012-08-27 18:41:14   Wakeup from Power Button
2012-08-27 18:41:14   Startup Sensitivity set from Pot to: 50
2012-08-27 18:41:14   SD2 powered by Internal AA batteries: 5.15V
2012-08-27 18:41:14   Temperature is 21 deg C (+/- 3 deg C)
2012-08-27 18:41:14   Initialising USB CDC Class
2012-08-27 18:41:14   Initialising Low-Level Disk I/O Layer
2012-08-27 18:41:14   CF Drive Mounted.
2012-08-27 18:41:14   Checking for DATA.DAT File..
2012-08-27 18:41:15   Data.dat file found
2012-08-27 18:41:15    -> Reading Header Information..
2012-08-27 18:41:15       Data.dat is ok.
2012-08-27 18:41:15    -> Scanning for First Unused Data Sector..
2012-08-27 18:41:15       Data.dat says file size is 1963776 kB and data starts on CF at sector 0x247
2012-08-27 18:41:15       First empty sector found at address 0x4600 in Data.dat
2012-08-27 18:41:15   No monitoring begin / end time parameters set on the card
2012-08-27 18:41:15   ------------ FORCED RECORD MODE ------------
2012-08-28 04:36:56   Power Button Pressed
2012-08-28 04:36:56   Record Report:
2012-08-28 04:36:56    -> Internal AA batteries: 5.04V
2012-08-28 04:36:57    -> Recording session began at 18:41:15
2012-08-28 04:36:57    -> Recording session ended at 4:36:56
2012-08-28 04:36:57    -> You recorded 113 kB (226 sectors) during this session
2012-08-28 04:36:57    -> Total size of data in data.dat = 130 kB (261 sectors)
2012-08-28 04:36:57    -> Total space left = 1963645 kB (3927291 sectors)
2012-08-28 04:36:57   ------------ LOW-POWER MODE ------------

Here is a partial screen capture, (call of an Eastern Red Bat) - I "included" the Dialog box showing the version of AnaBat software:

 To be continued...

Sunday, August 12, 2012

Review: The New AnaBat SD2 - Part 1 Of 2

The New AnaBat SD2 is a solidly built bat detecting device. I was originally a bit concerned with what I thought would be a steep learning curve (in order to even use the unit). After all, Titley Scientific offers on-going classes, for the purpose of instructing users on how to get the most from their Anabat systems.

But, I was pleased to see that it wasn't difficult to set-up and use at all. You can become acquainted with the User Manual fairly easily. I would guess that most Folks will be able to read through, and "absorb" it all, in just about an hour or two. And, be able to operate the machine properly.
Especially if you don't intend to use a PDA with the Anabat (in which case, you can "skip" those sections of the User Manual).
This is a good thing: Since there are, of course, instances when a researcher is out in the field (for several months, for example). More than likely, in a remote area of the world.

Layout of buttons: The arrangement of the Anabat's main controls - Sensitivity Knob, Power Button, Volume Buttons, etc., are all thoughtfully placed.

Acceptable weather did not present itself for quite some time, after the arrival of the test unit. When good bat detecting weather did finally roll around: I did not want to miss the opportunity of an evening of recording...So I made a quick preliminary check (of the Division Settings, etc.), adjusted the Sensitivity Knob,  and set it up to record bat data; quite easily...
The first thing I was pleased to discover, was how resistant it was to "man-made" sounds. And, how it would never record sounds made by my opening/closing of the window, or even nearby neighbors (who may have been mucking about). Most other detectors would register triggers for a lot of these events. So, it has outstanding rejection abilities (when it comes to non-bat sounds). 
As of yet, with the sensitivity knob set to ~ 5, I've yet to even record a tree-dwelling Katydid.

Another one of the things I noticed early on, was that the AnaBat reminds me of a computer network server!
In the past, I worked as a Computer Engineer for ~15 years, and as a Network Engineer for ~3. Which is why I noticed it right away; when I took my first look at the AnaBat's Log files. It was like a "flashback" to my days working in a server room. Every event was logged.

I can further illustrate my point, by pasting a couple of paragraphs, directly from the Titely Anabat User Manual:


"Each time the SD2 is turned on it creates a file in a log

directory (1 MB) on the CF card. These log files record all

of the events which occur while the detector is switched

on, such as the buttons pressed, operating modes, time

parameters set, errors which occurred and so on. These
log files are very useful for diagnosing problems."
CF card must be formatted (Quick Format is OK). Then, initialized using the 'Cfcread' app (on the Titely CD-ROM); this takes several minutes."
 


One might say, that the process of checking the bat recordings requires a step or two more, than other high-end (recording) bat detectors. Once again, I will share a cutting from the Anabat User Manual: 
 

"7. On completion of recording session…

Press POWER button. It is now safe to remove the CF card.

8. Download and view data

Use the CFCread program to download the saved data from the CF card

onto your computer. Then use the AnalookW program to view, analyse

and identify the bat calls to species. See the section on ‘HOW TO
DOWNLOAD DATA FROM THE CF CARD’ for details."
I prefer removing a memory card from a (high-end) bat detector, and being able to access it using virtually any .wav capable program. Other top-of-the-range bat detectors do this easily.
Now, as for power consumption:
 

"TIPS FOR PASSIVE MONITORING

Power and data storage space

For short term monitoring sessions the detector can simply be powered by AA

batteries. We recommend Alkaline or Nickel Metal Hydride rechargeable

batteries with a capacity of at least 2500mAh. These add very little weight

and may last 2-3 days depending on the length of your recording sessions,

battery type and condition etc. However in practice it would be safer to use

the AA batteries for one full night only before recharging/replacing them.

45
This is because battery capacity is also affected by other factors such as
temperature, and they may not last as long as expected in the field.
"
In testing, I found that all of my rechargeable/NiMh batteries held up very well. Providing enough power for an entire night's recording +... So, the AnanBat gets high marks for battery consumption.
  
The AnaBat's CF Card occasionally develops errors. I can see this being caused by "Operator error". Such as: Not powering off the unit before ejecting the CF card; and things of that nature. 
So, it's Nice to have file recovery tools / corrupt files -
The following is from page 87, of the User Manual:
 
"REPAIR OPTIONS FOR CORRUPT DATA.DAT FILES
A number of other options are available in CFCread under ‘Repair’ the menu bar which may help you fix corrupt DATA.DAT files."

I thought I would "enjoy" checking the time remotely, via usb cable... using cf Storage ZCAIM Interface...but, I had issues: My first attempts didn't work - back to the User Manual...

The AnaLookW software, is where due diligence is needed. In using the software to view subsequent bat recordings; one can see that visual analyzing is the "preferred" method of the software. Since one must utilize a few additional steps, in order to actually listen to the recorded bat calls. More on that later.  


To be continued, in Part 2 Of 2...

Tuesday, July 31, 2012

BatBox Griffin: The Latest Firmware Update (V23)

I was very intrigued, when I first learned of the new firmware release for Griffin; from BatBox, Ltd.
The firmware was made available to me, from Batbox, Ltd., to review and explore, etc. It will be made available, for all Griffin owners, on their Firmware Update Page Here - In about a week.

If your system is up to date (Ver.22) then, just before the update (to Ver.23) your firmware info should read similar to this:
PIC   V140
FPGA   V09.01.2012
S/W   V14.03.2012

Upon launching the upgrade application, it will begin it's (short) process, by displaying the following:
"Doing upgrade, please wait" and the system will begin to perform the upgrade on itself...
Eventually, the final text displayed on the screen will read:
FPGA Upgrade
Program
ToGo: (The seconds count down) 98..97....42...31... Until the system powers itself off (upon completion).

When you next power the unit on, the system will go through a few more upgrade-related splash screens (automatically) and will then return to the ready state.

If one checks the firmware status, the display should read something like this:
PIC   V140
FPGA   V09.01.2012
S/W   V05.07.2012

Which indicates that the upgrade has completed successfully.
At this time, I don't have any solid specifics to report. Since this firmware upgrade is so new, the official documentation has not been made available to me yet.
Also, It is currently 4:00 AM here in the Northeastern United States, and the peak times for (best) bat activity has already passed. I hope to test it's unattended recording improvements tomorrow night.

Happy bat detecting!

Thursday, July 12, 2012

The New AnaBat SD2: First Impressions

The new AnaBat SD2 bat detector from Titley Scientific has arrived. This loaner unit was well packaged; double-boxed, with the AnaBat unit and accessories well protected in grey foam. It's a very robust unit, with sturdy construction throughout.



As you can see, in the photos above - Aside from the CD ROM disc, which contains a the latest version of AnalookW call analysis software (along with User Manual in PDF, and other data). It is supplied with all necessary cables: Serial cable, Mini-USB to USB cable, 2GB CF Memory card, and a fused power cable (for powering the unit via a 12v DC power source). The CF Memory card Slot, features a protective cover that is secured with two (silver colored) thumbscrews.

Looking for The Next Bat Detector for Review!

Well… For now, I’d just like to say Thank You to The Netherlands! 🇳🇱  There will be 2 new bat detectors tested and reviewed here in the ne...