0% found this document useful (0 votes)
30 views22 pages

CAN100 Sniffing - 20240625

100

Uploaded by

muhammad.ansab
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
0% found this document useful (0 votes)
30 views22 pages

CAN100 Sniffing - 20240625

100

Uploaded by

muhammad.ansab
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/ 22

Document Title

CAN100 Sniffing

Version:[202012]

Product Model

[Document ID] 0
Document Title

Document Title [Document Title]

Version [1.00]

Date [YYYY-MM-DD]

Status [Draft | Release]


Document Control
[Document ID]
ID

General Notes
Queclink offers this information as a service to its customers, to support application
and engineering efforts that use the products designed by Queclink. The information
provided is based upon requirements specifically provided to Queclink by the
customers. Queclink has not undertaken any independent search for additional
relevant information,including any information that may be in the customer’s
possession. Furthermore, system validation of this product designed by Queclink
within a larger electronic system remains the responsibility of the customer or the
customer’s system integrator. All specifications supplied herein are subject to change.

Copyright
This document contains proprietary technical information which is the property of
Queclink Limited. The copying of this document, distribution to others, and
communication of the contents thereof, are forbidden without express authority.
Offenders are liable to the payment of damages. All rights are reserved in the event of
a patent grant or registration of a utility model or design. All specification supplied
herein are subject to change without notice at any time.

Copyright © Queclink Wireless Solutions Co., Ltd. 2015

[Document ID] 1
Document Title

Contents
Contents........................................................................................................................................... 2
0. Revision history .......................................................................................................................... 3
1. Introduction ................................................................................................................................. 4
1.1. Reference ........................................................................................................................ 4
1.2. Terms and abbreviations ............................................................................................... 4
2. Preparation.................................................................................................................................... 5
2.1. Tool Preparation .............................................................................................................. 5
2.2. Confirmation of Vehicle and Other Information .......................................................... 6
3. On-site Operation.......................................................................................................................... 8
3.1. Disassembling the Vehicle ............................................................................................ 8
3.2. Using an Oscilloscope to find CAN H/L ....................................................................... 9
3.3. Collecting the logs ........................................................................................................ 10
3.3.1. Connecting the CAN100 to CANBUS ............................................................... 10
3.3.2. Running the Software and recording the vehicle information ........................ 10
3.3.3. Scenario Testing............................................................................................... 11
3.3.3.1. IGN .......................................................................................................... 12
3.3.3.2. Drive ........................................................................................................ 13
3.3.3.3. Refueling (petrol/diesel vehicle) ............................................................. 14
3.3.3.4. Battery charging (electric vehicle) ........................................................... 14
3.3.3.5. Charger (electric vehicle)......................................................................... 15
3.3.3.6. Break pedal ............................................................................................. 15
3.4. Take photos ................................................................................................................... 15
4. Data and Photo Organization ...................................................................................................... 19
5. Creating a case and following ................................................................................................ 20

[Document ID] 2
Document Title

0. Revision history

Revision Date Author Description of change


1.00 [2024.5.23] Dylan Initial

[Document ID] 3
Document Title

1. Introduction

This document primarily outlines the entire process of using the CAN100 to support new
vehicle models and some potential issues that may be encountered during log collection. Here
is the overview of the Entire process
 Understand the parameters that the client is concerned about.
 Capture logs and take photos on-site according to the CANv3 DataLogger manual.
 Create a task in Zendesk and assign to Dylan. The subject format should follow:
[CAN100 Sniffing] Vehicle Model Year
 Follow up until the case is closed.
Note:Based on experience, assuming the data is correct, engineers may require approximately
two days to complete data analysis. Integrating into the new firmware could take around a
week. During the data analysis process, there might be instances where data needs to be re-
collected.

1.1. Reference

Table 1: Reference

SN Document name Remark


[1]
CANv3 DataLogger Introduction to Tools and General Steps
manual
[2] CANv3 DataLogger
scenarios For different parameters that client maybe interested in,
there are different application scenarios.

1.2. Terms and abbreviations

Table 2: Terms and abbreviations

Abbreviation Description
Oscilloscope In order to find the correct CAN high/low
CAN_H CAN High signal
CAN_L CAN Low signal

[Document ID] 4
Document Title

2. Preparation

2.1. Tool Preparation

Name Picture Remark


In order to find the
Oscilloscope correct CAN high/low

Wiring Kit Convenient Wiring

Pogo-pin It can quickly test the


connector.

Tools Standard car disassembly


tools, such as wrenches.

[Document ID] 5
Document Title

OBD Connector To connect the OBD

interface。

Power supply;

Disassembly Tool Kit Specialized Plastic Casing


Removal Tool(Optional).
Absolutely, handling
specialized plastic casing
removal should indeed be
entrusted to professionals.

CAN100/BLECAN100 CLV3 version. Please make


sure the version is greater
than 3.0.17.
Note: It is recommended
to bring two sets.

CAN100 debug cable Debug cable with RS232.


Note: It is recommended
to bring two sets.

2.2. Confirmation of Vehicle and Other Information


1. Please make sure the fuel level / battery level is low in order that it is easy to do the fueling
and charging scenarios.
Note: Car should have as less fuel level as possible (it is the best if low-fuel indicator is on), but
not more than 80%.
2. It would be better that there is fast charge station around the electric vehicle you are going to
test.
3. Please make sure it is allowed to take photos where you are going to collect data.

[Document ID] 6
Document Title

4. Confirm with Dylan whether there are installation diagrams and some tips available.

[Document ID] 7
Document Title

3. On-site Operation

Before going to the site, it is recommended to familiarize yourself with these two documents.
CANv3 DataLogger manual
CANv3 DataLogger scenarios

3.1. Disassembling the Vehicle

This part of disassembling the vehicle is best handled by professionals to prevent any damage
to the customer's car. There are a few points to reference when disassembling the vehicle.
 Look for twisted pair wires near the OBD interface(Usually in the driver's seat). Or the
yellow part.

 Search for twisted pair wires beneath the passenger glove compartment.

 Directly search for twisted pair wires from the dashboard interface.

[Document ID] 8
Document Title

3.2. Using an Oscilloscope to find CAN H/L

3.2.1. How to use tools

 Fluke
Refer to this video.
 Oscilloscope
The key is to select the correct range and sampling frequency.

3.2.2. How to find CAN bus

 Not every twisted pair wire is a CAN BUS.


 If the wire colors are the same, it is highly likely that they are the same CAN signals.
 The waveform characteristics of CAN High (CAN H) and CAN Low (CAN L) are as follows:

CAH High: Green. Voltage range 2.5 ~ 3.5V.


CAN Low: White. Voltage range 1.5~ 2.5V.
Note: It is possible that the CAN BUS can not be sniffed by CAN100, because the CAN
BUS is not correct, even though the voltage is correct.
 Attempt to find as many CAN buses as possible. (Objective: To identify the correct set of
CAN buses as accurately as possible in one attempt.)

[Document ID] 9
Document Title

3.3. Collecting the logs

3.3.1. Connecting the CAN100 to CANBUS

Note:
1. For log capturing, there is no distinction between CAN1 and CAN2.
2. Pay attention to distinguishing between CAN High and CAN Low.

3.3.2. Running the Software and recording the vehicle information

Accurately fill in the vehicle information, and you can include any other findings in the
description.

[Document ID] 10
Document Title

Next,

3.3.3. Scenario Testing

Different parameters correspond to different application scenarios. The same scenario can be
tested multiple times. Here are several typical application scenarios.
Before conducting tests, you must be familiar with vehicle operations, such as
o how to start the vehicle?
o how to retrieve vehicle information?
o how to reset certain accumulators, such as trip statistics?
Note: The ignition on is different to engine on.

[Document ID] 11
Document Title

3.3.3.1. IGN

You can input the notes here,

Scenarios notes:
The vehicle status of the test began with ignition ON.
1. Step1. Ignition Off.
2. Step2. Start/sop Button first time, screen on
3. Step3 . Start/sop Button second time, ACC on.
4. Step4. Step the break and Start/sop button third time to start engine(Engine ON).
5. Step5. In P gear. Accelerator pedal go to bottom.

[Document ID] 12
Document Title

6. Repeat step1-5 3 times.


7. Here is max RPM each time.
3700,3400,3500,3500
3.3.3.2. Drive

Scenarios notes:
1. Step1. IGN OFF
2. Step2. Switch to ignition on (Drive)
3. Reset trip count.
4. make picture of dashboard
5. Start engine
6. make driver for around 16 km.
7. stop engine
8. switch ignition on again
9. make another pic dashboard
10. stop log
Note. The max speed: 179 KM/H
Engineer Temperautre after driving in 90C degree.

Note: The speed should be more than 80 KM/H. The mileage should be more than 15KM.
If you want to get the coolant temperature parameter, you should start with cold coolant
temperature.

[Document ID] 13
Document Title

3.3.3.3. Refueling (petrol/diesel vehicle)

3.3.3.4. Battery charging (electric vehicle)

[Document ID] 14
Document Title

3.3.3.5. Charger (electric vehicle)

Note:
We must accurately record the number of times the charger is plugged and unplugged.

3.3.3.6. Brake pedal

3.4. Take photos

After finishing the log capturing, it's essential to record vehicle photos, including the vehicle's
exterior, CAN bus wires, PINs, etc. you can refer to the DataLogger manual.

[Document ID] 15
Document Title

Incorrect one Correct one Remark

This image can


only serve as a
reference. If it's
included in a
diagram, the
Fluke tool should
not be present.

[Document ID] 16
Document Title

It's best to be able to


see the PINs clearly.
Ensure that the
installation
personnel can
identify the
corresponding wires
based on your
pictures.

[Document ID] 17
Document Title

The photos
should be clear.

[Document ID] 18
Document Title

4. Data and Photo Organization

Before transferring the data and photos to QDC, we need to organize the photos, rename
them, and optimize the notes. This is because there may not be enough time to do these tasks
on-site.

Here is the example.

[Document ID] 19
Document Title

5. Creating a case and following

Creating a ticket on Zendesk.


For example:
Topic: [CAN100 Sniffing] Chery Tiggo 8 pro 2024
Assignss
Contents:
The parameters customer was interested in: VIN, RPM, Fuel level, Mileage, Fuel consumption.
Logs and photos link: https://qdc.queclink.com/share/s/-dQQlU6FTAqSAJFQjD3BHg
Notes: Other special requirements, etc.

[Document ID] 20
Document Title

6. FAQ

Part1: CAN BUS


1. The CAN signal of OBD is not available all the time. (Chevrolet tracker 2023)
2. It is possible that the CAN BUS signal can’t be sniffed by CAN100, because the CAN BUS is
not correct one, even though the voltage is correct. (Chevrolet tracker 2023)
Part2: Drive scenario
1. The speed should be more than 80 KM/H. The mileage should be more than 15KM.
2. If you want to get the coolant temperature parameter, you should start with cold coolant
temperature.
Part3: Vehicle
1. Chevrolet tracker 2023 does not have IGN on position. The screen is on only the engine is
on.
2. If the vehicle doesn’t have Ignition ON position, please take a video for Formula detailing
the positions that can be achieved (ACC, Engine ON, Engine OFF). you need to take
corresponding video as well to make it clear if you find other somethings is weird.
3. Some scenario steps that need to have Ignition ON, can be performed with ACC/engine
ON, on this particular vehicle model.

[Document ID] 21

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy