I was having a problem where my AP or even cruise control was not working after leaving work. I was also noting there was no speed limit signs being displayed.
This happen several days in a row last week and a couple of other time in the afternoon. I placed a service request through the app and noted the date and time this was happening. I also did a bug report the first few times. If I were to go out later that evening, AP and cruise would work as normal. My mobile appointment was scheduled for this Thursday. Yesterday I received a call from Tesla. The tech was able to locate the exact issue given the time frame and identified what was happening. So here's what's going on. Anytime the vehicle is sitting for an extended time using sentry mode, the vehicle will reboot the AP computer system. The primary AP computer would get hung up in this reboot. He mention the redundant computer would reboot but the primary computer was needed to process the data. I understood this to mean the redundant chip would maintain AP but the main system was needed to initiate the start. He mention they are aware of this and hope to have this resolved in an updated firmware.
Hope this helps anyone else that's experiencing the same issue. I still would recommend submitting a service so there are other documented cases.
This happen several days in a row last week and a couple of other time in the afternoon. I placed a service request through the app and noted the date and time this was happening. I also did a bug report the first few times. If I were to go out later that evening, AP and cruise would work as normal. My mobile appointment was scheduled for this Thursday. Yesterday I received a call from Tesla. The tech was able to locate the exact issue given the time frame and identified what was happening. So here's what's going on. Anytime the vehicle is sitting for an extended time using sentry mode, the vehicle will reboot the AP computer system. The primary AP computer would get hung up in this reboot. He mention the redundant computer would reboot but the primary computer was needed to process the data. I understood this to mean the redundant chip would maintain AP but the main system was needed to initiate the start. He mention they are aware of this and hope to have this resolved in an updated firmware.
Hope this helps anyone else that's experiencing the same issue. I still would recommend submitting a service so there are other documented cases.