I enabled the 80% charge limit from day one (September 2023) and after 159 cycles it is still at 100% maximum capacity.
I think it is also crucial to not allow deep discharge of the battery too frequently. Ideally keep the battery charge in the range of 40-80%. My usage is relatively low so I am mostly within that range.
Infrequently I have charged to 100% for longer days away from home. Enabling low power mode helps to prolong battery life on these occasions too.
“The issue occurred because some files containing positive test results exceeded the maximum file size that takes these data files and loads then into central systems, officials said.”
The Spider’s Web is a documentary film which covers this subject in detail. Well worth watching if you have an interest in finding out more.
“An investigation into the world of Britain’s secrecy jurisdictions and the City of London. Today, up to half of global offshore wealth may be hidden in British offshore jurisdictions and Britain and its offshore jurisdictions are the largest global players in the world of international finance.”
Elixir has the NimbleParsec library which generates parsing code that takes advantage of pattern matching for high performance and low memory usage due to the BEAM virtual machine optimisations.
As I read this, it's basically saying that a battery used for V2G power would spent more time at a lower state of charge which doesn't degrade the battery as fast, to such a degree that this factor outweighs the extra cycles on the pack? Seems like an extraordinary claim - I'd want to see it demonstrated experimentally and not just assumed based on a model (no matter how many times they say the model is 'verified').
I don’t think reducing the effective range of your car to preserve battery life will be very popular; people want the freedom to drive as far as they can, because it’s hard to predict when they will need that capability, and charging is very slow. If someone does have a very predictable routine they can just not overcharge their car in the first place and save the discharge wear.
> people want the freedom to drive as far as they can, because it’s hard to predict when they will need that capability, and charging is very slow
For most people, if they really need to drive hundreds of miles unexpectedly, I doubt spending 15 minutes at a high-speed charger to top up the batteries will be an issue.
As someone who drives an EV, I can tell you that it’s not the long distance trips, it’s having an unexpectedly busy day of errands in cold weather that gets you—realizing that you’re starting out at only 50% charge, which means you can’t make that last trip into the suburbs at the end of the day. There are very few fast chargers in densely populated areas and they’re often malfunctioning, or have queues. They also hurt your battery, so not to be used on a regular basis.
In Norway where chargers are a lot more common, it's not an issue. Of course if I want to charge at 4pm at a popular place it may be a queue but most of the times many chargers are available and functional.
> There are very few fast chargers in densely populated areas
I live in Norway so not a huge issue, and I expect it to get better. Circle K for example is pushing hard to build high-speed chargers at their stations.
For anyone interested in event sourcing with the actor model I've built an open source Elixir library called Commanded (https://github.com/commanded/commanded) which takes advantage of Erlang's BEAM VM to host aggregate processes. There's also an event store implemented in Elixir which uses Postgres for storage (https://github.com/commanded/eventstore).
The actor model provides the guarantee that requests to a single instance are processed serially, while requests to different instances can be processed concurrently. Distributed Erlang allows these instances to be scaled out amongst a cluster of nodes with transparent routing of commands to the instance, regardless of which connected node it is running on.
In Elixir and Erlang, the OTP platform provides the building blocks to host an aggregate instance as a process (as a `GenServer`). Following the "functional core, imperative shell" style I model the domain code as pure functions with the host process taking care of any IO, such as reading and appending the aggregate's events.
> In reality, it's impossible for a households to get a contract that follows market rate, you always pay the same per kWh no matter if it's Sunday or Monday, windy or calm.
In the UK you can use the Agile tariff from Octopus Energy (https://octopus.energy/agile/) which has half hourly dynamic pricing per electricity kWh. The next 24hrs worth of prices are released each day around 4pm and follow market cost. There’s a 12p/kWh surcharge between 4pm and 7pm during peak demand. Used in conjunction with a smart meter it bills per half hour usage and can go negative.
Twice in the last two week’s it has gone below zero due to recent storms. It’s a great tariff if you have an electric car to charge in the early hours when prices are cheapest and can reduce usage during the peak three hours. A home battery would also help out as it could be charged during cheap periods and discharged when prices are too high.
Tony Seba predicts the end of personal car ownership due to the disruption of transportation by new technology (batteries, electric vehicles, autonomous vehicles) and new business models, such as ride hailing and Transport-as-a-Service (TaaS).
Alberto Brandolini’s “Introducing EventStorming” [1] book is worth reading, even in its incomplete state, to understand the approach from its author.
There aren’t too many concepts to understand, it almost feels too simple to be of any value. But in all of the sessions I’ve been involved with participants have come away with a better understanding of the domain and often a useful model to begin working from.
Specialized ANGi is a Bluetooth hardware dongle that attaches to your helmet and will allow a contact to live track your ride (using Specialized’s app on your smartphone) and can also detect crashes and automatically send a text message to a contact. It’s available to purchase on its own or included with many Specialized helmets. I have one on a new MTB helmet after a recent crash on a trail.
I think it is also crucial to not allow deep discharge of the battery too frequently. Ideally keep the battery charge in the range of 40-80%. My usage is relatively low so I am mostly within that range.
Infrequently I have charged to 100% for longer days away from home. Enabling low power mode helps to prolong battery life on these occasions too.