2014 RAM 1500 Carputer + Off-Grid Mesh + Home RAG
Complete Master Build Document โ June 2026 (rev. 3.44)
**Deliverables โ dropzone
/carputer/: a multi-page website atsite/index.html(sidebar nav, one page per section, every wire diagram on its own page with pan/zoom) โ auto-rebuilt on every doc/diagram commit** via thepost-commithook (build_site.py) โ plus the raw.mdand the individual diagram PDFs (full-wiring-1..7,full-wiring-ALL, the switch/media sheets).
โ ARCHITECTURE OVERRIDE (rev. 3 โ current decision)
The carputer brain is the Dell OptiPlex 5080 Micro (i7-10700T, 16GB DDR4 as-bought โ 32GB recommended, 256GB NVMe), installed IN THE TRUCK 24/7. It is the boss: orchestrator, local LLM (Ollama, small models), voice (whisper.cpp + Piper), RAG, CAN, Flask/WebSocket UI, and the local-vs-Fireworks router. Heavy LLM reasoning offloads to the Fireworks API (cloud), not to local big-GPU hardware.
- The HP Z440 is SHELVED / out of scope. Wherever this document says "Z440," read it as the OptiPlex 5080 for the carputer role, or ignore it. The Z440 is not part of the current build and is not to be planned around.
- No big local GPU. The OptiPlex is CPU-only. Small local models (1โ4B) run on it; anything heavier goes to Fireworks.
- Cameras, Phase 1: recorded + live-viewed on the OptiPlex only while it is awake. There is no 24/7 parked recording in Phase 1. While parked, the OptiPlex hibernates (~2โ5W on 5VSB for WOL) and the ESP32 layer detects what it can (motion/door/vibration/blinker) and wakes the OptiPlex via WOL on an alert.
- Pi 5 + Hailo-8L is a ~1-year-out upgrade. When added, it becomes the always-on camera appliance (record + restream + detection), closing the parked-recording gap; the OptiPlex then stops touching video and is a pure brain.
Everything below predates this decision; this banner takes precedence on any conflict.
โก POWER ARCHITECTURE (rev. 3 โ 12V, settled)
System voltage: 12V. Settled. EPEVER TracerAN is 12V/24V-only (no 48V) โ confirmed. The 48V golf-cart bank is unused for this build.
- Charging: 400W solar โ EPEVER 30A MPPT, + 40A 12Vโ12V DC-DC charger (alternator, ignition-sensed, isolates the starting battery). DC-DC is the one missing purchase.
- Battery banks (all 12V, paralleled):
- Core capacity: FEENCE 100Ah (owned) + a capacity-add. rev 3.7: reconsidering "+2nd 100Ah" โ a single large 12V LiFePO4 (300-440Ah); rev 3.37 SIZED UP to ~7 kWh overland (2ร ~300Ah or 1ร 560Ah) โ better $/kWh, fewer parts (see ยง5.8 for current candidates + the buy-now-2026 rationale). โ ๏ธ Mount a big pack COOL (cab/bed), NOT under-hood โ engine-bay heat shortens LiFePO4 life, and no cheap LiFePO4 charges below 0ยฐC (BMS blocks it โ plan for PNW/BC winters).
- Overland/bed bank (later, REMOVABLE): quick-disconnect (Anderson SB), own fuse + disconnect, for extended dry camping. A single large pack can fill much of this role too โ tradeoff is one-big-unit (better $/kWh, single point of failure) vs distributed (redundant, the removable concept).
- Load reality (Z440 gone): Phase-1 awake load โ 100โ120W (OptiPlex ~80W via 12Vโ19V DC converter + ESP32 + CAN + a few cams). Parked: S3 suspend ~1-3W, S4 hibernate ~0.5-2W, deep-storage 0W (ESP32 hard-cut). One 100Ah + 400W solar rides parked for days. The big banks are for overland house power, not for feeding the carputer.
- OptiPlex power path (rev 3.5 โ DECIDED): run the OptiPlex on a 12Vโ19V DC-DC converter (~$73), NOT the inverter. An 800W inverter idles at ~6-20W with no load โ that idle would swamp the S3/S4 sleep savings (a 1-3W S3 becomes ~10-23W). A DC converter idles ~0.5-2W, so the sleep ladder's numbers are real. Side effect: nothing else needs 120V AC โ the OptiPlex no longer depends on the inverter.
- Inverter: WZRELB 800W/1600W pure sine โ now out of the OptiPlex power path; kept only as general camp/tool AC if wanted.
Base Vehicle: 2014 RAM 1500 Crew Cab โ 5.7L Hemi (rebuilt: FRP Hellfire 2.0 VVT cam, PAC 1275X springs, Vararam intake, 87-octane tune), ZF 8HP70 transmission (rebuilt), 4WD, 3.92 gears, MDS deleted
Drive profiles / mode switching โ findings (rev 3.42): researched whether the truck can do switchable perf/tow/economy drive modes.
- โ No live tune-switching on a gas RAM. HP Tuners SOTF (Switch on the Fly) is diesel-only (GM Duramax L5P/L5D, Dodge Cummins CM2350/CM2450, Ford 6.0 PowerStroke) โ not offered for any gas Chrysler/Dodge/RAM. No gas programmer switches tunes while driving; the factory "Drive Mode selector" experience needs a diesel or a newer drive-mode truck.
- โ Switchable = flash-between only. Store custom econ/tow/perf tunes (the tuner), re-flash the one you want (key-cycle, ~5โ15 min, engine off); MPVI3 flashes standalone, no laptop. 2014 needs NO PCM unlock (that's a 2015+ requirement) โ the easy year.
- Is frequent flashing bad? Flash-memory wear = non-issue (thousands-of-writes rated). Real downsides: (1) each flash has a small brick risk if voltage sags / it's interrupted โ always flash with a battery maintainer on, engine off; risk is cumulative with flash count. (2) Each flash resets trans/fuel adaptives โ relearn restarts (this is why the gear-hunting eased over ~600 mi) โ constant flashing = the trans never settles. (3) Slow. No per-flash cost (HP Tuners licenses the VIN; re-flashing the licensed truck is free/unlimited). โ Verdict: occasional flashing (tow tune for a towing weekend) is fine + intended; daily mode-flipping is impractical/ill-advised.
- Live levers that DO exist: factory Tow/Haul (trans behavior, live) + optional Pedal Commander (throttle feel, live โ the only true live "mode"). Handheld canned-tune programmers (Diablo/Edge/Underground/Livernois) are out โ their tunes aren't built for the Hellfire cam.
- Carputer role: profile dashboard + reminders ("flash the tow tune before hooking up") + swap the dash per context + drive the Pedal Commander mode + read Tow/Haul/throttle/AFR. It cannot switch tunes (nothing can, live, on a gas RAM).
- Recommended setup: one strong daily tune + a dedicated tow tune (flash for tow trips) + Tow/Haul + optional Pedal Commander for live throttle feel.
Sections
- 0. THE BINDING CONSTRAINT โ READ THIS FIRST
- 1. PROJECT OVERVIEW
- 2. HARDWARE โ ALREADY OWNED (No Cost)
- 3. CARPUTER โ HARDWARE TO PURCHASE
- 4. SYSTEM ARCHITECTURE โ THREE TIERS
- 5. POWER ARCHITECTURE (the keystone)
- 6. ESP32 NODE NETWORK (Tier 0)
- 7. CAMERA SYSTEM + NVR
- 8. CAN BUS INTEGRATION
- 9. SOFTWARE STACK
- 10. THERMAL MANAGEMENT
- 11. HOME RAG SERVER (HP Z440 #1)
- 12. OFF-GRID MESH + REMOTE ACCESS (Phase 2/3)
- 13. PENDING ACTIONS
- 14. PHASED ROADMAP
- 15. COST SUMMARY
- 16. ARCHITECTURE AT A GLANCE
- 17. MASTER PARTS LIST (BOM) (rev 3.43)
Wire Diagrams
Each opens on its own page with pan/zoom (mouse-wheel or pinch to zoom, drag to pan, or the buttons).
- Two-cluster architecture (Option B): FRONT + BED boards
- Full Wiring 1 โ Power: generation, storage & heavy runs
- Full Wiring 2 โ FRONT computer fuse/relay box (pin-level)
- Full Wiring 3 โ FRONT-board I/O + RS485 panel
- Full Wiring 4 โ Network & PoE
- Full Wiring 5 โ OptiPlex 5080: power, USB, audio, CAN, displays
- Full Wiring 6 โ Bed-battery combiner (BED board + DC Monitor)
- Stateful illuminated switch (momentary + independent LED)
- 2-switch panel โ DMWD momentary halo-LED on Modbus IO
- Lighted switch + separate state-indicator LED (ESP32-S3 master โ Modbus sub)
- How many switches per Cat5 โ conductor budget + how to scale (3 direct / 8 via module)
- FULL physical wiring โ 3-switch panel, every wire + connector (dash โ Cat5 โ controller)
- Displays & media routing โ 5080 as media hub
- Control wiring โ Option B (dual board) โ DECIDED
- Control wiring โ Option A (1 board + Modbus) โ alternative
- Sheet 2 (rev 3.10) โ control & loads
- Power wiring (early sheet)
- Power & fuses (early sheet)