Author Topic: Identify one mico is off bus during two micro communication via CAN  (Read 2699 times)

lijun0

  • Guest
Gentleman,
I have a questyion. When one micro. is receiving message using the CAN_Rx mudular in the basic FB librey how can I identify that the sending micro. is off bus. Since I tested to see the received data remains unchanged even the sender stopps or off bus. This is a safety concern. I had tried to use the Rx (updated) but found this dioesn't tell anything (alwase in off status). Any other means to identify this status?



lijun0

  • Guest
Re: Identify one mico is off bus during two micro communication via CAN
« Reply #1 on: August 02, 2015, 11:58:11 AM »
Sorry, after further test I found it can use the updated(Rx) to identify the status.

Thanks!

George

  • Guest
Re: Identify one mico is off bus during two micro communication via CAN
« Reply #2 on: August 02, 2015, 08:05:35 PM »
If your data is really sensitive, I would prefer to add a simple counter in data. That way you can easily detect a timeout or missing data packages.

Offline FStelzer

  • PLUS+1 Expert
  • ****
  • Posts: 50
  • Karma: +8/-0
Re: Identify one mico is off bus during two micro communication via CAN
« Reply #3 on: August 03, 2015, 06:24:52 PM »
Hey,
I always use the Rx output of the block and connect this to an off delay.
Then you can define the "error detecting time.
Connect all delay outputs with an OR . Goes the output of the OR Block TRUE, you know that there is an CAN Error.

Best regards
FStelzer
« Last Edit: August 04, 2015, 10:26:20 AM by FStelzer »

Offline bryantmorris

  • PLUS+1 Expert
  • ****
  • Posts: 51
  • Karma: +0/-1
Re: Identify one mico is off bus during two micro communication via CAN
« Reply #4 on: September 08, 2015, 06:44:06 AM »
Hey,
I always use the Rx output of the block and connect this to an off delay.
Then you can define the "error detecting time.
Connect all delay outputs with an OR . Goes the output of the OR Block TRUE, you know that there is an CAN Error.

Best regards
FStelzer

This is a great idea, thank you for the input