comemso
Contact
Product Finder
Applications
Start with the decisionApplications
Vehicle and charging station
EVSE ManufacturersOne test path for every charger firmware release.EV TestingVehicle, EVCC and charging-release validation.EVSE TestingCharging-station development through field operation.InteroperabilityReal EV and EVSE in one synchronized test record.
Battery, MCS and EMC
BMS TestingCells, sensors, balancing and controlled faults.BMS + EVCC + OBCValidate the interaction of battery, charging controller and on-board charger.MCS TestingCommunication, signals, cooling and megawatt power.EV Charging EMCKeep charging communication observable under EMC stress.
Production, commissioning and calibration
EVSE End-of-LineRepeatable acceptance and unit-level results.Commissioning & Field ServiceCommission, diagnose and verify installed chargers with an EV charger tester.Calibration & MetrologyTraceable energy verification at the charging point.
Products
Start with the decisionProducts & PlatformsProduct Finder
EVCA
EVCA PlatformCommunication, interoperability, high-power, MCS and EMC paths.EVCA ComOnlyFocused charging communication testing.EVCA Multi MobilePortable laboratory and field analysis.EVCA InteropAnalyse interoperability between a real EV and EVSE.EVCA FlexModular high-power testing and controlled faults.EVCA MCSMegawatt charging communication, low-level signals and system testing.
Easy Chester
Easy Chester PlatformEVSE production, commissioning, service and calibration.Easy Chester MicroWallbox tester for AC chargersEasy Chester UltimateDC fast charger tester (AC/DC)Easy Chester CalimeraAC and DC EVSE calibration systemEasy Chester EOL / EOL HPCEVSE end-of-line production tester
Battery, software and EMC
Battery Cell SimulatorBMS testing from compact bench to high-voltage HiL.SmartCal calibration (accessory)Automated calibration and adjustment of the Battery Cell Simulator.EMC LinkOptical charging communication through the chamber boundary.
Software
Start with the decisionSoftware Capabilities
comframe and integration
comframeThe test software for every comemso system.Integration & APIsREST, Python, CI/CD and laboratory orchestration.Protocol & Domain ModulesSelect released domain depth.Capabilities HubConnect the capability model across EV, EVSE and BMS testing.EVCA Capability HubExplore the detailed EV charging capability stack.
Analyse and test
Conformance Test LibrariesReleased executable test logic, verdicts and evidence.Automated Standards AnalysisMeasured behaviour, normative context and highlighted deviations.Professional SimulationConfigure nominal, boundary and non-conform behaviour.Manipulating GatewayTest a live correction hypothesis between real partners.
Reproduce and automate
Charge PlaybackReproduce the charging partner for the DUT.Charge Cycle AutomationTurn saved configurations into repeatable campaigns.
Knowledge
Start with the decisionStandards & Knowledge
Standards and test logic
Charging, Safety & EMCCharging behaviour, field safety, editions and test boundaries.ISO 15118 explainedParts, -2 vs -20, Plug & Charge and AFIR dates.AFIR for EV ChargingRegulation, responsibility and verifiable evidence.NACS (SAE J3400)Charging communication tests for the North American Charging Standard.UL standards & EVSE field safetyUL requirements and electrical safety checks at installed charge points.
Methods and terminology
Knowledge CenterTechnical explanations, methods and application guidance.GlossaryStable charging and BMS test terminology.EVSE Calibration MethodsCompare controlled real load and reference measurement.Testing a wallboxProcedure, standards, limits and test report for electricians.Battery Cell SimulationCells, balancing, faults, precision and BMS HiL.
Documents and tools
Resources LibraryCurrent brochures, webinars, guides and checklists.BMS testing whitepaperTemperature, environment, simulation and test wiring.EVSE Inspection GuidePractical commissioning and inspection workflow.Charger Uptime CalculatorEstimate downtime and field-service impact.Technical newsletterChoose product updates and events relevant to your tests.
Company
Start with the decisionCompany
Company
About comemsoEngineering purpose, history and operating companies.Development & manufacturingShort paths from development to system testingQuality & CertificationsManagement systems, validation and calibration evidence.Customer ProofNamed stories, endorsements and published configurations.SustainabilityEnvironmental management and measured progress.
People and network
Customer Care TeamDelivery, commissioning, training and support.Sales PartnersRegional commercial and service access.CareersWork on deep e-mobility testing.
Updates and contact
News & EventsProjects, releases, webinars and company updates.Request a technical demoDiscuss your test task with the comemso team.ContactSales, support and locations in one place.

North America

How do you test NACS (SAE J3400) charging communication?

Define whether the vehicle or charging station is the device under test, then agree the interface, protocol and edition used by the project. Exercise connection, negotiation, charging states and supported faults while recording communication and electrical responses together. A NACS coupler designation alone does not identify every application-layer test case or the tests it needs.

Test area and results

Test areaWhat to define or record
SAE J3400SAE J3400_202409, revised September 30, 2024. Coupler requirements for DC or single-phase AC; identify the edition and operating mode in the recipe.
Coupler and adaptersConfirm physical interface, ratings and adapter scope.
CommunicationDefine protocol profile, operating modes, message sequence and timing.
Vehicle DUTSimulate the charging station and observe the vehicle response.
Station DUTSimulate the vehicle and observe the station response.

SAE J3400_202409 covers physical, electrical, functional, safety and performance requirements for a coupler supporting DC or single-phase AC. Use the actual protocol/service and selected edition to define communication cases. [1] SAE J3400_202409 scope and edition

A repeatable test workflow

  1. Define the connector path. Record inlet, cable, coupler and any adapter, together with ratings and the applicable J3400-family documents. Keep AC and DC operating modes distinct.
  2. Choose the DUT and communication profile. Select station or vehicle as the DUT. Record protocol, supported services and authentication mode instead of inferring them from the connector name.
  3. Establish a mode-specific baseline. Run connection, negotiation, charging and stop with the agreed counterpart. Capture signals, messages and available electrical measurements.
  4. Exercise interface boundaries. Use the configured supported limit changes and interruptions. Where an adapter is included, record its identity and verify the approved connection and operating conditions.
  5. Review the results by layer. Separate coupler/adapter evidence, communication verdicts and power/safety results. Identify which layers and operating modes were actually executed.

Define the acceptance records

CheckEvidence for the verdict
Mode and protocolAC/DC mode, protocol and service selection are present in the report.
Interface identityThe actual coupler, inlet, cable and adapter identifiers match the test record.
Correlated responseRequested limits, signal states and measured response agree for the executed case.
Coverage statementThe conclusion identifies communication, power and mechanical/safety scopes separately.

Fault examples and diagnostic checks

Connector fits, negotiation fails

Compare protocol/services and physical communication setup before treating the mechanical connection as proof of compatibility.

Adapter-specific interruption

Compare a direct path and the approved adapter path under the same conditions, including signals and contact behaviour.

AC result reused for DC

Check that the report contains the operating mode and corresponding executed method before reusing its verdict.

Practical tip. Name the operating mode and communication profile in every saved recipe. “NACS test” alone does not identify the tested electrical and protocol behaviour.

Identify the interface and test role

Keep the mechanical interface, electrical operating mode and communication profile as separate configuration fields. For a station DUT, discuss the configured EVCA ComOnly or EVCA Flex vehicle simulation. For a vehicle DUT, discuss the configured charging-station simulation and power equipment. Confirm the NACS interface and released library before selecting the cases. A saved recipe should identify adapters, firmware and the source requirement so that a later test uses comparable conditions.

Questions about this test scope

Is NACS only DC?

The SAE J3400 scope includes AC single-phase and DC energy transfer. The selected test configuration determines which modes are covered.

Can I test without a real vehicle?

For a station DUT, a configured vehicle simulator provides the counterpart. Interfaces, protocol features and power equipment must match the required cases.

Does ComOnly replace a power source or load?

Communication-only testing and high-power energy transfer are different scopes. Agree the power setup separately.

Are adapters part of the test scope?

Identify the actual adapter, ratings and applicable requirements. A connector name alone does not establish adapter suitability.

Which edition should the report state?

State the exact normative edition, protocol profile, firmware and test-library version agreed for the project.

Why keep adapter identity in the trace report?

The adapter is part of the actual interface path. Its identity and approved use conditions are needed to reproduce a connection-specific result.

How should I compare direct and adapted charging?

Keep firmware, profile and operating conditions fixed, and compare the first changed signal, message or electrical response.

Can a communication verdict cover the coupler’s mechanical requirements?

Record those requirements and their evidence separately from message and signal results.

Sources and further reading

SAE J3400

Technical content: comemso. Updated .