Engineering Reference
Knowledge Base
Engineering references for vehicle controllers, EVCC, V2G, UDS, BCM, and AUTOSAR toolchains, structured for search and AI citation.
AUTOSAR Toolchain: KopherSAR, KopherConfig, SWC Designer, and KopherBoot
AUTOSAR rollout involves SWC design, communication database, ARXML, MCAL, RTE, bootloader, diagnostics, and validation. This article explains the KopherBit toolchain responsibilities.
What Is a Body Control Module? BCM I/O, CAN/LIN, and Commercial Vehicle Use Cases
A BCM controls lighting, doors, wipers, HVAC peripherals, low-voltage loads, and body signals. This guide explains BCM I/O architecture, communication needs, load control, and KCU BCM use cases.
EVCC and V2G Software Stack: ISO 15118-2 / ISO 15118-20 Technical Guide
EVCC is the vehicle-side charging communication controller. The V2G software stack handles ISO 15118, DIN 70121, EXI, SDP, TLS, and Plug & Charge communication details.
AUTOSAR DEM / DCM / FiM: ECU diagnostic module architecture
AUTOSAR Classic’s DEM (Diagnostic Event Manager), DCM (Diagnostic Communication Manager) and FiM (Function Inhibition Manager) together form the ECU diagnostic subsystem.This article organizes the responsibilities, interaction methods and KopherSAR of the three and its complete implementation.
AUTOSAR RTE Cross-partition IOC: Multi-core ECU safety and general functional isolation
AUTOSAR IOC (Inter-OS-Application Communication) in Classic RTE is a standard mechanism for cross-OS Application/cross-core communication.After isolating the secure partition from the general partition on a multi-core MCU such as Infineon TC387QP, the IOC is a legal cross-partition communication path.This article summarizes the generation process, configuration methods and restrictions of IOC by KopherSAR RTE.
BCM Body Control Module
KopherBit BCM (Body Control Module) is a body electronic control module that integrates multi-channel high/low drive and SPI architecture distributed intelligent switches. It is responsible for controlling body actuators such as lights, windows, wipers, door locks, seats, etc. It can be developed on the KCU platform through KopherSAR and KopherConfig configuration.
DIN 70121: CCS DC charging early communication standard
DIN 70121 is a CCS DC charging communication standard formulated by Germany's DIN. It was released before ISO 15118-2 and was widely deployed in early European and American DC fast charging piles.This article summarizes the protocol structure, message flow, and compatibility of ISO 15118-2 of DIN 70121, as well as the scope of support of KopherBit EVCC for DIN 70121.
EVCC：Electric Vehicle Communication Controller
KopherBit EVCC is a charging communication controller on the electric vehicle side. It implements ISO 15118-2 / ISO 15118-20 / DIN 70121 and other V2G communication protocols. It is responsible for identity authentication, charging schedule and power negotiation with SECC (charging pile) through PLC. It can be used as KCU Optional module or standalone daughter board for GEN2.
EDR Event Data Recorder: Vehicle event data recording system
KopherBit EDR (Event Data Recorder) is a vehicle event data recording subsystem that integrates data sources such as Crash Sensor, Airbag ECU, and seat occupancy sensors to record key vehicle status when an accident occurs to assist in post-event reconstruction and regulatory compliance.
KopherBit AUTOSAR Tool chain overview: from SWC design to ECU mass production
KopherBit provides a complete AUTOSAR Classic development tool chain: Kopher SWC Designer for application layer modeling, Kopher Network Designer to process the communication matrix, KopherConfig to integrate BSW configuration, KopherSAR for basic software, and KopherBoot to provide UDS Bootloader, KopherUDS are used as diagnostic host computers, covering the complete ECU development process from SWC design, configuration generation, burning to diagnosis.
ISO 15118-2: Electric vehicle and charging pile communication protocol (V2G PnC + AC/DC)
ISO 15118-2 is the V2G application layer communication standard between electric vehicles and charging piles, defining AC/DC charging process, Plug & Charge (PnC) authentication, TLS security layer and EXI message encoding.This article summarizes the implementation scope and integration method of KopherBit on the EVCC end of ISO 15118-2.
ISO 15118-2 PnC: TLS, X.509 Credential Chaining and Crypto Service Integration
ISO 15118-2 Plug & Charge (PnC) completes automatic authentication between electric vehicles and charging piles through TLS and X.509 certificate chains.This article summarizes the cryptography service integration (CryptoService), certificate chain structure and OEM Provisioning / Contract Certificate process of PnC in KopherBit EVCC.
ISO 15118-20: Bidirectional V2G charging and MCS communication standard
ISO 15118-20 is the second generation V2G communication standard of the ISO 15118 series. It supports bidirectional charging (V2G/V2H/V2L), Megawatt Charging System (MCS), wireless charging and more flexible energy scheduling negotiation. It is backward compatible with the ISO 15118-2 PnC process.
KCU CAN / CAN FD communication architecture
KCU GEN1 provides 4 channels of CAN 2.0B; KCU GEN2 (Phase B / Micro) is upgraded to 4 channels of full CAN FD (up to 2 Mbit/s data phase), one of which supports CAN wake-up function.This article summarizes the hardware configuration, Wake-up behavior and KopherSAR software integration of the KCU series on CAN/CAN FD communication.
KCU Analog/Digital/Frequency Input Channel
KCU GEN1 / GEN2 provides three channel types: analog input (AI), digital input (DI / MSDI), and frequency input (FI), which respectively correspond to different signal forms of vehicle sensors.This article organizes the channel configuration, signal conditioning circuit and KopherSAR I/O abstract interface of each generation of KCU.
KCU Vehicle Control Unit: KCU GEN1 and KCU GEN2 Specifications
KopherBit KCU GEN1 and KCU GEN2 are vehicle control units (Vehicle Control Unit).This article compiles the processor, power supply, I/O, communication interface, mechanism and environmental specifications of the two generations of products to assist system integration engineers in selection and introduction.
KCU GEN2 Micro: Lite Vehicle Control Unit Specifications
KCU GEN2 Micro is a KopherBit second-generation streamlined automotive control unit. It adopts Infineon TC387QP quad-core 300 MHz processor and provides 4 channels of CAN FD, 4 analog inputs, 4 low-order drive outputs and H-bridge. The motherboard size is 70×86×33 mm, which is suitable for subsystem control applications with limited space.
KCU Lite: lightweight vehicle control unit (Smart Module)
KCU Lite is a vehicle control unit launched by KopherBit for light-load/low-cost application scenarios. It provides a "Smart Module" distributed smart actuator architecture and supports multiple Connector pin assignment variants such as A2 / A2J / Smart PhaseA2 / Smart PhaseB1. It is integrated with the SC206E WIFI module and is suitable for lightweight applications such as E-Scooter, motorcycles, and body subsystems.
KopherUDS: UDS diagnostic host computer and programming tools
KopherUDS is KopherBit's UDS (ISO 14229) diagnostic host computer. It supports ECU firmware burning, DTC reading, SecurityAccess, RoutineControl, DataIdentifier reading and writing and other processes. It is compatible with CAN / CAN FD / DoIP and is compatible with KopherBoot Bootloader is tightly integrated with KopherSAR DCM/DEM.
Functional safety and security basics of Infineon TC387QP on KCU GEN2
KCU GEN2 uses the Infineon AURIX TC387QP main processor, built-in multi-core Lock-Step, HSM security module and ASIL-D friendly hardware security mechanism.This article summarizes the basics of functional safety (ISO 26262) and information security (R155 / R156) application of TC387QP in KopherSAR / KopherV2G / KopherBoot.
KopherBoot：Car specification UDS Bootloader
KopherBoot is a car-standard UDS Bootloader provided by KopherBit. It adopts ISO 14229 standard diagnostic service, supports CAN, CAN FD, and DoIP burning channels. It has built-in protection mechanisms such as SecurityAccess, CRC/signature verification, and automatic rollback of the Application section. It is compatible with NXP MPC5744P and Infineon. TC387QP platform.
KopherSAR: AUTOSAR Classic Basic Software (BSW)
KopherSAR is KopherBit's own AUTOSAR Classic basic software (BSW) suite, which provides CAN/CAN FD/LIN/Ethernet communication, UDS/DEM/DCM diagnostics, NM network management, CryptoService, Flash/EEPROM, I/O abstraction, RTE and other modules, and supports NXP MPC5744P / Infineon TC387QP and other automotive MCU platforms.
KopherConfig: AUTOSAR ECU configuration and ARXML integration tool
KopherConfig is KopherBit's own AUTOSAR Classic ECU configuration tool. After importing the network matrix from DBC, it automatically generates three major categories of ARXML files: Communication / AUTOSAR Platform / Service Components. It serves as the standard input for application layer SWC development and KopherSAR BSW configuration.
KopherV2G: ISO 15118 / DIN 70121 V2G software stack
KopherV2G is a V2G charging communication software stack provided by KopherBit, integrating SLAC, SDP, TLS, V2G TP, EXI codec and ISO 15118-2 / ISO 15118-20 / DIN 70121 state machine, which can be deployed in EVCC (vehicle side) and SECC (pile side), and integrated with the KopherSAR + KopherConfig toolchain.
UDS Bootloader: Diagnostic services for boot programs (ISO 14229)
KopherBit UDS Bootloader adopts the ISO 14229 (UDS) standard diagnostic service as the basis for ECU firmware burning communication. It sequentially completes the Flash erasure, writing and switching application process through SecurityAccess, RoutineControl, RequestDownload, TransferData, TransferExit, ECUReset and other services, which complies with vehicle regulations OEM Mass production and after-sales flashing requirements.
KCU High Side / Low Side Driver module
KCU GEN1 / GEN2 provide integrated high-side driver (HSD) and low-side driver (LSD) modules to support PWM output, load current measurement and channel diagnostics.This article summarizes the HSD/LSD API, diagnostic process and BSW integration methods of KopherBit in KopherSAR Driver Interface.
UDS Diagnostic Architecture: DEM, DCM, NM, and KopherUDS
UDS is the core diagnostic communication protocol for automotive ECUs. This article explains DEM event management, DCM diagnostic communication, NM network management, and KopherUDS use cases.
UDS ReadDTCInformation (0x19) Service Description
UDS ReadDTCInformation (0x19) is the core service for reading diagnostic trouble code (DTC) information in ISO 14229. It defines multiple sub-services (such as 0x01 reportNumberOfDTCByStatusMask, 0x02 reportDTCByStatusMask, 0x06 reportDTCExtDataRecordByDTCNumber, etc.), which can obtain DTC from the ECU. Quantity, status, snapshots, extensions and environmental conditions.This article organizes the service structure, common sub-services and KopherBit DCM/DEM integration methods.
What Is a Vehicle Control Unit? VCU and KCU Controller Technical Guide
A vehicle control unit coordinates propulsion, battery, charging, thermal management, and body signals. This guide explains VCU functions, I/O, communication interfaces, and KCU GEN1 / GEN2 use cases.
ODX-D Driven UDS Testing: From Database Import to ISO 14229-1 Test Case Generation
A walkthrough of using ODX-D as the single source of truth for UDS testing — PDX import, ISO 14229 service tree rendering, ENV-DATA-DESC driven DTC snapshot decoding, and ISO 14229-1 test case generation in KITE UDS Tester.
SOME/IP Service Discovery, Subscription, and TP — A Practical Walkthrough
A practical walkthrough of SOME/IP-SD Find / Offer / Subscribe flows, PDU header fields, endianness rules, and SOME/IP-TP segmentation, with hands-on steps for capturing SOA traffic in KITE Pulse against an ARXML database.
ASAM XCP on CAN: Building an Online Calibration and DAQ Master
From A2L / ELF address resolution and XCP session bring-up to calibration page switching, dynamic DAQ lists, and RAM-to-ROM Intel HEX export — a practical anatomy of an XCP-on-CAN master in the ECU calibration workflow.
UDS Reflash Sequence: 0x10 → 0x27 → 0x31 → 0x34 / 0x36 / 0x37 End-to-End
A step-by-step walkthrough of the full UDS (ISO 14229) reflash sequence — session control, Security Access, erase routines, RequestDownload / TransferData / RequestTransferExit, ECU Reset, and common NRCs.