DET Module IDs
Learning how to use the DET (Development Error Tracer) is essential while integrating Autosar modules. Learn about all the DET module IDs in this article
The DET (Development Error Tracer) is very useful when integrating new Autosar modules into your toolchain. It provides just enough information, so that you will not get stuck when you are debugging a new module within your ECU. As every Autosar-based build is a gigantic code base, having a place to start is essential. But the DET one-up's this by providing you the module ID, for the Autosar module causing an issue, the API ID, directing you to the specific API, and the type of error. With this information, you have a good place to start.
Now that you know how essential the DET really is, by this small description we have just provided (or, you already started by reading our article DET Overview (opens in a new tab), in which we go into further details, such as how you can see the errors and even add your own custom DET errors), today we will provide a detailed summary of all the module IDs used by the DET. In essence, this article will work a bit like ours on the UDS Frames and NRC Codes (opens in a new tab), a cheat sheet you (and we) can use every time a new error pops up in the DET and we need to know where to look next.
So, without further ado, here's the list of DET module-IDs in Autosar:
| Module Name | Module ID |
|---|---|
| ADC Driver (Adc) | 123 (0x7B) |
| BSW Mode Manager (BswM) | 42 (0x2A) |
| BSW Scheduler (SchM) | 130 (0x82) |
| CAN Driver (Can) | 80 (0x50) |
| CAN Interface (CanIf) | 60 (0x3C) |
| CAN Network Management (CanNM) | 31 (0x1F) |
| CAN State Manager (CanSM) | 140 (0x8C) |
| CAN Transceiver Driver (CanTrcv) | 70 (0x46) |
| CAN Transport Layer (CanTp) | 35 (0x23) |
| Communication (Com) | 50 (0x32) |
| COM Based Transformer (ComXf) | 175 (0xAF) |
| COM Manager (ComM) | 12 (0x0C) |
| Complex Device Driver (CDD) | 255 (0xFF) |
| Core Test (CoreTst) | 103 (0x67) |
| Crypto Service Manager (CSM) | 110 (0x6E) |
| Debugging (Dbg) | 57 (0x39) |
| Development Error Tracer (DET) | 15 (0x0F) |
| Diagnostic Log and Trace (DLT) | 55 (0x37) |
| Diagnostic Over IP (DoIP) | 173 (0xAD) |
| DIO Driver (Dio) | 120 (0x78) |
| E2E Transformer (E2EXf) | 176 (0xB0) |
| ECU State Manager (EcuM) | 10 (0x0A) |
| EEPROM Abstraction (Ea) | 40 (0x23) |
| EEPROM Driver (Eep) | 90 (0x5A) |
| Ethernet Driver (Eth) | 88 (0x58) |
| Ethernet Interface (EthIf) | 65 (0x41) |
| Ethernet State Manager (EthSM) | 143 (0x8F) |
| Ethernet Switch Driver (EthSwt) | 89 (0x59) |
| Ethernet Transceiver Driver (EthTrcv) | 73 (0x49) |
| Flash Driver (Fls) | 92 (0x5C) |
| Flash EEPROM Emulation (Fee) | 21 (0x15) |
| Flash Test (FlsTst) | 104 (0x68) |
| FlexRay Autosar Transport Layer (FrArTp) | 38 (0x26) |
| FlexRay Driver (Fr) | 91 (0x51) |
| FlexRay Interface (FrIf) | 61 (0x3D) |
| FlexRay ISO Transport Layer (FrTp) | 36 (0x24) |
| FlexRay Network Management (FrNm) | 32 (0x20) |
| FlexRay State Manager (FrSM) | 142 (0x8E) |
| FlexRay Transceiver Driver (FrTrcv) | 71 (0x47) |
| Function Inhibition Manager (FiM) | 11 (0x0B) |
| GPT Driver (Gpt) | 100 (0x64) |
| ICU Driver (Icu) | 122 (0x7A) |
| IO Hardware Abstraction (IOHwAbs) | 254 (0xFE) |
| IPDU Multiplexer (IpduM) | 52 (0x34) |
| Large Data COM (LdCom) | 49 (0x31) |
| LIN Driver (Lin) | 82 (0x52) |
| LIN Interface (LinIf) | 62 (0x3E) |
| LIN Network Management (LinNm) | 63 (0x3F) |
| LIN State Manager (LinSM) | 141 (0x8D) |
| LIN Transceiver Driver (LinTrcv) | 64 (0x40) |
| MCU Driver (Mcu) | 101 (0x65) |
| Memory Abstraction Interface (MemIf) | 22 (0x16) |
| Network Management (Nm) | 29 (0x1D) |
| NVRAM Manager (NvM) | 20 (0x14) |
| OCU Driver (Ocu) | 125 (0x7D) |
| Operating System (Os) | 1 (0x01) |
| PDU Router (PduR) | 51 (0x33) |
| Port Driver (Port) | 124 (0x7C) |
| PWM Driver (Pwm) | 121 (0x79) |
| RAM Test (RamTst) | 93 (0x5D) |
| Run Time Environment (RTE) | 2 (0x02) |
| SAE J1939 Diagnostic Communication Manager (J1939Dcm) | 58 (0x3A) |
| SAE J1939 Network Management (J1939Nm) | 34 (0x22) |
| SAE J1939 Request Manager (J1939Rm) | 59 (0x3B) |
| SAE J1939 Transport Layer (J1939Tp) | 37 (0x25) |
| Secure Onboard Communication (SecOC) | 150 (0x96) |
| Service Discovery (Sd) | 171 (0xAB) |
| Socket Adaptor (SoAd) | 56 (0x38) |
| SOME/IP Transformer (SomeIpXf) | 174 (0xAE) |
| SPI Handler / Driver (Spi) | 83 (0x53) |
| Synchronized Time-Base Manager (StbM) | 160 (0xA0) |
| TCP / IP Stack (TcpIp) | 170 (0xAA) |
| Time Service (Tm) | 14 (0x0E) |
| Time Sync Over CAN (CanTSyn) | 161 (0xA1) |
| Time Sync Over Ethernet (EthTSyn) | 164 (0xA4) |
| Time Sync Over FlexRay (FrTSyn) | 163 (0xA3) |
| TTCAN Driver (TtCan) | 84 (0x54) |
| TTCAN Interface (TtCanIf) | 66 (0x42) |
| UDP Network Management (UdpNm) | 33 (0x21) |
| Watchdog Driver (Wdg) | 102 (0x66) |
| Watchdog Interface (WdgIf) | 43 (0x2B) |
| Watchdog Manager (WdgM) | 13 (0x0D) |
| XCP (Xcp) | 212 (0xD4) |
Alright, now that you have the list, make sure to bookmark this page. You will not regret it when you bump your head debunking those pesky software issues we all run into. See you next time!
Author: Micael Coutinho (opens in a new tab)
References:
© AutosarToday —@LinkedIn