Thanks! Got a small project with CanOpen to do under high pressure. No previous knowledge in our organization helps too. But this video was really helpful in figuring out the basics.
Thanks for sharing! Our team ended up creating a new, more simple protocol due to restriction of low energy controller like STM32. It's called M2TP by the way and it's open source too, currently in development.
Good helpful video ! am new learner about CAN protocol in the automotive field , so what steps should i take to learn it the best way cause people say it's one of the hardest protocols and it feels exhausting
So very hard to follow with the speed and the explanation if he is writing a formal essay. Also the speed is a the pace of commercial. I wonder what intention is? to implant the idea? but with so much information, brains need to digest.
Thanks for the feedback - the pacing is perhaps a bit fast, but if you prefer a slower pace I can recommend reading the full article (link is in the description).
Just a little feedback that a lot of organizations are moving away from “master/slave” language these days. It is honestly hard to listen to this video because of this language. I have noticed for example that the Raspberry Pi foundation no longer uses these terms to describe SPI devices, instead using terms like “SPI TX” and “SPI RX” to reference communications pins rather than old terms like MISO and MOSI. I would have to do some digging to see what other people use but perhaps something like “controller/dependent” could be used. The protocol looks nice! Just wanted to give this specific feedback.
![CAN Bus Explained - A Simple Intro [v2.0 | 2021] 🌟](http://i.ytimg.com/vi/oYps7vT708E/mqdefault.jpg)
Thanks! Got a small project with CanOpen to do under high pressure. No previous knowledge in our organization helps too. But this video was really helpful in figuring out the basics.
Awesome to hear :-)
Thanks for sharing! Our team ended up creating a new, more simple protocol due to restriction of low energy controller like STM32. It's called M2TP by the way and it's open source too, currently in development.
This is interesting, but I haven't been able to find any specification of the protocol, and the documentation in general is quite sparse.
@@mcejp which protocol?
@@KangJangkrik M2TP
Best canopen video I watched, thank you!
Thank you! :-)
CSS Electronics Good Afternoon 👍
Great tutorial thank you very much 👍
From Nick Ayivor from London England UK 🇬🇧
Extremely helpful! Thanks so much!
clearly explained sir.. useful to me
Nice video, provides clarity. Tho one suggestion is that I wished you talked a bit more about PDO mapping
Best can open video
...tnxs
Good helpful video ! am new learner about CAN protocol in the automotive field , so what steps should i take to learn it the best way cause people say it's one of the hardest protocols and it feels exhausting
In the object dictionary, there is manufacture, that means the manufacture need to get approval from canopen company to get certified ?
very good
So the can bus is in the lowest layer of the osi model, and canopen is in the second lowest?
Yes, also there is a possibility for the data to be encoded in BSON format which is supposed to be the highest layer
Hello everyone! Could you help me for a project? I wanna heartbeat for sensors with arduino?
So very hard to follow with the speed and the explanation if he is writing a formal essay. Also the speed is a the pace of commercial. I wonder what intention is? to implant the idea? but with so much information, brains need to digest.
Thanks for the feedback - the pacing is perhaps a bit fast, but if you prefer a slower pace I can recommend reading the full article (link is in the description).
After 5 years of working with CAN and 19 minutes of this video, I still know nothing about CAN. Completely useless.
Just a little feedback that a lot of organizations are moving away from “master/slave” language these days. It is honestly hard to listen to this video because of this language. I have noticed for example that the Raspberry Pi foundation no longer uses these terms to describe SPI devices, instead using terms like “SPI TX” and “SPI RX” to reference communications pins rather than old terms like MISO and MOSI. I would have to do some digging to see what other people use but perhaps something like “controller/dependent” could be used. The protocol looks nice! Just wanted to give this specific feedback.
Seriously! I cannot believe you could be triggered by meaningful terminology.
@@davidzanich530 Relax, you only need to see the hair color to understand where this trigger comes from.