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?
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.
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.
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.
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.
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.
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
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?
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.
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.
