On 01/14/2011 05:56 PM, Willy Lambert wrote: >> >> So it seems to communicating :)
Congrats! > During a "stress test" I have 2 controller error messages : > > 39 <http://lxr.linux.no/linux+*/include/linux/can/error.h#L39>#define > CAN_ERR_CRTL_TX_WARNING > <http://lxr.linux.no/linux+*/+code=CAN_ERR_CRTL_TX_WARNING> 0x08 /* > reached warning level for TX errors */ > <http://lxr.linux.no/linux+*/include/linux/can/error.h#L40> > <http://lxr.linux.no/linux+*/+code=CAN_ERR_CRTL_RX_PASSIVE> > 41 <http://lxr.linux.no/linux+*/include/linux/can/error.h#L41>#define > CAN_ERR_CRTL_TX_PASSIVE > <http://lxr.linux.no/linux+*/+code=CAN_ERR_CRTL_TX_PASSIVE> 0x20 /* > reached error passive status TX */ ... > candump view : > > can0 0 [2] 81 00 >> can0 721 [1] 00 >> can0 0 [2] 01 00 >> can0 1A1 [2] 60 00 >> can0 721 [0] remote request >> can0 321 [5] FD FF FF FF FF >> can0 721 [1] 05 >> can0 321 [5] 0F 00 00 00 00 >> can0 721 [0] remote request >> can0 1A1 [2] 27 00 >> can0 721 [1] 85 >> can0 321 [5] 93 FF 04 00 00 >> can0 321 [5] 93 00 00 00 00 >> can0 321 [5] 93 00 01 00 00 >> can0 321 [5] 93 00 02 00 00 >> can0 321 [5] 93 00 03 00 00 >> can0 321 [5] 93 00 04 00 00 >> can0 321 [5] 93 00 05 00 00 >> can0 321 [5] 93 00 06 00 00 >> can0 321 [5] 93 00 07 00 00 >> can0 321 [5] 93 00 08 00 00 >> can0 321 [5] 93 00 09 00 00 >> can0 321 [5] 93 00 10 00 00 >> can0 321 [5] 93 00 11 00 00 >> can0 321 [5] 93 00 12 00 00 >> can0 321 [5] 93 00 13 00 00 >> can0 321 [5] 93 00 14 00 00 >> can0 321 [5] 93 00 15 00 00 >> can0 321 [5] 93 00 16 00 00 >> can0 321 [5] 93 00 17 00 00 >> can0 321 [5] 93 00 18 00 00 >> can0 321 [5] 93 00 19 00 00 >> can0 321 [5] 93 00 20 00 00 >> can0 321 [5] 93 00 19 00 00 >> can0 321 [5] 93 00 18 00 00 >> can0 321 [5] 93 00 17 00 00 >> can0 321 [5] 93 00 16 00 00 >> can0 321 [5] 93 00 15 00 00 >> can0 321 [5] 93 00 14 00 00 >> can0 321 [5] 93 00 13 00 00 >> can0 321 [5] 93 00 12 00 00 >> can0 321 [5] 93 00 11 00 00 >> can0 321 [5] 93 00 10 00 00 >> can0 321 [5] 93 00 09 00 00 >> can0 321 [5] 93 00 08 00 00 >> can0 20000004 [8] 00 08 00 00 00 00 67 0C ERRORFRAME >> can0 20000004 [8] 00 20 00 00 00 00 87 0C ERRORFRAME >> can0 721 [1] 00 >> can0 321 [5] 93 00 07 00 00 >> can0 321 [5] 93 00 06 00 00 >> can0 321 [5] 93 00 05 00 00 >> can0 321 [5] 93 00 04 00 00 >> can0 321 [5] 93 00 03 00 00 >> can0 321 [5] 93 00 02 00 00 >> can0 321 [5] 93 00 01 00 00 >> can0 321 [5] 93 00 00 00 00 >> > > > > May this be due to wiring quality ? Yes, or some mismatching bittiming. The bus errors are reported by the SAJ1000 chip and you can get more details information, if you use the "ip" argument "berr-reporting on". Also "ip -d -s link show can0" reports the number of bus-errors. Wolfgang. _______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
