The 7 most common pitfalls about passivation (and how to avoid them)
The 7 most common pitfalls about passivation (and how to avoid them)
Lithium Thionyl Chloride batteries are widely used by IoT developers. The chemistry offers a high operating voltage —stable during most of the application’s lifetime—a high pulse capability, and the highest energy density among primary lithium chemistries. It can operate over a wide temperature range, has proven to be a reliable and long-life solution, and it is also one of the cheapest options, which makes it a favorite choice when building smart devices.
Passivation —a surface protecting reaction which occurs spontaneously in all lithium batteries based on a liquid cathode— is playing a major role in many of these benefits. However, there are always two sides to a coin, and passivation, when not well managed, can adversely affect the operation of the application.
In this article we will go through the most common mistakes about passivation that our application engineers run into when receiving new application design submissions. Most importantly, we’ll discuss what you can do to avoid these pitfalls.
What is passivation?
Passivation is a surface reaction that occurs spontaneously on the lithium metal surface in all primary Lithium batteries with liquid cathode material such as Li-SO2, Li-SOCl2 and Li-SO2Cl2. A film of lithium chloride (LiCl) quickly forms on the lithium metal anode surface: this solid protecting film is called the passivation layer. It prevents a direct contact between the anode (Li) and the cathode (SOCl2); in layman terms, it prevents the battery to be in permanent internal short circuit and discharging of its own accord! It thus enables liquid cathode-based cells to have a long shelf life.
The passivation layer is electronically insulating, which may have some consequences for battery operation. The internal resistance of the cell is enhanced by the passivation layer, which can cause low voltage readings at startup (inferior to milliseconds range). This initial voltage delay is quickly followed by a depassivation stage, during which transport of lithium ions by diffusion through the pores of the passivation layer becomes predominant over initial resistance: cell voltage then recovers to its nominal value under the given load or current applied. The passivation restarts after each current drain interruption.
Passivation is influenced by several factors that will have an effect on the length and depth of the voltage delay such as its electrochemistry, the temperature in the field or the storage duration. The passivation layer builds up over time, and as a consequence, becomes thicker as storage time is extended. A passivation issue will therefore further impact the voltage response after a few months or years in the field. Voltage delay caused by lithium passivation is sometimes underestimated by IoT developers who are startled to see their application not behaving like it should. Let us point out a few of the most common mistakes and what can be done to avoid them.
Pitfall N°1: Trying to reduce your consumption at all costs.
If optimizing your device’s consumption in order to extend its lifetime is your primary goal, be careful not to lower your power consumption so much as to prevent the passivation layer breaking during the current connection. If the main energy consumption current is too low, ions from peak communication current won’t be able to flow through the passivation, which will be too thick, causing the voltage to drop below the cut off voltage and so, a loss of data transmission.
What to do
It will be necessary to find a good trade-off between the application’s lifetime and its discharge rate. The current load must ideally allow for a rapid and efficient depassivation whilst offering the longest possible battery lifetime. If your application requires high current pulses, the initial voltage drop could also lead to a premature end of life. In this case, adding a capacitor to your battery is also an option: The capacitor will store the energy and release it when necessary, permitting a smoother depassivation of the battery.
Pitfall N°2: Not taking into account the field temperature of your application
Temperature has a significant impact on the evolution of the passivation layer. The higher the temperature, the faster the growth of the passivation layer, and the larger the LiCl crystals formed. Conversely, at cold temperatures, the electrolyte viscosity is higher which in turn slows electrochemical and diffusion reactions. The effect of passivation would likely be more visible, especially under high current draw.
What to do
Give some consideration as to where your application will be stored and deployed and which temperatures it is likely to be exposed to. Our application engineers will help you choose the right battery chemistry or adapt your device according to your power needs.
Pitfall N°3: Overlooking the application’s minimal cut-off voltage
As explained above, passivation can induce low voltage readings at current startup. As a result, applications featuring high cut off voltage are more prone to suffer from voltage delay. Voltage recordings below cut-off would likely trigger a "low battery" warning signal or worse, the current charge could be insufficient to break the passivation layer. This would mean that the cell voltage may never be able to recover to nominal values, which in turn could result in a loss of data to be transmitted or a reset of the device.
What to do
Lower the cut-off voltage for each of the application’s components as much as you can whilst being mindful of the current consumption. Indeed, since the power of the battery is the product of voltage and current, reducing a device’s operational voltage will enhance current consumption for the battery, thus imparting a lower lifetime. Again, the key to success will be to find the right trade-off between the application’s lifetime and its discharge rate.
Pitfall N°4: Choosing a battery that is bigger than necessary
Some IoT designers think that a bigger battery will deliver current over a longer period of time. This is partly true. However, for a given average current a bigger battery will be more prone to passivation than a smaller one because current density referring to electrode overall surface area is comparatively lower. And as explained in our first point, a current that is too weak doesn’t allow for depassivation. In effect, the device could very well not start at all and all the battery energy would be wasted.
What to do
Trust our experts to recommend to you the perfect battery construction and size to match your application’s lifetime and power needs.
Pitfall N°5: Not considering the specific pulse requirements in the discharge profile of your application
Two aspects must be considered to evaluate the passivation’s risk: the maximum peak current value AND the pulse’s frequency.
- High pulses applications might be disrupted by passivation: pulses are likely to perturb the crystals of the layer. More active materials will be needed to rebuild the layer after the current’s pulse. Those perturbations of the layer put a strain on the passivation’s effects: voltage drops and voltage delays during the pulse are to be expected.
- Applications featuring long pauses between pulses have more chance of being disrupted by passivation too, as the passivation has more time to rebuild and grow between two pulses.
In a nutshell:
- If your application features high pulses with low frequency; you will be facing a high risk of passivation and disruption of service.
- If your application features high pulses with high frequency, you will have a lower risk of passivation but a high average current, and therefore a high-energy consumption.
- If your application features low pulses and high frequency, passivation shouldn’t be an issue.
- And finally, if your application features low pulses and low frequency, the risk of passivation will be moderate, depending on the exact values and of other environmental conditions.
What to do
Again, it’s all about anticipating your application’s power requirement to find the right trade-off between your consumption profile and the energy load. If your application requires a high and / or a frequent pulse, you might need to design a bespoke energy solution that will offer a sufficient lifetime for your application. If you have a low frequency pulse, then you should evaluate with your battery manufacturer what is the passivation risk and get their advice to reduce it.
Pitfall N°6: Taking the information indicated on the datasheet at face value
We have seen before that passivation is affected by a number of parameters that are specific to each application. No matter how much we would like to, it is impossible to provide all technical information useful for any possible field application of a given battery product within a single datasheet. The pulse levels and current information indicated on a datasheet are fixed values that don’t take into account your application’s specificities.
What to do
Apart from training yourself to become a battery expert, you could alternatively talk to our engineers who will be able to analyze your application’s specific power prerequisites and constraints and apply our 100 years of experience in battery chemistry to recommend you the best options to match your needs. You can also test your application in conditions that are as close as possible to reality, or test the battery by stocking it in a warm environment to make it age prematurely before testing the pulse. The values won’t especially be exact but you will be able to evaluate the overall field behavior of the battery.
Pitfall N°7: Believing that a test at ambient temperature is fully representative of the overall field behavior of your application
Test, test, test, but don’t think that a test at ambient temperature and over a short period of time can replace a real life test over several years. Passivation is a natural phenomenon that evolves over the years and depends on the various temperatures that the application is exposed to. Unfortunately, its aging can’t be modeled or accelerated which leaves too many unknowns for an accelerated test to be 100% conclusive.
What to do
Nothing can replace a real life test of your application, but our application engineers have seen, tested and recommended battery solutions for many applications and can help you evaluate as accurately as possible the effect of passivation in your device.
Forewarned is forearmed! But nothing can replace our experience so do not hesitate to get in touch with one of our experts to ensure the best chances of success for your application!
You might also be interested in this article : The 8 most common pitfalls when choosing a battery for your IoT device (and how to avoid them)