-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
AP disengaged while driving - Radar Failure (release 2019.8.3)
- Thread starter GolanB
- Start date
There are a few ways to get IP accounting data of your network; in some cases, it's available from next-generation access-points, like those from Ubiquiti Networks. In this case, there was a layer-7 application analysis done by a very cheap and cost-effective consumer firewall device called the FIREWALLA which I have been beta-testing. It runs open-source linux, and BRO to analyze the network traffic, and it comes with its own iOS App to report the data. Typically this sort of analysis was only available on enterprise firewalls with deep-packet-inspection (like those from Palo Alto Networks and others), but the features have recently made their way down to consumer networking solutions. I've had success with the FirewallA, but I am still playing with it. It's not rated to handle more than 500Mb/sec, so if you have 1Gb/sec to your home (over fiber) it may slow your traffic down a bit.
This afternoon, while coming back home from the office, I experienced a nearly identical failure of AutoPilot while driving through the Holland Tunnel to NYC. The AutoPilot disengagement is the third time in a little over a week; this occurred while running 2019.8.3.
In all cases, I received the "red hands" warning to take over driving immediately.
In all cases, the car lost visibility of its surroundings, including road markers, and vehicles.
In all cases, the AutoPilot (autosteering function) was not available for re-engagement for approximately 10 minutes until I was well out of the Holland Tunnel, and back in NY. The error I received was "Reduced Front Radar Visibility."
Tesla got back to me this afternoon with the following info:
- They used my data (bug report, videos, TeslaCam, timestamps) to reproduce the issue.
- They've found that a prior issue has resurfaced in the current code base.
- They're scheduling a fix in a future release. The fix is expected to arrive in the 2019.12.X codebase.
- The issue has to do with AutoPilot's functionality in Tunnels.
- They'll provide me further status in the next week or two.
I managed to capture the event on Video since this was reproducible. In this extended video, you can see the failure occur within the first third of the tunnel.
Video:
In all cases, I received the "red hands" warning to take over driving immediately.
In all cases, the car lost visibility of its surroundings, including road markers, and vehicles.
In all cases, the AutoPilot (autosteering function) was not available for re-engagement for approximately 10 minutes until I was well out of the Holland Tunnel, and back in NY. The error I received was "Reduced Front Radar Visibility."
Tesla got back to me this afternoon with the following info:
- They used my data (bug report, videos, TeslaCam, timestamps) to reproduce the issue.
- They've found that a prior issue has resurfaced in the current code base.
- They're scheduling a fix in a future release. The fix is expected to arrive in the 2019.12.X codebase.
- The issue has to do with AutoPilot's functionality in Tunnels.
- They'll provide me further status in the next week or two.
I managed to capture the event on Video since this was reproducible. In this extended video, you can see the failure occur within the first third of the tunnel.
Video:
I had the exact same thing happen to me a few days ago while driving north out of Manhattan. Same alert and same issue as you describe. About 10 minutes later while driving it went back to normal. I'm still on 2019.5.15 though. Also I have been having my screen shut off while driving. It happens randomly when nothing particular is happening....very unsettling.
Our Model 3 was updated to version 2019.12.1.2, and we just started seeing the same "cruise control not available; reduced front radar visibility" error. I was able to briefly engage Autopilot last night, but then the system abruptly disengaged and I had to take over immediately. The car is reasonably clean. I tried a reboot (hold down both scroll wheels while pressing brake pedal), to no avail. So I've scheduled a service appointment (a few weeks out).
What were the conditions in which you were driving, including whether you were on busy roads, highway, tunnel, bridges and the weather that day? My specific case related to the performance of Autopilot while engaged in a tunnel (more specifically, the Holland Tunnel in NYC). Did it occur more than once, and are you able to replicate the issue?
While you wait for your service appointment, I recommend you call Tesla Support and see if you can get in touch with anyone there who works together with the AutoPilot team. They were able to determine my issue was software related and didn't want me to bring the car into service. This may not be your case, but they should be able to do some analysis. If it's helpful to you PM me and I'll send you the name of the Tesla employee that is handling my case.
I haven't had a chance to retest in version 2019.12.1.2 since my Model 3 has been in with Tesla to get its rear glass replaced after a fracture formed. I'm due to pick up tomorrow and will try again then. I didn't get a clear answer as to whether the fix is installed in this release, but I suspect it hasn't been, only that there have been general 'improvements.'
I spoke with a Tesla rep and was advised to try rebooting using the “Turn Off” button on the car’s Security and Privacy screen. Failing that, their recommendation is to let Service look at it. I was told that Mobile Service should be able to handle an issue with the front radar.
In our case, the failure seems general in nature, whether we’re on freeways or our local mountain roads. The weather has been mostly dry.
In our case, the failure seems general in nature, whether we’re on freeways or our local mountain roads. The weather has been mostly dry.
alee
Member
Just to follow up, it turns out that our front radar issue was caused by a front license plate decal that I mounted too high. So, the hardware on our car is fine! See Ticketing for no front plate in Santa Monica and stick-on front plate option
I have yet to lose radar in the tunnel while AP has not been engaged, its pretty much only happened when its enabled - and the rate of failure is approximately 1 in 3 trips. I'll speak to Tesla again tomorrow and see if they have any updates on when a fix will be released.
alee
Member
Interesting. Mine cut out entirely in the tunnel even w/o AP on.
Got 2019.16.2 this afternoon. Not tunnel bound for a while so won't be able to test... but AP seems pretty squirrely on this version.
I received an update from Tesla today informing me that 2019.16.2 "should resolve the issues" I experienced with the autopilot shutting down in the Holland Tunnel.
I hope to test this further tomorrow on my route back -- this week I took an alternate route and was not able to test.
I hope to test this further tomorrow on my route back -- this week I took an alternate route and was not able to test.
xxxholic
Member
I had this same exact thing happen to me today, I am on v10 (2019.32.11). I received an additional notice about the sensor - not working correctly.
I wish I had seen this thread before I posted a very similar issue. I have the latest software update, so I guess the issue is still unresolved.
teslamotorsclub.com
Autosteer/Cruise Control unavailable exiting HRBT
Without fail, autosteer and adaptive cruise control will become unavailable when exiting the Hampton Roads Bridge-Tunnel (HRBT) on I-64 west bound. It will be unavailable for quite a distance after the exit of the tunnel (several miles). I have had this happen every time, with different Tesla...
teslamotorsclub.com
smatthew
Active Member
Don't dig up 2yr old threads. Link to them.I wish I had seen this thread before I posted a very similar issue. I have the latest software update, so I guess the issue is still unresolved.
Autosteer/Cruise Control unavailable exiting HRBT
Without fail, autosteer and adaptive cruise control will become unavailable when exiting the Hampton Roads Bridge-Tunnel (HRBT) on I-64 west bound. It will be unavailable for quite a distance after the exit of the tunnel (several miles). I have had this happen every time, with different Tesla...
Similar threads
