Professional Documents
Culture Documents
03 CAN Bus Rev C - 1
03 CAN Bus Rev C - 1
CAN BUS
It is based on de-centralized
system, where there are several
main programmed units telling
what to do and what do they
hear
2
BASIC STRUCTURE OF CAN BUS
At 80s Bosch designed CAN Bus to reduce cabling at ABS
brakes, then things got out of hand and it expanded to its
current form. BMW 850 at 1980s was one of the first CAN
Bus users
The letters and the physical part is the same, but the
language is different and so are the messages what they
are sending through
PLUS AND MINUS OF CAN BUS
+ -
Wide support from different No deterministic, reply times can only be
manufacturers quaranteed for highest priority messages
Fast, light & relatively easy to build For transferring big amounts of data
requires another protocol
Standardized
Lenght of the bus is limited
Relatively low price components
Optimizing the parameters of the bus
Good offering with different tools etc can be difficult
Lines between the units are the CAN busses transferring data. They deliver
information between the units. Bit like Ethernet cable or WLAN from computer.
DECENTRALIZED SYSTEM
CAN bus systems can be seen as de-centralized system
Example of decentralized system:
1 bit
1 byte
CAN BUS SIGNAL EXAMPLE
Speed means practically frequency
how fastly the bus is being read and
at which rate the nodes try to change
the voltage in the bus
SWG
SCOPE
MEANING OF SIGNAL REFLECTION
If the ends of the cable is shorted, then signal form
changes
CAN CAN
NODE NODE
MEANING OF SIGNAL REFLECTION
In short: The energy of the signal from the
transmitting unit is reflected back to the sender and
the wave form suffers
Messages form up of
voltage changes
FILL
FILL
FILL
CAN MESSAGE TYPES
Data Frame
Most common message type, Error Frame
containing all the neede fields to form Error frame violates formatting rules of
up the message CAN messages. It is transmitted when
node detects error in a message, and
Remote Frame causes the other nodes to send an error
Intended purpose of remote frame is to frame as well. The original transmitter
request data from another node. will then retransmit the message. Error
Difference to Data frame is done by counter system tries to prevent the bus
recessive RTR bit in the arbitration field from overloading in case the node
and it does not contain any data. keeps on sending the messages that
don’t get through
Overload Frame
Similiar to error frame. It is transmitted At some situations if node goes to
by a node that becomes too busy. passive error state it can continue to
Primary using purpose is to provide for send 6 resessive bits, in this way it is
an extra delay between messages. not anymore affecting to the bus
communications.
CAN MESSAGE PRIORISATIONS
Priorisation message can be seen as logical
AND-function with 0 dominant
+5V
For example 3 CAN Nodes which are sending +5V
+5V
CAN ERROR COUNTERS
CAN bus has error calculators which are calculating
the amount of errors in messages
ERROR
BUS OFF
PASSIVE Tx errors > XXX
CAN NODE INTERNAL CONSTRUCTION
Most of the CAN Controllers require 5 Volt control
supply, but in certain condtitions it is possible to use
3.3 Volt supplies
Twisted pair
Standardized protocol
Multimeter
Measurement Adapters
BASIC PRINCIPLE– MOST COMMON TERMS
• Node Device attached to the bus. For example PLC, valve, computer or sensor.
• Node-ID Every device in bus has their own address which they are using to communicate in bus.
Bus cannot have two similiar Node-IDs or they will conflict.
• Bit rate Speed of the bus. Must be same with all the devices in the bus, for example 500 kbit/s.
• NMT Protocol which controls the state of the nodes. NMT-message can be used for example to
start or shut down a device in the bus.
• NMT-master Every bus must have an NMT-master. It has the responsobility of controlled start
of the devices in the bus and stopping the bus data transfers.
• Heartbeat Bus devices active status information, which sends a status of the node to the
bus ( running, stopped etc.)
BASIC FAULT FINDING WITH MULTIMETER
MOST COMMON FAULTS IN BUS
Connection problem outside the bus, for
Connector problem example with powering or groundings
- Water/moisture creates leakages - Lack of grounding of
- Corrosion powering for example due
to a connector failure etc.
Connection mistakes
- When making reconnections Broken component
“being one off” or not attached at all - Sometimes for some
reason, some things just
Node which isn't programmed, incorrectly get broken
programmed, or incorrectly configured
- When a new spare part is delivered Outside components which generate
and it is not configured or programmed high level of EMC faults for example
correctly - If something “out of normal”
is added to the machine, it
might cause unforeseen
consenquences
BASIC PRINCIPLES TO FOLLOW
Gold plated connectors everwhere where possible, not to be mixed with tin
ones