EX. NO.1.

B
CANKING – CAN SIMULATION SOFTWARE
02-07-2019

AIM:

To implement a Controller Area Network using the CANKing Simulation Software.

System Requirements:

Operating System: Windows

Driver: Kvaser’s CANlib 3.9 driver

CANBUS

The CAN bus is a broadcast type of bus. This means that all nodes can “hear” all transmissions.
There is no way to send a message to just a specific node; all nodes will invariably pick up all traffic.
The CAN hardware, however, provides local filtering so that each node may react only on the
interesting messages.

The bus uses Non-Return To Zero (NRZ) with bit-stuffing. The modules are connected to the bus in a
wired-and fashion: if just one node is driving the bus to a logical 0, then the whole bus is in that state
regardless of the number of nodes transmitting a logical 1.

The CAN standard defines four different message types. The messages uses a clever scheme of bit-
wise arbitration to control access to the bus, and each message is tagged with a priority.

The CAN standard also defines an elaborate scheme for error handling and confinement which is
described in more detail in Section 9, “CAN Error Handling”

CANKing

CANKing is a CAN bus monitor and general-purpose diagnostic tool. It is especially suited for
interactive development work. CAN messages can be easily sent and the corresponding impact on
the target module observed. To use CANKing it is necessary to purchase one of our CAN interfaces
such as the Kvaser Leaf USB to CAN converters. It is a free software that comes with the Kvaser
product. This product allows the user to see all CAN messages on the bus in either either decimal or
hexadecimal forms. It also allows the user to send out simple test messages.

CanKing for Windows is a CAN bus monitor and general-purpose diagnostic tool. It is especially
suited for interactive development work. CAN messages can be easily sent and the corresponding
impact on the target module observed.

CanKing Features:

 Send & Receive CAN and Extended CAN messages

  Supports CAN FD, both ISO and non-ISO
 Log to File (Up to 4 Channels)
 Filter Messages
 Generate Error Frames
 Timed Transmission
 History Transmit List
 Traffic Generator
 Virtual CAN Channels
 Choose your own Bus Parameters
 CANkingdom Message Formatters
 Supports Custom Formatter
 J1939 Identifier Formatter

SOFTWARE SIMULATION:
In the templates window, the number of CAN channels can be selected under “Standard”
toolbox. The CANKing supports up to maximum 5 channels for simulation. Under “CAN Kingdom”
tool, CAN Kingdom Basics can be selected.

Fig.1.1. CanKing Templates window

After the CAN channels are getting selected, The CAN Controller window is opened. The CAN
controller window consists of all the parameters for bus monitoring in the Configuration tab and
Hardware filters tab.
 Fig. 1.2 CAN Controller window

Bus Configuration This section is for setting up the bit rate and bit timing for the CAN controller.

 CAN Channel Selects the CAN channel.

 CAN Mode Selects the CAN mode. There are different modes available depending on the
selected controller. The modes are CAN, CAN FD and CAN FD non-ISO.

 CAN - Classic CAN.

 CAN FD - CAN with Flexible Data-Rate, ISO compliant.
 CAN FD non-ISO - CAN with Flexible Data-Rate, not ISO compliant.

 Access Mode Selects the access mode. There are three different modes available.

 Init Access - The default mode. It means that the Can King owns the
handle and can set bit rate and CAN driver mode. At most one thread
can have init access to any given channel.
 No init access - Means that Can King will not try to (nor is it allowed to)
change the prevailing bit rate on the channel.
 Exclusive Access - Ensure that KvaserCanKing has exclusive access to
the CAN channel.

 Silent Mode Selects the CAN driver mode: Normal (unchecked) or Silent. Silent mode means
that nothing is transmitted on the bus. The interface is in a non-obtrusive listening
mode and can not affect the ongoing traffic. Not all controllers supports silent
mode.
 Bus Speed Selects the speed in Kbits per second on the CAN bus

 SJW Selects the size of the Synchronization Jump Width. The size of SJW is limited
by the size of the phase segments.

 Bit timing Tseg1 - The number of quanta before the sampling point. Not including sync
segment.

Tseg2 - The number of quanta after the sampling point.

The Formatter Window

The Formatter Window converts CAN messages to text strings.

Fig. 1.3 CanKing Formatter window

 Standard Text Format

Creates lines with the CAN Identifier, message flags, length, and contents, plus a time stamp and
a letter indicating the direction of the message.

 Pass Filter

Acts as a software message filter. Only messages with CAN identifiers within a certain range are
let through.

 Direction Filter

Here one can choose to receive TX or RX or both.

Transmitting and Receiving messages:On the CAN Controller screen, the correct CAN Channel is
selected depending on what card and drivers are properly installed. The correct Baud Speed (same
bit rate as set for all nodes) is selected On the Bus Statistics tab, “Go On Bus” options is selected.
Now it is possible to send and receive messages. To send messages go to Messages->Universal-
>Universal.In the Output Window, the received messages can be seen.

In the CAN message Window, the message data can be given by configuring the length of the data
(DLC). For CAN FD, the DLC supports maximum of 64 bits. After selecting the data bits, the data are
sent to the CAN bus.

Fig. 1.5 CanKing Message window

The output window shows the information about the channel which transmits the data, Identifier
number, Data length, actual data and time required for data transfer on the bus.

Fig. 1.6 CanKing Output window

RESULT

Thus the Controller Area Network protocol was simulated using CANKing Simulation Software.