Group

Camera Traps / Feed

Looking for a place to discuss camera trap troubleshooting, compare models, collaborate with members working with other technologies like machine learning and bioacoustics, or share and exchange data from your camera trap research? Get involved in our Camera Traps group! All are welcome whether you are new to camera trapping, have expertise from the field to share, or are curious about how your skill sets can help those working with camera traps. 

discussion

TrailCam - Browser tool for preparing trail camera observations

Hi everyone,I am developing a tool called iNat BioPoster TrailCam:It can also be accessed from the iNat BioPoster website through the “TrailCam App” menu:https://...

1 1

I’m continuing to improve this project and would really appreciate feedback from anyone who can test it. Thank you to everyone who can help the workflow with this web app becomes much faster and more efficient.

iNat TrailCam Local — V25

  • Observation folders now include the time of the first screenshot, helping keep separate wildlife events organized.
  • JPG files include EXIF, XMP, and IPTC metadata so iNaturalist can attempt to prefill basic information during upload.
See full post
discussion

Camera Trap Suggestions for Time-lapse Seabird Monitoring?

Hi all!I'm looking for recommendations for camera traps (or any sturdy outdoor cameras) which are able to record continuously or in time-lapse mode without having to be triggered...

2 0

Most trail cameras (rugged, small, weather resistant) have a “timelapse” mode, however, not all will do a full 24-hour timelapse of photos.  

The factory firmware for the Browning trail cameras we use only allows timelapse during the day (after sunrise, before sunset).

I hacked the firmware on Browning Advantage, Edge, Elite HP4, and Elite HP5 ReconForce and SpecOps cameras so that they have an “All Day/Night” timelapse mode (including the flash at night).  The PIR sensor is active even during timelapse, so the camera will also trigger on motion. If you don’t want this, you can put a piece of tape over the PIR sensor.  

 

See: https://winterberrywildlife.ouroneacrefarm.com/2024/07/14/timelapse-feature-enhancements-for-browning-trail-cameras/

The firmware is available on my github site: 

https://github.com/robertzak133/unified-btc-reverse

Note that my firmware does not work with later models HP5 (serial numbers starting 128 or greater), or with the new HP5-Ultra cameras.  The latter has a new security feature which prevents this type of firmware hacking.  So if you go down this path, you would need to find a source of earlier model cameras.  

 

Alternatively, I am told that GardePro cameras offer an all-day/night timelapse mode right out of the box, but I have not tried this.  In general, we find the image quality of the GP cameras to be lower than that of the Browning ReconForce/SpecOps models, but that may not be an issue for your project.  In any case, you should check with vendor to make sure.  See: 

https://winterberrywildlife.ouroneacrefarm.com/2026/05/23/gardepro-a60-trail-camera-teardown-and-review/

You’ll have to experiment to find a timelapse frequency that will allow the batteries to cover your desired 72-hour target.  For internal batteries, Li-Metal primary AA cells (e.g. Energizer Ultimate Lithium) are your best bet vs. other battery chemistries by something like a factor of two.  On Browning cameras, operated through the night, you would probably need a frequency of 1 photo every 10 seconds, or perhaps every 30 seconds, to get through a continuous 72 hours on a set of 8 EUL AA cells.  It will depend largely on duration of the night, due to the relatively higher energy required to operate the flashes.    If you use an external battery, my firmware will take a photo every 1 second, max (factory firmware once after 5 seconds, max).   

 

-bob

See full post
discussion

PantheraID: individual jaguar identification with computer vision, built from 14 years of camera trap data.

Hi everyone,I wanted to share a project I've been working on and get some advice from this community. I developed PantheraID, an individual jaguar identification...

1 0

Would love to talk. We build the AI model MiewID (currently v4.1) and Wildbook, which has been deployed for jaguars on Whiskerbook.org. Happy to share ideas. Data cleaning and multispecies approaches to increase data volume and promote generalization are really the levers that have worked for us.

See full post
discussion

Camera trap recommendations

Hi everyone! I’m looking for camera trap recommendations for a pilot study in Rwanda focused mostly on capturing small to large mammals (both domestic and wild).I’m hoping to find...

12 0

Thank you everyone for your recommendations! We were awarded the grant, so I will share this information with our team, taking all your advice into consideration with our budget. 

See full post
discussion

Getting behavioral data out of datasets that weren't built for it

Burning question:There's so much monitoring data already- camera trap archives, acoustic recordings, GPS tracks - but almost all of it was collected to answer presence/absence or...

11 0

This thread is exactly the conversation I was hoping to start - thank you all.

Janelle, your point about context is the crux of it. A crocodile with its mouth open could be thermoregulating, resting, or hunting, and the still frame alone won't tell you which - it's the surrounding signals (eyes, posture, what else is in the scene) that disambiguate. That's the whole problem in miniature: behavior isn't legible without context, and most datasets strip the context out. I love your reframe of observer bias as signal, too - the order in which individuals approach and explore a new camera is behavioral data, not just noise to wait out. And it points at exactly where I think this goes: no single stream is enough. Thermal, acoustic, eDNA, movement - layered together, you start to reconstruct a scene rather than just catalog detections.

Kim, the continuous thermal deployment you're describing is the kind of capture I'd love to understand better - sustained, passive, weatherproof is where the rare and off-frame behaviors actually live. Would be curious how much behavioral signal you're seeing in that data vs. presence/absence.

Henri, your bee work is striking - we're clearly circling the same core idea from different systems. I'd be glad to compare notes; I'll follow up directly.

More soon - this is the good stuff.

Maggie

I have tens of thousands of camera trap bycatch African mammal videos that are available for analysis to anyone who can turn them into published papers, data that is actually useful for conservation, or publicity for wildlife and conservation.

They are already manually sorted into carnivores / herbivores and the carnivores are sorted and/or tagged to species. I do not have the resources to do anything further with them. 

 

 

See full post
discussion

Mini AI Wildlife Monitor

Hi All!I've been working on various version of small AI edge compute devices that run object detection and Identification models for ecological monitoring!I've recently been...

28 14

Wow, what a great project.

This is a great project! Some comments:
RaspberryPI though accessible is not the best fit for video pipelines and AI workloads or off grid deployments:
- it lacks onboard ISP which means either software implemented ISP, distorted data or on camera non energy optimized ISP.
- it lacks any power management techniques, low power modes, etc.
- it runs from SDCard using the same one for OS, swap and data, any corruption can lead to full loss.
- it runs any AI/ML workload on CPU which is extremely non efficient and any addon accelerators such as Hailo8 add a lot to power consumption and heat dissipation representing more challenges.

The advantages are of course plenty of documentation, community and all kind of makers addons, hats, etc.

For something more realistic, real life suitable I would suggest using something based on SoC with integrated NPU such as Hailo 15, Renesas RZ/V, Synaptics SL1680, MediaTek Genio or even the I.MX8M Plus for very light AI/ML workload. All of these have variety of SBCs, kits or even standalone smart camera oriented designs available from different vendors.

Yes, there are quite a few SBCs that use SoCs with integrated NN acceleration. 
Except I think you are massively downplaying the advantages of the Raspberry Pi
"plenty of documentation, community and all kind of makers addons, hats, etc."
That is quite literally everything that makes the Raspberry Pi. 


I've played with plenty of SBCs that are cheaper and have better specs than the Raspi, but they are almost useless because of the lack of "documentation, community and all kind of makers addons, hats, etc."

For a purpose built product by a team of engineers (with a lot of time and money behind them) then these SoCs with inbuilt NN are likely the future of this for of edge Ai deployment. But unless someone develops a well supported and well documented, general purpose device that uses one of these SoCs, then the default will still be the RasPi.

See full post
discussion

Building the perfect camera trap (Guide)

I know there are several people and teams going through the journey of building their own trail cameras – so I decided to make the guide I wish I had when we were still building...

5 4

Hey Bob, thanks for the kind words! Your articles on Winterberry Wildlife have really been a big inspiration for me! There are extremely limited numbers of articles on trial cameras, and you have some nice in-depth hardware level which I have been reading 😊 

You are completely right about the battery life and trigger speed tradeoff. If I remember right, there are a few cameras which offered “real time” images but in return the battery was drained in a few days and people started to complain on forums. In early stages of development there is also much about limiting the services at boot, as you mention putting the camera function as early in the boot sequence as possible, creating your own camera configs and so on. 

Great guide — this is exactly the kind of resource the community needs. A few additions from a hardware embedded perspective that might be worth including:

On PIR sensors — the standard Fresnel lens + PIR combination has a fundamental limitation in hot environments: when ambient temperature approaches body temperature (~35°C in African savannah), the thermal contrast between the animal and the background drops dramatically and trigger reliability degrades. This is worth calling out explicitly for tropical and arid deployments, where the standard PIR may miss animals during the hottest part of the day. Some teams have moved to passive radar (Doppler microwave) as an alternative trigger for hot environments — less species-selective but more temperature-independent.

On power architecture — one thing I'd add to the component deep-dive is the power switching circuit. Most commercial cameras use a simple battery holder with no protection. For DIY builds, a proper battery management IC with overcurrent protection, low-voltage cutoff, and reverse polarity protection adds almost no cost but prevents a lot of field failures, especially when using lithium primaries in extreme temperatures.

On IR illumination — the choice between 850nm (faint red glow, better image quality) and 940nm (truly invisible, lower image quality, shorter range) is well covered in most guides, but what's often missed is thermal management of the IR LEDs themselves. High-power IR LEDs run hot and can significantly raise the enclosure temperature in a sealed housing — worth mentioning as a factor in enclosure thermal design, particularly for cameras that run night-long video.

On the shift away from hardware — curious what drove that decision. Was it the enclosure/thermal challenges, the PIR reliability issue, or something else entirely?

Thank you for sharing.

See full post
discussion

AI Edge Compute Based Wildlife Detection

Hi all!I've just come across this site and these forums and it's exactly what i've been looking for!I'm based in Melbourne Australia and since finishing my PhD in ML I've been...

25 4

I find the performance of micro-nano sized models that run on MCUs impractical for many applications. This is due to the low FPS, tiny Image resolution processed and very low model capacity.
I think people underestimate the huge jump in complexity from something working on the benchtop detecting a person from a meter away to trying to detect a cat-size object several meters away in a noisy environment.

See full post
discussion

Cellular and Lora camera traps

Dear all, I'm looking for feedback from field experience using cellular and/or LoRA camera trap. How is the reliability of those systems and how strong have to be the...

4 0

Hi Antoine,

I had not seen these before, but I'll echo Rob in wondering if the radio links in these are truly what most would consider 'LoRa'.  That tech/protocol generally has very low data transfer rates and would be quite challenged in sending pictures.  That said, what they call it may not be relevant if it works for you. I would just be cautious of thinking it could integrate with other 'LoRa' devices or networks.  Some other web sites that mention this system describe the radio link as 'proprietary'.

Kyler

Antoineede they are a mesh style of camera, one links to the other and then send pictures back to the home unit where you either send them via cellular or you check the sd card. The cover Lora and cuddielink cameras do this but they play hell on battieries.

I had a cuddelink system and got rid of it , the home unit was to hook up to a pc and then from there you could easily wept a scrip to send to txt message or email etc but they scrapped that idea 

I can share some practical perspective on the LoRa camera trap architecture for remote high-relief terrain with poor connectivity.

The core concept — cameras not connected to network, base station at a connectivity point relaying via LoRa — is sound and well-proven. A few things to consider for your specific conditions:

On LoRa range in strong relief — this is where the technology shines and where it disappoints unpredictably. In open terrain, 5-15km gateway range is achievable. In steep valleys or dense canopy, a node in a gully might only reach 200-300m. The solution is careful gateway placement on ridgelines or elevated points, and in complex terrain, one or two dedicated relay nodes at intermediate heights. Test before committing to a layout.

On reliability in heavy rain — LoRa itself is very robust in rain (the signal is largely unaffected by precipitation). The vulnerability is the hardware: connectors, antenna connections, and enclosures. For the gateway, use N-type or SMA connectors with proper weatherproofing, and position the enclosure under a simple rain shield. Cheap LoRa modules with U.FL connectors are more vulnerable — consider a fiberglass enclosed gateway with a proper outdoor antenna.

On the commercial options you mentioned — the Covert LoRa uses a proprietary LoRa implementation that requires their own base station, not standard LoRaWAN. This limits flexibility significantly. If you want to integrate with open platforms like The Things Network or ChirpStack and use standard sensors alongside the cameras, a system built on standard LoRaWAN is more future-proof even if it requires more initial setup.

Happy to discuss specific gateway options or architecture for your terrain.

See full post
discussion

Our first Lynx

Last month we delivered 10x thermal wildlife cameras to Lammi Biological station, Helsinki University. These are a brand new type of system for the wildlife world, a number of...

4 2

Congratulations. The thermal images look great!

Woah!! Amazing videos. Super cool project!

See full post
discussion

A thermal (at 1280x1024 resolution) impression of Kasteel park Born, The Netherlands

I'd like to share some of the first video content filmed with our new 1280x1024 thermal module. We are proud to announce that Wildlife Security Innovations has a new partnership...

6 3

Hi Kim,

I come from automotive CV where false positives around vulnerable road users are a constant challenge, especially with edge cases at night and in low-visibility conditions (in Greenland or Canada winter conditions might skew the video clarity).

I’m curious about how this is handled in conservation/anti-poaching setups, particularly in IR-based detection systems that can pick up humans at range in darkness.

In automotive we rarely try to classify object intent, rather just direction of movement and proximity, so I’m wondering how systems in your context avoid over-interpreting a detection (e.g. differentiating a hiker or worker from a genuine threat scenario), and what role something like restricted location, known poacher trails, activity, or time of day might play into interpreting the detection.

Is the system usually designed to be triggered based with a manual triage backend or if there might be some degree of automated triage? Or if the methods you use are mostly for animal detection a la camera traps and human detections are an added benefit?

Would be great to hear how you structure that pipeline in practice.

Thanks,

Ron

Great questions! Actually, I added AI object detection with large models to my system back in 2019, before I got involved in wildlife, it was for security purposes. I got involved in wildlife in 2023. I think the vast majority of wildlife users of AI are using very small models deployable on low power systems. So they would have many false positives and negatives I expect.

My systems have not yet been used for poacher detection. When I developed it for security, I needed to make it so reliable that I could have it wake me at night. So false positives and misses had to be very small. To that end I wrote the software so it could combine several other mitigating factors. Such as multiple modules at the same time, statistical based triggers etc. For example, we could make it detect a person requiring both a high confidence thermal match and a low confidence visible match in order to trigger. That sort of thing. It can be made very reliable.

I don't think you need to determine intent with the system. That can be left to the humans. So long as they can be notified. With our systems, in addition to getting the notification they can then come in live and view the situation from multiple camera actions. Very effective visibility is the key and rapid detection and clear notification. For my home security setup, I'm using yolov6 large model with inference on 1280x1280 images. The large model is a 140 million parameter model. It's very good with both recall and accuracy. I can't remember the last time any false detection woke me. And it never misses anything.

It also had from the very start a flexible state machine built in that can be menu configured to combine all kinds of state before it triggers.

(I'll find out about low visibility situations soon as I'll be deploying some thermal systems to Greenland next month).

BTW. On my roadmap is to develop a very long distance IR system that could detect humans at 1km with reliably in complete darkness but I don't have the funding for it at the moment. It would use a zoomable IR system with a 30-180mm thermal zoom at 1280x1024 resolution. It's kind of a dream system on mine and I'm determined to build it.

See full post
discussion

Safe and Sound project report: Is Camtrap DP a suitable standard for (bio)acoustic data?

Dear WILDLABS community,We are pleased to share with you the publication of the Safe and Sound project report: Is Camtrap DP a suitable...

2 10

Your report on extending Camtrap DP to bioacoustics resonated with something we are just beginning to explore in Mindoro Island, Philippines.

We have ongoing camera trap deployments in interior forest habitats and are beginning to examine the acoustic layer embedded in those recordings, particularly for nocturnal species such as the Mindoro Boobook. The discussion around terminology and how datasets are structured feels especially relevant, though I am still trying to understand how frameworks like Camtrap DP would apply in practice to this kind of data.

It is encouraging to see this direction being shaped at the community level. I will be following this closely as we continue to learn and figure out how our own datasets might eventually align.

Thanks for this!  I've shared this post with the WildTrax (https://wildtrax.ca/) team and CanAvian (https://canavian.ca/) to investigate. We're exploring data standards as part of a recent initiative so this will be very helpful! @jeffcullis 

See full post
discussion

Issues with new model of wildlife cameras

Has anyone else used Reconyx Professional HyperFire 4K cameras?We have previously used the Reconyx PC900 and HyperFire 2X cameras in our research. Starting last summer, we...

1 0

Hi Jennifer,

Reconyx are some of the best cameras, so it sounds like you may have been unlucky with the batch.

The 4 cameras you visited 2 months later (100% battery life) would appear to indicate that there's a trigger issue with the PIR, although you'd expect at least some drop in power even with 2 months idle consumption (1-2%). The 8/12 then running out of power with less than you'd expect photos wise however points to a possible brown out, which would be linked to battery chemistry if there's a pull of current and the camera is restarting in say 50% of the triggers, but you'd need some very old rechargable alkalines that have already been used for several years etc.

What did you use battery wise for the deployment?

If you sent them back for an inspection I would be interested to hear what the reason was.

Good luck!
 

See full post
careers

Biodiversity Monitoring Scientist

This role would suit someone with a background in ecology or environmental science who enjoys combining fieldwork, data analysis, and applied research to support real-world environmental outcomes.

0
See full post
discussion

Call for Collaboration: Share your voice at ICTC next week! 

Hello, fellow WILDLAB-ers! I'm Mandy, your current Human-Wildlife Coexistence Group Leader!  :)I am heading to the ICTC conference in Peru next week and while reviewing the...

5 6

Hi Anna!

Is there anything that sparks your curiosity, which I can address for you? Take a look at the upcoming day 2 and day 3 sessions, and if you see anything that intrigues you, please let me know! I'll happily join the session that aligns, and share your thoughts! ☺️

Kind regards,

Mandy

See full post
discussion

Nature Tech Unconference - Anyone attending?

Hi all, anyone planning to attend the Nature Tech Unconference on 28th March at the London School of Economics Campus in London, UK? (the event is free to attend but...

11 2

Myself and the Fauna & Flora Conservation Technology team will be there (@Chelsea_Smith  and @ugyenpenjor ) and also the WILDLABS team @HRees ! See you!

See full post
discussion

Synchronizing camera traps

Did anyone ever succeed in synchronizing camera traps?In some of my deploymment, I wish for a wider view. I have thought about synchronizing two standard camera traps set up at an...

4 0

I've looked into adding external triggers to camera traps.  I've documented that effort here.  Basically, it involves board level work to hijack the trigger signal.  But as this signal is open drain, it's straightforward to wire-OR several of these signals from multiple cameras.  In your case, you can perform this OR operation using simple wireless units.

I'm afraid I don't see a way to abstract and extract the trigger functionality cleanly into a drop-in product.  Perhaps the best that can be done is to convert all participating cameras into slave units by replacing the IR sensor with a connector to which a master triggering source is attached.  This still requires individual board work, but is at least straightforward.

See full post