EV and EVSE test systems

EVCA ComOnly CCS Core: CCS tester for charging communication

Use EVCA ComOnly as a CCS tester for charging communication with the CCS Core. Select the MCS or ASIA Core for the corresponding controller interface. Develop and test the dialogue between vehicle and charging station with the supported protocols, signalling and test roles before adding a complete power test bench.

Find your test solution

EVCA ComOnly family: CCS, MCS and ASIA communication testers

Controller DUTsTest real EVCC or SECC implementations

Simulated counterpartControl the charging communication partner

Core selectionCCS, MCS or ASIA for the required interfaces

Shared softwareConfigure, analyse and automate with comframe

Your path to CCS communication testing

From the communication task to the ComOnly configuration.

For EVCC and SECC testing, define the controller role first, then review the technical scope and align the concrete configuration.

1 · Suitable systemEVCA ComOnly CCS CoreTest a real EVCC or SECC against a simulated charging-communication partner.View the system principle →2 · Technical scopeEVCC/SECC test objective and controller responseThe existing timeout example shows the communication test approach. It is not presented as a published completed test record.View the test objective →3 · Next stepDefine the communication scopeSpecify EVCC or SECC, protocol, Core, signal paths and the required automation interface.Discuss the configuration →

CCS tester for EVCC and SECC communication development

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.

Controller roles at the ComOnly interface

The controller remains real; its communication partner is simulated
Real controller	Simulated communication partner	Core and interface
EVCC	SECC / charging-station side.	Select the CCS, MCS or ASIA Core for the protocol and controller signal interface.
SECC	EVCC / vehicle side.	Use the corresponding EV-side interface and released simulation profile of the selected Core.

CCS uses the configured pilot and PLC interfaces, MCS uses 10BASE-T1S and its selected signal access, and ASIA uses CAN and protocol-specific states. ComOnly focuses the controller bench on communication and signalling. For tests with a high-voltage source or load, select the matching EVCA power-test configuration; these power components are separate from ComOnly. Exact connections and supported profiles are configuration-specific.

Core selection · Published Core front-panel views · CCS reference connectors and dimensions

One ComOnly principle, three protocol directions

ComOnly cores and interfaces: CCS, MCS and ASIA

CCS, MCS and ASIA cores provide different physical interfaces, communication links and protocol families.

EVCA ComOnly CCS

Use the CCS Core as a CCS tester for EVCC and SECC development. AC and NACS communication are also available within the configured scope.

Access Control Pilot, PLC (power line communication) and high-level communication at the controller.

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

Develop MCS controllers and test 10BASE-T1S communication and low-level signals at the controller bench. Add a full MCS power-test configuration when the task requires charging 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.

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

EVCC and SECC tests: simulated partner and controller response

The DUT (device under test) remains real; its communication partner is configurable.

Communication test objective: timeout after a missing charging message

EVCC / SECC negative test: controlled condition and controller reaction
Test element	Defined scope
Starting condition	Select the real EVCC or SECC, Core, protocol version and supported session state. Keep the controller configuration and other simulated-partner conditions constant.
Changed partner behaviour	Withhold a selected message using the supported simulation functions. The expected message and permitted timing come from the chosen protocol and test requirement.
Expected controller reaction	Check timeout detection, the required state transition and any specified diagnostic reaction. Compare with the defined requirement rather than a universal timeout value.
Evaluation	Correlate the last message, simulated signal states, controller response and timing. Preserve configuration, traces and the acceptance decision for regression; a Test Library verdict requires the corresponding released test case.

Use this illustrative communication test to assess timeout handling and the required controller response. Validate physical high-voltage shutdown and the complete power path in the matching EVCA Flex or full EVCA MCS configuration. The example describes a test objective; measurements and pass criteria belong to the actual test run.

Professional Simulation · Automated Standards Analysis · Conformance Test Libraries

Conceptual ComOnly controller test configuration connecting a CCS Core with an EVCC or SECC through PLC and Control Pilot signals — Conceptual test configuration; interfaces and supported standards depend on the selected ComOnly configuration.

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

Typical DUTs: EVCC ECU, onboard charging controller, charging inlet controller, protocol stack, modem or communication chipset.

EVCA ComOnly

↔

Configure. Simulate. Measure. Analyse. Automate. Document.

EVSE

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

Typical DUTs: SECC ECU, charge-point controller, charger communication module, protocol stack, modem or controller chipset.

Controller-response analysis: signals, messages, states and timing

View physical and low-level states alongside PLC, 10BASE-T1S or CAN and the application protocol. Use the interface and timing context to interpret each controller reaction.

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

ComOnly functions for simulation, protocol analysis and regression

Capabilities depend on the selected core, protocol, hardware, software licences and Test Libraries.

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

Compare measured values, states, timings and protocol events with executable requirements to identify 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.

API

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.

Configuration rule: simulation support, protocol version, security profile, capability licence and conformance Test Library are separate scopes. The quotation must state the exact combination needed by the DUT.

Protocol families and implementation profiles

CCS, MCS and ASIA protocol profiles and released Test Library scope

Define core, DUT role, interface, protocol generation, optional services, security context, simulation depth and evidence separately.

EVCA ComOnly CCS

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.

EVCA ComOnly MCS

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.

EVCA ComOnly ASIA

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.

Independent validation

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 listing

Scope distinction

Configure simulation and standards-conformance test 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

These published reference values apply to the CCS tester with CCS Core in the 2024 brochure configuration; MCS and ASIA dimensions and interfaces require separate confirmation.

Rear panel of EVCA ComOnly with power, signal and CAN connections

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 the controller interface to reusable test records

EVCC/SECC test integration: comframe, API and HiL

Extend the controller bench into HiL, regression and customer toolchains while reusing its communication test logic.

Controller bench

Use compact manual or semi-automated setups for early hardware and software development.

comframe workflow

Configure behaviour, visualise data and correlate events. Keep the resulting records so you can reuse them in later tests.

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.

EVCA ComOnly CCS Core straight front view — CCS Core front panel with controller, pilot, PLC and sniffer interfaces according to the shown configuration.

EVCA ComOnly MCS Core angled view — MCS Core with EV and EVSE service, LAN, PHY and low-level signal access.

EVCA ComOnly ASIA Core front panel — ComOnly ASIA Core for CHAdeMO and GB/T DC communication. Interface and function scope depend on the selected configuration.

From controller development to regression testing.

Vehicle and charger teams validate EVCC and SECC implementations; semiconductor and software teams test modems, chipsets and protocol stacks. Laboratories investigate standards and prepare conformance campaigns.

Specify the controller test for your quotation

ComOnly configuration: controller role, Core, interfaces and software

1
DUT and role. EVCC, SECC, ECU, protocol stack, modem or chipset.
2
Core and interface. CCS and NACS, MCS, or ASIA with the required controller and signal connections.
3
Communication depth. Low-level states, PLC, 10BASE-T1S or CAN, high-level messages, timing and certificates.
4
Simulation depth. Nominal, boundary, invalid, delayed, missing and supported non-conform behaviour.
5
Automation and evidence. Test Libraries, API, reports, regression and traceability.
6
Growth path. Interop, Multi Mobile, EVCA Flex or the full EVCA MCS architecture.

Find your test solution Contact application engineering

Select the system by test objective

ComOnly, Interop, Multi Mobile and Flex by DUT and physical test scope

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	Communication and controller testing. HV source and load belong to a separate power-test configuration.	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.

Product documents

Brochure and technical datasheet

EVCA ComOnly brochure

Product overview · English · PDF

Open brochure

EVCA Flex ComOnly datasheet

Rev. 01.02 · English · PDF

Open datasheet

All resources

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?

ComOnly provides communication and controller testing at the EVCC or SECC bench. The configuration focuses on signals and protocols; an internal source, load or high-voltage power stage is outside that scope. Choose 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?

For the CCS tester with CCS Core, published 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

Configure EVCA ComOnly for your controller.

Define the EVCC or SECC, charging protocol, signal paths and automation interface for your communication test bench.

Find your test solution Contact application engineering