Monday, 2 November 2026

List Sequence Programming for Repeatable Battery Charge and Discharge Tests

Introduction: Repeated charge and discharge profiles come down to three values per step, and understanding how they interact is what makes a test repeatable.

Anyone who scripts battery tests on a programmable battery simulator hits the same question sooner or later: the instrument can change voltage and current, but how does a script express an entire charge and discharge profile and run it hundreds of times without drifting? The answer is sequence logic. A List sequence turns a test plan into ordered steps, each carrying a target voltage, a current direction and magnitude, and a step time, then repeats that block as many times as the run needs. The sections below explain how those steps work together, what step time and loop count actually change, and why clean voltage and current rules matter once a profile starts repeating.

How a List Sequence Turns a Test Plan into Voltage and Current Steps

Start with a familiar plan: charge a portable device up to a target terminal voltage, hold it there, run the device until the terminal voltage falls, rest, then repeat the whole pattern. A List sequence turns that plan into rows. Each row is one state the simulated battery sits in, and each row carries three decisions — the terminal voltage to hold, the current flowing out of or into the simulator, and how long the state lasts. Read that way, a sequence is test logic rather than software code: it describes what the battery terminal does, in order, which is exactly the boundary an automation script needs to control. Step order carries meaning because each step begins where the previous one ends. A charge step that lifts the terminal to a target hands that voltage to the discharge step behind it, and the discharge step decides how quickly the terminal falls back. Treating a sequence as a story about the battery terminal, rather than as a pile of unrelated settings, is the mental model that keeps a profile honest. The MATRIX MBP 2100 series supports per-step voltage, output or input current, and step time directly, with a loop count spanning 0 to 99999 to cover the repetition. Where the sequence lives matters less than what it contains. On the MBP 2100, sequence files can be exported over USB alongside parameter files, CSV logs, and waveform records, so the same step logic can move from a bench setup into a production rack and back again. Writing the profile once and reusing the file is what separates a repeatable test from a set of hand-entered values that nobody can reproduce next month.

What Step Time, Loop Count, and Stop Conditions Change in Repeated Profiles

Not every value in a sequence describes the battery. Step time, loop count, and the conditions that end a run describe the shape of the test itself, and changing any one of them changes what the repeated profile actually demonstrates.

  • Step time sets the pace of each state. A thirty-minute constant-voltage charge step and the same step cut into thirty-second slices answer different questions, because short slices expose transient response while long slices show settled behavior. Step time should match the rhythm at which the device under test really draws on its battery.
  • Loop count decides how many times the whole block repeats. A twelve-step profile run for five hundred loops produces six thousand states in the same order, which is what repetition means in practice. Raising the loop count does not reorder the steps; it lengthens the observation window and reveals whether later cycles still behave like the first.
  • A loop count of zero means infinite repetition. That meaning is documented, and it suits continuous durability work where the host script or the operator decides when to stop. Choosing between a finite count and an endless loop is really a choice about who owns the endpoint of the test.
  • Stop conditions decide how a run ends. A finite sequence finishes when its last full loop completes, while an endless loop keeps going until something stops it. In either case, CSV logs and waveform records captured for each loop let a script developer line up the first cycle against the last.

Underneath those four values sits a single idea: repetition is a promise about consistency, not about volume. A thousand loops of a badly timed profile produce a thousand copies of the same confusion, while fifty loops of a well-paced one produce data worth comparing.

Why Repeated Charge and Discharge Profiles Need Clear Voltage and Current Rules

A repeated profile is only as repeatable as its rules are complete. The voltage rule says where the terminal must sit during each step; the current rule says how much flows and in which direction. Mix those two up, or leave either vague, and the result is a curve that looks plausible once and then wanders on every pass. Most authors settle the voltage rule first, since it describes the state of charge the device cares about, then use current direction to mark the discharge stretch of the same profile. Published material on discharge simulation and cell emulation follows the same principle: a controlled sequence of setpoints is what produces a response someone else can reproduce. Real cells make the job harder. Open-circuit voltage and internal impedance both shift with state of charge, which Texas Instruments covers in its fuel-gauging and battery-modeling material, so a sequence that steps between fixed voltage points is a sketch of discharge behavior rather than a full model. That is fine for what a sequence is for. The practical consequence is that voltage and current values deserve deliberate choices, and step times should stay consistent between loops within the same file. Once the rules are fixed, the profile stops describing one battery and starts describing a class of behavior — which is the thing a script developer can reuse across devices and across production runs.

Conclusion

List sequence programming is less about writing code than about writing down what a battery terminal should do, in order, and how many times it should do it. Voltage, current, step time, and loop count are the four levers, and each one shapes the repeated profile in a different way. Get the rules clear at the start, keep the pacing consistent, and the same file can carry a charge and discharge profile from a lab bench into an automated rack without anyone having to reinterpret it.

FAQ

Q: How does a List sequence use voltage, current, and step time to build a repeated battery profile?

A: Each step holds one target voltage, one current value with a direction, and one duration. Run in order, those steps describe how the simulated terminal moves through the profile; the loop count then repeats the whole block. Change any of the three values and the repeated profile changes with it.

Q: What does a loop count of zero mean in a battery simulator List sequence?

A: Zero means infinite repetition, as documented for the MBP 2100 series. The sequence keeps cycling until the host script or the operator stops it, which suits long durability runs where a fixed endpoint is not the point. Any value from 1 to 99999 sets a finite number of repeats instead.

Q: Why can the same charge and discharge profile require different step times for different portable devices?

A: Devices draw current at different rates, so the terminal voltage moves at different speeds. A short step time suits fast, low-power hardware where transients matter, while a long step time suits devices that settle slowly. Matching step time to the device's rhythm is what keeps the repeated curve readable.

Sources / References

Texas Instruments: Fuel Gauging and Battery Modeling Fundamentals

SWEEP TOOL FOR R&S® NGU201, NGU401 AND NGM200 | Rohde & Schwarz

5992-2597EN_2026-02-28 PDF Asset Page | Keysight

MATRIX MBP 2100 Series Programmable Battery Simulator

No comments:

Post a Comment

Choosing Hidden Door Hinges for Flush Interior Doors at Home

Introduction: A flush interior door needs hidden hinges that keep the reveal even, allow a full swing where the room permits it, and stay ...