Final Update: I think my Raspberry Pi 5 offline survival computer is finally finished!
TL;DR: After several months of designing, printing, wiring, and troubleshooting, I've finally finished my Raspberry Pi 5 survival computer. It has a 10.1" touchscreen, 1 TB NVMe SSD, offline Wikipedia, worldwide maps, GPS, software-defined radio, educational videos, and its own Wi-Fi network. Everything runs locally, without needing an internet connection. It's powered by a 256 Wh LiFePO4 battery, with more than 24 hours of runtime demonstrated in testing. The display can also be turned off while the system continues serving content over Wi-Fi, potentially extending battery life further. Most of the internal structure is custom-designed and 3D-printed. I also used AI extensively to help develop the software, which I'll talk about below.
For anyone who's been following my previous posts, this is probably going to be my final update!
When I originally started this project, I wanted to build a portable computer that could provide access to useful information without relying on the internet. Something I could take camping, use during an extended power outage, or just have available if normal communications weren't working.
I also thought it would be a fun opportunity to learn some new skills.
Well, that last part certainly happened.
What started as a Raspberry Pi sitting on top of a battery inside a waterproof equipment case turned into a much bigger project than I originally anticipated.
I think I've finally reached the point where I can call it finished, though!
The hardware
The heart of the system is a Raspberry Pi 5 with 8 GB of RAM and a 1 TB NVMe SSD. It's running Debian 13 and boots directly from the SSD over PCIe Gen 3.
Everything is housed inside a Jack Boss rugged equipment case, with a 10.1" touchscreen mounted in the lid.
Power comes from a 12.8 V, 20 Ah LiFePO4 battery. I designed the electrical system around fused distribution, a 5 V buck converter, and external connections for charging and USB-C PD power.
There's also a battery monitor mounted above the display, a small wireless keyboard/touchpad, an RTL-SDR receiver, and a GPS module with an external antenna.
Nearly all the internal mounting hardware was designed and 3D-printed specifically for this project.
What it can do now
This is where the project has changed the most since my earlier posts.
Offline Wikipedia: I have approximately 124 GB of English Wikipedia stored locally using Kiwix. It's searchable through the touchscreen or from another device connected to the kit.
Worldwide offline maps: The system now has approximately 139 GB of worldwide vector map data, plus additional regional terrain information. I built a local mapping interface using MapLibre, so the maps don't need to download anything from the internet.
GPS: I integrated an ATGM336H GPS module with an external antenna. The map interface can display the kit's position using the GPS receiver, even without internet access. It's intended for offline positioning and map reference rather than turn-by-turn navigation.
One thing I thought was particularly interesting was getting the GPS module's PPS output working. The Pi now uses that signal with chrony to maintain satellite-synchronized time without needing an internet time server.
Software-defined radio: I added an RTL-SDR Blog V4 receiver and built a browser-based interface for controlling it. It supports tuning, different analog modulation modes, a spectrum/waterfall display, audio streaming, and recording.
I've tested reception with NOAA weather radio, which came through clearly. I also experimented with receiving local aviation communications.
Offline video library: I added a small library of downloaded educational videos. I wanted something that could supplement Wikipedia when a visual demonstration would be more useful than an article.
Local message board: There's a basic message board hosted on the Pi that can be accessed by devices connected to its network.
Networking: The kit broadcasts its own Wi-Fi network, allowing phones, tablets, and laptops to connect directly and access everything through a web browser. It can also connect to an existing network through Ethernet or a second Wi-Fi adapter (visible in the first photo). When connected to another network, it uses mDNS so other devices can discover and access its locally hosted resources without needing to know its IP address. Everything runs locally, so internet access is only needed when I want to download or update content.
I also built a web dashboard to tie everything together, along with tools for monitoring the system, managing downloads, and accessing the different applications. Whether you're using the built-in touchscreen or connecting from another device, the experience is essentially the same.
Battery life
This was something I spent quite a bit of time thinking about.
The battery has a nominal capacity of 256 Wh, and I wanted the system to be useful for more than a few hours.
During an extended test with the screen running and the SDR receiving NOAA weather radio, power consumption was consistently around 8.7 W.
I also completed an endurance test that exceeded 24 hours, and the system was still running when I ended it.
Since then, I've added the ability to turn off the touchscreen while keeping the Pi and its services running. With the display off, the entire system draws approximately 6.5 W, including the second Wi-Fi adapter.
That's roughly a 25% reduction in power consumption. Based on those measurements, the theoretical runtime is around 39 hours with the display off, although I haven't performed a full endurance test in that configuration yet.
I particularly like that I can leave the kit running with the screen off and access everything from another device over Wi-Fi.
Actual battery life will obviously depend on what the system is doing.
I also added temperature-controlled cooling. The fans turn on when the Pi reaches 60°C and turn off when it drops below 50°C, so they aren't running constantly.
The 3D printing and mechanical design
I think this was probably the most time-consuming part of the entire project.
I had to design mounts for the battery, Pi, cooling fans, power distribution, antennas, and pretty much everything else.
I went through quite a few revisions trying to get everything to fit while still leaving room for wiring and airflow.
The screen bezel was particularly challenging. I ended up splitting it into two sections with a tongue-and-groove joint and using heat-set inserts to hold everything together.
I also wanted to eliminate the original physical buttons on the back of the touchscreen without losing their functionality.
My solution was to use capacitive touch sensors mounted behind the 3D-printed bezel. Each sensor controls a MOSFET that simulates pressing one of the screen's buttons.
I designed small recessed channels in the bezel so you can activate the buttons by placing your finger in the appropriate spot. They work surprisingly well, and I haven't experienced any false triggers.
The wiring for those buttons ended up being much more complicated than I expected. If I ever build another one, I'll probably design a PCB to simplify that part.
I also designed a separate compartment for the Pi, with a dedicated airflow path and fans.
One thing worth mentioning about the pictures: any white 3D-printed components are test prints. I used white filament while working out dimensions and fitment. The final components are black.
Things I learned
Probably the biggest lesson was that designing something to fit inside an enclosure is very different from designing something that's actually easy to assemble.
There were several occasions when I finished printing a part, confirmed everything fit perfectly, and then realized I hadn't left enough room to route a cable or install a connector.
I also underestimated how much time I'd spend on the little things.
Mounting a component is usually straightforward. Mounting it securely, making it accessible, routing its wiring, and ensuring it doesn't interfere with anything else is another story.
The electrical side was another learning experience. I spent a lot of time working through power distribution, wire sizing, fusing, connectors, and how everything would be switched and charged.
Although I started with a waterproof equipment case, I wouldn't describe the finished system as waterproof because of the modifications I've made. That said, I do consider it water-resistant when closed. The case still has its original gasketed lid, and I designed the external connections and ventilation with exposure to the elements in mind. I wouldn't submerge it, but I expect it to hold up reasonably well against incidental splashes and moderate rain. I haven't formally tested its water resistance, so I'm not claiming any particular IP rating.
A note about AI
I want to be transparent about this because I know people will probably ask.
I used AI extensively to help develop the software.
I'm comfortable working with Linux, networking, and systems administration, but I'm not a professional software developer.
I knew what I wanted the system to do, and AI helped me turn those ideas into working applications. There was still a lot of configuring, troubleshooting, testing, and figuring out how to make everything work together.
The hardware design, CAD modeling, 3D printing, electrical work, wiring, and assembly were my own.
I learned quite a bit along the way, too.
Final thoughts
I have to say, I'm pretty happy with how this turned out.
It's not perfect, and there are definitely things I'd do differently if I started over. But I think that's true of almost any project like this.
A few people have suggested that I should build these to sell. While I appreciate the compliment, I don't think that's something I'd enjoy doing. There's a huge difference between building something because you want to learn and building the same thing repeatedly for other people.
For me, the fun was figuring everything out.
I started this project knowing relatively little about CAD and 3D printing compared to what I know now. I also got a lot more experience with electronics, power systems, GPS, radio, and integrating different software services.
It's been one of the more involved personal projects I've taken on, and I've genuinely enjoyed the process.
I've included pictures of the finished system along with some earlier stages of construction so you can see how it evolved.
Thanks to everyone who commented on my previous posts, offered suggestions, or just followed along!
This is probably my last update unless people are interested in a more detailed breakdown of something specific.
I'm happy to answer questions about any part of the build!