PROFESSIONAL PLANNING & TROUBLESHOOTING SUITE

Make the first project decisions—and the first fault response—with fewer costly assumptions.

Nine transparent tools help overseas operators, fleets, EPCs and distributors frame project requirements, guide a safe connector-release response and classify standard OCPP 1.6 fault categories before qualified service review.

01 / Transparent assumptions02 / Conservative input limits03 / Cost-control prompts04 / Local engineering handoff

Safety scope — planning and first response only

Never force a connector, bypass a lock or interlock, defeat protection, open an energized charger cabinet, or work on live conductors. If there is smoke, fire, arcing, a burning smell, abnormal heat, exposed conductors, collision damage or water ingress, do not touch the vehicle, cable or charger: keep people away and contact the site operator and local emergency services. Final diagnosis and electrical work require the exact vehicle/charger manuals and qualified local personnel.

NINE PROFESSIONAL TOOLS

Start with the constraint—or fault—that matters most.

Every tool states its scope and produces a conservative next-action checklist. Inputs remain in the browser and are not transmitted automatically.

01Site power plannerEnergy throughput · grid headroom · staged deployment 02Configuration selectorAC/DC mix · gun count · site type 03Cable reach checkerPreliminary routing · slack · custom length review 04Payment readinessRoles · network · support · local requirements 05RFQ brief builderComplete buyer requirements · fewer quotation revisions 06Safe unplug assistantStop session · unlock vehicle · release without force 07Connector-lock triageVehicle-side lock · station-side fault · escalation 08OCPP fault referenceOCPP 1.6 categories · ownership · safe next checks 09Incident brief builderExact code · session context · service-ready evidence

TOOL 01 / SITE POWER

Energy and available-power planner

Estimate the average DC energy throughput required during the charging window, then compare it with a transparent model of service capacity, existing peak demand and operating reserve.

Fixed planning assumptions: 0.95 power factor, 92% conversion efficiency and 20% energy-throughput margin.
Existing peak demand is subtracted after the selected service reserve.
Output identifies staged deployment and managed-charging questions before grid expansion is assumed.

Vehicles served per dayAllowed: 1–500 Energy needed per vehicle2–200 kWh/day Effective charging window0.5–24 hours Expected simultaneous connectorsMust not exceed vehicle count Electrical service capacity20–20,000 kVA; use verified service data Verified existing peak demand0–20,000 kW from a representative load study Service operating reserve10–40% preliminary reserve

Unknown existing peak demand is not zero. Use verified service and representative existing-load data with utility and qualified engineering review. Keep proposed upgrades separate from currently available capacity. Compare fleet expansion before and after a planned supply upgrade ↗ · Updated October 24, 2026. A preliminary site fit does not verify each vehicle's charging limit or departure target; check individual vehicle needs too.

TOOL 02 / EQUIPMENT STRATEGY

Charger configuration selector

Build a planning shortlist from operating pattern, simultaneous access, physical constraints and expected growth. The selector does not replace model drawings, a site survey or electrical review.

Separates long-dwell AC demand from time-sensitive DC demand.
Uses simultaneous access—not daily traffic alone—to discuss connector count.
Treats cabinet footprint as only one part of the installation envelope.
Uses observed phase-one demand as an expansion gate instead of assuming a full first-day build.

Site type Typical vehicle dwell time0.5–24 hours Vehicles served per day1–500 Simultaneous charging points1–100; must not exceed vehicle count Installation space Primary connector requirement Unattended public payment Expansion expected within 24 months

Enter required simultaneous access, not just the number of points remaining during maintenance. Four vehicles need access but only two points remain available ↗ · Updated October 25, 2026. This selector does not simulate outages, queues or energy feasibility. Run different dwell groups separately and review combined demand. For multiple points, request exact-model simultaneous-output evidence. Changes clear the old result; no compatibility approval is given.

TOOL 03 / LAYOUT

Cable reach layout checker

Check whether a planned cable length has preliminary geometric margin after routing allowance and handling slack. Standard charging cable is typically 5 metres; custom lengths can be discussed.

Uses straight-line geometry only as a starting point.
Adds user-selected routing allowance and handling slack.
Never approves cable thermal performance, bend radius or accessibility.

Horizontal bay offset0–10 m Charger setback from vehicle0–5 m Vertical difference0–3 m Routing allowance15–40% Handling slack0.5–2 m Planned cable length3–15 m planning input

Check each expected inlet position, then review neighbouring bays occupied together. Separate positive margins do not approve cable interaction or shared access. Two reach results, one combined layout review ↗ · Updated October 26, 2026. Preserve accessible routes during storage, handling and connection. Never improvise extensions or move installed equipment. Recheck changed equipment drawings; unchanged cable length does not preserve an old layout result.

TOOL 04 / UNATTENDED OPERATION

Payment and charging-start readiness check

Identify integration gaps before selecting an unattended payment host. The result is a project checklist, not approval of a payment method or local regulatory position.

Separates charger, operator platform, payment and support responsibilities.
Checks exception handling instead of assuming permanent connectivity.
Helps avoid late integration changes and duplicated hardware.

Connected charging devices1–100 preliminary topology input Customer payment journey defined? Charger/controller compatibility checked? OCPP / operator platform responsibilities defined? Offline and failed-payment flow defined? Receipt, tax and local payment rules reviewed? Customer support and refund ownership defined? Privacy and cybersecurity review assigned?

A missing payment response needs a defined status-check owner and customer message. This checker cannot query or reconcile a transaction. Plan for an unresolved payment result ↗

Treat payment authorization, charging start and first delivered-energy evidence as separate acceptance gates. A pilot result does not automatically cover added devices or changed partners. Review the pilot-to-rollout evidence worksheet ↗ For offline planning, identify the affected payment, charging-backend or local-control path and the journey phase. Which connection is offline? ↗

TOOL 05 / PROCUREMENT

Commercial EV charger RFQ brief builder

Create a consistent project brief that reduces quotation revisions and makes technical boundaries visible. The draft stays in the browser until the buyer chooses to copy or open their own email or WhatsApp.

Prompts for country, site, power, connectors and operating model.
Separates confirmed requirements from items still under review.
Includes certification and schedule without implying availability.

Destination country / city Site / buyer type Estimated quantity Power range Gun count Connector Verified AC input information Charging cable requirement OCPP / platform requirement Payment / authorization Certification / tender requirement Target schedule

Site constraints and notes

Before you request a price: make every bid answer the same brief

Two quotes for the same advertised power may cover different installation, platform, payment and support scopes. Use this original buyer worksheet to record what is confirmed, what remains under review, who will supply the missing evidence, and which exclusions must stay visible during comparison.

Site and supply: record the destination and intended use. Enter AC supply data only when verified by the site owner or qualified electrical professional. Put unverified capacity, simultaneous demand and expansion plans in the notes as “under review”. The requested charger rating does not prove that the site can support it.
Vehicle and layout: list actual connector requirements, bay layout and cable routing. Treat the cable field as a project request, not a guarantee that a standard cable reaches every vehicle. Use the layout checker for preliminary questions; qualified review is still required.
Platform: specify the OCPP version and selected operator platform, not just “OCPP supported”. Ask the supplier and platform provider to agree the required functions and acceptance evidence for the exact equipment and software.
Commercial boundaries: ask each quote to identify included and excluded civil/electrical works, commissioning, connectivity, payment fees, warranty support and delivery scope. State exact tender or certification requirements as requirements; do not mark them as achieved without applicable evidence.

Four gates for a comparable quotation

One frozen input brief: give every bidder the same destination, vehicle duty, charging window, verified supply information, bay plan and required interfaces. Date the brief and identify unresolved items instead of silently changing assumptions between quotes.
One evidence matrix: ask what exact hardware, firmware, connector, OCPP version, CSMS and payment path each statement covers. A protocol name alone is not model-specific interoperability or certification evidence.
One exclusions schedule: make civil works, upstream electrical work, communications, payment fees, commissioning, local approvals, freight, spares and support ownership explicit. Compare total scope, not only equipment price.
One acceptance plan: name the owner and evidence for factory review, site commissioning, backend/payment checks, delivered-energy verification and handover. Final criteria remain project- and market-specific.

Use separate notes lines for delivery, installation, platform onboarding and handover responsibilities. Line breaks are retained in the draft; they do not verify a commitment. Worked example: delivered equipment is not an operational site ↗

Warranty and service scope: record the requested term separately from the supplier's offer. Ask who covers parts, labour, travel and freight, and distinguish response time from repair time. The generator preserves your questions; it does not verify coverage. Build the warranty and service scope request ↗

Certificate evidence and quoted configuration: keep the requested OCPP version and station/CSMS role separate from evidence status. If a certificate attachment names a different product or software version, record the difference and ask for clarification; the generator does not authenticate certificates or establish their applicability. Worked RFQ example: match the certificate evidence to the quote ↗

Illustrative brief: small fleet depot, supply not yet confirmed

Destination: Dubai, UAE. Site: Fleet depot. Quantity: 2. Requested power: “60 kW per unit requested; feasibility under review”. Guns: Dual gun. Connector: CCS2, only if confirmed for the actual fleet. AC input: leave blank until verified. Cable: “layout review pending”. OCPP: “version and platform under review”. In notes, request an initial and expansion option and list who owns the supply survey, layout review and platform tests. These are example buyer inputs, not an engineering design or a promise of model availability.

Review before sending: the generator marks blank optional text fields “Under review”. It does not certify compatibility, select protective devices, approve construction or automatically send the brief. Review the generated text before using Copy, email or WhatsApp. Do not enter passwords, payment-card data or access tokens.

Protocol context rechecked September 17, 2026: Open Charge Alliance OCPP protocols. OCPP standardizes communication between charging stations and central systems; the current OCA page lists OCPP 1.6, 2.0.1 and 2.1. The procurement worksheet above is our guidance, not an OCA specification, interoperability result or certification test.

Create your project brief · Review payment responsibilities · Return to Xiaochong Energy home

TOOL 06 / DRIVER-SAFE RESPONSE

Safe charge-connector release assistant

Build a conservative sequence when a charging connector will not release from a vehicle. The vehicle usually controls the vehicle-side lock; the exact manual-release method is model-specific.

Requires you to confirm charging has stopped before showing normal release steps.
Checks vehicle unlock, Park and cable side-load.
Stops immediately for heat, damage, water, smoke or arcing.

Any danger sign?Smoke, fire, arcing, burning smell, abnormal heat, exposed conductors, collision damage or water ingress Charging-session status Vehicle in Park? Vehicle and charge port unlocked? Cable weight or side-load present? Exact vehicle owner’s manual available?

Do not use pliers, screwdrivers or improvised tools. Do not pull, twist or lever the connector. A model-specific emergency release is a last step only after charging has stopped.

For the manual question, Yes means the official instructions match the vehicle make, model, model year and market; otherwise leave No. A similar manual is not a matched procedure ↗ · Updated October 11, 2026. Unverified instructions block physical-removal guidance. This tool cannot inspect your manual or equipment.

An earlier unlock indication may no longer describe the current state. After a delay, keep unlock Unknown unless presently confirmed under the applicable instructions; do not pull to check or race a countdown. This tool cannot detect a lock change. Review current unlock status after a delay ↗ · Updated October 29, 2026.

A displayed 0 kW does not confirm that the session has ended or the charge port is unlocked. Interpret “complete” using the applicable manual; select Unknown when stopped state or normal unlock is unconfirmed. Keep power, session state and unlock separate ↗ · Updated October 20, 2026. Never pull on the connector to test a displayed value.

TOOL 07 / LOCK-FAULT TRIAGE

Connector and charge-port lock triage

Separate a vehicle-side charge-port lock, a station-side connector lock and a recurring mechanical or control fault before assigning service ownership.

Keeps driver actions outside the energized cabinet.
Removes damaged equipment from service.
Escalates repeated faults with a complete evidence set.

Where is the connector held? Observed condition Visible damage, debris or contamination? Session status Frequency Operator can identify charger and connector?

Any danger sign now?Smoke, fire, arcing, burning smell, abnormal heat, exposed conductors, collision damage or water ingress. Do not approach unsafe equipment to check.

Conflicting station and vehicle reports leave the current session unresolved. Keep session Unknown until the applicable evidence confirms it; this tool cannot reconcile reports or read telemetry. Keep both observations in the handoff ↗ · Updated October 30, 2026.

New: the plug released—does that close a recurring incident? ↗ · Updated October 21, 2026. Keep frequency tied to the existing incident history; record a later release and service disposition separately. This form cannot verify either. Safety gates take priority and edits clear old results. Record the outcome in an incident brief ↗ · Vehicle-side release checks ↗

TOOL 08 / OCPP 1.6 REFERENCE

Standard fault-category reference

Interpret the standard errorCode category carried in an OCPP 1.6 StatusNotification. It is not a universal decoder for charger-screen codes, vehicle DTCs or vendor-specific vendorErrorCode values.

Uses the official OCPP 1.6 category set.
Separates public-safe checks from qualified service.
Does not mix OCPP 2.0.1 component events into OCPP 1.6.

Source of the code OCPP 1.6 category Operational state Has the fault occurred more than once?

Any danger sign now?Smoke, fire, arcing, burning smell, abnormal heat, exposed conductors, collision damage or water ingress. Do not approach unsafe equipment to check. Record existing observations; never retry to answer this form.

A confirmed OtherError with missing vendor detail remains a reported category, not a diagnosis or NoError. Distinguish missing export details from absent message fields ↗ · Updated October 31, 2026. This reference cannot inspect logs or decode manufacturer fields.

Confirm that the category came from OCPP 1.6 StatusNotification.errorCode, not just that OCPP is in use. A received Heartbeat is not a reported errorCode ↗ · Updated October 22, 2026. An online label does not supply a missing category; leave its source Unknown until the record is verified. NoError is not safety clearance. Recurrence defaults to Unknown and edits clear old output.

TOOL 09 / SERVICE EVIDENCE

Charging fault incident brief builder

Capture the evidence a vehicle OEM, charger supplier, operator platform or field technician needs without guessing the root cause.

Records the exact message, time, charger, connector and session.
Adds vehicle, plug, authorization and environment context.
Requires your sensitive-data review; it does not automatically redact the report.

Exact displayed / backend code Source Date, time and time zone Charger ID / model Connector / EVSE ID Session / transaction ID Vehicle make, model and year Approximate state of charge Connector standard Authorization method Weather / environment Visible condition Danger signs now?Smoke, fire, arcing, burning smell, abnormal heat, exposed conductors, collision damage or water ingress. Do not approach equipment to answer. Sensitive data removed?

What happened and what safe actions were tried?

Correcting a connector ID after the report was copied ↗ · Updated October 23, 2026. Editing clears this preview but cannot recall old copies. Explain a verified correction in Notes, regenerate and review before copying again. Record any recipient notification in your approved support system; this tool has no revision history or delivery integration.

OFFICIAL REFERENCE BASIS

Built from primary technical sources.

The release and fault-response logic was checked against official Open Charge Alliance material, charging-network support documentation, vehicle owner guidance and electrical-safety rules. Always use the exact manuals for the installed charger and vehicle.

Open Charge Alliance: OCPP uptime and error reporting ↗ChargePoint: removing a stuck connector ↗Tesla owner guidance: charging instructions ↗OSHA: damaged electrical equipment and qualified testing ↗

MODEL-SPECIFIC REVIEW

Turn the planning result into a verified shortlist.

Send the country, site type, power information, connector, quantity, layout and operating requirements. Xiaochong Energy will review the relevant equipment and identify what still requires local engineering or certification confirmation.