CAN Diagnosis and Reverse engineering with PicoScope 7 Automotive

In this video we use PicoScope 7 Automotive software to decode CAN serial data and detect CAN wiring faults using, Maths, Masks & Actions. We then apply reverse engineering techniques to identify ECU's present on the CAN network, direction of CAN messaging (using a current clamp) and finally calculate the timing between physical events (such as brake pedal application) and the appearance of brake pedal activation messaging appearing on the CAN network.
-------------------------------------------------------
🔽 Links 🔽 -
PicoScope A-Z - www.picoauto.com/library/pico...
Newsletter - www.picoauto.com/news
Instagram - / lifeatpico
Facebook - / picoauto
-------------------------------------------------------
#picoscope #oscilloscope #automotive #diagnostics #picoauto #automotivediagnostics #picoautomotive

[@freeride202]

The use of a current clamp is mind blowing. I see many people asking how to figure which module matches which ID. I too have been wondering this but with the use of the current clamp, you can see the which packet is coming out of the module. This is awesome information. I love how new techniques see to be endless with this scope. Mine is still going strong after 14 years and is still one of the most advanced tools in the industry.

[@TechScottBrown]

Wow, this was an awesome demonstration. I have been diving deep into CAN with PICO and this video uncovered a few techniques that will help me tremendously. Thank you very much for taking the time to assemble this demonstration.

[@traildisc155]

I messaged you in instagram

[@kylewhitaker9707]

Great video as always Steve. Looks like Ben may have "set you up" lol. Good stuff!!

[@ademiltonxavier5405]

Last week I used my 4425 to help with a CAN J1939 network diagnostics and it went very well

[@marcsinnaeve9937]

Thanks steve. I learned something.... as usual. Cheers

[@Thefox2000unit]

This is outstanding stuff! 👍🏻

[@juergenscholl2843]

Thank you for this video!
A math channel CAN HI minus CAN LOW additionally will allow to see regular network activity which doesn't show up on a CAN HI plus CAN LOW math channel.

[@DrivelineMaster]

I found the serial decoding interesting. I did notice that even when you did not introduce a fault the serial data indicated that some packets had faults. I'm also interested in how you determined the ID of a module and if that ID to module is uniform across all vehicles or are the specific by manufacture. In other words 1A0 was ABS for Audi but could ABS for a Ford be different?

[@nwadeswim]

Also wondering

[@jonsdiagnostic5879]

You cant

[@overload3996]

Its up to, and in favor to the vehicle maker, and programmer for class C _ CAN FD designers. As class B is different single or dual wire. SAE has loads of resource available.

[@DrivelineMaster]

I dug a little deeper and it seems from what I can tell is nobody has a list and its all done by personal testing of monitoring ID's and then disconnecting modules. For this video my guess is that two factors made it easy to identify the ABS module. 1) the module was easy to get to under the hood and 2) the brake light input signal was easy to activate and watch for. I suspect that each manufacture and it may also be year and model specific has their own module ID's. This sucks for technicians.

[@benmoody2975]

@@DrivelineMaster Yes, but many people have done this for you and there are various sources of .dbc files on the internet if you search

[@phillipzan2005]

Relatively good video. Here is my question. If I see 1A0 has errors how do I figure out that is the ABS module? It's not like the manufactures will just tell me. Because other than seeing a fault the decode and and the other tests kinda becomes useless to us none engineers.

[@Bikerman42]

Great video. I would also like to know where you find the code information.

[@rodvan-zeller6360]

At 18:48 if one of the terminating resistors was in the module you disconnected would you be able to decode anything with the disruption?

[@tullgutten]

15:50 as you say the sample rate doesn't need to be that high and turn it down almost everything went to errors 😂
And you had a notification throughout the whole capture before that the bitrate allready could be too low to have proper decoding and the canbus bits all have triangular edges so right on the edge of just enough

[@petermc1743]

Excellent thank you! I'd love to find the packet header address information (e.g. 1A0 = ABS). Is this a CAN standard or is it proprietary to manufacturer or even model? Anybody?

[@hvacinstalacije1985]

Hi,
Can we simulate PWM for AC Compressors , do you have a guide ?

[@nwadeswim]

Also interested in where to source the packet IDs!?

[@Piotrek0101]

look for css can in.. you know better where😉

[@nwadeswim]

@@Piotrek0101 I'm confused

[@Piotrek0101]

@@nwadeswim i cant share on YT complett adress. Company name is „css electronics” from denmark. They have a many useful files. Free of charges.

[@sammy5576]

where do you get wiring diagrams from?

[@harlabhsingh4349]

Thanks Steve very nice can you tell us how can scoping can network when you have Gatway module Plz Thanks

[@carbie5614]

Man, I have been trying to understand scopes, Pico scope for over a year now and I still know absolutely nothing. I see how to do stuff I just have no idea what I am looking at or the connection of the traces, just realized what a trace is, to any sensor. Maybe Sort of when watching Pine hollow auto diagnoses. I will keep watching though maybe an epiphany will happen.

[@rexjames0015]

You try to pull it off but CAN is really quite beyond you isn't it steve?