Very well explained and informative video, thank you! I have since learned CAN bus physical/transport layers (including the 4 message frame types) and have been using the CANopen protocol to program a number of PLCs professionally, but have seen this j1939 protocol being used a few times with CAN 2.0B especially within the IC engine ECUs (I’ve only really needed to use 2.0A so far). Hence, this has inspired me to start learning it so I can understand and control how our PLC/ECUs components talk to each other! :D SAE 1939-71 is going to fair out to be a _very_ useful reference I imagine…
Thanks for the feedback! Yes, J1939-71 would be a good resource for the purpose of recording J1939 data :-) See also our J1939 DBC that takes the contents of the J1939-71 PDF (PGNs & SPNs) and puts it in the standardized DBC format.
Thank you for the explanation, I am now learning J1939 Can for fleet management. So the best practice to extract data from vehicle is to log it first, decode and decide what data that we need to extract?
Our recommendation is at least that you should start by "logging everything" during an initial evaluation period. You can then DBC decode the data and review what CAN IDs you can decode and which of them contain data that is relevant to your use case. All irrelevant CAN IDs can be filtered out via the CANedge configuration. For the remaining relevant CAN IDs, we then suggest to evaluate what frequency you need the data at. For example, Engine Speed is typically broadcast at 500-1000 Hz on the CAN bus, but most use cases need it at only 1-10 Hz. By using our prescalers to handle this on the device you can typically reduce your data size by 95%+ without loosing relevant information.
Hello, Could you tell me please if I want to reprogram a tractor display to add one more language to it how can I start? I don't have any experience in programming but now I want to learn. Could you tell me some instruction?
how do I connect to the 3 pin connector via diagnostics. I have 493033 data link connector from Cummins inline 7. I cannot find any tutorials and or anything relative on using this through diagnostic software.
Hi, why J1939 is only used in trucks? it seams to me a good protocol that car manufactures can benefit from too right, given they already have their CAN infrastruture
![CAN Bus Explained - A Simple Intro [v2.0 | 2021] 🌟](http://i.ytimg.com/vi/oYps7vT708E/mqdefault.jpg)
![Unified Diagnostic Services (UDS) Explained - A Simple Intro [2022]](/img/n.gif)
Behind music is so good it feels like really learning ,progress and the way it explained wonderful 👍👍👍
Very well explained and informative video, thank you! I have since learned CAN bus physical/transport layers (including the 4 message frame types) and have been using the CANopen protocol to program a number of PLCs professionally, but have seen this j1939 protocol being used a few times with CAN 2.0B especially within the IC engine ECUs (I’ve only really needed to use 2.0A so far). Hence, this has inspired me to start learning it so I can understand and control how our PLC/ECUs components talk to each other! :D
SAE 1939-71 is going to fair out to be a _very_ useful reference I imagine…
Thanks for the feedback! Yes, J1939-71 would be a good resource for the purpose of recording J1939 data :-) See also our J1939 DBC that takes the contents of the J1939-71 PDF (PGNs & SPNs) and puts it in the standardized DBC format.
amazed with explaination.....very helpful video
Helpful information. Starting around 2:50, it appears that the slides are incomplete.
Very clean, clear and easy to follow great video!
Thank you for the explanation, I am now learning J1939 Can for fleet management.
So the best practice to extract data from vehicle is to log it first, decode and decide what data that we need to extract?
Our recommendation is at least that you should start by "logging everything" during an initial evaluation period. You can then DBC decode the data and review what CAN IDs you can decode and which of them contain data that is relevant to your use case. All irrelevant CAN IDs can be filtered out via the CANedge configuration. For the remaining relevant CAN IDs, we then suggest to evaluate what frequency you need the data at. For example, Engine Speed is typically broadcast at 500-1000 Hz on the CAN bus, but most use cases need it at only 1-10 Hz. By using our prescalers to handle this on the device you can typically reduce your data size by 95%+ without loosing relevant information.
Awesome video, thanks for sharing
Wonderful understanding ...
Well detailed, thank you i learned a lot from this video
Glad to hear Rayen!
Thank
Hello,
Could you tell me please if I want to reprogram a tractor display to add one more language to it how can I start?
I don't have any experience in programming but now I want to learn.
Could you tell me some instruction?
Thank you!Very useful!
Thank you!
What it means the code MpJ1939? (In this case i want to know about "Mp" that is included)
Let us know if you have any questions regarding the J1939 protocol!
how do I connect to the 3 pin connector via diagnostics. I have 493033 data link connector from Cummins inline 7. I cannot find any tutorials and or anything relative on using this through diagnostic software.
Hi, why J1939 is only used in trucks? it seams to me a good protocol that car manufactures can benefit from too right, given they already have their CAN infrastruture
@@_tranquangtien8854 i know that it is used in fendt tractors too
My truck displays a fault code CAN j1939 active fault.
How can mapped to j1939 please explain it