EV and EVSE test systems
EVCA ComOnly: CCS tester for EVCC and SECC
Use EVCA ComOnly with CCS Core as a CCS tester for the Combined Charging System. Connect a real EVCC or SECC to a configurable simulated communication partner. Select the MCS or ASIA Core for the corresponding interfaces, protocols, signals and test roles.
Your path to CCS communication testing
Choose the ComOnly configuration for your communication test.
Define whether the real DUT is an EVCC or SECC. Choose the Core, interfaces, protocol release, simulation functions and automation needed for your communication tests.
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.
Use comframe to correlate signal states, decoded messages and timing with the controller response. Repeat supported normal and negative cases across software versions, and keep the configuration and traces for regression review.
Controller roles at the ComOnly interface
| 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. Choose the connections and supported profiles for your controller. For tests with a high-voltage source or load, use a separate EVCA power-test configuration alongside the communication test.
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 directly at the controller bench.
Start EVCC or SECC development with an MCS communication partner you can configure and repeat.
- 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
| 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 the specified diagnostic reaction against the selected protocol and test requirement. |
| 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 example to plan a timeout test and evaluate the controller response. Record the measurements and compare them with the acceptance criteria defined for the actual run. The system comparison and FAQ explain the options for physical power tests.
Professional Simulation · Automated Standards Analysis · Conformance Test Libraries
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 configurable EV behaviour at the controller interface
- Challenge negotiation, limits, timeouts and negative cases
- Assess protocol conformity and robustness before power integration
- Use supported Test Libraries for controlled verdicts and reports
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
Choose the core, protocol, hardware, software licences and Test Libraries for the functions you need.
Monitor the supported communication signals and view their quality, states and timing alongside the charging sequence.
Find physical-layer causes earlier.Compare measured values, states, timings and protocol events with executable requirements to identify clear deviations.
Reduce manual trace interpretation.Configure the opposite charging participant for EVCC and SECC development.
Use one bench for both controller roles.For supported profiles, vary message content, timing, optional messages and non-conform behaviour without rebuilding the test environment.
Reach difficult state-machine scenarios.Replay supported recorded charging behaviour at the physical interface, giving the controller a repeatable counterpart from the field session.
Bring difficult field behaviour to the bench.Execute supported standards-based test cases with controlled steps, automated verdicts and traceable reports.
Move from ad hoc checks to evidence.Integrate supported functions into HiL (hardware-in-the-loop) benches, laboratory automation and continuous regression workflows.
Reuse the controller test in the development toolchain.Configure applicable certificate and security context for supported ISO 15118-based charging profiles.
Test more than nominal message exchange.Keep configuration, measurements, protocol events, evaluations and test results together so your team can review and reuse them.
Make every result attributable.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.
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 listingConfigure 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.
- 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.
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
Reuse your communication tests in HiL, automated regression and your existing toolchain.
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
Extend your test setup with Interop, Multi Mobile, Flex or the full MCS system as your physical test requirements grow.
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
- 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
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 brochureEVCA Flex ComOnly datasheet
Rev. 01.02 · English · PDF
Open datasheetFrequently asked questions
EVCA ComOnly FAQ
What is EVCA ComOnly?
EVCA ComOnly is the communication-focused configuration of the EV Charging Analyzer/Simulator platform. Connect a real EVCC or SECC to a configurable simulated counterpart and test low-level signals, communication links and protocol behaviour. Use its configured analysis and automation functions to evaluate and record the controller response.
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?
Test EVCC and SECC communication, 10BASE-T1S, service and LAN access, MCS low-level signals and controller behaviour. Specify the ISO 15118-20 profile, signal access and released functions for your MCS configuration.
Customer experience
Customer feedback on the EVCA platform.
“Currently the best and most complete vehicle simulator / sniffer / man in the middle we have used.”
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.