• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 33 subscribers
  • Views 829 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.

SN65HVD230: CAN communication break down

Kum Hoo Lee
Expert 1855 points
Part Number: SN65HVD230


Dear Sir/ Madam,

i am using this device in IoT agriculture. In our network, it has controller and some slaves and we use CAN to connect them. Our controller uses ARM M4 (TM4C123), slave using ST STMF103 and CAN Transceiver is SN65HVD230D.

Controller runs free RTOS and slave is non RTOS.

The problem that sometime we fail to send messege from controller to slave or back. Normally first group of data sent out successfully but will fail at the second group of data. We suspect that the problem caused by noise when engine start. Although after we fix this noise issue, the problem still appear. It seems not caused by the noise itself.

Suspect that the issue maybe caused by we just send messege one way but no handshake. It has some task use CAN module in one time or CAN interrupt is conflict with RTOS. Can you give us some advice about this problem and what should i check or take care on the CAN transceiver design in terms of SW and HW? How to do a handshake? Hope to hear from you soon.

Thanks and best regards.

KH

  • 0
    TI__Guru 62920 points
    Hello,

    Handshaking in CAN is just done through the ACK bit, which occurs at the end of the frame and allows each node to signal back to the transmitting node that the CAN frame was properly received. You should be able to observe this bit if you monitor the CANH and CANL lines on an oscilloscope. That would we good to do to help debug this issue, anyway, since it may help indicate any hardware issues that are present.

    In addition, if you could check the transmit and receive error count registers in each CAN node it could give you a better idea which node is generating errors in the communication.

    Regards,
    Max