Scope and operating assumptions
This note addresses temperature-boundary protection in series-string LiFePO4 (LFP) traction packs of the kind retrofitted into Club Car or E-Z-GO chassis for golf and light utility duty, where seasonal storage and outdoor charging expose the pack to cold mornings and hot afternoons. Vehicle models, regions and OEM electrical architectures differ, so nothing here asserts fit, chemistry or authorization for any specific vehicle or pack, and no model-specific LFP data is implied. The scope is the control chain — sensed cell or pack temperature, protection decision, actuation of the charge path or load path, and the recovery condition — together with how a service team should interpret the associated telemetry. Two general, documented principles anchor the discussion: charging lithium cells at low temperature drives lithium plating, which permanently degrades performance, and both charge and discharge are only permitted inside a defined temperature window. Exact setpoints are product-specific and remain unspecified here; one manufacturer's published illustration is used only to illustrate mechanism, never as a JTM figure. Pack opening, energized wiring and protection bypass are out of scope.
Working principle and control logic
The protection loop is causal and observable:
- Measured input: one or more temperature sensors report cell or pack temperature in degrees Celsius to the battery management system (BMS). Sensor placement matters; surface or busbar sensors can lag true cell temperature during fast thermal transients.
- Decision: the BMS compares the reading against a charge-permission window and, separately, a discharge-permission window. These windows need not be symmetric. A documented stationary-LFP illustration permits discharge over a wider cold range than charging, which charges only above a positive lower limit — reflecting that plating risk is specific to the charging direction.
- Output/state change: when the temperature is inside neither charge window, the BMS withdraws the charge-permission signal or opens the charge path; when the discharge boundary is crossed (classically at the hot end, and in some designs at extreme cold), it disconnects the load. Well-integrated systems route this through a remote on/off or enable line so the charger or load is commanded off rather than merely blocked at the pack terminals.
- Release or recovery: permission returns only when the sensed temperature re-enters the allowed window, usually with a hysteresis or delay so that a sensor hovering at the boundary does not chatter the contactor or enable line. Recovery is therefore a temperature event, not a timer or a manual reset, unless the specific design adds one.
The mechanism behind the charge inhibit is electrochemical, not merely conservative policy: charging at low temperature can deposit metallic lithium on the anode instead of intercalating it, a degradation that reduces usable performance and is irreversible in service. That is why the inhibit is directional — a pack may still be allowed to discharge in conditions where charging is forbidden.
A second, related behavior matters for interpretation: in some architectures the state-of-charge (SOC) percentage shown to the operator is computed in an external battery monitor, not inside the pack, and at low temperature the display may not track actual available energy. In that documented arrangement, watching cell voltages during cold discharge is the more reliable indicator of remaining margin.
Parameters and interfaces
- Temperature (°C): the controlling input; note whether telemetry reports one pack value or multiple cell-adjacent sensors, since a single sensor can miss a local cold or hot spot.
- Charge-permission signal (logical enable, e.g. a remote on/off line): asserted only within the allowed charge window; its state, not the operator's intent, governs charger output.
- Load-disconnect state (logical/contactor): changes when the discharge boundary is crossed; recovery follows temperature re-entry.
- Hysteresis/delay (°C and seconds): the gap between trip and release thresholds that prevents oscillation at the boundary; values are design-specific.
- SOC (%) and cell voltages (V): when SOC is monitor-derived, treat it as an estimate whose accuracy degrades at temperature extremes; per-cell voltages remain direct measurements and are the better cold-weather reference.
- Communication links (such as CAN or Bluetooth app connections) may carry these values; the logged samples are the evidence, the transport is not.
No JTM-specific thresholds, identifiers or pinouts are asserted; a source manufacturer's numbers are not JTM specifications.
Verification and fault diagnosis
Safe verification uses logs and observation, never intrusive testing:
- Confirm directionality: on a cold morning, a pack that powers the vehicle but refuses or terminates charging until warmed demonstrates the expected directional inhibit, not a charger fault. Distinguish this from a charger-side fault by checking whether the charge-permission state and temperature reading move together in the log.
- Correlate state changes with temperature: plot permission state against sensed temperature across a warm-up. Clean transitions with a stable gap between trip and release indicate hysteresis working as designed; repeated rapid toggling near one threshold suggests a sensor at the boundary or a noisy measurement.
- Treat a stalled SOC during cold discharge with caution: if SOC is computed externally, compare per-cell voltages; voltage decline under load, consistent across cells, is expected, while one cell diverging sharply points to a cell-level constraint rather than an estimator issue.
- After any deep discharge event, prioritize recharge and minimize time spent depleted — documented practice for lithium packs — and check that the next charge completes fully rather than repeatedly, since balancing commonly occurs during a completed charge with adequate time at voltage.
Limitations
This note describes general, evidence-supported mechanisms; trip temperatures, hysteresis, sensor counts and interface details vary by product and firmware and require the applicable product documentation. Field logs establish behavioral consistency, not certified performance or capacity. The SOC-caveat applies specifically to architectures where estimation is external; packs with internal estimation behave differently. Charger negotiation, heater control and balancing strategy are addressed only where they interact with the temperature-permission chain.