Scribd
Upload
63 views7 pages

Can Bus Decoding and Module ID

The document discusses decoding CAN bus data to identify module IDs. It describes connecting to the CAN bus, measuring the bus speed, setting up serial decoding in software. It then explains how to isolate module IDs by disconnecting individual modules and comparing the messages. It provides steps to create a ID document to decode module names from IDs in captured bus data.

Uploaded by

Sideth Chiv
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
63 views7 pages

Can Bus Decoding and Module ID

The document discusses decoding CAN bus data to identify module IDs. It describes connecting to the CAN bus, measuring the bus speed, setting up serial decoding in software. It then explains how to isolate module IDs by disconnecting individual modules and comparing the messages. It provides steps to create a ID document to decode module names from IDs in captured bus data.

Uploaded by

Sideth Chiv
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

Can bus decoding and module ID’s

Connect to the can bus and capture the bus activity.

You will need to know the bus speed for the bus to be decoded. If this is not
known zoom in on the smallest bit of data and measure the length of the data.
You now need to add the math calculation A-B
This will then give us a 0 to 2 volt calculation the ECU will see and we use this
for the decoding.

Now go into serial decoding and select can. Select A-B, the baud rate
depending on the speed and the threshold of 1 volt as this is the mid voltage
the 0 to 2 volt scale.
You will now see the bus data displayed below your bus capture. The data can
then be exported into excel.

There will be a large number of messages repeated and as we are only trying to
identify ID’s we can remove duplicate ID’s but selecting the ID column and then
remove duplicates.
To work out the origin of the ID we can now disconnect or remove the power
supply to one of the modules run the bus capture again and export the
messages and remove the duplicates as before.
You can then copy the ID column with the module off line to a new column and
then copy the ID column with all the modules and place it next to it.
Highlight both columns, select home, conditioning formatting then duplicate
values.

Highlighting unique values in red identifies the modules that are there only on
the full ID list. This confirms these ID’s not present with the module off line are
linked to that module.
Note: it doesn’t confirm the ID message comes from that module only the
absence of that message. Its possible other modules will not send that ID with
that particular module off line.
We now need to create a ID document for pico to read.
Go back to your waveform and click on data to text and select create sample.
This will then give you a blank excel form. You then copy and paste the unique
ID’s and paste into the new document and input your description of that
module next to it and save. Do this just for your affect module or all the
modules on the network to give you a full module list.

Now you can go back to your pico bus capture. Select data to text and open
your new decode table.
Now the ID is replaced with the name you have given that ID. (test in my
example)

For extended diagnosis you can then apply a filter for that ID. You can then
monitor the data related to that ID. This is also useful for diagnosis is the
module is going off line but no affecting the bus as you can monitor this ID on
the bus and carry out a wiggle test / road test to see if the module goes off line
anywhere on the bus network.

You might also like