Let the hacking begin... (Model S parts on the bench)

That makes a lot of sense then, thanks. I'm still wondering what, if any, difference the MCU itself has that would require a different part number for the premium audio version then.

I'm half expecting a caravan of black Model X to descend upon my house any minute now... lol. Well, really, there isn't much they can say about it. I'm not violating any laws or contracts by doing things with these parts and hardware that I legally own. So, ideally, Tesla will just leave me alone, but I wouldn't be surprised if they say something.

 

I only have the CAN bus connected between the MCU and the IC currently. I'm working on getting some CAN sniffers/injectors setup now for that bus and the other *four* (five total) CAN buses on this car. Probably will be a few days before I actually have time to tinker with all of the CAN stuff.

Not sure what you mean by "the servo controller." There appear to be five CAN bus connections and some LIN connections on the MCU. The LIN stuff looks to work for homelink, the seat heaters, the electrochromatic mirror dimmers, and some 12V battery monitoring system I'm unsure about.

- - - Updated - - -

*shrugs*

I don't feel like I'm obligated to notify Tesla of anything at all, honestly. If they provided me with the hardware and such to tinker with, and maybe even some additional info and insight to make the job easier, then sure, they would be the first to know of anything I come up with. But I purchased the hardware I'm working with myself and I'm doing so basically blind to the inner workings. Also, considering pretty much anything I do here is going to involve some form of hardware hack and not something that some random person is going to be able to do to some random Model S to cause any issues... honestly, I'll probably just post my findings here and be done with it. If Tesla wants to follow along, they're more than welcome to just like anyone else. I'll gladly entertain their questions/comments/concerns.

- - - Updated - - -

Yeah, I was honestly thinking the same thing when I came up with the initial idea. Would require a switch of some kind to toggle between the rearview cam and the connected HDMI device, though, which would likely have three settings: Rear, Aux, Auto... where auto would default to the rear cam when nothing was connected to the aux HDMI.

Honestly, this will probably be the easiest part once I get a hold of a rear cam to play with...

 

That's probably possible too. Once I nail down the rear cam communication that would be a logical next step. Anyone have a spare rear cam?

 

Yeah, this is from a pre-autopilot car (not too far behind really) that is still on v6.1.

The Line outs are in shielded wire in their own 20 pin connector on the back of the MCU. No RCAs, although that would've been nice.

XM/AM/FM appear to come from a separate radio module. There are left and right line inputs (in another harness) that come from that module (I don't have it) along with line inputs from driver and passenger microphones.

 

So, I'm toying with CAN data on the powertrain bus. Funny enough if I play back CAN logs to the bench setup I get speed readout, a broken power meter (it seems offset by something like -300 kW and stays pegged on beyond full regen), and my energy usage graph updates, rated miles show, etc.

Up to 13 errors on the display though... lol.

I think the most interesting part is that the odometer on the IC and the trip meters are incrementing as I play the drive data...