-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
2022 Tesla Model 3 LR Projector to Matrix headlight retrofit
- Thread starter GoPowerup
- Start date
Technically I was using PROC_ICE_X_SAFE_SET-VEHICLE-CONFIG. We did have access in that the command does work for a very limited set of options with the tbx-external or whatever our access is called. But additional options require additional levels of access.
The other strategy I assume is to get onto the car's main network and get shell access right into the gateway itself. But easier said than done obviously.
Nintendo80
Member
Is not I agree, but we still can not change it (headlight global no global) with the available toolbox.
I presume Tesla has a mothership database that tracks all the options and features of each vehicle delivered. Curiously, even if one manages to change the headlamp type on the car, will this create a conflict with or cause the mothership to command the car to roll back the changes during service or firmware/feature updates?
yes, toolbox only lets you change 3 options: wheel type, tow package and ecall.
But that has nothing to do with secured configs. you can freely change a lot of other stuff taking directly to the gateway.
The "signed config" you described is only required for relatively few options like vin, level of autopilot purchased and other such usually paid features (though rear heated seats is surprisingly not in that list)
That's what a tesla mobile guy told me, he can change it, but if it's not from engineers then it will be shortly reverted as the changes are not in the mothership.
Tesla does not revert this kind of hw changes.
Sure doesn't. I have had rear fogs enabled for a while now. No issues after many updates..
Just for info, we can change any values in gateway like country code, autopoit, tailights, headlamps, premium connectivity etc..., and block reverse by bot mothership. No need root acces for it.
And how do we change it when we can’t do it through toolbox? As when changing an id apart from tow package or home link we get an error unauthorised…
emptyspaces
Member
I'm interested in doing this, does it require changing the vehicle region or just enabling the specific option? I have had them on other euro cars and I live in a climate where I feel they should be required on all vehicles due to snow/fog.
Ditto. I'd like to learn more about this.
Created an account to thank you and @verygreen for all you have done so far. I've been digging around primarily so I can enable passenger lumbar on my 2023 MY. It would be nice to be able to make this simple config change without needing to fork over $500.
I guess I've been sleeping. So the 2023 MYs have lumbar motors in the passenger seat, but not enabled and of course with switch missing? Once enabled, how is it controlled? Touchscreen?
No, it's retrofitted in with 2 parts that can be ordered from Tesla. I haven't actually done the retrofit yet until I confirm the gateway is set to enable passenger lumbar on the respective ECU. You can actually install the parts, but as long as the Tesla is configured to driver only lumbar, the passenger com bus will be disabled and the controls won't work.
Thank you.
. In theory, having someone with Toolbox issue [ {"configid":32,"data":"01"} ], should re-enable the passenger side, and if you then install parts 1118494-00-G and 1098530-00-F, you should have working passenger lumbar.I tried this with the latest version of toolbox 3 on my account and it sadly said the change was unauthorized by my account level. I have a 2019 sr+ I am trying to make several small gateway changes to, like adding pws speaker etc., and none of those changes it takes even if I try this way above. Has anyone been able to successfully issue any gateway change command that isn't listed as changeable by the tesla 3 toolbox dashboard? I even went as far as reverse engineering how they are sending commands from toolbox 3 scripts to odin via a secured web socket. I was able to send odin a command I crafted with the same token I captured from my computer even, however it validates your access level by the tokenv2 that's sent, so changing things "unauthorized" is still blocked. I've been poking around for a way to get access to the gateway directly, but have been met with the firewall on the driver side diag port obviously. I've heard something about broadReach ethernet on the tuner side being the way in to talk to the gateway directly, but unsure how people are authenticating even with it. I have a broadR reach adapter so I plan to poke around on that, but have heard the mcu needs to be in recovery mode first. If anyone has any info on this stuff, or has made any progress on it, feel free to pm me.Thank you.
Similar threads
