What Is CAN Bus?
In full, CAN Bus is a controller Area Network used in most vehicles to connect the ECUs with corresponding sensors. It is a lower cost yet robust way of sending message-based protocols. In another way, it can be described as the complete version of the human nervous system. Therefore, nodes act as the central networking base and can also be referred to as the electric control units.
A control unit can be in various forms, per se. It could be the engine unit, airbags, or even the transmission base. Most modern vehicles have as many as seventy electronic control units. To break this further, the CAN Bus enables communications between these electronic units without rapid wiring as previous makes did. This ease allows for additional actions like software installations. The main incentive of CAN Bus, therefore, is to minimize the workload on the controlling computer while still enabling a smooth flow of communication between each ECU. Apart from running connection and signals, it also:
- Gives your vehicle a lower weight
- Enables the control system easy to operate or regulate
- Shares a data line lowering the risk of connection errors
- Has modules which make the diagnostics of the vehicle quite simplified
- Is also more affordable compared to the ease of use
CAN Bus Development History
Recognizing that wires tend to be quite different due to designs, sizes, and makes also affects CAN Bus usage. Robert Bosch is mostly accredited with his discovery of the BUS in the late twentieth century.
Pre CAN: In this wake, a theater was only wired connections from one ECU to another.
1986: Bosch developed the model of CAN Bus in 1986, which later made headlines in an SAE Meeting. He later published the 11 bit, and 29 bit CAN versions in 1999.
1993: Later on, in 1993, CAN received ISO Certification to begin working and adoption.
2012: In 2012, Bosch released the CAN FD 1.0 with flexible data rates.
The Future Of CAN Bus
There is a future for the use of CAN Bus. This is mostly because of its adoption in the marine industry and another field of electric handling. The elevation of the flexible data rate version of CAN also brightens the future if adopted. The major use of the internet is another attributing factor giving CAN a promising future as well. The future is also rife, considering the development of cloud technology and improved cellular networking such as mobile data and Wi-Fi. The continued adoption also ensures it is here to stay. Virtually all cars and ships are being built with this technology in mind and it’s a great repulsion towards its extinction.
Advantages Of CAN Bus
Flexible Data Rates
With a speed rate of about one megabit, this system is regarded as one of the fastest internet connections ever. This makes it more appealing as compared to other types of BUS. The support of a larger bandwidth is also good to go. It also contains a chip that receives all messages, decides how relevant they are before acting accordingly. Such criteria will allow for the inclusion of any other useful nodes.
The reduced running of wires in the vehicle’s body is a plus for this type of BUS. The less complexity it oozes also increases usage by several companies.
ECUs communicate only through a single CAN interface, which therefore minimizes possible errors and charges. A lot of resources, including money and time, is saved. The amount of time spent wiring is lowered a great deal. This implies that the cost that would be channeled into buying wires is also significantly saved. You can get ample time, especially for flash programming.
The CAN Bus is suited for several electric-based environments. This is a good option considering the several numbers of electric interactions with which the industries are associated.
Another way to retract a number of errors, especially for the CAN Bus, savors compatibility. This can be useful in realizing bit error, CRC error, and even form error.
CAN are typically prioritized through ids so that those with the highest priority are not interrupted. Such a good example is vehicle systems.
What Is A CAN Bus Message And How Do You Log And Convert It?
A CAN Bus message comprises eight components that make it easy to log in with a CAN interface or logger. CAN message uses a format CAN 2.0B for its messages. This system has numerous components that work with one another. They should also be integral. A logger is needed to log any kind of information.
Components Of A CAN Bus Message
- SOF: this acts as a tip-off that sends a signal that a message is about to be received.
- CAN-ID: usually has the identifier for the message that is on the way
- RTR: enables electronic control units to request information from one another
- Control: determines the length of data to be used
- Data: contains the actual information from the data sets to be used or presented
- CRC: is uses to check how integral the data is
- ACK: confirms if the CRC above is working in good condition
- EOF: seals the end of the message
Logging in therefore requires three scenarios:
- The CAN ID
- Data field
Therefore, interfaces or loggers act as the nodes on the BUS system and will read all the messages. They are then transferred to a waiting storage in the form of an SD card. It is prudent to note that applications require various scenes to connect to the logger or interface.
How To Log CAN Bus Data And Convert Into The Human-readable Form
To be able to read such information, a conversion must be done first. This means you can also decode CAN-BUS data. To convert a raw data set into readable form, you can reversely engineer the CAN Bus data, a challenging task to partake. For every ID, you have to be sound of the parameters being used. For instance, in 64 bits of data in 34d, you are most likely to find CAN data emanating from three parameters. They all have different bit start as well as bit lengths. To code CAN information, you should have each CAN signal. Basically, it will involve the conversion by combining the decimal values of the information offered.
It uses the formulae: (Scaled data value)= (offset) + (scale) multiplied by the raw decimal data value
N/B: For every parameter, offset and scale values have to be known.
What Is The Link Between CAN Bus And J1939, OBD-II And CANopen?
The comparison is a must for a very tricky situation. There is a need to make sure that there are higher protocols to be observed. Some of them include CAN Bus and J1939, OBD-II, and CANopen. This is why both have to run together. In this context, therefore, CAN Bus provides the communication criteria. While more than eight megabits can be difficult for the CAN to handle, the higher protocols like the one mentioned are quite useful.
Also referred to as SAE J1939, it is used for higher trucks and buses. Its messages use the extended version of the 29-bit identifiers. Its parameters are also identified through a suspect parameter number, which is grouped into a larger parameter number.
As the full translation of OBD-II, on-board diagnostics is a self-diagnosing technique that reports what is wrong with a vehicle. It specifies the number of diagnostic trouble codes easily retrieved through a CAN logger from any vehicle. It also has support for several real-time parameters like speeds and fuel consumption. To log data from OBD-II, the logger must request data by submitting certain CAN frames with specific ids to the CAN Bus.
They are widely used in industrial applications that are automated. The can is built on physical layers and the data linking layer. A data logger is used for logging data from CANopen apps through the technique as ex-post data conversion varies depending on the specified application.
The CAN Bus is a nice technique to include as part of most vehicles’ systems due to its features and costs. This is a way to save you from numerous expenses that come along, especially if you opt for old models. Such a good way of operation for your vehicle should not be taken lightly.