2011/5/13 Wolfgang Grandegger <[email protected]>

> Hi Willy,
>
> On 05/13/2011 10:42 AM, Willy Lambert wrote:
> > 2011/5/3 Willy Lambert <[email protected]>
> >
> >> Hi all,
> >>
> >> I have a "visibly working" can network but some arbitration errors often
> >> occur. I am using socket_can under canfestival and have configure a set
> of 3
> >> node (0x05,0x32,0x33) with periodic PDO (TX and RX) plus a nodeguarding
> on
> >> each node. The bus is at 250K and the period of the SYNC word is 10ms.
> Here
> >> is the candump extract of a period (there are always in the same order)
> :
> >>
> >>  can1   80  [0]
> >>   can1  332  [5] 93 00 00 00 00
> >>   can1  1B2  [2] 27 00
> >>   can1  20000002  [8] 01 00 00 00 00 00 00 00   ERRORFRAME
> >>   can1  1B3  [2] 27 00
> >>   can1  20000002  [8] 02 00 00 00 00 00 00 00   ERRORFRAME
> >>   can1  2B2  [6] 93 00 00 00 00 01
> >>   can1  20000002  [8] 02 00 00 00 00 00 00 00   ERRORFRAME
> >>   can1  2B3  [6] 93 00 00 00 00 01
> >>   can1  333  [5] 93 00 00 00 00
> >>   can1  3B2  [7] 00 00 00 00 04 00 0A
> >>   can1  3B3  [7] FE FF FF FF 02 00 0A
> >>   can1  705  [0] remote request
> >>   can1  732  [0] remote request
> >>   can1  733  [0] remote request
> >>   can1  705  [1] 05
> >>   can1  732  [1] 05
> >>   can1  733  [1] 05
> >>
> >>
> >> Here is some additionnal stats :
> >> root@beta:~# ip -d -s link show can1
> >> 4: can1: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UNKNOWN
> >> qlen 10
> >>     link/can
> >>     can state ERROR-ACTIVE (berr-counter tx 0 rx 0) restart-ms 1000
> >>     bitrate 250000 sample-point 0.875
> >>     tq 250 prop-seg 6 phase-seg1 7 phase-seg2 2 sjw 1
> >>     sja1000: tseg1 1..16 tseg2 1..8 sjw 1..4 brp 1..64 brp-inc 1
> >>     clock 8000000
> >>     re-started bus-errors arbit-lost error-warn error-pass bus-off
> >>     0          0          9684       0          0          0
> >>     RX: bytes  packets  errors  dropped overrun mcast
> >>     225353     84576    0       0       0       0
> >>     TX: bytes  packets  errors  dropped carrier collsns
> >>     32163      66462    9684    0       0       0
> >> root@beta:~#
> >>
> >>
> >> Should I ignore these errors ? Should I review my scheduling ?
> >>
> >
> > My I bump this ? If the question is mal-formed or innapropriate on this
> > mailing liste please tell me so I don't wait for an answer :p
>
> The error is definitely reported by the CAN controller and therefore
> it's due to an electrical problem on the CAN bus. Well, I'm not a CAN
> *hardware* expert and therefore I can't tell if such error do harm or
> can even be ignored. Googling for "can arbiration lost" revealed:
>
>
> http://www.cancapture.com/knowledgebase/18-cancaptureknowledgebase/33-kb-arbitration-lost-error-messages.html
>
> which seem to answer you question to some extend.
>

Thanks, your are really better than me in googleling

Is there a mean to disable this error un socketCan ?



>
> Wolfgang.
>
_______________________________________________
Socketcan-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/socketcan-users

Reply via email to