Multiple cameras are blocked or blinded.

[Liver]

Every morning, same error message. Multiple cameras are blocked or blinded.

First several times it happened, I checked them and cleaned them. Inspected and found nothing.

Now, it’s a daily thing. It happens every morning. I drive for about a mile and it all resolves. Pretty much like a routine.

Any idea what is going on?

I have a service appointment tomorrow and I’ll bring it up with them as well. Service appointment for the the AC scheduling module going out.

I have the Beast, if it matters.

Thanks.

Sponsored

 

[dalton108]

I’m assuming it’s predawn when you leave. And I’m assuming you live somewhere where there’s not a lot of street lights.

I get this on my cyberbeast anytime I’m driving around in rural areas where there’s no light it’s only one of mine (the left pillar camera) most of the time but if it doesn’t see light it thinks it’s blind. I think they just need to calibrate them better.

 

[vinsk]

My cameras are going blank all the time randomly on a regular basis. They get resolved the next day after the truck takes rest. Most annoying part is when I'm trying park using backup cameras. The rearview camera goes blank multiple times a day which is ridiculous considering the fact that it's the only option available to see what's behind !

 

[Ruffles]

I got this a lot on my 2020 model y in the winter at night. The side cameras would get condensation on them. I haven't had my Cyberbeast in the winter yet but I was hoping this had been resolved. I thought I read that there were heaters by the cameras.

 

[Woodrick]

Every morning, same error message. Multiple cameras are blocked or blinded.

First several times it happened, I checked them and cleaned them. Inspected and found nothing.

Now, it’s a daily thing. It happens every morning. I drive for about a mile and it all resolves. Pretty much like a routine.

Any idea what is going on?

I have a service appointment tomorrow and I’ll bring it up with them as well. Service appointment for the the AC scheduling module going out.

I have the Beast, if it matters.

Thanks.

Don't bring it up with them when you get there, they aren't supposed to add things per se. Just add it to the service thread that is already started and see what they say.

 

[Liver]

Don't bring it up with them when you get there, they aren't supposed to add things per se. Just add it to the service thread that is already started and see what they say.

after owning 3 Teslas over the last 11 years. It’s doesn’t matter if I bring it up with them at the service center or the app. Result is the same.

YMMV.

 

[Woodrick]

after owning 3 Teslas over the last 11 years. It’s doesn’t matter if I bring it up with them at the service center or the app. Result is the same.

YMMV.

You've had this same error on your previous 3 cars?

 

[Liver]

I’m assuming it’s predawn when you leave. And I’m assuming you live somewhere where there’s not a lot of street lights.

I get this on my cyberbeast anytime I’m driving around in rural areas where there’s no light it’s only one of mine (the left pillar camera) most of the time but if it doesn’t see light it thinks it’s blind. I think they just need to calibrate them better.

this is exactly my situation. I live so far out, I have to take 3 county roads just to get to a farm to market road. Yes, pre dawn and no lights except for random home lights. No road markings either.

yes, it’s mostly the left pillar that is blind but it’s multiple then left then corrects.

I’ll ask about calibration.

 

[SCTesla]

this is exactly my situation. I live so far out, I have to take 3 county roads just to get to a farm to market road. Yes, pre dawn and no lights except for random home lights. No road markings either.

yes, it’s mostly the left pillar that is blind but it’s multiple then left then corrects.

I’ll ask about calibration.

Calibration won't fix it, but it also won't always negatively impact FSD.

Bright lights and extreme darkness will throw up that message. Been that way since 2021 on all my Teslas.

 

[ÆCIII]

IMO Tesla certainly needs to reconcile camera performance in extremes of dynamic range for travel in dark areas.

Others and I have experienced this error consistently when traveling at night on road trips. Many people like to begin traveling well before dawn, to avoid peak traffic times in congested areas along a route.

These false errors compromise the FSD experience and data collection, because the cameras are not blocked or blinded at all with the software mistakenly triggering those false errors when cameras cannot detect a certain amount of light.

If Tesla seriously intends to make FSD viable and commonly used for autonomous transport or robotaxi, then they need to reconcile these issues by either integrating higher dynamic range capable cameras, or updating their software to handle low light situations in the existing cameras of hardware suites they have now. Many people will be traveling in rural or dark areas at night or before dawn. If FSD vision remains limited to daylight or minimal light, then that is an impediment which will be noticed and focused on by skeptics far and wide, so this issue needs resolved.

Currently, these errors are annoying because in addition to a message displaying, there is a constant beep or tone accompanying the message on screen. This may be something the NHTSA is requiring Tesla to do, but a better solution is needed. The constant beeping of this type error is also a distraction with diverts attention to the screen from the road. As a minimum, I think an option to mute the audible tones accompanying the message should be a feature, such as, "Mute Further Audible Warnings for Current Drive - Driver Assumes All Liability and Responsibility", etc. or something like that.

Ultimately, I think the cameras and software should be able to perform satisfactorily without giving any such errors at all, even if an updated camera with IR emitters which switches to infrared at night becomes necessary, like many security cameras currently available can do.

TBH, these errors appearing in a Cybertruck are not encouraging. I was hoping this type of issue would've already been resolved in HW4 cameras, due to having continually experienced it in HW3 cameras. Traveling in lower light situations before dawn or at night is done very frequently by many so these are not isolated corner cases at all. I hope Tesla has an optimal solution in their improvements and innovation pipeline.

- ÆCIII

 

[dalton108]

IMO Tesla certainly needs to reconcile camera performance in extremes of dynamic range for travel in dark areas.

Others and I have experienced this error consistently when traveling at night on road trips. Many people like to begin traveling well before dawn, to avoid peak traffic times in congested areas along a route.

These false errors compromise the FSD experience and data collection, because the cameras are not blocked or blinded at all with the software mistakenly triggering those false errors when cameras cannot detect a certain amount of light.

If Tesla seriously intends to make FSD viable and commonly used for autonomous transport or robotaxi, then they need to reconcile these issues by either integrating higher dynamic range capable cameras, or updating their software to handle low light situations in the existing cameras of hardware suites they have now. Many people will be traveling in rural or dark areas at night or before dawn. If FSD vision remains limited to daylight or minimal light, then that is an impediment which will be noticed and focused on by skeptics far and wide, so this issue needs resolved.

Currently, these errors are annoying because in addition to a message displaying, there is a constant beep or tone accompanying the message on screen. This may be something the NHTSA is requiring Tesla to do, but a better solution is needed. The constant beeping of this type error is also a distraction with diverts attention to the screen from the road. As a minimum, I think an option to mute the audible tones accompanying the message should be a feature, such as, "Mute Further Audible Warnings for Current Drive - Driver Assumes All Liability and Responsibility", etc. or something like that.

Ultimately, I think the cameras and software should be able to perform satisfactorily without giving any such errors at all, even if an updated camera with IR emitters which switches to infrared at night becomes necessary, like many security cameras currently available can do.

TBH, these errors appearing in a Cybertruck are not encouraging. I was hoping this type of issue would've already been resolved in HW4 cameras, due to having continually experienced it in HW3 cameras. Traveling in lower light situations before dawn or at night is done very frequently by many so these are not isolated corner cases at all. I hope Tesla has an optimal solution in their improvements and innovation pipeline.

- ÆCIII

My cyberbeast is my fourth Tesla and it is the only one I’ve ever seen this on. I still own a model S plaid and a model Y that we drive regularly both of which have been on FSD since the score 100% beta days (I got the model S because I was able to transfer my FSD from my prior model three performance and I stayed on the same branch of beta). personally I have never seen this in any other car only the Cyberbeast.

 

[dalton108]

Calibration won't fix it, but it also won't always negatively impact FSD.

Bright lights and extreme darkness will throw up that message. Been that way since 2021 on all my Teslas.

When I say calibration I don’t mean to go into maintenance mode and calibrate his individual cameras I mean they need to calibrate the entire system better so that it knows when it’s just dark when it thinks it’s blocked/blind. Somebody else said that this has been happening routinely on HW3 cars and all I can say is that I’ve had two HW3 cars (both on beta since the first month of the first public release) and I’ve never seen this before on either of them. I certainly don’t see it on HW4 S Plaid.

For me it has been a Cyberbeast only issue.

 

[Deleted member 26267]

We live in one of the darkest areas in the country, and we get this every time we get just outside of town. It has never happened during the day, so I've ignored it and chocked it up to being that it's so dark that the camera can't see and thinks it's blocked. As soon as we get back into even a small amount of light it goes away.

Sponsored