Trent

Texan. EV Enthusiast. Husband. IT professional I love to hang out in the consoles of Cisco equipment. | CCNA

[Trent @talmen]

@MarsHomestead Updates always auto-download if one is available anytime the car is on WiFi. It doesn't install it automatically unless you have that option turned on (or rarely, it will force you to choose an install time if it has a critical safety or recall update included).

[Trent @talmen]

@Tesla Won't be rolling out for cars with Intel MCUs unfortunately.

[Trent @talmen]

Demand charges should not be a thing for DCFC sites. I am aware that some utilities have eliminated demand charges for public EV charging or have a modified demand charge schedule. Though that is for from universal. Demand charges were not made with the type of business model in mind that charging networks use. These demand charges make low volume rural areas hard or impossible to serve. Those are the areas that need DCFC the most to fill gaps in the charging networks. Utilities should only bill for the cost of generation + delivery.

Demand charges make sense for large commercial buildings, warehouses and factories but not for DCFC sites where power is essentially just being resold to EV owners.

[Trent @talmen]

It's from the glycol liquid cooling loop in the cable. V3 and V4 chargers have this in the cable to keep it from overheating under very high kW loads. It didn't come from the car; it came from the charge handle and cable, which get torn apart during this maneuver, breaking the loop and releasing the liquid. That's part of why fixing it costs so much.

[Trent @talmen]

@Avatrode This is the Abilene, Tx supercharger. Since he's towing, I'll give him a pass here. These chargers were not setup to accommodate towing.

[Trent @talmen]

Not possible here. This is the Abilene, Tx supercharger, I recognize it. Hard to notice in the picture but the chargers are in a Target parking lot right up against the freeway access road. There isn't room to pave on the other side as that would be in the middle of the access road.

[Trent @talmen]

@IowaTesla I don’t have it to protect the screen, I have one with a matte finish. Greatly reduces glare and reflections.

[Trent @talmen]

@perlyngemark @minchoi @wholemars I think Ryzen was 2022 (or late 2021) but it wasn't rolled out fleet wide at the same time so depends on your model I think. I have a 2021 Model Y (Jan build date) and it's still the Intel MCU with HW3 autopilot computer.

[Trent @talmen]

@JeebsTX Dalhart is on one of the common routes to Colorado. That's probably why.

[Trent @talmen]

Sadly, around town here, I can never get big streaks due to several circumstances that I still have to disengage for... eg. dip in the road the car does not slow down for in my subdivision that it absolutely needs to slow down for unless I want to have premature suspension maintenance or a parking lot where it routinely tries to enter through the "exit-only" driveway. Those are not the only things. While FSD 14.1 Lite (HW3) is very good and performs much better then v12, I still have to disengage it somewhat frequently for stupid little things which mostly tend to be mapping issues.

[Trent @talmen]

@FrunkToTrunk @SoCalRuss1983 If it doesn't show up in the map, it's because it's not a part of the destination charger network. It's a program the owner has to join. But there is nothing stopping anyone from just buying a wall connector and installing it.

[Trent @talmen]

Not all Destination chargers are free, it's up to the charger's owner if they want to have a fee and what it is. There was a destination charger at a hotel in Athens, AL that was set to $0.75/kWh. A ridiculous amount of money, considering there was a cheaper Supercharger across the street.

[Trent @talmen]

Overall, 14 Lite is vast improvement over the previous version, except for one big regression, my car was experiencing sudden and jarring brake stabs on the highway. It would only happen about once every 20-30 min for me and seemingly at random. Couldn't not correlate a cause or pattern to any of them. It does not happen in the city though. The events were very brief, the car usually correcting itself before I can even react to take control back, but they are still strong enough to be jarring and uncomfortable.

I had one notable event though. I've had many brake stab events on v14 on the highway but one time (and has only happened one time so far), the brake stab was actually so aggressive that it disengaged FSD and I got the red hands/take over message and alarm.

I have had passengers ask me to turn FSD off because of the brake stabbing. Such a dumb bug to sour an otherwise stellar update to FSD for HW3. I did see that it looks like an update (14.1 lite) went out to early access last night and early consensus seems to suggest that the brake stabbing and accelerator surging (which I haven't experienced much of) seems to be improved.

I also want to note, on the later versions of v12, I never had any significant unexplained phantom breaking so this behavior is completely new to me on 14 lite.

[Trent @talmen]

@JonBbC_TechGeek What about the random break stabbing? That was new in 14 lite. I rarely if ever had any break stabbing events on v12 but now I can't go more then 30 or 40 minutes on the highway without a jarring break stabbing event.

[Trent @talmen]

v14 lite is definitely a big step up. In almost all scenarios, it works better then v12….. Except now it random break stabbing on the highway. That alone almost makes it uncomfortable to drive with other people in the car. They don’t like it and I quickly get requests to turn it off when it does that. They need to get that fixed. That issue alone has soured some of my friends opinion of FSD when they ride with me… which is sad because aside from that, it’s so good. I’d hate for their impressions of good system to be ruined by an otherwise stupid bug.

[Trent @talmen]

@courtneyknill @bdactual I don't know, I'm a night owl. I prefer to be active in the evenings and night but I'm also pro permanent-standard time.

[Trent @talmen]

@bkhottakes Must be an older map. Taylor County, TX has 3 Braums and we have now for over a year now. Map shows 0.

[Trent @talmen]

@ScottTArcher It's $200/yr. The $400 fee is for new cars if they get the 2yr registration... have to pay for 2 years of EV fees up front.. so $400. At the annual renewal though, its $200 EV + Standard Reg Fee. Mine is ~$275/yr.

[Trent @talmen]

The only frustrating issue I've really had with HW3 the last couple of months now is speed control.

I wish there was an easy way to report incorrect speed mapping data with Tesla. I've been manually disengaging to trigger the report feature but that hasn't seemed to do much or really anything... even after making several reports on the same roads. Oddly enough, my speed control issues only seem to occur on roads posted 50+Mph where the speed profiles kick in.

There are several rural state and US highways around here in Abilene where the maps and car think the speed limit is 60Mph when it is actually 75Mph. I can't use FSD on those roads due to FSD maxing out around 60+65Mph which then creates a backlog of cars behind me and then I have to manually disengage or intervene to get the car to go the speed limit. Also creates inaccurate trip planning SoC values since the arrival SOC is calculated with that slower speed limit.

I also don't know where it's getting that 60Mph value from at all. All other maps (Google, Apple, even Bing) seem to all have correct speed limits set. They all even recognize the recent reduction of the speed limit on TX Loop 322 that TXDoT lowered a month ago from 75Mph to 65Mph. Ironically, for that highway, the car still thinks it is 75Mph even though all other mapping apps I use have updated to show the new 65Mph limit already. I've reported that one too through the disengagement reporting feature.

Around the city though, it's been mostly ok. I do have to navigate and park manually most of the time. That doesn't bug me though. I know officially that 12.6.4 doesn't support parking lots and parking.

[Trent @talmen]

@NVIDIAGeForce #RTXOn