- cross-posted to:
- hackernews@derp.foo
- cross-posted to:
- hackernews@derp.foo
Our Chevy Blazer EV Has 23 Problems After Only 2 Months::undefined
You must log in or register to comment.
So they got a lemon and decided to write an article about it… definitely not intended to cause more EV hesitation, of course not.
It should be noted that this car does not yet qualify for Lemon status and qualifying for lemon status is actually harder than the average person would casually think in most US states. So it’s actually entirely fair that they wrote the article, as they do with every car in their long term test fleet. Manufacturers use all sorts of tactics to hide real world reliability data, if you’re looking to them to source it you’re buying your rat poison from the rat company.
Fair
IMO, it’s a chevy issue more than an EV issue. We have a 23 Suburban for work that you can tell they gave zero fucks when assembling.
Yeah, seems like everything is going that way recently.
It’s Edmunds, not GasCarsOnly.com. They’re just reporting on their cars. All those Alfas that everyone bashed a few years back wasn’t to try to convince people not to buy gas cars, just not to buy the Alfa.
Same here. You shouldn’t give GM a pass for their shit tier cars just because they’re EV.
This is not normal for EVs. The only real problems I’ve had with my Tesla model 3 since 2018 was some paint issues and a sticky blinker, which they came to my work and replaced.
It’s sucks that all these companies seem to be trying to screw over their EVs when they are vastly better. I’ve traveled all over the US in mine. I’m currently on another cross country road trip and the charging system just works. 1,300 miles in 24 hours with charging for the first day. Without stopping at all, that’s still a 19.5h drive.
The charging system for Teslas is a lot better than other EVs tbf, having driven a big 3 EV the charging situation is a hellscape since it couldn’t use superchargers
That is, of course, changing soon with other manufacturers adopting NACS.
Yup! Best to wait till then to get one probably
Yep. That’s why I got a Tesla in 2018. It really can go anywhere in the country.
EV’s have lots of problems of their own and they’re far from immune to most issues.
This person’s entire issue is probably due to a bad ECM or a bad/shorting out 12v battery.
Yep. I’ve had my few issues, but there has been way less maintenance.
Sounds like you drive too much.
“Another cross country road trip” - you’ve driven across the country multiple times??
Why not train? Bus?
If you bought an EV to help save the planet, you’re not really helping by driving that much.
The USA does not have train or bus infrastructure. We looked at it but it would take weeks to get home on a train. It’s just not viable, but I wish it was. I take the bus in the city I live in almost anytime I can.
I have driven from Mississippi to Washington when I’ve moved and I’ve driven from MS to Denver during COVID to see friends (we did the whole 2 week quarantine before and took many precautions). I am driving back to see family for the holidays because flying is 2x the price plus dog boarding. We’re bringing our dog so we don’t have to pay the $700+ to do that.
For CO2 emissions: flying 2,000 miles both ways would be 1.2 metric tons of CO2 per passenger (using an online tool I found). We are driving 2,500 miles both ways, and having an extra passenger makes it more efficient per passenger. So for 2 passengers, 5,000 miles in a Tesla is 1 metric ton of CO2 total, which is 0.5/passenger, over half of what flying would do. Sure, I could just not go see my grandpa who has been struggling to breathe and in pain almost daily, but I haven’t seen my family in 2 years, and I miss them.
I’ll be honest, this is less than 20 minutes of just ERROR log lines (nevermind warnings) in the application I’m working on.
Is that bad? Sure. But a large portion is also because it’s over a hundred individual software components and logging has been implemented badly with software that grew over time. Just saying that there’s a log message means ~nothing.
In fact I would argue that if done well, this is the way it should work:
- Display to the user if there’s an immediate problem. Something needs fixing or urgent investigation.
- Persist it to a warning-log if it’s something that’s not bad, stuff all works or redundancy is still holding easily (meaning it’s still redundant, say 1 out of 4 redundant units failed or a component stopped sending diagnostics but is still working), and the next time it’s in for something else, a mechanic/technician can also quickly check whether there’s a real problem.
Here’s to betting you wouldn’t hold this opinion stuck on the side of the highway in the middle of Wyoming or something similar.
What do you mean? Is Wyoming big on electric cars? (No clue, not from the US)
Wyoming contains some of the longest stretches of US road without available services. IE: If you get stuck because your car broke down, you’re gonna have a bad time.
Oh, in that case I might have worded my post badly. I explicitly meant non-critical stuff would make sense to not openly show. There’s so much that can go beepy beep on moder wheeled computers that showing it all to the user would result in needing 10x the telephone support staff.
And there’s a lot that’s perfectly fine to leave as it is, and just have someone look at it the next time it’s in for a check-up anyways.
For stuff where the car can break down, yeah fuck no, don’t hide that. I was mostly musing how to do a shown/hide split in a sensible manner.
This is the second article in as many days describing issues with a review unit.
https://insideevs.com/reviews/701169/2024-blazer-ev-stranded-broken/
