Running Tesla Model 3 Computer on Desk with Salvaged Parts
Hardware Setup from Salvaged Parts
A researcher needed Tesla hardware for bug bounty research and sourced components from crashed vehicles. The Tesla Model 3 computer consists of two parts: the MCU (Media Control Unit) and the autopilot computer (AP) layered together. The unit is iPad-sized, about as thick as a 500-page book, and comes in a water-cooled metal casing.
Searching for "Tesla Model 3 MCU" on eBay revealed multiple listings in the $200-$300 range from salvaging companies that dismantle crashed cars. These sellers often include photos of the original vehicle and allow filtering for parts from the same car.
Required Components
- DC power supply: Adjustable 0-30V model, 10A version recommended (the setup can consume up to 8A at peak)
- Touchscreen module: From salvaged Model 3, found for $175 on eBay
- Display cable: 6-pin cable with Rosenberger 99K10D-1D5A5-D connector (2 pins for 12V/ground, 4 for data)
The cable proved difficult to source individually. Tesla publishes wiring "Electrical Reference" documents publicly on their service website, showing exact pin configurations. The researcher discovered the cable is similar to LVDS cables used in BMW vehicles and ordered a compatible version.
Powering Up and Network Access
Using Tesla schematics and online references, the researcher identified the correct pins for 12V and ground on the computer's cut cables. After attaching power supply clips to the stripped wires, red LEDs began flashing and the computer started.
Without a screen, interaction was limited. The researcher connected an Ethernet cable to the port next to the power connector. The car's internal network lacks DHCP, requiring manual IP configuration: 192.168.90.X/24 with X higher than 105 to avoid conflicts.
Internal Network Details
From an older /etc/hosts file found on Reddit:
- 192.168.90.100 cid ice # mcu
- 192.168.90.102 gw # gateway
- 192.168.90.103 ap ape # autopilot
- 192.168.90.105 ap-b ape-b # also autopilot
- 192.168.90.60 modem # has the ftp server
SSH on port 22 and a webserver on port 8080 were open on 192.168.90.100 (the MCU), confirmed to still be accessible on newer models.
📖 Read the full source: HN AI Agents
👀 See Also
OpenClaw Agent Pipeline Used to Write and Publish Three AI Novels in a Week
A developer used OpenClaw to create a four-agent workflow that wrote, edited, and published three complete novels to Amazon KDP in seven days. The pipeline included specialized agents for writing, editing, marketing, and orchestration.
Running a 6-agent behavioral coaching pipeline on self-hosted Qwen3 235B with vLLM
A developer built a 6-agent cognitive pipeline for behavioral coaching running entirely on self-hosted Qwen3 via vLLM, using Qwen3 30B on 2x RTX 4090s for development and Qwen3 235B on RunPod A40 pods for production.
OpenClaw setup on 8-year-old Raspberry Pi with $0 spent
A developer successfully set up OpenClaw on an old Raspberry Pi 4 with 8GB RAM, running 24/7 for three weeks with minimal costs. The setup includes basic skills like ClawHub, Notion, GOG, local Whisper, and Nano Banana, plus a human-like memory system and five agents.
Direct Mobile Document Ingestion to OpenClaw: iOS to Raspberry Pi Health Workflow
A developer shares an architecture for pushing documents directly from an iOS mobile client to a local OpenClaw instance on a Raspberry Pi, using QR-based pairing and dedicated endpoints for health record processing.