Running Tesla Model 3's computer on my desk using parts from crashed cars
David Schütz embarked on an impressive quest to run a Tesla Model 3's computer on his desk, salvaging parts from crashed cars. This detailed hardware hacking journey, from identifying obscure connectors to resurrecting a fried board, captivated Hacker News. The story resonated deeply with the community's appreciation for reverse engineering, open documentation, and the intricate dance between software and complex physical systems.
The Lowdown
The article details a fascinating journey into hardware hacking, where the author, David Schütz, successfully powered up a Tesla Model 3's Media Control Unit (MCU) and autopilot computer (AP) on his desk using salvaged parts. Motivated by Tesla's bug bounty program, which required direct hardware access, Schütz pieced together the necessary components and overcame several significant challenges to bring the complex system to life outside a car.
Key steps and challenges included:
- Part Acquisition: Sourcing an MCU, a touchscreen, and a power supply from eBay, often from salvaged crashed cars.
- Wiring Woes: Identifying the correct 12V and ground pins for power, and then struggling to find the proprietary Rosenberger 6-pin cable connecting the MCU to the display. Generic "LVDS" cables proved incompatible.
- Documentation Discovery: Tesla's publicly available "Electrical Reference" proved invaluable for pinouts and part numbers, revealing the cable's part number and confirming it was part of a larger wiring harness.
- Hardware Mishap & Repair: An attempt to improvise a display cable led to a short circuit, burning out a power controller chip on the MCU. With the help of a friend, the specific chip was identified and replaced by a PCB repair shop, saving the project.
- The Loom Solution: The only way to obtain the specific display cable was to purchase an entire dashboard wiring harness (a "loom"), a bulky and unexpected expense.
- First Boot: Upon connecting the loom, the system successfully booted, displaying the car's operating system on the touchscreen.
- Network Exploration: Initial investigation revealed an exposed SSH server (requiring signed keys) and a REST-like API (ODIN) used by Tesla's diagnostic tools.
The project highlights the determination required for deep hardware research and reverse engineering. With the system now operational, the author plans further exploration into the UI, network interfaces, CAN buses, and firmware extraction, paving the way for potential bug bounty discoveries.
The Gossip
Hacking Hardware for Hands-on Hilarity
Many commenters lauded the author's ingenuity and persistence in getting the Tesla computer running on a desk. They shared similar experiences with automotive tinkering and hacking, expressing admiration for the detailed problem-solving involved, from power supply challenges to intricate wiring. The spirit of open exploration and the satisfaction of understanding complex systems were central to this appreciative discussion.
Tesla's Transparent or Tense Terms?
A significant portion of the discussion revolved around Tesla's "Root Access Program" within its bug bounty, which offers permanent SSH certificates for researchers who find rooting vulnerabilities. Commenters debated whether this policy strikes a good balance between security and research, or if root access should be a standard right for car owners. The broader topic of right-to-repair for vehicles, the availability (or historical unavailability) of Tesla's service manuals, and the potential implications of owner-modified software on safety and liability were also hot topics.
Circuitry Conundrums & Connector Confusion
The article's detailed account of electrical challenges sparked numerous discussions about automotive hardware specificities. Commenters delved into the nuances of automotive power systems (e.g., nominal 12V vs. actual 14.4V charging voltage and transients), the evolution and usage of LVDS in various applications, and the surprisingly elusive nature of specific automotive connectors. The author's eventual need to buy an entire wiring harness ("loom" or "harness") was a particularly salient point, leading to discussions about industry practices and terminology.
Specialist Scrutiny & Cross-Disciplinary Complexities
The author's surprise at discovering the necessity of a wiring harness, rather than individual cables, sparked a meta-discussion about domain expertise. Commenters debated the tendency for professionals, particularly software engineers, to underestimate the complexities of fields outside their primary specialization. This led to a humorous yet pointed exchange about the "reality has a surprising amount of detail" phenomenon and how tools like LLMs might influence cross-disciplinary understanding.