Hi all,

I have a 2017 Accord touring. Had the windshield replaced this past summer. The glass place installed an aftermarket windshield (I now know that any non-OEM windshield will cause problems with the sensing suite). When pressed for a resolution, the service center blamed the camera (citing the error code) and told me I would have to take it up with a dealer. The crack in the windshield was nowhere near the camera and I have never had any issues with the camera or sensing suite. I did have the windshield calibrated and re-calibrated the following day.

The errors appeared for the first time about a week after the initial crack. It spread from the edge of the windshield almost to the middle in that time period and the first time the errors appeared was the day before the windshield was replaced.

What's strange is that the errors seems to come and go randomly. Some times when I start the car, the sensing suite initializes and functions just fine, other times the errors all appear. It's for this reason along with the fact that the windshield camera was never touched, nor malfunctioned in any other way that I believe the camera is just fine. Additionally, the service center dodged my calls and emails for days until I showed up in person and demanded a refund for the calibration, so I don't trust their explanation. It was apparent they just wanted me to go away.

Does anyone have any insight as to what could be tripping the errors? My thought process is that if it's intermittent, there must be a way to stop it from happening or "trick" the computer into allowing it to initialize. Honestly, all I want is my cruise control.

Thanks to anybody with any info in advance. I realize this might be just something I have to live with, but figured it's worth the inquiry.

-Cheers

 

The problem is 100% windshield related.

 

Oh, most definitely. Any thoughts on why sometimes the car is fine with the windshield? I'm just trying to identify the variable. Maybe it's impossible cause it's just one of those unpredictable things? Just leaves the system in an unstable state...