""" During regenerative braking, Tesla will still activate the brake lights when the vehicle is slowing down, even if the brakes aren't being used at all. Tesla determines whether to turn on your brake lights based on your vehicle's rate of deceleration. If you're unsure if your brake lights are on, look at your Tesla screen, the car in the display shows the brake lights lit up when the brake lights are activated. [0] """
[0] https://www.notateslaapp.com/tesla-reference/1051/how-tesla-....
In fact it looks like the new standards are going to be defined by the rate if deceleration regardless of the means used to do so. Which means basing the lights on an accelerometer is the most reliable way to meet the spec. It shouldn’t matter how you are slowing down, just that you are.
Showing a speeding vehicle behind you that you've lost control and should slow down is well within the conops of brake lights.
I believe the poster is asking why do we need another sensor to achieve that goal? We already have a speedometer based on wheel motion. A trivial computation gives acceleration.
Redundancy is a good thing. Do we feel manufacturers are cross-checking accelerometer with the speedometer? If not, there is no redundancy gained.
On the other hand, if your speedometer is faulty, or not working, you'll know pretty fast. If your dedicated accelerometer is faulty, you might have no idea what your brake lights are doing in the back.
Dunno; it just feels "we need to know acceleration, let's add an accelerometer" is a non-imaginative, add-cost, add-complexity idea. Again, if we think ABS and speedometer and the new accelerometer are being cross-checked and sanity-checked, awesome, but I'm just a bit cynical of that, compared to adding the 3rd thing to do the same thing.
You're on a forum where a lot of people think Kubernetes is a good idea.
;-)
However, Kubernetes is actually incredibly complex. It's powerful, but holy hell does it add complexity. And yet it's basically a buzzword and people are using it in very basic scenarios that don't call for the complexity that Kubernetes adds.
So that's where my joke comes from. There are people that behave as if adding unnecessary complexity is a feature.
I'm assuming you read the context of loss of traction being a requirement.
A $9000 repair bill in 6 years when your mechanic tells you “Sorry your car is immobilized and won’t start, the deceleration brake light sensor went and we need to remove the motor and 3/4 of the wiring harness to replace it”. And for anyone who thinks I’m being sarcastic, try owning a BMW or an Audi and you’ll know it’s the truth.
That's an dishonest argument (perhaps not intentionally). NOTHING is "pennies" to a consumer when it comes to repairing a vehicle. More frequently, you pay $1,500 in labour and parts to replace something that costs "pennies" in some bulk manufacturer wholesale catalogue.
Modern cars are getting more and more awesome, in terms of safety and convenience; but the sticker shock when going to dealership for repair is also becoming bigger and bigger, and it absolutely is intertwined with the significant effort to make 3rd party or even self-repair difficult to impossible.
So again, IFF this is an easily replaceable part that is thought-through and cross-checked intelligently with other existing sensors, brilliant. But can you at any level understand my skepticism that any of these are true? :)
Because the car doesn't precisely know the wheel's radius. The radius depends on the rim, tire, and tire pressure - and the car's operator may have accidentally or deliberately chosen something unexpected for any one of those 3 parameters.
The operator would also experience an incorrect speedometer. For the purposes of a brake light it'd be off (either lighting up too soon or too late) by some amount but I imagine it'd be "close enough" except for the most pathological cases of tire sizes.
In any case, with standard gas/brake pedals on ICEs, I can barely tap the brakes and have my brake lights turn on without any deceleration on my part, or I can do that and still be pressing the gas and so actually be accelerating with my brake lights on.
Edit: Or is detecting deceleration more sensitive? I guess I don't know how precise it needs to be relative to how precise a speedometer needs to be.
Changing wheel size enough to affect readings of speed does not change the broad slope of the derivative of wheel speed.
There you go, you answered your own question. When it comes to safety features, "almost" always working isn't really good enough.
Later a second light was added for the taillight but they did it in the same bulb.
> I know electric cars don't have to creep like an automatic ICE
They don't have to, but funny enough, it's an option in a Tesla. My wife uses it simply because it's what she's used to.
When slowing down with regenerative breaking it triggers the lights basin on how fast it’s slowing down.
So if it’s just a tiny bit (slowing from 35 to 30 over a few seconds) it won’t kick on, but from 70 to 35 over a few seconds would.
I drive a Jeep Wrangler and between its manual transmission and the fact that it's less aerodynamic than a cow, I can and often do slow from highway speeds to ~25 MPH without touching the brakes. It's never been an issue.
I don't think that's the usual expectation. Maintaining absolute braking distance is what railways do, whereas cars commonly operate on relative braking distance plus a safety margin accounting for your reaction time.
Over here, both driving schools and other general road safety education talk about keeping 2 seconds following distance (or half your kph-speed in metres, which corresponds to 1.8 seconds following distance), and traffic engineers commonly give the capacity of a single lane of traffic as 1800 vehicles/hour, which again corresponds to 2 seconds distance (this time as measured vehicle front to vehicle front, instead of tail to front of following vehicle).
This sounds like a recallable defect in the OP’s car’s software.
It's really annoying to signal something to others that you don't intend.
I think there are a bunch of things tesla does that prevent you from being a good driver.
some examples:
- you can't flash your headlights (unless you traverse menus on the touchscreen)
- you can't set the wiper interval
- quickly turn on the defrost?
- turn on the hazard lights? (you should google it, it's funny)
newer cars go even further - no stalks, touch controls for turn signals, horn and wipers on the steering wheel
My 6 month old Model Y has a dedicated button for hazard lights on the ceiling.
I can flash lights by pulling the left stalk (I forget if forward or backwards).
Wiper interval I do miss but what I usually do is either hit the wiper button once on the stalk and set via screen or use the voice interface to say “wipers speed 1”.
Can’t you turn defroster on with the voice interface too?
You can flash the high beams which is good enough, IMO.
> - you can't set the wiper interval
You absolutely can. In my Model 3, if I press the button on the left stalk, it makes the wipers wipe once and shows the wiper options on the screen. I can set them to Off, Slow, Medium, Fast, and Auto.
The only exception is when the car is on Autopilot. Then, it's forced to be Auto. The quality of Tesla's auto-wiper software is questionable, though.
> - quickly turn on the defrost?
There's a button for that now.
> - turn on the hazard lights? (you should google it, it's funny)
? It's a button above the mirror?
Yep. FWIW, Hazard Lights is the one control that is mandated to be a physical button by US law.
flashing high beams at night is a good way to set people off and wind up in a road rage incident. some people interpret that signal very aggressively and will retaliate.
I totally agree, when you are decelerating at more than x/(m|k)ph light should come on.
On a different matter, first generation car, and there is a huge flaw with a high percentage of Ioniq5/Ev6/Genesis GV, have a ICCU (Integrated Charging Control Unit) failure at around a year of ownership. My car at the dealer for over a month without an ETA on part delivery :(
I don't watch TC because the padding doesn't come across as entertaining to me; it feels like a lot more beating around the bush. There's a _lot_ of repetition.
This isn't even the worst example, because the additional content is at least part of the entertainment (even if not the most efficient).
Padding is par for the course among Youtubers. If you play a lot of video games, you'll notice this, because gaming news and tutorials are often done on Youtube.
There are a couple of different thresholds for algorithmic promotion and monetization - I believe 10 minutes is the biggest one - so a lot of videos are padded with filler content just to make the threshold.
You'll also see it on videos for "how to pronounce ______", because they can't monetize below a certain threshold, so they'll pad it with useless filler in order to make the video over 30s long.
Content follows the money. Even if it’s anemic like YT, it’s still a lot more than zero.
In the video, he researches relevant laws in the EU and US, and explains the details and implications of those laws. He compares to previous solutions from another manufacturer, GM, and also personally verifies that his car's automatic cruise control mode does properly use brake lights, and also shows how that is following the letter of the law.
There is no cruft in the video, just a lot of densely packed content. Yes you can summarize the video in a few sentences, but you miss out on a lot of the details.
This might be a hot take, but if you're actually paying attention to driving it's not exactly difficult to see a vehicle decelerating in front of you, brake lights or not.
So while my brakes aren't on the whole time, they are on when I first make myself a problem that needs to be managed.
What? No, you put in the clutch, pull out of gear into neutral, rev match up to the engine speed for the lower gear, plop the shifter into it, release the clutch. What do you use the friction brakes for? Hell, you can skip the rev matching completely if you don't mind clutch wear and jerkiness.
Deceleration threshold is great solution because it signal what is happening.
When we cross the Cascades or Rockies in our Land Rover Discovery towing an Airstream, we have to shift and engine brake on the downslope for miles (to avoid overheating the breaks) and it's noticeable that the trailer brake lights go red, while the Land Rover doesn't unless I tap the brake pedal.
Indications that the car in front of you is breaking include brake lights, distance between you and them, and weight transfer to the front (nose down, rear up). Only one of those is affected by the thick pedal.
What law says that?
https://oregon.public.law/statutes/ors_811.495
> A person commits the offense of unlawful coasting on a downgrade if the person is the driver of a vehicle on a downgrade and the person coasts with the gears or transmission of the motor vehicle in neutral or with the clutch disengaged.
However, this only refers to going downhill. It says nothing about approaching a red light or any other scenario where you might consider choosing to coast.
I ride a motorcycle and I give Teslas a lot of cushion when riding behind. They're common enough in the bay area to be treated specially, because of the one pedal driving (my car is set to "creep", but it is still strong at 70mph).
The way the car changes speed and the way the Model S looks from behind, it takes a bit of time before you realize it is getting too big in your PoV without lights coming up, particularly as people lift off through turns or highway onramps.
The cars which are bigger or higher up like an ID4 or Rivian seem to not suffer from this sort of "hidden width" that the Tesla has, the wheel flares melt into the backdrop when looking at it.
I don't think Technology Connections is ever going to drive a Tesla or test it, but the low profile fast cars are much harder to figure out speeds off from parallax without the brake lights.
This was also an issue when I had a larger manual car with a medium size (4.6l) v8.
At lower speeds <45mph, it was entirely possible for me to be significantly decelerating using only the engine, where I would make sure to at least flash my brake lights several times.
Do the brake lights come on if you don't have the accelerator depressed at all?
Why do a recall? Sounds like it's a simple software fix. Can be deployed over the air.
Which is why it's so annoying when Tesla recalls hit the news. So many people treat it like a huge event, when really, it's just a small software update.
- He owns a 2022 Hyundai ioniq 5, USA version
- The brake lights generally work fine, however when in one-pedal mode (i.e. accelerator does regenerative braking for the first X% of travel) they only activate when the vehicle is about to stop so long as the driver has the accelerator ever slightly depressed
- This is a problem because the regenerative braking is quite strong - he goes from 60 mph/96 kph to 0 in 13 seconds and the stop lights never illuminate
- He thinks this should not be allowed and Hyundai should recall the cars to fix this
- However, in the US this is perfectly legal - regenerative braking is not considered as part of the "service brake", so illuminating the stop lights is not required
- The EU on the other hand just fixed this gap in the law in March, by requiring that stop lights be illuminated whenever the deceleration exceeds 1.3 m/s^2