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

Developer builds simplified AI agent hosting for non-technical users
A developer created a tool that automatically handles AI agent hosting with private cloud instances, allowing non-technical users to connect via Telegram using their own API keys. The solution was built after failed attempts to walk a non-technical user through standard Docker-based setups.
QWEN3.6-27B-MLX-8bit Matches 122B for Local Workflows at 29.5GB
A user running multi-hour local workflows says QWEN3.6-27B-MLX-8bit (29.5GB) matched a 79GB model on orchestration, research, and writing — just slower — freeing 50GB of RAM.

Automate Jellyfin Media Downloads with OpenClaw: Fix Failures in Sonarr/Radarr Chain
A Reddit user adds OpenClaw to their Jellyseerr→Sonarr/Radarr→Prowlarr→qBittorrent chain to automatically troubleshoot and fix broken downloads, indexer issues, and metadata mismatches.
OpenClaw + Shopify: AI agents handle inbox, email, iMessage, and even product creation from photos
A user details setting up OpenClaw to handle Inbox, Email, and iMessage for order info, plus using Claude with Shopify CLI to perform any store action via text. A notable workflow: send a photo from iPhone, OpenClaw reads it and posts the product with all fields filled.