I guess Elon Musk and a lot of other people that suggested the same process is wrong then?
Sure wouldn't be the first time.
Folks who actually directly access the computer systems have all explained this, roughly 7694 thousand times previous.
It doesn't go anywhere.
A moment of critical thought would provide you the same answer though.
There's well over a million Teslas on the road today.
There's be well over 2 million by years end.
Likely ~4 million by end of 2022.
Who's listening to all those bug reports you imagine all get sent back to the mothership?
How many employees do you imagine they'd need to hire full time
just for that task?
Even the manual doesn't indicate you should log a service ticket for bug report, I guess it's a hidden fact.
You should log a service ticket when something is wrong with your car.
The bug report allows the tech assigned to your service ticket to remotely access that report and see the logs that got saved when you hit bug report that are stored on the car.
E
From Manual (whatever the last sentence means periodically reviews notes):
Contacting Tesla For detailed information about your Model Y, go to
www.tesla.com, and log on to your Tesla Account, or sign up to get an account. If you have any questions or concerns about your Model Y, call 1-877-79TESLA (1-877‑798-3752). NOTE: You can also use voice commands to provide feedback to Tesla. Say "Note", "Report", "Bug note", or "Bug report" (in the English language) followed by brief comments in your language of choice. Model Y takes a snapshot of its systems, including your current location, vehicle diagnostic data, and screen captures of the touchscreen. Tesla periodically reviews these notes and uses them to continue improving Model Y.
Yeah- it reviews them if there's a service ticket opened.
Since they stay local to the vehicle- and they don't have the manpower to listen to what would doubtless be millions of bug reports a year from the fleet without any corresponding actual service request tied to them.
There's folks here who've mentioned submitting dozens of bug reports for incorrect speed limits in the maps, for years, for example. (without anything happening of course- since again- nobody's hearing them.
Also folks who've directly asked Tesla techs and been told the same thing. The bug report is for the tech to look at if you open a ticket by logging into your car and reading it, since that's the only place it goes.
This post being one among many
I don't have any personal information on the subject one way or another - I've left a few, and never been contacted about them, but I wasn't really expecting to be contacted. Your description is distinctly different from the description we were given a couple years ago. Where did you develop...
teslamotorsclub.com
"I believe @greentheonly on Twitter (
@verygreen here on TMC) looked at the code and figured out that when a bug report is captured it isn’t transmitted, just stored. My own experience with a mobile tech appears to verify this as well. They were troubleshooting an audio issue that I and several others were experiencing a year ago and the mobile tech asked me to shoot him an email whenever I created a bug report about the issue. He said that he would then remotely connect to my car and download the recently captured bug report log files. Unless I notified him there was a bug report to look at he would had no way of knowing I submitted a bug report"
For example (from Green):
(if you scroll up a bit in the twitter thread he actually posts a screen shot of Teslas internal code running on the car computer that captures and stores the data locally- nothing in the code "sends" it anywhere- and he's mentioning he's never seen any evidence of Tesla "fetching" it either other than service centers in relation to open tickets.)
Obviously it won't hurt anything (except very marginally wearing out your emmc onboard storage I guess- a much bigger issue for MCU1 cars)-- but unless it's related to a ticket you're going to open, it won't be doing anything but wasting your own time.
