2. HARDWARE — ALREADY OWNED (No Cost)
Compute / Storage
| Item | Specs | Role |
|---|---|---|
| Dell OptiPlex 5080 Micro | i7-10700T (8c/16t), 16GB DDR4 as-bought (1 slot used, 64GB max → upgrade to 32GB), 256GB NVMe — Linux Mint 22.3 | Carputer brain (in truck 24/7) — orchestrator, local LLM, voice, RAG, CAN, UI |
| HP Z440 #1 / #2 | E5-1630 v3, 32GB ECC, K4200 | SHELVED — out of scope (see rev. 3 banner) |
| Dell Precision 5820 | Xeon W-2265 (12c), 64GB, RTX A4000 16GB + A5000 24GB | Primary workstation (unchanged) |
| TerraMaster F4-424 Pro | Celeron N5105, ~8TB RAID5, 2×250GB NVMe cache, 2.5GbE, Docker | Document storage |
| Samsung S24 Ultra | — | Personal phone / dev tool / truck-control screen (PWA — see §4.5) |
| GreenYi tailgate backup cam | AHD, dynamic guidelines, IP68 | Already installed — reverse view |
| Raspberry Pi 3 B+ | quad 1.4GHz, 1GB, USB-2 100Mbit NIC — Linux | OWNED. Always-on tier: MQTT broker + wake-coordinator + status/control PWA + telemetry log + Wolfbox pull + Tailscale. Pi 4 upgrade = FUTURE (see §4.4) |
| ESP32 WROOM-32 | dual-core 240MHz, WiFi+BT | OWNED. Demoted (rev 3.4) to optional fault-isolation reserve — "the second board" only if the single Waveshare can't hit 100% (see §6) |
| Cudy LT18 4G LTE router | Cat 18, WiFi 6, OpenWrt | OWNED (rev 3.4 — was on the buy list). Truck internet + LAN router + WiFi; likely also the Tailscale subnet router (verify opkg/flash) → may replace the GL.iNet entirely (see §4.1) |
Power / Solar (ALREADY OWNED — confirmed from prior chat)
| Item | Specs | Role |
|---|---|---|
| Newpowa/mono 100W 12V panels ×4 | 400W total | Solar charging (confirmed) |
| EPEVER 30A MPPT (TracerAN, ASIN B081GQSZLM) | 12V/24V ONLY — no 48V (CONFIRMED), max PV 100V, + BLE adapter | Charge control. System is 12V, settled. |
| FEENCE 12V 100Ah LiFePO4 | 100A BMS, 1,280 Wh (12.8V×100Ah nominal), 4S/8P capable | House battery #1 (owned). Charge: 14.4V abs / 13.6V float / 11.0V LVD |
| 48V 100Ah LiFePO4 golf cart kit | 200A BMS + charger, 4,800 Wh | ⛔ UNUSED in this build — system is 12V (settled, see power banner / §5.5). Kept for an unrelated future use. |
| WZRELB 800W pure sine inverter | 12V→120V | AC for the OptiPlex (runs <10% load) |
| Ampeak 400W inverter | 12V→110V | Small/spare |
| WonVon 100A Bluetooth shunt | Battery monitor | Power telemetry |
| 12V→19V 10A DC converter | 190W, boost | OWNED. Powers the OptiPlex (hardwire, §5.9). 19V in tolerance (Dell spec 19.5V) |
| Wiring kit | MC4, Y-parallel, 10AWG 50ft, 40A PV breaker, crimpers | Install |
This existing solar gear is most of the power infrastructure the carputer needs. Only a DC-DC charger is missing (see §5).
Other owned
| Item | Specs | Role |
|---|---|---|
| 12,000 lb winch | ~400-460A at rated line pull | OWNED — OUT OF SCOPE for the carputer. Lives on its OWN heavy circuit off the starting battery with its own contactor; NEVER on the house bank or any carputer relay. The DC-DC isolation means a 400A pull won't brown out the carputer (house side). No telemetry/integration planned (monitor-only judged low-value). Inventory note only. |
Tools & Diagnostics (ALREADY OWNED — rev 3.38)
| Item | Specs | Role |
|---|---|---|
| OBDLink MX+ | BT OBD2 scanner (iOS/Android/Windows), STN chip, all 5 OBD2 protocols + MS-CAN | Diagnostics / PID verification. Best-in-class BT adapter. On the 2014 RAM (Mopar/FCA) it pairs with AlfaOBD for deep per-module diagnostics, actuator tests, read/clear codes — and OBD Fusion/Torque for live PIDs. NOT the raw-CAN discovery tool (that stays the SH-C31G/Canable, §8); use it for guided diagnostics + confirming which PIDs the truck answers before writing can_reader.py decoders. |
| OBDLink EX | USB (wired) OBD adapter, STN chip | Wired OBD interface. Marketed for FORScan — that's Ford/Mazda, so the FORScan use does NOT apply to the RAM. Its value here = a rock-stable wired OBD link for AlfaOBD/OBD-app diagnostics on the OptiPlex/Windows, and a fallback to the MX+. Raw CAN discovery still on the SH-C31G. |
| HiLetgo USB Logic Analyzer | 24MHz, 8-ch, UART/I²C/SPI, sigrok/PulseView | Bench debug for the ESP32 / Modbus / RS485 work (§6). Capture the ESP32↔Modbus RS485 comms (TTL side), the TCA9554 I²C, SPI. ⚠️ Input −0.5 to 5.25V only → probe 3.3/5V TTL signals and the TTL side of the RS485 transceiver, NEVER the differential A/B pair or any 12V vehicle line (will fry it). |
| ANCEL BM200 | 12V BT battery monitor; cranking + charging-system test; 70-day history (logs every 2 min); IP67; ~1.5mA draw; 4-device app | Starter-side battery health. Mount on the STARTER / lead-acid winch-buffer battery — covers cranking strength + alternator-charging health + abnormal-voltage alerts, which the WonVon shunt (house bank) and DC Monitor (LiFePO4 banks) don't. BT-app only (not wired into the carputer); a weak-starter alert here is the no-start early warning. |
| HP Tuners MPVI3 + VCM Suite | OBDII tuning interface — BT 5.0, USB-C, standalone logging, hi-res accelerometer, Pro Feature Set; 6 credits on the device; Stellantis (Dodge/RAM) supported | ECU tuning + pro scanning/logging — the tool behind the truck's existing 87-octane tune (§1). ⚠️ VCM Suite is Windows-ONLY → run on the Dell Precision 5820, NOT the Linux OptiPlex (see software note). MPVI3 also does laptop-free standalone logging + Android TDN tune delivery. Keep tuning (occasional, Windows) separate from the carputer's live-CAN read (always-on, Linux, §8). |
Owned diagnostic / tuning software (rev 3.39):
- HP Tuners VCM Suite (VCM Scanner + Editor) — Windows-only, runs on the Precision 5820. No Linux build (it's .NET; HP Tuners hasn't announced one, and Wine is unsupported + unreliable for USB flashing — don't plan on it on the OptiPlex). The in-truck Linux box doesn't need it: its CAN role is live read via SH-C31G/python-can, not flashing.
- AlfaOBD (Android) — Stellantis/FCA dealer-level diagnostics + config (lights, locks, TPMS, key programming, actuator tests, read/clear module codes). Pairs with the owned OBDLink MX+/EX. ✅ 2014 RAM = pre-2018 = NO security gateway (SGW) → full access, no bypass needed. This is the "AlfaOBD" referenced in §8.
- Torque Pro (Android) — lightweight OBD2 PID/gauge/DTC app for quick live data; powertrain PIDs only, no bi-directional/module access (that's AlfaOBD's job).