Moving to the UI pa...
Clear all

Moving to the UI part8

1 Posts
1 Users
Member Admin
Joined: 3 years ago
Posts: 381
Topic starter  

To process your raw CAN or LIN data, you will typically need a DBC file (CAN database).

This file contains information on how to decode the raw CAN data and extract relevant CAN signals like temperatures, engine speed etc.


 OBD2, CANopen, CAN FD, and SAE J1939.

How decoding raw CAN data will look like

  • OBD2

    OBD has a self-diagnostic capability that mostly mechanics use to analyze car issues and the overall health of the car. OBD2 determines trouble codes (DTCs) and real-time data (RPM, speed, etc) that can be recorded through OBD2 loggers.

  • CANopen

    CANopen is typically used in embedded control applications such as industrial automation and is based on a CAN meaning that the CAN bus data logger is also capable to log CANopen data.

  • CAN FD

    CAN FD is essentially a CAN bus with a flexible data rate and an extension of the classical CAN data link layer. In comparison with classical CAN protocol, CAN FD increases the payload from 8 to 64 bytes. It also allows a higher data bit rate, depending on the CAN transceiver.

  • SAE J1939

    J1939 is commonly used in heavy-duty vehicles. J1939 parameters such as RPM and speed are analyzed by a suspect parameter number (SPN). Afterward, they are grouped into parameter groups and classified by a PG number (PGN).

A high-speed transfer data rate offers DoIP diagnostics, more precisely approximately 100 times of CAN diagnosis.

This topic was modified 4 months ago by admin


©2023 LocalAd


We're not around right now. But you can send us an email and we'll get back to you, asap.

WordPress Ads

Log in with your credentials


Forgot your details?

Create Account