CAN Bus stands for “Controller Area Network” Bus.
CAN-bus is one of those technologies that everyone experiences every day, without actually knowing about it. Because it is so widely used, in everything from cars and trucks through to boats, factories and even building management systems, the chances of interacting with it on a daily basis are pretty high.
CAN is a vehicle bus standard designed to allow microcontrollers and devices to communicate with each other in applications without a host computer. It is a message-based protocol, designed originally for multiplex electrical wiring within automobiles, but is also used in many other contexts.
You should get to know this protocol as it will allow you to expand your expertise and opportunities in design and building equipment in the following areas: Automotive, Medical, Military, Industrial Machines, Aviation, etc.
There is quite a bit of info on CAN Bus available on the Internet, but not much showing CAN Bus communications in a very practical way. And that’s what I am going to do in the course.
At the end of my course, you are not only going to understand the CAN Bus theory but I am going to show you how to use CAN Bus hardware and software in my usual practical approach.
CAN bus was developed due to the increasing number of features, and therefore electronic components, that were being added to automotive vehicles.
An example using an automatic door of a minivan to see how CAN bus plays a role.
Network Arbitration is defined from a practical standpoint.
A look at the network arbitration methods for Modbus RS485 and Ethernet on a LAN.
The CAN Bus Network Arbitration Method - Part 1
The CAN Bus Network Arbitration Method - Part 2
A look at the typical CAN Bus frame format and the names / purposes of the various sections.
The bus system used is a pair of wires. This lecture explores the voltages that exist on the wire pair and how logic 0 and 1 are represented.
The purpose of the message identifier field is 2-fold: it acts as a unique identifier as well as sets the priority of the message on the network.
Most of the messages that are transmitted on the CAN Bus network will happen without collision.
How the message identifier implements non destructive collision detection at the byte level.
The contents of the data byte field are not specified by the CAN Bus specification.
This section is ended and in the next section we look at some practical before jumping back into more theory.
A look at the website of the company Tangent Technolabs where the CAN training kit was acquired.
A look at the CAN Bus hardware that will be used in this section; how it is set up on my work bench.
The lecture runs through the configuration plan for the CAN Bus nodes 1 and 2, that needs to be done to create the CAN Bus network.
Programming CAN Bus Node 1
Programming CAN Bus Node 2
The hardware is started and the inputs are actuated.
Looking at the Connection of the CAN Bus Analyzer on the Work Bench
Using the CAN Bus analyzer to View Message Data on the CAN Bus Network
This lecture looks at the following parts of the standard CAN data packet: SOF, EOF, DLC, R0, IDE and CRC.
Remote Transmission Request and The Remote Frame.
A look at the ACK field in the CAN data packet.
A look at the basic CAN implementation used in the world today.
Over the years, different industries have taken the basic CAN Bus protocol and built their own protocols on top of it.