Search results

I’m not surprised Tesla made FSD disengage at a toll plaza. How can it know which lane to use? Only you know if you can use the high speed lanes instead of the low speed ones. There’s lots more Tesla has to do before they hit Level 3 autonomy, let alone “auto taxi” operations.

11.4.4 is pretty old, and it has lots of problems. I had it about a year ago, and the vehicle would cut thru parking lots to get past traffic slow-downs among other weird stuff. I'm surprised anyone still has it.

That’s for the original owner to transfer to a new vehicle. If the original owner doesn’t or can’t transfer FSD, AFAIK the FSD software “license” doesn’t transfer to the new owner of the used vehicle, only the hardware.(moderator note: a purchased FSD license DOES transfer with the sale of the...

In the past, FSD software didn’t transfer when the vehicle was sold - the new owner had to re-purchase the software. The hardware does go with the car. Has the software policy changed?

I’ve been posting this problem for years. 12.3.6 is worse than V11 for me because mine now slows down in the left-side HOV lane as it passes the planned exit on the right, potentially causing a collision accident with traffic behind me. The right turn signal also comes on for me as I approach...

AFAIK, it does not recognize NTOR signs, along with a host of other things like road work flaggers.

FSD doesn’t on mine.

It was a vehicle support representative on the 800 national support line. The highway "stack" currently has significantly different behaviors from 11.4.9.

See my comment above. Tesla says it’s V12, city and highway.

I spoke to a Tesla representative on the phone Monday, and she told me categorically that V12 does not use V11 as a highway stack. Highway or city, it’s all V12.

In my opinion, 12.3.4 isn’t behaving on the highway like 11.4.9. There are some new behaviors present, like moving out of the right lane at a busy on-ramp and turn signals when the vehicle is making an on-ramp merge, that I never experienced with 11.4.9.

The double-line HOV boundary presents a big challenge to FSD & the Nav database. There are some HOV lane entry/exit points, and either the Nav database has to contain them for route planning OR FSD needs to start reading freeway signs.

I had HOV lane engaged as well in the V12 episodes. The rationale for not leaving the HOV lane should depend upon whether the white line boundary is a double white line, which means leaving the HOV lane is illegal, or a single white line, which is legal to cross.

Wow, 12.3.4 works remarkably well for me. The yellow line incident hasn't happened again. That's not to say it doesn't have problems (see another post I made in this thread earlier). I haven't yet subjected it to a couple of scenarios that V11 failed in my area. 11.4.9 was absolutely...

Mine signals for turns at a reasonable distance from the city street turn, makes the turn a bit slowly, but then accelerates way too hard for a few seconds away from the turn. Makes no sense.

I've discovered that the old HOV bug in FSD still exists in V12, and it's actually nastier than in V11. The problem arises when the vehicle is in FSD on a freeway, a route has been mapped involving a right lane exit, and the vehicle is moving in an HOV lane on the left with a single-white-line...

I'm becoming a fan of V12 with 12.3.4. I've seen some very interesting and positive behaviors, like correctly selecting when to pass on waiting for a pedestrian to cross the street and when to stop & wait. Today, I witnessed a really amazing behavior. I had FSD engaged on a major multilane...

Tesla & Elon have said nothing about assuming liabilities for accidents while using FSD in the future like Mercedes did. Who does Elon think will cover autotaxi accidents?

I once was a Tesla stock holder, but sold out at about $850/share after the stock plunge began and I became thoroughly disgusted with Musk.

Oh, the contactor problems rang a bell. I was trying to check the health of my 12 V battery with the HV battery safety plug pulled (which disables the HV contactor). I had turned the car off in the Safety menu & left the passenger door open. The 12 V battery voltage fell to 12.2 V, which...

Second try, I navigated to a Costco south of downtown Seattle from home, about 11.5 miles. This time, the vehicle kept to its lane instead of straying over the double-yellow line near the start of the drive. I made it to Costco without an intervention, the drive went very well, and 12.3.4 did...

I got 12.3.4 last night and gave it a quick try this morning to a local Starbucks. It did well on my little side road (not speeding but going a bit slow), then made a great unprotected left turn onto a main 2-lane road. It then strayed over the double yellow center line and showed no intention...

I PAID for FSD plus MCU2 and HW3, and I’m still waiting for V12. I’m not happy to see rumors that Tesla is working on FSD for MCU1 cars while I’m left behind.

This is good news to me. I got switched to the 2024.2.x branch recently, and I’ve been expecting a long wait to get FSD 12.x.

I’ve been told to do this by Tesla support folks after each update.

After every software update, I always power the vehicle off for 5 minutes, then reactivate the vehicle by opening the driver’s door, then 2 scroll wheel + brake pedal reboot

They’re history messages. I would have expected the tech to clear them out as one would with OBD2 after a repair is complete that generated the errors.

After my last Tesla SC visit, the tech left a bunch of vehicle errors in the Service mode listing from when he fixed the vehicle. They’re now old meaningless errors, but they persist in the display nevertheless. Is there any way for me to purge those errors from the listing myself? Do I have...

The clicking noises are back. Do I need to replace the axle nuts & torque them to spec? I think Tesla considers them to be one-use items.

Also, the thread in the Model 3 discussions about rear axle clicking include a video of someone loosening the axle nut, pressing in the axle end & forcing grease back into the splines to quiet the clicking. I found this in the Tesla Model X rear CV axle remove/replace instructions: So, at...

I’ve noticed recently that I hear a clicking noise from my left rear wheel when going thru a drive-thru lane. It only happens at very low speed and is synchronized with the tire rotation. Looking around TMC, I see discussions about this problem with M3 and MS, but no mention of this with MX...

Part 5: After leaving the vehicle at the SC for a week, they decided to change out the coax cable running from the camera mount to some ECM. On the first visit, they determined the coax cable was OK. I have no idea how they determined this. I don't know why they ultimately determined the...

The “new” battery won’t actually be new, unfortunately.

2017 MX, running 2023.44.30.14 I thought Service mode offers a HV battery health test under the HV System tab, but I don't see it. I just ran my battery down to 17% after a trip, then went to the Service menu & found no access to the test. Is this feature only for newer vehicles? A different...

Call the nationwide Tesla support number and report the incident. 877-798-3752. That can start the diagnostics process. You'll probably end up in a SC for this. Are you still within the original warranty? If so, it shouldn't cost you anything.

DAS = Driver Assistance System, including autosteer, cruise control and FSD. CAN is a vehicle digital data communication system something like Ethernet but slower. All newer vehicles (for the past 10 - 20 years) have it, certainly any vehicle with OBD-II. You can look the term up in Google...

PART 4: Everything works fine this morning! FSD and visualizations are back. No service alerts like yesterday at 3 PM. Maybe a deep sleep overnight fixed the camera comm issues?? I’ve talked to the SC service manager, and they’ll look at it again tomorrow.

Part 3: After a problem-free drive including FSD this morning, I checked Service mode again for errors & found none. Then, I went out to pick up dinner at 5 PM and had no autosteer, no cruise control, no visualizations. Merde. I went into Service mode & found four errors, two of which are...

An update to my saga with lost FSD functionality and visualizations. At a service center yesterday, the windshield camera assembly was replaced based on their analyses of vehicle data which we can't see. The cameras themselves seemed to be working, but some module in the camera assembly...

It's not necessary to reload software after resetting DAS. Some new information for the DAS errors I was seeing in Service mode. Yesterday, I had my windshield camera assembly replaced because I lost FSD and detailed visualizations. I had limited visualizations in the driver screen, so the...

Outdated map data is your explanation. You’ll have to wait for a map update to fix the speed drop.

I’ve got a 2017 MX with HW3 & FSD running 2023.44.30.8. This morning, I lost FSD (both autosteer & cruise control) plus road visualizations. I tried the two thumb wheel reboot, didn’t help. I looked at the Service mode data, and on the camera page the primary & secondary power for the ECU...

I experienced problems with FSD and HOV lanes a year to two years ago. If I had FSD activated and HOV lane use not selected, the vehicle would not stay in the lane next to the HOV lane. I complained a lot, and that bug finally got fixed recently. More recently, FSD won't exit a left-side HOV...

Under “Navigation”, do you have “Use HOV Lanes” enabled?

I didn't post what I did to fix my problem of the garnish not being attached to the fender. I took off the tire, then disconnected the inner fender liner from the fender and body such that I could peel back the fender liner near the garnish attach point that was disconnected. I looked at the...

That's a good point. I have no idea why all the cameras would temporarily fail. I haven't seen this happen in recent memory.

I observed something today. When I started out, Autowipers absolutely would not work. I also noticed that the FSD icons like Autosteer did not appear, and if I tried to activate FSD, I got an error message that it wasn’t available. After I reached my destination, I did the two-thumb wheel...

Hell no, this isn’t documented anywhere. Nor are all the different alert sounds & what they mean - you have to learn them by experience, which is ridiculous. I’m just suggesting something that appeared to work/help. You loose nothing by trying.

I did too, but mine improved doing what I described.

When in rainy conditions & Autowipers on, try triggering single-wipes repeatedly as the view gets too bad. The goal is that after doing this a few times, the Autowiper algorithm will kick in and start running. It may take a few repeats of this process to see improvement. Mine are working...