• Locked Locked
  • Replies 1 reply
  • Subscribers 33 subscribers
  • Views 265 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TCAN1043-Q1: CANopen

user5789841
Intellectual 345 points
Part Number: TCAN1043-Q1

Hello TI Experts,

Recently I have got a request from customer , they want to use CANopen protocol  (hardware shall support CANopen FD , CAN FD, ISO 11898-1/-2 , CAN 2.0a and CAN 2.0b)

but this is my first time heard it , so I don't know how to select CAN transceiver and CAN controller ?

And I would like to know what different between CANopen and classic CAN or CAN FD ? Does they can share same hardware concept or we need add some special circuit ?

Thank you!

  • TI__Guru 53555 points

    Hi User,

    Thanks for sharing your question on E2E.

    The CANopen communication system assumes the use of the ISO 11898-2 CAN physical layer specification, so any CAN transceiver that meets this standard will be suitable for use with this software. From my understanding, CANopen is a higher level manager of system information that uses the CAN physical and protocol layers as a base for the lower level layers. Therefore any pin controlled CAN transceiver (such as the 8-pin TCAN1044A or 14-pin TCAN1043A) may be used with typical drivers for mode control. More advanced transceivers such as the TCAN1145 that have a SPI interface for mode control and configuration may need to have drivers to allow the higher level CANopen functions to manage the hardware. 

    Similar to the ability for CANopen to abstract the physical layer transceiver portion of the CAN interface, the ISO 11898-1 protocol layer of CAN that is supported by the CAN controller will be abstracted by the software to higher level functions. Because there is more complexity in connecting the features of a CAN controller to this software, the existing of drivers for the specific device will likely be more important here. Since the CAN controller typical exists inside the MCU, I would recommend looking into processors that are advertised to supply CANopen or similar software stacks to make sure you will get firmware support for this product. 

    Let me know if you have any more questions. 

    Regards, 
    Eric Schott