The practical answer.
Commission the actual battery and charger as a versioned pair, including the approved charging profile and any hardwired or communication-based authorization. A matching connector, nominal voltage or CAN label is insufficient. Record how charging starts, follows permitted limits, stops and handles unavailable data, then release only the vehicle configurations covered by the evidence. A handshake is an interface contract; it is not always CAN and is not proof of universal lithium compatibility.
Identify the exact charger, profile and battery pair
Begin with charger model, serial identity where relevant, hardware and software revisions, and the selected approved charge-profile identifier. Record the corresponding battery model and configuration. A voltage-family name such as 36V or 48V does not identify chemistry, charge termination, temperature restrictions or the full permitted operating window. Preserve the actual approved specification rather than translating a familiar label into an assumed charging voltage.
Delta-Q's IC Series documentation describes optional CAN integration and configurable charging approaches. Its algorithm guidance also limits the intended users and warns that an unsuitable battery and algorithm combination can perform unacceptably. These are reasons to use an authorized, documented selection process, not instructions to download a profile or change charger settings independently. This article does not claim that a specific Delta-Q product or algorithm is compatible with a Jetray reference.
Define the authorization sequence without assuming one universal protocol
A charging authorization can be communicated through an approved physical control interface, a documented protocol or another specified architecture. If CAN is used, its physical connection does not establish matching messages. The responsible suppliers should agree message identifiers, units, scaling, timing, validity, timeout behavior and any required state sequence. Do not invent a protocol from a connector pinout or assume that different devices interpret a field named current in the same way.
Separate connection detection from permission to deliver energy. Identify what makes the charger ready, what battery conditions allow charging, what limits are requested and which measurements confirm the actual behavior. State which component owns each decision. The purpose is a reviewable interface contract for the proposed installation, not an assertion that every lithium battery needs the same handshake or that optional communication makes an otherwise incompatible charger appropriate.
| Review item | Normal-state evidence | Exception-state question |
|---|---|---|
| Identity and profile | Exact charger, battery and approved profile versions | What changes require a new review? |
| Authorization | Documented connection and charging-permission states | What happens when permission is absent? |
| Limits | Requested and observed values with correct units | How are reduced or zero allowances handled? |
| Communication if used | Protocol, validity and update contract | What is the approved response to stale or missing data? |
| Fleet release | Vehicle group and signed configuration baseline | Which units remain outside the evaluated scope? |
Review interruptions and limits before an acceptance demonstration
The responsible teams should specify behavior for a known zero charge allowance, a stale message, an interrupted connection and an applicable protective condition. Those states are different and should not all map to a silent retry. Define the approved recovery procedure and any service involvement. This article does not prescribe fault timing, authorize protection bypass or direct operators to disconnect charging equipment during normal fleet use.
Perform any fault-simulation work only through the qualified team's approved validation setup. A charger display can show a broad state while the battery-side current differs from an assumption, so measure the quantities that answer the actual test question. Record both the requested limit and the observed result where those data exist. A green completion symbol is useful only with a defined meaning and evidence that the evaluated battery and vehicle state satisfy the released requirements.
Freeze a pilot record before repeating the configuration
Use a pilot to establish a controlled baseline, not to imply that every visually similar cart is covered. An illustrative fleet might contain one group with a documented charger version and another with an older replacement charger. Approval of the first group would not automatically cover the second. The actual grouping, sample plan and acceptance criteria must be set by the responsible vehicle and battery teams using the fleet's real configurations.
The record should connect the vehicle, battery, charger, profile, installation and relevant software versions to the results. Preserve operating conditions, charging observations and unresolved items. If repeated use is part of the approved evaluation, retain those records rather than selecting one favorable cycle. The cited Delta-Q guidance is product-specific; it must not be converted into a universal number of cycles that qualifies every battery or replaces the project's full release criteria.
Preserve serviceability after the first successful charge
State how the approved pair will be recognized in receiving and maintenance. An apparently equivalent replacement charger can introduce a different profile or communication behavior, and a revised battery may change the documented interface. Agree how substitutions and software updates trigger review. Service staff should have released instructions, not a copied button sequence from an unrelated internet example or an informal assumption that the last used profile is correct.
For Jetray, the 36V published battery reference is distinct from the 36V LiFePO4 evaluation and the 48V-class system inquiry. Treat all related links as starting points for current model-specific information. Send the actual charger identity, profile, vehicle information and interface questions to [email protected]. Request documented compatibility for the proposed assembly and keep battery acceptance, vehicle release and commercial warranty as separate evidence-based decisions.
Frequently asked questions
Does a charger labelled lithium work with every lithium battery?
No. Chemistry, series arrangement, permitted voltage and current, temperature restrictions and control behavior must be matched to the actual assembly. A broad category label or familiar plug is not a controlled compatibility statement. Obtain the responsible suppliers' approval for the proposed pair.
Is CAN communication mandatory for a lithium conversion?
Not universally. The approved architecture determines the interface. Where CAN is used, the devices still need an agreed protocol and validated state behavior. Where it is not used, the responsible teams must define how the intended charging permissions and limits are implemented and verified.
Can a fleet repeat a successful pilot without further configuration checks?
Only the configurations covered by the released approval can be treated as covered. Confirm that vehicle, battery, charger, profile and relevant software match the baseline. Differences require the responsible team's assessment; this article does not establish a universal interchangeability rule or a fleet certification.
Sources & further reading
- Delta-Q IC Series: optional CAN and charger integration documentation ↗
- Delta-Q: IC Series charging-algorithm use and authorized-party conditions ↗
- Jetray original product and application navigation ↗
Prepared from primary technical sources and original engineering analysis. All numerical scenarios are hypothetical planning examples, not Jetray measurements, customer cases or verified product ratings. Catalogue links are evaluation references; exact application suitability and approval require documented project validation.
Prepared for the golf cart battery projects collection. General engineering guidance does not replace a model-specific datasheet or application validation. Source review: 5 November 2026.