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

Tesla "logs" vs reality... potential problem?

Az_Rael

Supporting Member
Jan 26, 2016
5,605
8,766
Palmdale, CA
Even passing there's no reason to put your pedal to the metal. In those cases, it is perfectly sane for the car to be given first reading and only allow it if the sensors show clear ahead. That's just plain common sense stuff. What "edge case" could you possibly come up with otherwise?


Well, there is a very poorly designed freeway entrance ramp up in Northern California that caused this fellow some repeatable trouble due to the car detecting a potential collision and not letting him accelerate

"Obstacle detected" - blocking acceleration - very dangerous!

So there are real edge cases.
 
  • Informative
Reactions: bhzmark

Ken7

Member
Feb 11, 2017
880
857
New York
I think we are talking about two slightly different but interwoven things.
Case 1 (this thread so far):
Vehicle's handling/ logging/ error reporting of the TPMS data it is receiving and logging consistency. Given that TPMS is saying X, what should happen?
Case 2 (what I think you are referring to):
Is what TPMS saying accurate? Is it behaving correctly?


There had been a fault (low pressure), which was resolved (tire inflated), but had not cleared (car not driven after fill). OP contacted Tesla, logs were indicated to not show original fault or current display of fault that OP was looking at (potential lack of feedback from UI/ logging/ rep communication issue)

In the words of the great Samir Nagheenanajar "why does it say paper jam when there is no paper jam?. Or in this case. "Why are you saying there is no fault when it is saying there is a fault?"
Yes, I think these points are somewhat interwoven. I'm more concerned about inconsistencies between accurate TPMS data and logging inconsistencies than inconsistencies of inaccurate warning lights and logging data. In the latter case, there really aren't any 'inconsistencies' because the logging data is accurately reporting no issues. It's the warning lights that are inaccurately reporting issues. So in that latter case, Tesla is correct in saying, "We don't see any issues". Sure, that's because there are none. It's the customer's faulty diagnostics that are causing this apparent inconsistency.

Not sure if I'm making myself clear...at least that's what my wife says. ;)
 

mongo

Well-Known Member
May 3, 2017
12,892
38,067
Michigan
Yes, I think these points are somewhat interwoven. I'm more concerned about inconsistencies between accurate TPMS data and logging inconsistencies than inconsistencies of inaccurate warning lights and logging data. In the latter case, there really aren't any 'inconsistencies' because the logging data is accurately reporting no issues. It's the warning lights that are inaccurately reporting issues. So in that latter case, Tesla is correct in saying, "We don't see any issues". Sure, that's because there are none. It's the customer's faulty diagnostics that are causing this apparent inconsistency.

Not sure if I'm making myself clear...at least that's what my wife says. ;)

Yeah, originally I thought the situation was the latter part of your statement (that the display was messed up and all was well). As the conversation progressed, it showed that the problem was the former part (accurate TPMS flagged issue and the logging (as reported by Tesla) appeared inconsistent).
 

About Us

Formed in 2006, Tesla Motors Club (TMC) was the first independent online Tesla community. Today it remains the largest and most dynamic community of Tesla enthusiasts. Learn more.

Do you value your experience at TMC? Consider becoming a Supporting Member of Tesla Motors Club. As a thank you for your contribution, you'll get nearly no ads in the Community and Groups sections. Additional perks are available depending on the level of contribution. Please visit the Account Upgrades page for more details.


SUPPORT TMC
Top