Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

Toolbox 3 Gateway Configuration Edit on Model 3 / Y?

This site may earn commission on affiliate links.

terranx

Active Member
Aug 29, 2019
3,596
5,018
USA
Anyone out there know how to do this? As best as I can tell, the menu the tesla techs use (something to the effect of dashboard -> infotainment -> vehicle configuration change) isn't present in the version of toolbox us mere mortals get access to. However, under actions, PROC_ICE_X_SAFE-SET-VEHICLE-CONFIGS is available. The parameters it accepts are ConfigParams (type List) and Configs Require Ice Reboot (presumably yes/no, true/false, 0/1, etc -- can be left blank though I believe).

1669580343186.png


From what I can tell digging through the app.f5d3cbaebb2ad903a936.js file, this action is what's invoked when making the gateway config changes the official way. I just can't figure out how to format the input. For example I'm trying to change id 32 to 01, and I've tried sending {32, 01} and many variants (with quotes, different brackets, etc), to no avail. I mostly get an error about not being to cast the input as a List.

Anyone out there know what to do or can help with some hints? I can share any other relevant info
 
  • Like
Reactions: WhiteM3P-
You could try setting 150 to 2 -- that's what sets the caliper color to red on the S/X. But my M3P has that set to 0, so it might just be something that's hardcoded on the model 3s

Code:
configid:
150 (cfg_calipercolortype)
data:
00 (UNKNOWN)
02 (RED)
Do any one successfully change this config to make the caliper color into red? I rent a toolbox today. seems like I have to use a windows laptop to downlow the Toolbox Proxy in order to connect to the proxy than running service shell. I am wondering if I successfully using the service shell am I need to use command `gw-diag SET_CONFIG_DATA 00 150 02` to change the configid 150 cfg_calipercolortype into 02 which is RED. But what does the 00 means after the SET_CONFIG_DATA.
 
  • Like
Reactions: WhiteM3P-
Upvote 0
Do any one successfully change this config to make the caliper color into red? I rent a toolbox today. seems like I have to use a windows laptop to downlow the Toolbox Proxy in order to connect to the proxy than running service shell. I am wondering if I successfully using the service shell am I need to use command `gw-diag SET_CONFIG_DATA 00 150 02` to change the configid 150 cfg_calipercolortype into 02 which is RED. But what does the 00 means after the SET_CONFIG_DATA.
I used that command to change the color for non performance vin cars. You need to reboot gateway for it to show up. And it still won't show in your phone app image.
 
  • Like
Reactions: Merchant Zhang
Upvote 0
I used that command to change the color for non performance vin cars. You need to reboot gateway for it to show up. And it still won't show in your phone app image.
You are correct. It only show on screen UI. I tried it today. And when I try this command first time it stuck. I try two times and car reboot and shows on screen. Do anyone know how to get all config id value though serivce shell?
 
Last edited:
  • Like
Reactions: PhilippDen
Upvote 0
You are correct. It only show on screen UI. I tried it today. And when I try this command first time it stuck. I try two times and car reboot and shows on screen. Do anyone know how to get all config id value though serivce shell?
I would also highly appreciate to know the command to see all config id including their active values :) would be very helpful, thanks to everyone for sharing all the details :)

So to do it with service shell, you'd have to check one by one which is a pain in the ass obviously. Command would be
Code:
gw-diag "GET_CONFIG_DATA 00 [configid]

Other ways:
use the "gw_read_configs" command and enter the following as the parameter
Code:
['0', '1', '2', '3', '4', '5', '6', '7', '8', '9', '10', '11', '12', '13', '14', '15', '16', '17', '18', '19', '20', '21', '22', '23', '24', '25', '26', '27', '28', '29', '30', '31', '32', '33', '34', '35', '36', '37', '38', '39', '40', '41', '42', '43', '44', '45', '46', '47', '48', '49', '50', '51', '52', '53', '54', '55', '56', '57', '58', '59', '60', '61', '62', '63', '64', '65', '66', '67', '68', '69', '70', '71', '72', '73', '74', '75', '76', '77', '78', '79', '80', '81', '82', '83', '84', '85', '86', '87', '88', '89', '90', '91', '92', '93', '94', '95', '96', '97', '98', '99', '100', '101', '102', '103', '104', '105', '106', '107', '108', '109', '110', '111', '112', '113', '114', '115', '116', '117', '118', '119', '120', '121', '122', '123', '124', '125', '126', '127', '128', '129', '130', '131', '132', '133', '134', '135', '136', '137', '138', '139', '140', '141', '142', '143', '144', '145', '146', '147', '148', '149', '150', '151', '152', '153', '154', '155', '156', '157', '158', '159', '160', '161', '162', '163', '164', '165', '166', '167', '168', '169', '170', '171', '172', '173', '174', '175', '176', '177', '178', '179', '180', '181', '182', '183', '184', '185', '186', '187', '188', '189', '190', '191', '192', '193', '194', '195', '196', '197', '198', '199', '200', '201', '202', '203', '204', '205', '206', '207', '208', '209', '210', '211', '212', '213', '214', '215', '216', '217', '218', '219', '220', '221', '222', '223', '224', '225', '226', '227', '228', '229', '230', '231', '232', '233', '234', '235', '236', '237', '238', '239', '240', '241', '242', '243', '244', '245', '246', '247', '248', '249', '250', '251', '252', '253', '254', '255']

That will dump every config. But the config ids won't be associated with the plain text definitions, that you'll have to figure out on your own.

Finally there's a log file stored in the gateway that you can read with toolbox. I think there's a command called "gw read file" or something to that effect. I think it was UDSDEBUG.LOG or MODINFO.LOG that had the info. Within that you can find something like the excerpt below

Code:
...
HPick 21:53:29.046::Config exteriorColor id=7, value=6 len=1
HPick 21:53:29.046::Config drivetrainType id=8, value=1 len=1
HPick 21:53:29.046::Config airSuspension id=9, value=2 len=1
HPick 21:53:29.046::Config epasType id=10, value=1 len=1
HPick 21:53:29.053::Config packEnergy id=14, value=3 len=1
HPick 21:53:29.053::Config devSecurityLevel id=15, value=3 len=1
HPick 21:53:29.054::Config restraintsHardwareType id=16, value=101 len=1
HPick 21:53:29.054::Config brakeHWType id=17, value=5 len=1
HPick 21:53:29.054::Config homelinkType id=18, value=1 len=1
HPick 21:53:29.054::Config rightHandDrive id=19, value=0 len=1
HPick 21:53:29.054::Config vdcType id=21, value=1 len=1
...

The caveat is that shows what each config was set to at the time of the last software install. So if you changed anything and didn't redeploy the software, that won't be reflected in the log. And for anything that's more than a single byte value, it will show an ASCII representation instead of the numerical values -- but you generally won't be messing with those anyway.

There might be a way of dumping the full list and all possible values from somewhere, but I haven't figured that out (and currently don't have an active toolbox subscription).
 
Upvote 0
As far I know there is cat command and we can basically cd like a linux computer (well its linux) meaning we just need someone (I can do but need to pay again for toolbox) to just go through every possible directory and just cat everything and thus find some or configs etc. its just a thing of time until we may find a unsecured config which allows something or ....
 
  • Like
Reactions: davidalindsey
Upvote 0
As far I know there is cat command and we can basically cd like a linux computer (well its linux) meaning we just need someone (I can do but need to pay again for toolbox) to just go through every possible directory and just cat everything and thus find some or configs etc. its just a thing of time until we may find a unsecured config which allows something or ....
Yeah I did play with that and read through some interesting files (but nothing groundbreaking). Some files require root access which we obviously don't have. And you also can't read any gateway files that way. The gwxfer command is supposedly present and should allow for transferring stuff to and from the gateway, but I couldn't get it to work using any of the known syntax.

If a few people want to split a month (or better yet, a year) of toolbox, I'd be game. But I know it's hard to trust internet strangers with that sort of money.
 
Upvote 0
Yeah I did play with that and read through some interesting files (but nothing groundbreaking). Some files require root access which we obviously don't have. And you also can't read any gateway files that way. The gwxfer command is supposedly present and should allow for transferring stuff to and from the gateway, but I couldn't get it to work using any of the known syntax.

If a few people want to split a month (or better yet, a year) of toolbox, I'd be game. But I know it's hard to trust internet strangers with that sort of money.
Also to be honest, even if someone found something I would not recommend sharing it here or somewhere else, because it would get patched within 0.1seconds from tesla as 99.99% someone from tesla is watching here and monitoring everything. Where I think maybe its a good idea to make like a closed community or something where people can share what they found and everything.
 
Upvote 0
I mean you could try setting the configs to the s/x values, but I highly doubt the model 3 software would see those as valid values
Yeah it would be pretty neat to have the UI show up as a yoke for M3.
But highly doubt it since they can't even get the 2.0 center console to show up in the UI.
I have that flag config for the 2.0 as it shows up in the app as 2.0.
Car is a 2018 M3P.
But I guess Tesla UI designers lazy to change the UI for air conditioning to show up as 2.0 console, lol
 

Attachments

  • 20240612_195311.jpg
    20240612_195311.jpg
    309 KB · Views: 7
  • Like
Reactions: WhiteM3P-
Upvote 0