I'm actually somewhat surprised the OS fully boots when it's not connected to the expected vehicle peripherals
Running Tesla Model 3's computer on my desk using parts from crashed cars
131–140 of 356 posts
Re: Running Tesla Model 3's computer on my desk using parts from crashed cars
#132From the article > Tesla offers a “Root access program” on their bug bounty program. Researchers who find at least one valid “rooting” vulnerability will receive a permanent SSH certificate for their own car, allowing them to log in as root and continue their research further. Pretty interesting. Sounds like Apple's Security Research Device Program[0], where you're loaned a rooted iPhone, but with a clear qualificati…
If they don't give root, researcher may have incentive to keep vuln secret for root access. Looks reasonable.
Re: Running Tesla Model 3's computer on my desk using parts from crashed cars
#133> Turns out that actual cars don’t have individual cables. Instead they have these big “looms”, which bundle many cables from a nearby area into a single harness. This is the reason why I could not find the individual cable earlier. They simply don’t manufacture it. I was really surprised to read this at the end of the article -- how could someone be this deep into a project of this depth and not realize this?! Not o…
I'm sure you're an expert, pro at everything.
I wasn’t criticizing them.
Re: Running Tesla Model 3's computer on my desk using parts from crashed cars
#134I used to work for a company that made third party scan tools. We had racks of ecus disconnected from the car with just a diagnostic connector and power. nothing got to a real car without first trying it on the rack. I remember on time we figured out a bmw (pre obdii) had the bytes offset from the standard documentation (it was a semi-standard protocol that some other cars used at the time), we went from we communica…
I spent the last week successfully reverse engineering my car / various scan tools to get the right information to diagnose a fuel pump problem (and to do so without the incredible awkwardness of many of the tools) It's pretty amazing what Claude + Ghidra + knowledgable coaching can accomplish. It was basically just setting direction, setting up an incremental workflow with the right kind of documentation, and questi…
Just dump it in a gist. That your of knowledge should be free
Re: Running Tesla Model 3's computer on my desk using parts from crashed cars
#135Earlier quoted context omitted.
In Canada we generally call it the sleeve, or the wrap.
I'd understand either of those, but I'd go with "tubing" https://www.3m.com/3M/en_US/p/c/electrical/wire-cable/tubing...
That's heat shrink tubing, but we're talking about one of these:
[1]: https://www.holley.com/products/engine/engine_dress_up/hoses... [2]: https://www.oreillyauto.com/detail/c/dorman-conduct-tite/lig...
Re: Running Tesla Model 3's computer on my desk using parts from crashed cars
#136It's funny how the biggest problem turned out to be a mostly mechanical part, the rather trivial 6-pin connector.
Given the presence of the wiring schematics and the mechanical dimensions, I'm surprised that the author did not try to 3D-print the mechanical parts of the connectors, givem that the electrical parts extracted from the BMW connectors did fit.
Re: Running Tesla Model 3's computer on my desk using parts from crashed cars
#137From the article > Tesla offers a “Root access program” on their bug bounty program. Researchers who find at least one valid “rooting” vulnerability will receive a permanent SSH certificate for their own car, allowing them to log in as root and continue their research further. Pretty interesting. Sounds like Apple's Security Research Device Program[0], where you're loaned a rooted iPhone, but with a clear qualificati…
It's a mixed bag. This only applies to the infotainment system and not the autopilot computer.
They've also revoked certificates from researchers personal cars in the past
Re: Running Tesla Model 3's computer on my desk using parts from crashed cars
#138From the article > Tesla offers a “Root access program” on their bug bounty program. Researchers who find at least one valid “rooting” vulnerability will receive a permanent SSH certificate for their own car, allowing them to log in as root and continue their research further. Pretty interesting. Sounds like Apple's Security Research Device Program[0], where you're loaned a rooted iPhone, but with a clear qualificati…
> Researchers who find at least one valid “rooting” vulnerability will receive a permanent SSH certificate for their own car
It feels like this is something you should get by being owner of the car, and not have to do free speculative research for the manufacturer to get it.
Re: Running Tesla Model 3's computer on my desk using parts from crashed cars
#139Earlier quoted context omitted.
> Software people tend to overestimate their knowledge of other disciplines, writing it off as "easy" or work beneath them You should see what happens when someone involved in the sciences, e.g. Chemistry, gets their hands on Claude Code.
What happens?
They suddenly act as if Claude has awarded them with a second PhD in CS. Now they know everything and everything you tell them gets filtered through Claude.
It's like "software dude thinks he can do hardware", but on steroids. They don't know what they don't know and they think they have a panacea in their hands.
Don't you know? Software is beneath them and the fiddly bits are just standing in the way of them getting their BigImportantWork™ done.
Re: Running Tesla Model 3's computer on my desk using parts from crashed cars
#140I used to work for a company that made third party scan tools. We had racks of ecus disconnected from the car with just a diagnostic connector and power. nothing got to a real car without first trying it on the rack. I remember on time we figured out a bmw (pre obdii) had the bytes offset from the standard documentation (it was a semi-standard protocol that some other cars used at the time), we went from we communica…
That's super cool, I'm currently struggling with scan tools for a 1999 Mercedes E300 Turbodiesel. I had one that worked OK for about a decade (Autel something or other) with a 38pin connector, but it recently bricked itself with a message like "connect via USB to Updata" which I assume means its firmware somehow erased itself. Cannot figure out how to "updata" it, doesn't seem to connect via USB, the Autel software runs under Wine but doesn't appear to recognize the device... gave up and bought an iCarsoft device which sorta kinda works. It can talk to every module except for the ECU (Bosch MSA 25.1 I believe?) however if I tell the device that my car is a different model (1995-1997 naturally aspirated) I can blindly clear ECU DTCs, which is good enough because this thing is barely more complicated than a toaster. All that is to say, this space is ripe for some open hardware/software love.