This is an old revision of the document!

Bear Detection System

Constantinescu Alexandru-Iulian - ACES

aconstantinescu1108@stud.etti.upb.ro

1.Description

The purpose of this project is to detect the presence of bears in areas populated by humans and notify one or more people. In order to achieve this an ultrasonic sensor will measure periodically the distance to the nearest object. If the distance is small enough, it means something came in front of the sensor and a camera will take a photo of it. Afterwards, a neural network will analyze if in the photo there is a bear of not. If there is a bear, the photo of the bear will be uploaded via WiFi on a Firebase server and emailed to one ore more people.

2.Hardware

For this project I used:

HC-SR04 ultrasonic sensor
ESP32-CAM module (with OV2640 camera)
FT232 OKY3410-1 FTDI-USB adapter
Mini USB cable
a small breadboard
11 jumper wires (6 M-F, 5 F-F)

For uploading the code to the board a configurations similar to this is necessary:

The FTDI-USB adapter (depicted above in red) is necessary as the ESP32-CAM module has no port for connecting directly a computer to receive data. Through it the module will also receive power. The VCC and GND pins can be linked directly between ESP32-CAM and FTDI232 but I chose to use a small breadboard between them, to be able to also power the ultrasonic sensor. On the FTDI232 there is also a jumper, which is used for selecting the voltage between 3.3V and 5V. I used 5V as recommanded by the online community.

Also, the pin GPIO0 from ESP32-CAM needs to be put to ground in order for the module to be in flash mode.

For normal functioning mode, the jumper between GPIO0 and GND needs to be removed from ESP32-CAM, and the board restarted via the reset button on it afterwards.

As the board and the sensor need only to be supplyed with power, the configuration above can also be changed to something similar to this, to be more portable (with maybe a resistor between the battery and the sensor and board, if the voltage provided by the battery is greater than 5V):

ESP32-CAM also has a slot for a microSD card of up to 4GB but I used only the SPIFFS filesystem on it. I chose to partition the 4MB of PSRAM as 3MB for App data and 1MB for SPIFFS

Besides the hardware components mentioned above, in order for this implementation to work, it also needs a WiFi connection

3.Software

The flowchart of the software functionality is the following:

Because the part with computing the distance is quite simple (I use the formula distance=(duration/2)*0.0343 after I get the duration from a function call) I will talk a bit more in depth about the other parts of the software implementation:

3.1. Neural network

As a neural network I built a binary classification model.

For training I made a dataset of 448 hand-picked bear images from Flickr (External Link and External Link). For the other class I picked 465 images with humans from cctv cameras, dogs and cats, as they are the most likely to be detected instead of bears. I got those images from kaggle datasets (External Link, External Link and External Link). I also used 38 images for the validation set.

Example image:

Because the dataset I made is quite small I used Albumentations library for image augmentation.

The final version I have is from here: External Link, with small changes considering I have a different dataset. This model is MobileNetV1 with transfer learning, in order to be a binary classifier.

I also tried a model based on MobileNetV3Small and a custom model with few layers. Those proved ineffective as after converting to Tensorflow Lite their size was too big for the ESP32-CAM, especially the custom model.

After training the model for 30 epochs I got an accuracy of about 87%:

As can be seen in the image above, the model is overfitting, probably because of the dataset having too few images

This lightweight model had only 2.89 MB after training and 302 KB after being converted to TfLite, but 1.9MB after being converted again to an array which I put and used on the board.

Because on the board besided the code, libraries and the 1.9 MB model needs to be space also for tensors for running the model, I had more success with training the model for images of about 100×100 pixels, which is well below the minimum resolution of ESP32-CAM of 320×240 pixels

By increasing the input size of the model, the model itself doesn't have a big increase in size, but the space needed for tensors increases considerably. Also, additional layers might need to be added to the model, to downsample the bigger input size.

After getting the converted tensorflow model as an .tflite file I converted it to a header using the command:

 xxd -i model.tflite > model.h

Afterwards I uploaded the header from the ArduinoIDE sketch.

In the header file, changing the array of weights to be const moved the array the Flash memory, making it easier to fit the model on the board

3.2. Firebase Storage

For storing the bear images online I chose Firebase because it's free, easy to use and to setup.

In the code for uploading photos to Firebase you need an API-Key which is unique to the project, user email and password, and a Storage Bucket ID, which is also unique to the project. The website where the images can be seen looks like this:

The code for uploading to Firebase I got from here: External Link

3.3. Email sending

For sending a new image via email I choosed using a SMTP server from gmail, following this tutorial: https://www.youtube.com/watch?v=jfw1XdqlvW8&ab_channel=UtehStr