On 14.11.2010 16:26, Willy Lambert wrote: > Hi all, > > *The short story is :* > > I manage to use vcan0 but the same tests fails on my real can interface. I > am not sure about my HW livelyness but I really don't know where to look at > to see if everything is working. >
> > and uses the same commands after having changed "vcan0" into "can0" in my > can.log file. You can assign CAN network devices to replay on different CAN interfaces. In your case: canplayer -l i -I can.log can0=vcan0 ... would do it (without changing the original logfile) So make fist sending tests better try 'cansend' or 'cangen' ... --- Generally you can't set a bitrate on vcans (as they do not have a CAN controller HW ;-) vcans are only software devices like the loopback device for IP traffic. > As a result I have a full buffer error message (killing cansend) : > >> r...@alpha:/opt/ard# ../canplayer -l i -I can.log >> sendto: No buffer space available >> > > Here, I am totally lost, I don't know what to look at, I don't event know if > my can hw is running. Could someone ligth up my path ? > I tried different configuration like : > _ no cabling > _ cabling can0 into can1 > _ cabling on open can0 > I am not sure about my 120 Ohm resistors, I will check this on Monday, but > as I am just trying to send is the real bus needed ? You always need a properly terminated CAN bus AND a second CAN node (operationg at the same bitrate!) that acknowledges the CAN frames sent by your machine. >> r...@alpha:/opt/ard# cat /proc/net/can/stats >> >> 11 transmitted frames (TXF) This is only network layer statistics, that handled the CAN frame on send. >> r...@alpha:/opt/ard# ifconfig >> can0 Link encap:UNSPEC HWaddr >> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 >> UP RUNNING NOARP MTU:16 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Obviously nothing was sent. Check termination/second CAN node. Regards, Oliver _______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
