The UDS (Unified Diagnostic Services) diagnostic protocol is a diagnostic communication protocol in the automotive electronics ECU environment. This communication protocol is used in almost all new ECUs manufactured by OEM Tier 1 suppliers. These ECUs control various functions of the vehicle, including Electronic Fuel Injection (EFI), engine control system, transmission, anti-lock braking system (ABS), door locks and brakes, etc.
Before the birth of the car diagnostic protocol, the repair master could only rely on his experience to repair the car, because the car parts would not tell you what went wrong. But since there is a diagnostic protocol, once a component has a problem or has a problem, it will save the fault information in memory. In this way, the maintenance master can read these fault information through the communication bus. For example, after an ECU experiences an undervoltage fault, it will store the DTC (Diagnostic Trouble Code) represented by the undervoltage fault. The snapshot information (such as the vehicle speed at that time, the voltage value read, etc.) when the fault occurs can be accurately saved, and this information can help test engineers and after-sales technicians find the cause of the fault.
At present, most of the tests are measurement acquisition rather than diagnostic acquisition, so most data acquisition on the market is focused on the function of measurement acquisition. However, in order to meet the different needs of customers, it is very necessary for the data acquisition equipment to support certain diagnostic functions. In this regard, the data acquisition equipment solution of IPETRONIK in Germany can support the corresponding UDS diagnosis function while measuring and collecting.
After the vehicle ECU is connected to the IPElog2 RT with the custom line, one channel occupied by the IPElog2 RT can be used for UDS diagnosis, while the other channels can normally collect other bus data and connect modules of the vehicle. Then, the data can be transmitted to the PC through Wi-Fi or network cable, and the data can be viewed remotely in real time through IPEmotion ME, or even uploaded to the MQTT server through the 4G data card, so that engineers can view the data remotely.
Device connection diagram:
— Hardware support —
| IPElog2 - Extensible Data Logger:
• Input channels can be combined (up to 16 CAN FD, 6 LIN, 2 ETH);
• 4 switchable high-speed and low-speed CAN input channels;
• Fast startup, no message loss (NML), wake-up on CAN/LIN/FlexRay bus;
• cFast memory card, data storage up to 120GB;
• Integrated 4G, Wi-Fi and GPS receiver;
• Can be displayed via IPEmotion ME;
• CAN FD, LIN, ETH, DIG I/O input channels are completely electrically isolated;
• Developed for applications in harsh environments;
• Software integration via XCP on ETH/A2L format.
- software support-
| IPEmotion RT-Data Logger Software:
1. On the CAN and ETH interfaces, UDS diagnostic measurements can be run.
Please click here to view the remaining 30% exciting content!
| Past review
▶ Integration of IPETRONIK data acquisition and third-party software
