rusefi
/
rusefi_documentation
mirror of https://github.com/rusefi/rusefi_documentation.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix CAN sniffer (#95) 

* fix CAN Sniffer page

* few more oopsies

* wrong extension

* wrong extension

* another link
This commit is contained in:
David Holdeman 2020-08-29 22:02:21 -05:00 committed by GitHub
parent d2f0622059
commit eeb1277bfc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
CAN-Sniffer.md
View File

@ -4,11 +4,11 @@ In this HOWTO I will explain how to see raw CAN message flow with less than $30
## Step 1: shopping cart
1. Get an [http://www.st.com/web/catalog/tools/FM116/SC959/SS1532/PF252419 STM32F4DISCOVERY] micro-controller board - there are 'Order Now' buttons at the bottom of the official page.
1. Get an [STM32F4DISCOVERY](http://www.st.com/web/catalog/tools/FM116/SC959/SS1532/PF252419) micro-controller board - there are 'Order Now' buttons at the bottom of the official page.
![STM32F4Discovery](Images/2014-08-21T15-20-24.645Z-stm32f4_discovery.jpg)
2. Get an [http://www.wvshare.com/product/SN65HVD230-CAN-Board.htm SN65HVD230 CAN Board]
2. Get an [SN65HVD230 CAN Board](http://www.wvshare.com/product/SN65HVD230-CAN-Board.htm)
![SN65HVD230 CAN Board](Images/sn65hvd230-can-board_l_1_5.jpg)
@ -28,7 +28,7 @@ Run some wires from these pins to CANH (high) and CANL (low) screw terminals of
Here is how the end result should look like:
![CAN hardware end result](Images/CAN_hardware.png)
![CAN hardware end result](Images/CAN_hardware.jpg)
Ignore the white wire - we do not need it.
@ -36,35 +36,37 @@ Run female-female jumper wires to connect TX on the CAN module with pin PB6 on t
Hardware is ready!
![CAN hardware attached to Discovery](Images/CAN_hardware2.png)
![CAN hardware attached to Discovery](Images/CAN_hardware2.jpg)
## Step 3: software
1. Download and install [http://www.st.com/web/en/catalog/tools/PF258168 STSW-LINK004 STM32 ST-LINK utility]
1. Download and install [STSW-LINK004 STM32 ST-LINK utility](http://www.st.com/web/en/catalog/tools/PF258168)
2. Firmware: download and unzip [http://rusefi.com/images/forum_posts/CAN/rusefi_can_sniffer.zip rusefi_can_sniffer.zip]
2. Firmware: download and unzip [rusefi_can_sniffer.zip](http://rusefi.com/images/forum_posts/CAN/rusefi_can_sniffer.zip)
2. Uploading the firmware: Connect stm32f4discovery to your laptop using a mini-USB cable (one should come with the board), install driver, start St-Link Utility.
![ST Link Utility](Images/st_link_utility.png)
click 'Target'>'Program...'
![ST Link Start](Images/st_link_start.png)
Point the utility to the rusefi_can_sniffer.hex file and hit 'Start'
Close ST Link Utility.
3. Now it's time to connect the micro USB cable. Keep miniUSB cable connected - you should have two USB cables connected. When you do this for the first time your Windows would prompt for drivers, you should download & install [http://www.st.com/web/en/catalog/tools/PF257938 virtual COM driver]
3. Now it's time to connect the micro USB cable. Keep miniUSB cable connected - you should have two USB cables connected. When you do this for the first time your Windows would prompt for drivers, you should download & install [virtual COM driver](http://www.st.com/web/en/catalog/tools/PF257938)
Once the driver is installed, you can verify serial connectivity by opening your Device Manager - we are expecting to see a Virtual COM Port.
![Device Manager](Images/device_manager.png)
Remember the number of the COM port.
4. Download and launch [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty] telnet application.
4. Download and launch [Putty](http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html) telnet application.
![Putty](Images/putty.png)
![CAN hardware attached to laptop](Images/CAN_hardware3.png)
![CAN hardware attached to laptop](Images/CAN_hardware3.jpg)
Now connect the obd connector to your vehicle and you should see the CAN messages flowing in putty.
![CAN messages on computer screen](Images/CAN_end_result.jpg)