dl_a175 / Cruise Control Not Available after 2022.36.2 Firmware

[GBMaryland]

I started noticing funky issues recently when FW 2022.36.x was deployed to my car.

The error I’m receiving is either DL or DI A175.

Along with a cruise control error that also prevents auto pilot from running.

Strangely, I just noticed that my car is making three beeping. Sounds when I try to lock it, and the lights tend to stay on when I park the car.

No doors, windows, or the trunk are open…

Has anyone else been seeing stuff like this?

 

[TSLY]

Reboot

 

[GBMaryland]

I did reboot the head unit.... Is there a way to reboot the reboot of the car?

 

[JP Bark]

I got this error on my second leg of my morning commute today.
Originally I thought it was due to being in a construction zone, but did not work later outside of that area.

This happened on my 22 Model 3.
Did the reboot fix this?

 

[GBMaryland]

A reboot did not fix the issue. It started, for me, after a recent firmware update. I also noted that during one of the events the car was honking three times when I went to lock it. (Though no doors were open, or the fronk, or the trunk....)

 

[scooterdme@me.]

i am having same issue

 

[scooterdme@me.]

i am having same issue

im t hinking about recalibrating camera?

 

[rolling green]

updated last night to .36 and received notification "charging stopped...if unexpected, check Controls>Service>......." in the middle of the night. Went out to see what was going on and the car was charging normally. Strange, first issue I've seen after an update.

 

[GBMaryland]

Yeah, I mentioned to Tesla when I went to pick up the parts at the Rockville, MD, service center. "Open a SR in the app."

They've got serious F'ing issues, as in a lack of customer service.

Anyway, I suspect this is a firmware issue.

 

[JonB65]

Yeah, I mentioned to Tesla when I went to pick up the parts at the Rockville, MD, service center. "Open a SR in the app."

They've got serious F'ing issues, as in a lack of customer service.

Anyway, I suspect this is a firmware issue.

I would recommend multiple reboots. I had an issue of codes popping up out of nowhere after I installed the FSD beta update a couple of versions ago. Two reboots did not solve the issue and thinking something was seriously wrong, I had it towed to Owings Mills SC. They disconnected the 12V battery to clear the codes, could not duplicate the problem, and I got my car back several days later. No issues since then. If you check around, you can find the procedure to disconnect the 12V battery. I would try that and seeing if it helps before you go the SC option.

 

[GBMaryland]

Thanks, I’ll look into that; the folks at the Rockville service center just have issues…

They have enough problems that I’m concerned about even bringing the car to them

 

[JP Bark]

I did a car shutdown and a steering wheel reset before I left work and did not have any more errors... Very strange bug.

 

[GBMaryland]

Do any of you guys have S3XY Buttons? I noticed that if you tried to put it in 25% regen breaking (aka Passenger Vomit Comet protection mode) that it also generated that error. Not sure if it was S3XY buttons or if it was some Telsa screwup issue....

 

[jjrandorin]

Do any of you guys have S3XY Buttons? I noticed that if you tried to put it in 25% regen breaking (aka Passenger Vomit Comet protection mode) that it also generated that error. Not sure if it was S3XY buttons or if it was some Telsa screwup issue....

Someone in the model 3 subforum has their frunk randomly opening, and that stopped after they disconnected their "s3xy" buttons. Just a thought /shrug.

Frunk opening itself after 2022.36.2

So this is weird. Got 2022.36.2 OTA last night. Went to the garage this morning and my frunk was open. Closed it. Unplugged the charger. The frunk opened. Closed it. Rebooted the car. Opened the driver door to get out. The frunk opened. Shut the M3 down via Controls > Safety > Power...

teslamotorsclub.com

 

[TSLY]

Updated last night and tested Autopilot because of this post. My AP worked.

 

[GBMaryland]

There is definitely something to the S3XY Buttons…

I’m wondering if Tesla screwing with them?

It goes away when I turn them off or disconnect the controller…

 

[GBMaryland]

S3XY buttons appear to have a compatibly issue with the latest firmware.

There is only a beta commander firmware available and will not auto update unless beta firmware is enabled…

 

[beven-32@hotma]

I also have "cruise control unavailable" issue.

It worked briefly today, Then stopped again. I have recalibrated the cameras. All the driver visuals are still there. Just no cruise or autopilot.

Only 1800kms on the car. I have booked a service appointment. Running firmware 2022.36.2.

 

[dimitar.ns]

I also have "cruise control unavailable" issue.

It worked briefly today, Then stopped again. I have recalibrated the cameras. All the driver visuals are still there. Just no cruise or autopilot.

Only 1800kms on the car. I have booked a service appointment. Running firmware 2022.36.2.

This happens when the Commander version is older and not compatible with 36.2. Please, update the Commander to 2.10.69 and the issues will disappear. Better to avoid Tesla service when we know the root cause of the issues.

 

[TriKKyOne]

This happened to me and I don’t have S3XY buttons.

Basically, the only thing that fixed it was time. Got to destination, locked car, stayed for an hour, came back and all was well and the error hasn’t returned.