EV charging communication tester
EVCA ComOnly: Charging Communication Tester
Develop the conversation between a vehicle and charging station before adding a complete power test bench. EVCA ComOnly supports selected communication protocols, signalling and test roles in a compact system.
Test the controller before adding the power stage.
EVCA ComOnly connects a real EVCC or SECC to a configurable charging communication partner. Use it to develop controller software, protocol stacks, modems and chipsets before a complete vehicle or charger is available.
comframe correlates signal states, decoded messages and timing, so nominal and negative cases can become repeatable regression tests. Select another EVCA configuration when voltage, current, switching or cooling enters the test scope.
One ComOnly principle, three protocol directions
Select the core by the controller interface, not by a generic product name
CCS, MCS and ASIA use different physical interfaces, communication links and protocol families. The shared value is the same: a real controller under test, a configurable charging counterpart and one evidence workflow.
EVCA ComOnly CCS
EVCC and SECC development for AC, CCS and NACS communication.
Use control-pilot access, PLC (power line communication) and high-level communication to test the controller without a complete vehicle or charger.
- IEC 61851-1, DIN 70121 and ISO 15118 communication by configured release
- PLC to EV, PLC to EVSE and optional PLC sniffer hardware
- Professional Simulation and Charge Playback for supported profiles
- DIN 70122 and ISO 15118-4/-5 Test Library scope by configuration
EVCA ComOnly MCS
MCS controller, 10BASE-T1S and low-level signal testing without megawatt power.
Start MCS EVCC or SECC work before the coupler, cooling circuit and external power equipment are required.
- EV and EVSE test directions on the MCS communication interface
- Service, LAN, PHY1 and PHY2 access
- Insertion Detection, Charge Enable and protective-earth signal context
- ISO 15118-20-based application behaviour by released configuration
EVCA ComOnly ASIA
CHAdeMO and GB/T DC controller development with CAN and protocol-specific low-level states.
Test the Asian DC charging controller path without building a complete vehicle or high-power charger setup.
- Real EVCC or SECC with a simulated CHAdeMO or GB/T counterpart
- CAN communication, message timing and value analysis
- CHAdeMO release and GB/T 27930 generation defined per configuration
- Low-level state access and application-specific evidence by released scope
One system, two controller perspectives
Put a real EVCC or SECC against a configurable charging counterpart
The DUT (device under test) stays real. Its charging partner becomes repeatable, measurable and deliberately challengeable.
Vehicle controller development
Test the EVCC
EVCA ComOnly behaves as the charging-station communication controller and challenges the EVCC from connection detection through session negotiation and error handling.
- Simulate SECC or EVSE behaviour for the selected protocol family
- Vary states, values, message order, optional content and timing
- Verify controller reactions, limits, certificates and state transitions
- Automate regression across software versions and parameter sets
Charging-station controller development
Test the SECC
EVCA ComOnly behaves as the vehicle communication controller and supplies controlled vehicle, battery and protocol behaviour to the SECC implementation.
- Simulate EV behaviour without a complete vehicle or battery system
- Challenge negotiation, limits, timeouts and negative cases
- Assess protocol conformity and robustness before power integration
- Use supported Test Libraries for controlled verdicts and reports
Trace the cause across the communication layers.
Correlate physical and low-level states with the selected PLC, 10BASE-T1S or CAN link and the application protocol. A decoded message alone cannot explain a controller reaction without its interface state and timing.
Configured simulation varies messages, values, delays and supported negative behaviour. Released analysis functions and Test Libraries add evaluations, deviations and reports. The selected core, protocol release and licences define the available depth.
Relevant EVCA capabilities
Create a controllable test partner, not another passive protocol viewer
Capability availability depends on the selected core, protocol, hardware, software licences and Test Libraries. The value comes from combining the applicable functions around one controller risk.
Signal quality measurement
Monitor supported communication signals and correlate quality, states and timing with the charging sequence.
Find physical-layer causes earlier.Automated Standards Analysis
Relate measured values, states, timings and protocol events to executable requirements and clear deviations.
Reduce manual trace interpretation.EV and EVSE simulation
Represent the opposite charging participant with configurable behaviour for EVCC and SECC development.
Use one bench for both controller roles.Professional Simulation
For supported profiles, vary message content, timing, optional messages and non-conform behaviour without rebuilding the test environment.
Reach difficult state-machine scenarios.Charge Playback
Reproduce recorded charging behaviour physically at the interface so the controller interacts with a repeatable field-derived counterpart.
Bring difficult field behaviour to the bench.Conformance Test Libraries
Execute supported standards-based test cases with controlled steps, automated verdicts and traceable reports.
Move from ad hoc checks to evidence.Automation and integration
Integrate supported functions into HiL (hardware-in-the-loop) benches, laboratory automation and continuous regression workflows.
Reuse the controller test in the development toolchain.Certificate and security workflows
Configure applicable certificate and security context for supported ISO 15118-based charging profiles.
Test more than nominal message exchange.Evidence and reporting
Keep configuration, measured values, protocol events, evaluations and test results together for review and reuse.
Make every result attributable.Protocol families and implementation profiles
Build the test strategy around the exact controller implementation
Do not treat a standard name as complete test coverage. Define the core, DUT role, interface, protocol generation, optional services, security context, simulation depth and evidence separately.
AC, CCS and NACS communication
- Low-level context
- IEC 61851-1, control pilot and the applicable SAE J1772 or NACS interface context.
- Communication link
- PLC-based high-level communication, including optional PLC sniffer hardware in the published reference configuration.
- Application protocols
- DIN 70121, ISO 15118-2 and ISO 15118-20 by configured release, with ISO 15118-3 communication-layer context.
- Test evidence
- DIN 70122 and ISO 15118-4/-5 Test Library scope where released and configured.
MCS communication and low-level signals
- Low-level context
- MCS-specific Charge Enable, Insertion Detection, protective-earth and physical interface access by configuration.
- Communication link
- 10BASE-T1S, service and LAN access, plus PHY1 and PHY2 measurement or integration points.
- Application protocol
- ISO 15118-20-based MCS communication according to the released edition, amendment and service profile.
- Test evidence
- Simulation, monitoring, pre-conformance or Test Library scope must be stated separately from the protocol name.
CHAdeMO and GB/T DC communication
- Low-level context
- Technology-specific EV and EVSE states and interface signals according to the selected system and connector path.
- Communication link
- CAN communication with protocol-specific message timing, values and controller reactions.
- Application protocols
- CHAdeMO release by configuration, plus GB/T 27930 variants in the relevant GB/T 18487.1 charging context.
- Test evidence
- Released simulation, monitoring and test-case scope depends on protocol generation, DUT role and hardware configuration.
EVCA is listed by CharIN for Charging System Basic and Extended DC EVSE profiles
CharIN currently lists comemso as a validated Conformance Test System vendor for the Charging System Basic and Extended DC EVSE application profiles. The applicable EVCA system, test direction and Test Library scope must be confirmed for the project.
View the CharIN CCTS listingSimulation support is not the same as complete conformance coverage
Specify the role, protocol edition, test standard, Test Library release, certificate or security context and expected report. This is especially important for evolving ISO 15118-20 and MCS profiles.
Published 2024 CCS reference configuration
Compact hardware for the controller bench
The brochure describes a compact ComOnly CCS reference with insulated banana sockets, CAN and PLC interfaces. Treat these values as the published CCS reference, not as universal dimensions or interfaces for every current MCS or ASIA configuration.
- Model numbers
- 116-2-015 CCS Core, 116-2-016 with PLC sniffer, 116-1-011 ComOnly case.
- Dimensions
- 18.6 × 15.8 × 32.6 cm.
- Reference weight
- Approximately 3 kg.
- Power input
- 24 V DC.
- Published connections
- Insulated banana sockets, SUB-D9 for CAN data and RJ45 for PLC data.
- Published protocol scope
- AC, CCS and NACS, with the simulation and Test Library scope stated in the brochure.
Current configurations, interfaces, model numbers, dimensions and weights are defined by the quotation and released documentation.
Package contents
EVCA ComOnly, 24 V power supply, CAN cable and termination, firmware update kit, Quick Start Guide and user manuals in the published reference package.
Usable software
The brochure lists comemso com.frame and Vector CANoe with a comemso project. Current licence and integration scope remain configuration-specific.
Upgrade path
The 2024 brochure positions ComOnly as the communication-focused entry into EVCA Flex. Add power, switching and electrical fault depth when the test objective grows.
From controller pin to reusable evidence
Integrate communication testing into the workflow you already use
Start as a compact controller bench. Expand into HiL, automated regression, customer toolchains or a broader EVCA system without replacing the communication test logic.
Controller bench
Use compact manual or semi-automated setups for early hardware and software development.
comframe workflow
Configure behaviour, visualise data, correlate events and retain reusable evidence.
API and HiL integration
Embed supported functions into automated laboratories, HiL systems and regression pipelines.
Platform expansion
Move into Interop, Multi Mobile, Flex or the full MCS system when the physical test boundary grows.
From controller development to regression testing.
Vehicle and charger teams can validate EVCC and SECC implementations on a repeatable bench. Semiconductor and software teams can exercise modems, chipsets and protocol stacks across implementation profiles; laboratories can investigate standards and prepare conformance campaigns.
The MCS configuration brings the same approach to 10BASE-T1S and the supported MCS controller signals before megawatt power and cooling are required.
From controller risk to quotation
Specify the DUT, counterpart and evidence before selecting interfaces
EVCA ComOnly is not one fixed bill of materials. A useful configuration defines the implementation profile and the tests that must remain repeatable.
- 1DUT and role. EVCC, SECC, ECU, protocol stack, modem or chipset.
- 2Core and interface. CCS and NACS, MCS, or ASIA with the required controller and signal connections.
- 3Communication depth. Low-level states, PLC, 10BASE-T1S or CAN, high-level messages, timing and certificates.
- 4Simulation depth. Nominal, boundary, invalid, delayed, missing and supported non-conform behaviour.
- 5Automation and evidence. Test Libraries, API, reports, regression and traceability.
- 6Growth path. Interop, Multi Mobile, EVCA Flex or the full EVCA MCS architecture.
Select the system by test objective
Use ComOnly for the controller. Move to another EVCA path when the boundary grows.
ComOnly is not a smaller universal tester. Its strength is concentrated communication depth with a protected route to mobile, real-pair and power testing.
Scroll horizontally on small screens.
| Selection criterion | EVCA ComOnly | EVCA Interop | EVCA Multi Mobile | EVCA Flex or full EVCA MCS |
|---|---|---|---|---|
| Primary question | Does the EVCC or SECC communicate correctly and robustly? | Why did a real EV and real EVSE fail together? | What is happening around the real charging interface in lab or field? | How does the complete interface behave with real power, faults, cooling or high-voltage integration? |
| Typical DUT | EVCC, SECC, protocol stack, modem or chipset. | Real EV and real EVSE pair. | Vehicle, charging station or charging interface. | EV, EVSE, subsystem, power stage or full MCS interface. |
| Counterpart | Simulated EV or EVSE communication partner. | Both partners are real, with synchronised analysis and manipulation. | Simulation, monitoring or real interface depending on configuration. | Configured simulation plus external source, load and application hardware. |
| Power boundary | No internal HV source or load. Communication first. | Real-pair measurement or project-specific setup. | Mobile and field-oriented electrical context. | Scalable voltage, current, power, switching, electrical faults, cooling and safety. |
| Best next step | Add standards, Test Libraries, automation or another core. Expand when power is required. | Reproduce and verify the interoperability cause. | Link field evidence back to development and release campaigns. | Validate the complete physical test boundary. |
Frequently asked questions
EVCA ComOnly FAQ
What is EVCA ComOnly?
EVCA ComOnly is the communication-first configuration of the EV Charging Analyzer/Simulator platform. It tests real EVCC or SECC implementations against a configurable simulated counterpart and correlates low-level signals, communication links, protocol behaviour, automation and evidence without requiring an internal high-voltage power stage.
Which EVCA ComOnly variants are available?
The product family is configured for three main protocol directions: EVCA ComOnly CCS for AC, CCS and NACS communication, EVCA ComOnly MCS for MCS controller and 10BASE-T1S work, and EVCA ComOnly ASIA for CHAdeMO and GB/T DC communication. Exact interfaces, protocol generations and test functions are configuration-specific.
Can EVCA ComOnly test both EVCC and SECC controllers?
Yes. For EVCC development the system represents the charging-station communication counterpart. For SECC development it represents the vehicle communication counterpart. The real controller remains the DUT while its partner becomes repeatable and configurable.
Does EVCA ComOnly transfer charging power or high voltage?
Its primary role is communication and controller testing. It does not require an internal source, load or high-voltage power stage. Move to EVCA Flex, EVCA MCS or another configured EVCA system when real voltage, current, power, switching, cooling or electrical fault injection become part of the test objective.
Which standards are covered by EVCA ComOnly CCS?
Published CCS reference information includes IEC 61851-1, DIN 70121, ISO 15118-2, ISO 15118-3 and ISO 15118-20 communication. NACS and SAE J3400 context can be configured where applicable. Simulation support, protocol version, security profile and Test Library availability must be specified separately.
What does EVCA ComOnly MCS test?
The MCS configuration focuses on EVCC and SECC communication, 10BASE-T1S, service and LAN access, MCS-specific low-level signals and controller behaviour without requiring a megawatt power stage. The exact ISO 15118-20 profile, MCS signal access and released functions depend on the configuration.
EVCA system planning
Match the EVCA path to the real test boundary.
Specify the DUT, simulated role, charging family, physical depth and software scope.