Abstract
Controller area network is widely used protocol in automotive industry. Every controller in the network is required to configure its CAN hardware/software to communicate with the other controllers. The problem current industry facing is to handle configuration of CAN stack for different ECU hardware driven by market need. Each cluster variant is using hardware specific CAN stack provided by third party (in this case Vector). Presently, we have to manually configure each variant. This activity is duplicated across multiple variants for each release. This causes addition effort/ variant and re-work effort in case of erroneous configuration. The objective of this paper is to propose a common method to configure CAN stack independent of ECU hardware platforms. This paper has application in the scenario of single ECU having multiple hardware variants.