Will this work on a RPi 3B (not +) #242

robintw · 2022-04-30T16:43:55Z

robintw
Apr 30, 2022

I'm interested in building this project, but I only have a Raspberry Pi 3B, not a 3B+. Pi's are in very short supply at the moment, so I can't easily get a 3B+.

Is there any reason this wouldn't work on a 3B? I notice the requirements say a 3B+, but apart from a slightly increased CPU speed, and some networking improvements, I can't see a massive difference in specs.

See here for a specs comparison.

nilspupils · 2022-04-30T20:16:47Z

nilspupils
Apr 30, 2022

It has not been tested on a Pi 3B so far, and i have the feeling it might not work, but it would be great if you would try it and report back! Happy testing!

2 replies

slowrunner Jun 27, 2022

I have it running on a Pi 3B (not +) in a Flirc metal case, and it seems to be working well.

I up'd swap to CONF_SWAPSIZE=1024

=== PERFORMANCE ON Pi3B - OUTSIDE AIR 91degF ===

 17:33:17 up  5:49,  2 users,  load average: 1.90, 2.25, 2.33
               total        used        free      shared  buff/cache   available
Mem:             909         468         156           3         284         380
Swap:           1023         187         836
temp=68.2'C
frequency(48)=1200000000
throttled=0x50000

(Lousy power cable to Pi under voltage at boot)

svc-user Jun 29, 2022

I recorded 60.8° today. UI is responsive and recording/analyzing is not falling behind ☺️
Using 30 second recordings with 10 second extraction length.

clsheppard · 2022-05-01T15:33:46Z

clsheppard
May 1, 2022

Pi 3B was not sufficient.

I just happened to try an install on Pi 3B v1.2 this morning. The install did not fail, but the webserver was blank. Moved the same install to a Pi 3B+ (no changes to the install) and the web portal came up as expected.

Edit: My experience must have been user mistake. I've read enabling zRAM helps (lost the link) and folks below report it is working. I write this so my post up top does not mislead people. (Sorry.) Better info below. 👇

0 replies

danmed · 2022-05-01T20:13:43Z

danmed
May 1, 2022

I have it running on a 3B but it does hang up atleast once a day resulting in needing a reboot.. This likely explains it

0 replies

svc-user · 2022-05-03T09:09:10Z

svc-user
May 3, 2022

I've had an installation running on a Pi 3B for a few days, with no hangs. I've enabled a large swap partition and is actively cooling with a 12V fan on the GPIO pins.

The blank page problem I suspect is due to configurations issues and not the PI's specs.

My setup is currently not high-volume when it comes to recordings, so maybe a higher load gives me problems.

0 replies

mcguirepr89 · 2022-05-03T17:02:51Z

mcguirepr89
May 3, 2022
Maintainer

It may be worth setting the Recording Length to 30 seconds and maybe add a larger swap space per @bdoner's comment to mitigate some of the hardware constraints. You can see what changes are needed to install on a Raspberry Pi 0W2, which may be helpful for you all here.

My best,
Patrick

0 replies

svc-user · 2022-05-03T17:32:19Z

svc-user
May 3, 2022

My Pi is currently not overclocked, and analysis is ~12s. Plus a little extra and 15 seconds are too short recordings for it to keep up. My current setting is 30s like Patrick suggests, and at that pace it has no issues following along.

I am wary about how it'll be behaving when summer hits and the temperatures goes up by 20-30 degrees.

3 replies

svc-user May 9, 2022

Update: I found my Pi was faulty and simply didn't get enough voltage from the PSU. A fix has been made and the ~12s to process 30s of audio has now been reduced to ~2.2s :)
this is still when the CPU is sufficiently cool at around 35C.

mcguirepr89 May 9, 2022
Maintainer

Cool thanks for the update! Hardware troubleshooting is so mysterious sometimes

svc-user May 10, 2022

Update: I found my Pi was faulty and simply didn't get enough voltage from the PSU. A fix has been made and the ~12s to process 30s of audio has now been reduced to ~2.2s :) this is still when the CPU is sufficiently cool at around 35C.

This is btw not true. I am in need of new glasses :)

I have a line in birdnet_log.sh that reads;
21:06:51 systemd[1]: birdnet_analysis.service: Consumed 2.307s CPU time.
I also have a line that reads;
21:08:05 server.py[551673]: ANALYZING AUDIO... DONE! Time 8.0 SECONDS

It seems as someone has recently changed what's getting logged. So I'm not sure if that makes it 10.3 seconds total, which is still an improvement, but less dramatic!

mcguirepr89 · 2022-05-03T17:40:44Z

mcguirepr89
May 3, 2022
Maintainer

I am wary about how it'll be behaving when summer hits and the temperatures goes up by 20-30 degrees.

Me too -- we're the vanguard for these tests, so we'll see!

3 replies

svc-user Jul 11, 2022

Just to update everyone. I've seen my Pi 3B cross just above 60C some times. It slows down the web interface, but doesn't halt completely. The recording and analyzing works without an issue 💪

Svardsten53 Jul 11, 2022

I do not think my 4B has ever been below 60C. It is usually around 70-72C without any problems. I need to have it in a box to keep the cats away. 😉

mcguirepr89 Jul 11, 2022
Maintainer

Thanks for the update, @bdoner!

Klages · 2022-06-09T12:39:20Z

Klages
Jun 9, 2022

Birdnet runs on my Pi 3B, but it is not very stable.
The Temperature averages on 66°C, the Pi starts to throttle the CPU at 70°C. If this happens, the Web Interface is not reachable anymore.
I would say, it can work for testing. But for continous operation, i cannot suggest it.

CPU idle:

CPU load:

Memory:

9 replies

mcguirepr89 Jun 9, 2022
Maintainer

I see now where you changed to log output --

data.redacted.com

Now that I know this, I suggest doing the following:

stop_core_services.sh &&
sudo systemctl restart caddy

The command above is an effort to stop the things using system resources so that they can all be used by Caddy during certificate challenges. If they are able to complete with the services stopped, then you can restart them (or reboot) after the certificate maintenance.

Klages Jun 9, 2022

Yes, I configured the URL with HTTPS. I've changed it to HTTP in ~/BirdNET-Pi/birdnet.conf but there still seems to be an issue:

-- Journal begins at Mon 2022-04-04 16:41:41 CEST, ends at Thu 2022-06-09 15:41:20 CEST. --
Jun 09 15:07:32 caddy[14780]: runtime.Version=go1.18.1
Jun 09 15:07:32 caddy[14780]: os.Getwd=/
Jun 09 15:07:32 caddy[14780]: LANG=en_GB.UTF-8
Jun 09 15:07:32 caddy[14780]: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
Jun 09 15:07:32 caddy[14780]: NOTIFY_SOCKET=/run/systemd/notify
Jun 09 15:07:32 caddy[14780]: HOME=/var/lib/caddy
Jun 09 15:07:32 caddy[14780]: LOGNAME=caddy
Jun 09 15:07:32 caddy[14780]: USER=caddy
Jun 09 15:07:32 caddy[14780]: INVOCATION_ID=879c9d9d13cd46a7abf63084b9ed834a
Jun 09 15:07:32 caddy[14780]: JOURNAL_STREAM=8:56479
Jun 09 15:07:32 caddy[14780]: {"level":"info","ts":1654780052.572069,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":""}
Jun 09 15:07:32 caddy[14780]: {"level":"info","ts":1654780052.6242967,"logger":"admin","msg":"admin endpoint started","address":"tcp/localhost:2019","enforce_origin":false,"origins":["//localhost:2019","//[::1]:2019","//127.0.0.1:2019"]}
Jun 09 15:07:32 caddy[14780]: {"level":"info","ts":1654780052.6265514,"logger":"http","msg":"server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS","server_name":"srv0","https_port":443}
Jun 09 15:07:32 caddy[14780]: {"level":"info","ts":1654780052.6273534,"logger":"http","msg":"enabling automatic HTTP->HTTPS redirects","server_name":"srv0"}
Jun 09 15:07:32 caddy[14780]: {"level":"warn","ts":1654780052.6276472,"logger":"http","msg":"server is listening only on the HTTP port, so no automatic HTTPS will be applied to this server","server_name":"srv1","http_port":80}
Jun 09 15:07:32 caddy[14780]: {"level":"info","ts":1654780052.6295,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0x4000338f50"}
Jun 09 15:08:59 systemd[1]: caddy.service: start operation timed out. Terminating.
Jun 09 15:08:59 caddy[14780]: {"level":"info","ts":1654780139.2841618,"msg":"shutting down apps, then terminating","signal":"SIGTERM"}
Jun 09 15:08:59 caddy[14780]: {"level":"warn","ts":1654780139.284398,"msg":"exiting; byeee!! 👋","signal":"SIGTERM"}
Jun 09 15:09:02 caddy[14780]: {"level":"info","ts":1654780142.834695,"logger":"http","msg":"enabling automatic TLS certificate management","domains":["data.redacted.com"]}
Jun 09 15:09:02 caddy[14780]: {"level":"info","ts":1654780142.8785362,"logger":"tls","msg":"cleaning storage unit","description":"FileStorage:/var/lib/caddy/.local/share/caddy"}
Jun 09 15:09:02 caddy[14780]: {"level":"info","ts":1654780142.9002547,"msg":"autosaved config (load with --resume flag)","file":"/var/lib/caddy/.config/caddy/autosave.json"}
Jun 09 15:09:02 caddy[14780]: {"level":"info","ts":1654780142.9006174,"logger":"tls","msg":"finished cleaning storage units"}
Jun 09 15:09:02 caddy[14780]: {"level":"info","ts":1654780142.9033306,"msg":"serving initial configuration"}
Jun 09 15:09:02 caddy[14780]: {"level":"info","ts":1654780142.9062054,"logger":"tls.cache.maintenance","msg":"stopped background certificate maintenance","cache":"0x4000338f50"}
Jun 09 15:09:02 caddy[14780]: {"level":"info","ts":1654780142.9089696,"logger":"admin","msg":"stopped previous server","address":"tcp/localhost:2019"}
Jun 09 15:09:02 caddy[14780]: {"level":"info","ts":1654780142.9090922,"msg":"shutdown complete","signal":"SIGTERM","exit_code":0}
Jun 09 15:09:02 systemd[1]: caddy.service: Failed with result 'timeout'.
Jun 09 15:09:02 systemd[1]: Failed to start Caddy.
Jun 09 15:09:02 systemd[1]: caddy.service: Consumed 1min 30.335s CPU time.
-- Boot 80cdf06d2847446383a4ca58f48b3701 --
Jun 09 15:10:03 systemd[1]: Starting Caddy...
Jun 09 15:10:29 caddy[811]: caddy.HomeDir=/var/lib/caddy
Jun 09 15:10:29 caddy[811]: caddy.AppDataDir=/var/lib/caddy/.local/share/caddy
Jun 09 15:10:29 caddy[811]: caddy.AppConfigDir=/var/lib/caddy/.config/caddy
Jun 09 15:10:29 caddy[811]: caddy.ConfigAutosavePath=/var/lib/caddy/.config/caddy/autosave.json
Jun 09 15:10:29 caddy[811]: caddy.Version=v2.5.1 h1:bAWwslD1jNeCzDa+jDCNwb8M3UJ2tPa8UZFFzPVmGKs=
Jun 09 15:10:29 caddy[811]: runtime.GOOS=linux
Jun 09 15:10:29 caddy[811]: runtime.GOARCH=arm64
Jun 09 15:10:29 caddy[811]: runtime.Compiler=gc
Jun 09 15:10:29 caddy[811]: runtime.NumCPU=4
Jun 09 15:10:29 caddy[811]: runtime.GOMAXPROCS=4
Jun 09 15:10:29 caddy[811]: runtime.Version=go1.18.1
Jun 09 15:10:29 caddy[811]: os.Getwd=/
Jun 09 15:10:29 caddy[811]: LANG=en_GB.UTF-8
Jun 09 15:10:29 caddy[811]: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
Jun 09 15:10:29 caddy[811]: NOTIFY_SOCKET=/run/systemd/notify
Jun 09 15:10:29 caddy[811]: HOME=/var/lib/caddy
Jun 09 15:10:29 caddy[811]: LOGNAME=caddy
Jun 09 15:10:29 caddy[811]: USER=caddy
Jun 09 15:10:29 caddy[811]: INVOCATION_ID=0c3373e47aac4ba2b9f3568173b83cce
Jun 09 15:10:29 caddy[811]: JOURNAL_STREAM=8:13900
Jun 09 15:10:29 caddy[811]: {"level":"info","ts":1654780229.6518753,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":""}
Jun 09 15:10:29 caddy[811]: {"level":"info","ts":1654780229.884517,"logger":"admin","msg":"admin endpoint started","address":"tcp/localhost:2019","enforce_origin":false,"origins":["//localhost:2019","//[::1]:2019","//127.0.0.1:2019"]}
Jun 09 15:10:29 caddy[811]: {"level":"info","ts":1654780229.8860078,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0x40003730a0"}
Jun 09 15:10:29 caddy[811]: {"level":"info","ts":1654780229.886316,"logger":"http","msg":"server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS","server_name":"srv0","https_port":443}
Jun 09 15:10:29 caddy[811]: {"level":"info","ts":1654780229.8863735,"logger":"http","msg":"enabling automatic HTTP->HTTPS redirects","server_name":"srv0"}
Jun 09 15:10:29 caddy[811]: {"level":"warn","ts":1654780229.88649,"logger":"http","msg":"server is listening only on the HTTP port, so no automatic HTTPS will be applied to this server","server_name":"srv1","http_port":80}
Jun 09 15:11:50 systemd[1]: caddy.service: start operation timed out. Terminating.
Jun 09 15:11:50 caddy[811]: {"level":"info","ts":1654780310.2961428,"msg":"shutting down apps, then terminating","signal":"SIGTERM"}
Jun 09 15:11:50 caddy[811]: {"level":"warn","ts":1654780310.3222432,"msg":"exiting; byeee!! 👋","signal":"SIGTERM"}
Jun 09 15:11:55 systemd[1]: caddy.service: State 'stop-sigterm' timed out. Killing.
Jun 09 15:11:55 systemd[1]: caddy.service: Killing process 811 (caddy) with signal SIGKILL.
Jun 09 15:11:55 systemd[1]: caddy.service: Killing process 870 (caddy) with signal SIGKILL.
Jun 09 15:11:55 systemd[1]: caddy.service: Killing process 871 (caddy) with signal SIGKILL.
Jun 09 15:11:55 systemd[1]: caddy.service: Killing process 872 (caddy) with signal SIGKILL.
Jun 09 15:11:55 systemd[1]: caddy.service: Killing process 873 (caddy) with signal SIGKILL.
Jun 09 15:11:55 systemd[1]: caddy.service: Killing process 1077 (caddy) with signal SIGKILL.
Jun 09 15:11:55 systemd[1]: caddy.service: Killing process 1086 (caddy) with signal SIGKILL.
Jun 09 15:11:55 systemd[1]: caddy.service: Killing process 1087 (caddy) with signal SIGKILL.
Jun 09 15:11:55 systemd[1]: caddy.service: Main process exited, code=killed, status=9/KILL
Jun 09 15:11:55 systemd[1]: caddy.service: Failed with result 'timeout'.
Jun 09 15:11:55 systemd[1]: Failed to start Caddy.
Jun 09 15:11:55 systemd[1]: caddy.service: Consumed 1min 24.310s CPU time.
-- Boot 59a13f49c2af4aecab3aa4063cf1a6d8 --
Jun 09 15:39:58 systemd[1]: Starting Caddy...
Jun 09 15:40:25 caddy[793]: caddy.HomeDir=/var/lib/caddy
Jun 09 15:40:25 caddy[793]: caddy.AppDataDir=/var/lib/caddy/.local/share/caddy
Jun 09 15:40:25 caddy[793]: caddy.AppConfigDir=/var/lib/caddy/.config/caddy
Jun 09 15:40:25 caddy[793]: caddy.ConfigAutosavePath=/var/lib/caddy/.config/caddy/autosave.json
Jun 09 15:40:25 caddy[793]: caddy.Version=v2.5.1 h1:bAWwslD1jNeCzDa+jDCNwb8M3UJ2tPa8UZFFzPVmGKs=
Jun 09 15:40:25 caddy[793]: runtime.GOOS=linux
Jun 09 15:40:25 caddy[793]: runtime.GOARCH=arm64
Jun 09 15:40:25 caddy[793]: runtime.Compiler=gc
Jun 09 15:40:25 caddy[793]: runtime.NumCPU=4
Jun 09 15:40:25 caddy[793]: runtime.GOMAXPROCS=4
Jun 09 15:40:25 caddy[793]: runtime.Version=go1.18.1
Jun 09 15:40:25 caddy[793]: os.Getwd=/
Jun 09 15:40:25 caddy[793]: LANG=en_GB.UTF-8
Jun 09 15:40:25 caddy[793]: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
Jun 09 15:40:25 caddy[793]: NOTIFY_SOCKET=/run/systemd/notify
Jun 09 15:40:25 caddy[793]: HOME=/var/lib/caddy
Jun 09 15:40:25 caddy[793]: LOGNAME=caddy
Jun 09 15:40:25 caddy[793]: USER=caddy
Jun 09 15:40:25 caddy[793]: INVOCATION_ID=e1970a027ead4dfd924c5cfdb7a44990
Jun 09 15:40:25 caddy[793]: JOURNAL_STREAM=8:13025
Jun 09 15:40:25 caddy[793]: {"level":"info","ts":1654782025.1601129,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":""}
Jun 09 15:40:25 caddy[793]: {"level":"info","ts":1654782025.413321,"logger":"admin","msg":"admin endpoint started","address":"tcp/localhost:2019","enforce_origin":false,"origins":["//localhost:2019","//[::1]:2019","//127.0.0.1:2019"]}
Jun 09 15:40:25 caddy[793]: {"level":"info","ts":1654782025.415069,"logger":"http","msg":"server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS","server_name":"srv0","https_port":443}
Jun 09 15:40:25 caddy[793]: {"level":"info","ts":1654782025.4151952,"logger":"http","msg":"enabling automatic HTTP->HTTPS redirects","server_name":"srv0"}
Jun 09 15:40:25 caddy[793]: {"level":"info","ts":1654782025.4152427,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0x4000234000"}
Jun 09 15:40:25 caddy[793]: {"level":"warn","ts":1654782025.4152982,"logger":"http","msg":"server is listening only on the HTTP port, so no automatic HTTPS will be applied to this server","server_name":"srv1","http_port":80}
klages@birdnet:~/BirdNET-Pi$

after that i tried with stop_core_services.sh && sudo systemctl restart caddy which seemed to help. The caddy service is now running again.

So to me it seems that this is more of a problem with the system resources of the pi 3b than with the configuration of HTTPS, is this correct?

mcguirepr89 Jun 9, 2022
Maintainer

So to me it seems that this is more of a problem with the system resources of the pi 3b than with the configuration of HTTPS, is this correct?

It seems that the Pi 3B is not able to handle the certificate maintenance for the system while also performing its analytic tasks -- I suppose this would mean that the RPi3B works fine as a local-only data-collector, but not as a public-facing, SSL-serving, CA-domain-ownership-challenge-completing website as can be achieved on the RPi3B+ and RP4B

Klages Jun 9, 2022

Alright, maybe it is worth mentioning this in the requirements
Luckily, my Pi4 will arrive next week. I will transfer the installation to it then.

I want to thank you for your fast and excellent support! :) Can I donate you something for your great work?

PS: Increasing the Swap space greatly increased the speed of my instance!

mcguirepr89 Jun 9, 2022
Maintainer

I will be more explicit that the full installation is only for certain models, not including the 3B ~~ thanks for helping us reach this determination!! I don't have a 3B to test with myself, and 3B+ works well, so this is great info.

I do accept sponsorship and donations via my GitHub sponsorship page, though I do want to reiterate that all of my support and the project itself is 100% free and without conditions :) -- with that said, sponsorship is an amazing help!

oliverk71 · 2022-06-09T14:17:38Z

oliverk71
Jun 9, 2022

From my point of view: I would not recommend a Pi 3B or 3B+. The Pi 4B seems more suitable to me, although birdnetpi generally works on the 3B, too. I feel that many of the problems I encountered are because I use a 3B (crackling noise for example). Unfortunately I could not get a 4B - since November 2021. At least not 4GB which I would prefer over the 2GB.

1 reply

nilspupils Jun 27, 2022

You can get one at the link i posted.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Will this work on a RPi 3B (not +) #242

{{title}}

Replies: 9 comments 18 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

Select a reply

Will this work on a RPi 3B (not +) #242

Replies: 9 comments · 18 replies

mcguirepr89 May 3, 2022 Maintainer

mcguirepr89 May 9, 2022 Maintainer

mcguirepr89 May 3, 2022 Maintainer

mcguirepr89 Jul 11, 2022 Maintainer

mcguirepr89 Jun 9, 2022 Maintainer

mcguirepr89 Jun 9, 2022 Maintainer

mcguirepr89 Jun 9, 2022 Maintainer

Replies: 9 comments 18 replies

mcguirepr89
May 3, 2022
Maintainer

mcguirepr89 May 9, 2022
Maintainer

mcguirepr89
May 3, 2022
Maintainer

mcguirepr89 Jul 11, 2022
Maintainer

mcguirepr89 Jun 9, 2022
Maintainer

mcguirepr89 Jun 9, 2022
Maintainer

mcguirepr89 Jun 9, 2022
Maintainer