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.
My legal expertise here is as deep as yours but from what I read the California law is limited to 18 months or 18,000 miles and from your timeline you are past that. Now a sharp lawyer might try to argue that the problem arose before that and defendant would counter that you took no action until Nov 2018, past the 18 months.Why wouldn't lemon law apply here? The 15 minutes of reading I just did, which clearly makes me an expert, makes it sound like it applies. This is a safety issue that Tesla had tried to fix multiple times without success.
I seriously don't want to deal with a lawsuit. I just want my car to work
I have a dashcam and audio system installed. Why do you ask?
Have you tried disconnecting the Dashcam? It feels like I have read someone having problems with their GPS after a dash cam install.
Who installed the audio system and what system? Changing the wiring around the MCU maybe related.
I Mostly agree! But the folks at SC are incompetent.The "antenna" referred to here is not just the antenna. The GPS module is mounted as close to the antenna as possible. PunchIT had a bad module and it looks as if cryptyk does too. But replacing it once didn't fix the problem. So that focuses attention on the harness between the GPS module and the computer up front (as has been suggested here). This is the kind of thinking that should be done by the SC - not by a bunch of guys on the internet.
The "antenna" referred to here is not just the antenna. The GPS module is mounted as close to the antenna as possible. PunchIT had a bad module and it looks as if cryptyk does too. But replacing it once didn't fix the problem. So that focuses attention on the harness between the GPS module and the computer up front (as has been suggested here). This is the kind of thinking that should be done by the SC - not by a bunch of guys on the internet.
Sort of. Each satellite has an (atomic) clock whose offset from "GPS" time is tracked by the ground segment of the system. The receiver has its own clock which is, hopefully, reasonably close to the system clock. Every so often each satellite announces "At the tone the time will be" and has sent (in the low speed Nav message) orbital parameters from which someone who knows about where he is and about what time it is can figure out about when he should receive the tick from each satellite. Given that he knows the geometry he can figure out how many nS error a meter change in latitude would make. If the tick from a satelite is off by x nS and the rate of change of delay is y nS/m then he is off in latitude by x/y m and he corrects his position by x/y and tries again. If you can remember back to high school math he is using Newton's method. It is, of course, appreciably more complicated than that because he has dozens of statellites (GPS and GNSS) and he has error in latitude, longitude, altitude and clock to deal with. This is going to sound pretty hairy but he is trying to locate himself in space-time, a 4 dimensional coordinate system. Time is, as far as the math is concerned, just another dimension. In this problem y isn't a number. It is a matrix with one row for each satellite and 4 columns, one each for x, y, z and t.Here's what I think, based on the info from Doberstein: GPS receivers are little clock-shops with clever tricks employed to synchronize the receivers own clocks with the satellites' clocks' signals in a way that allows calculation of a position ...tic, tic, tic, calc, you are here!
I implied above that position and clock are corrected by estimating expected time of reception of ticks, comparing to actual arrival times and multiplying the vector of errors by the inverse of the sensitivity (y) matrix and it can indeed be done this way but in the modern receiver the equivalent is done using a Kalman filtering algorithm. This takes the current estimated position (including clock offset) and operates on it to predict a new estimated position using a model of the receivers' motion (actually, x, y, z, t and their first derivatives are estimated). From this new state expected arrival times are computed as are residuals (the error between the expected and actual). These errors are weighted by the "Kalman gain matrix" and used to correct x,y,z,t and the velocities. At each iteration the filter looks at the residuals and determines the quality of the estimates. If the satellite data looks shabby more reliance is placed on the vehicle model and less on the observed residuals and conversely. Thus if you go into a tunnel where there is no satellite data the receiver will keep moving you along a straight line until it's determination that the estimate quality (no satellite info) is too poor and then it will shut down. This is what I believe is happening here.It seems to me that the mis-locating or non-locating malfunction (especially the moving, mis-locating failure mode) has to be a failure of the receivers' reference clocks to sync properly, causing a slight shift of the computation of position.
If the clock isn't operating at all you get no position estimates at all. Remember that to the math time is just another measure of distance (the transit time from a satellite to the receiver is called its "pseudorange" by the GPS folks). A wildly wandering clock would lead to huge residuals and the RAIM (see below) function would shut everything down.Perhaps the 'locked up" failure is the reference clock not operating at all, or it's so out of phase that the receiver just sits, waiting.
The receiver, if functioning properly, is not ticking along happily if the clock loop goes out of lock. It would immediately shut down. An important part of GPS receiver design is RAIM (Receiver Autonomous Integrity Monitoring).My leaning is to the semi-functioning reference clock, because the GPS receiver is clicking along, happy as a lark, thinking everything is working properly.
PLL chip fails but this would be detected by RAIM immediately.I have no idea how any of the GPS clocks might fail in such a manner,
Not if you understand how these beasts work.but the symptoms are much more indicative of that than of antenna problems.
That is what a prudent tech would do. Another post shows that they get enough low level diagnostics from the module (in case it isn't clear the module usually incorporates the antenna but it doesn't have to be that way) that they can, for example, see that the module is seeing satellites but can't use any. A blown clock chip could cause that! But so could interference with the Nav message reception, a faulty RAIM circuit etc., etc.Tesla is about to do the rear-window/antenna 'fix' to our car.
No, it's probably not the antenna as that's a pretty simple device. It's probably bad cabling or a bad interface but it could be a bad module and certainly that's where diagnosis should start given that the modules are so cheap.Not. Antennas.