The wheel size selector doesn't seem to work, choosing 19" doesn't show European Model S with Tempest 19"
Can you please post a link to a car that has these wheels? Thanks.
You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
The wheel size selector doesn't seem to work, choosing 19" doesn't show European Model S with Tempest 19"
On a related note, is there a reason why the configurator doesn't have an option for the 20" Cyberstream wheels for the Model X?
I did not see/notice the Option Code Lookup tool. Thanks for the pointer. I just tried it and got zero results. :-(Sure, PM me the VIN and I'll take a look. But if you enter it on the Option Code lookup page and it doesn't display, it's likely not in the database.
Also, didn't HW4 cars also eliminate the ultrasonic sensors?
There are several new options I need to add to the interface which I can get to later this week. Thanks for your support!
OK there's an easier way.I did not see/notice the Option Code Lookup tool. Thanks for the pointer. I just tried it and got zero results. :-(
Very cool. Unfortunately, it still isn't clear. Current listings for HW3 cars on EV-CPO show something like APH4 AP 3.0 under Autopilot. HW4 cars show something like AP04 AP 4.0. The trick outlined above doesn't return those values. A google search says that the APF2 code seen below refers to the fact that I've paid for FSD; it does not convey anything about the version number of the hardware. It is also odd that it is saying the vehicle is a Plaid, when it isn't.OK there's an easier way.
I'm pretty sure this is in a FAQ or something somewhere on this forum but here's a quick run down:
Using chrome for desktop (not mobile) go to tesla.com and log into your account. Open up (click on 'manage' ) your vehicle. Now click on "details" under the image of your car. A pop up window should appear with the list of options you have; but it's not exhaustive, and it doesn't include option codes. Right click on this pop up window, and select from the chrome-pop-up menu "view page source"
Now you have the HTML code for that pop up window of options for your car. press CTRL-F (for find in page) and search for the word, "options" it should appear only once. To the left of the word "options" is a list of option code strings. Each of which starts with a $ sign.
Copy all of them and paste them into the EV-CPO option decoder. Done.
Good luck
I'm not sure how else to find out, short of a visit to your local SC.Very cool. Unfortunately, it still isn't clear. Current listings for HW3 cars on EV-CPO show something like APH4 AP 3.0 under Autopilot. HW4 cars show something like AP04 AP 4.0. The trick outlined above doesn't return those values. A google search says that the APF2 code seen below refers to the fact that I've paid for FSD; it does not convey anything about the version number of the hardware. It is also odd that it is saying the vehicle is a Plaid, when it isn't.
View attachment 940269
Also for the plaid thing - EV-CPO doesn't have official definitions of each code;
But if you type APH3 into the code decoder at ev-cpo, it spits back AP2.5!
AFAIK they just use what is commonly understood as the definition. Based on a process of deduction and elimination
Hey man, chill out! Sorry if how I wrote my post wasn't clear, but IMO what I was trying to say is EXACTLY what you said. I am a fan of your site. Have been a paid member on and off over the years, and use it a lot for my own interests, and to send listings to friends who are interested. I know you are limited to what you can "infer from the codes as they exist in the listings" - this is exactly what I meant by "a process of deduction and elimination". I was only trying to explain that you are limited as to what you can decode from what has been shown in listings. IMO to "infer" is not very different from deducing, and eliminating other possibilities. If anything I think "deduction and elimination" is more exact and precise than just claiming "we infer this". For example, "we see code XYZPQ on both a 2021 Plaid, and a 2018 75, so we can deduce that it is not specific to either, and eliminate that possibility." But this is nothing more than a semantic debate.I'm sorry, but you clearly do not know nor understand how it works, so I'd appreciate if you didn't make comments like this. Thank you.
I've had to deal with option codes from one of the Big 3...Ok, sorry then. But I but a significant amount of time into the option codes and categories and decoding hundreds of pages of HTML and JSON to find the best option code definitions, so it's more work than just inference or deduction that seemed to be what you implied. I probably put more time into the option codes than anything else.
And yes, I do need to do a little catch-up on the veryt latest codes.
And thank you for your support.
All good.Ok, sorry then. But I but a significant amount of time into the option codes and categories and decoding hundreds of pages of HTML and JSON to find the best option code definitions, so it's more work than just inference or deduction that seemed to be what you implied. I probably put more time into the option codes than anything else.
And yes, I do need to do a little catch-up on the veryt latest codes.
And thank you for your support.
Not expecting too much. Rather, I'm just leveraging a helpful tool I've used for years to try and answer a question that has proved to be very elusive. I find it fascinating and frustrating that Tesla is making it so difficult to answer that question definitively.To the main point: I think that @theflyer was possibly expecting too much from your site. My post with circles and examples of gaps, was not meant to be critical of your site or work, but rather just examples of what to expect, since - as you have pointed out yourself - the data for what various codes mean are limited.
My guess is Tesla is trying to delay backlash when it turns out HW4 and AP4 have no benefit without software still to be developed.I find it fascinating and frustrating that Tesla is making it so difficult to answer that question definitively.
When it comes down to it, all that matters is whether you buy FSD or not. If you buy it, then they (for now anyway) say you will get any required HW updates to run FSD when it does go to general release. If you don't then you may need to pay for HW updates if necessary.My guess is Tesla is trying to delay backlash when it turns out HW4 and AP4 have no benefit without software still to be developed.
This is not true. There is no upgrade path from HW3 to HW4. Elon claims HW3 can still achieve self-driving and the difference with HW4 is not that great. I don't believe much of anything anymore, even while remaining optimistic about FSD strategically. I have a HW3 model S with FSD beta and now what I believe to be a HW4 model X so it'll be interesting to see how the situation evolves. It doesn't appear the X can yet get FSD beta, but it does have NOA using the original highway stack. TeslaFi is not showing any HW4 vehicles getting the new FSD push that went out yesterday/today to those that bought/subscribed to FSD but had yet to get the software pushed to them.When it comes down to it, all that matters is whether you buy FSD or not. If you buy it, then they (for now anyway) say you will get any required HW updates to run FSD when it does go to general release. If you don't then you may need to pay for HW updates if necessary.