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.
Summary
KopherConfig is a AUTOSAR Classic ECU configuration tool provided by KopherBit, which can automatically generate ARXML files from the DBC communication matrix and provide complete engineering materials for SWC (Software Component) design and KopherSAR BSW configuration.The exported ARXML is divided into three categories: Communication/System (network system description), AUTOSAR Platform (default Implementation Data Type, IDT), Service Components (service components provided by BSW to the application layer).
Technical Role
KopherConfig plays the role of Configuration Authority in the AUTOSAR Classic development process:
- Import from external engineering assets (DBC, ARXML communication matrix, signal list).
- Integrate with KopherSAR BSW configuration (CanIf, PduR, COM, DCM, DEM, NM, Csm, NvM and other modules).
- Automatically generate ARXML materials required for application layer SWC development.
- Export standard data for use by downstream tools such as SWC Designer / Network Designer.
When developers use SWC Designer or other AUTOSAR Authoring Tool for application layer modeling, they must import the ARXML generated by KopherConfig to ensure that the IDT, Port, Interface, and Service on the SWC side are consistent with BSW.
ARXML output file type
| File type | Path | Description |
|---|---|---|
| Communication / System | [Workspace]/Config/Communication.arxml | System Description (System Description) generated from the imported DBC, including Network Node, Pdu, Frame, Signal, Cluster and other information. |
| AUTOSAR Platform | [Workspace]/Config/AUTOSAR_Platform.arxml | AUTOSAR Standard default IDT (Implementation Data Type), all BSW and SWC are developed on this basis. |
| Service Components | [Workspace]/Config/ServiceComponent/SWC_*.arxml | BSW provides service components used by the application layer, such as modeSwitchPort_SWITCH_PORT_[CAN Channel]_CanSMIndication in SWC_BswM.arxml and other Mode Switch Ports. |
Architecture
| Components | Roles |
|---|---|
| DBC Importer | Parse Vector DBC and create Network Node / Frame / Signal / Pdu. |
| ARXML Exporter | Export Communication.arxml / AUTOSAR_Platform.arxml / SWC_*.arxml. |
| BSW Configurator | Configure KopherSAR BSW modules (Can / CanIf / PduR / COM / DCM / DEM / NM / Csm, etc.). |
| Service Component Generator | Generates corresponding SWC ARXML for BSW service components (such as BswM, ComM, Dcm, Dem). |
| Signal Mapping | Map Signal to SWC Sender/Receiver Port. |
| BSW Code Generation | Generate final BSW code, integrated with KopherSAR. |
Key Capabilities
- Generate Communication ARXML from DBC with one click to avoid manual writing.
- Supports CAN, CAN FD, LIN, and Ethernet/SOME/IP (via import of ARXML communication matrix).
- Automatically generate Service Component ARXML (BswM, ComM, Dcm, Dem, etc.) corresponding to KopherSAR BSW.
- Built-in consistent IDT foundation to avoid Type inconsistency between SWC and BSW.
- Integrated with KopherSAR code generator, BSW code can be reproduced with one click after configuration changes.
- Supports multi-ECU workspace management to facilitate collaborative development of multiple nodes in the vehicle.
Engineering Inputs Required
| Input | Purpose |
|---|---|
| DBC/ARXML Communication Matrix | Generates Communication.arxml. |
| ECU role definition | Specify the Node name of the ECU in the network and the PDU it receives/sends. |
| Diagnostic requirements | DTC List, SecurityAccess, Programming Session, etc., as the basis for DCM/DEM configuration. |
| NvM configuration | Persistent data sections, defaults, write strategies. |
| Security Policy | Csm/KeyM module, SecOC, Secure Boot configuration. |
| OS/Multi-Partition Planning | Application Partition, Task, Security Partition Strategy. |
How KopherBit Supports This
- KopherConfig Tool: graphical workspace, DBC import, ARXML generation, and BSW configuration completed in one stop.
- Integration with KopherSAR: BSW code can be generated directly after configuration is completed, without third-party integration.
- Integration with SWC Designer: The output ARXML can be used as standard input for application layer SWC design.
- Training: KopherBit provides KopherConfig operation instruction and AUTOSAR Classic configuration courses.
FAQ
KopherConfig Difference with Vector DaVinci / EB tresos?
KopherConfig is KopherBit’s own tool, deeply integrated with KopherSAR BSW and KCU hardware.Importing DBC, configuring BSW, generating ARXML, and generating BSW code can be completed in a single tool;no third-party authorization is required. It can also coexist with other AUTOSAR Authoring Tool and export standard ARXML for their use.
Is ARXML import supported instead of just DBC?
support.In addition to DBC, AUTOSAR System Description ARXML can also be imported as a communication matrix source.
What is Service Component?
In the AUTOSAR specification, the BSW module exposes its functions to the application layer SWC through the Service Component.For example, BswM provides mode switching Service Port, and Dcm provides diagnostic request Service Port. These exist in SWC_*.arxml in the form of SWC for RTE routing.
Why is IDT (Implementation Data Type) important?
IDT is a data type definition (such as uint8, boolean, enum) common to all BSW and SWC.If BSW and SWC use different IDTs, errors or inconsistencies will occur during RTE interface.KopherConfig uses AUTOSAR_Platform.arxml as the benchmark to avoid problems.
Does it support multi-ECU vehicle workspace?
support.Multiple ECU configurations can be managed in the same workspace and assigned to each ECU node from the shared vehicle network matrix to facilitate multi-node collaborative development of the vehicle.
JSON-LD
{
"@context": "https://schema.org",
"@type": "TechArticle",
"headline": "KopherConfig: AUTOSAR ECU configuration and ARXML integration tool",
"description": "KopherConfig produces Communication / AUTOSAR Platform / Service Components ARXML after import from DBC, as standard input for SWC design and KopherSAR BSW configuration.",
"url": "https://kopherbit.com/knowledge/kopherconfig-configuration-tool/",
"datePublished": "2026-05-09",
"dateModified": "2026-05-09",
"inLanguage": "zh-TW",
"keywords": ["KopherConfig", "AUTOSAR", "ARXML", "SWC", "BSW", "DBC"],
"articleSection": "AUTOSAR",
"author": { "@type": "Organization", "name": "KopherBit", "url": "https://kopherbit.com" },
"publisher": { "@type": "Organization", "name": "KopherBit", "logo": { "@type": "ImageObject", "url": "https://kopherbit.com/logo.png" } }
}