Clear errorframe

Clear errorframe

[Laurenz]

Hi,

when I "cansend can0 000#" and no device is attached to my bus, "candump 
-e any,#FFFFFFFF" will print a no-acknowledgement-on-tx errorframe forever.

Is there a way to clear the error?

Cheers
Laurenz

Re: Clear errorframe

[Wolfgang Grandegger]

Hello,

Am 19.07.2016 um 16:12 schrieb Laurenz:
> Hi,
>
> when I "cansend can0 000#" and no device is attached to my bus, "candump
> -e any,#FFFFFFFF" will print a no-acknowledgement-on-tx errorframe forever.
>
> Is there a way to clear the error?

That is *normal* behaviour. It's the hardware retrying to send out the 
message. Is it necessary to send such an error message for each retry? 
Well, that's discussable. What CAN controller are you using?

Wolfgang.

Re: Clear errorframe

[Laurenz]

Hi Wolfgang,

> What CAN controller are you using?
This was an Ixxat USB-to-CAN V2.

I tested with an PCAN-USB and it sends one 
controller-problem{rx-error-warning,tx-error-warning} followed by one 
controller-problem{rx-error-passive,tx-error-passive} in the same test.

So I can just ignore the repeated error? I will write to Ixxat support, 
maybe they can change it.

Thanks
Laurenz

Re: Clear errorframe

[Wolfgang Grandegger]

Hello Laurenz,

Am 20.07.2016 um 10:49 schrieb Laurenz:
> Hi Wolfgang,
>
>> What CAN controller are you using?
> This was an Ixxat USB-to-CAN V2.
>
> I tested with an PCAN-USB and it sends one
> controller-problem{rx-error-warning,tx-error-warning} followed by one
> controller-problem{rx-error-passive,tx-error-passive} in the same test.

The exact message depends on the CAN controller.

> So I can just ignore the repeated error? I will write to Ixxat support,
> maybe they can change it.

Yes, you could change your error message mask in case you are not 
interested in such messages.

In general, it might be a better policy to treat such errors like bus 
errors allowing to enabled them on demand.

Wolfgang.