Hi Wolfgang!
Wolfgang Grandegger wrote: > > On 01/21/2011 02:59 PM, uprinz wrote: >> > Not sure what you want to do. Any process can receive CAN messages from > any CAN bus. By defining a filter, you can restrict the messages > received on a certain socket. > That sounds good. My Master needs to do lots of automated reconfiguration and detection on our slaves. But the master hardware has some sensors too. To not mix the parts up the idea was to write independent software for both, the master and the sensors. Wolfgang Grandegger wrote: > >> Is there special care to be taken about the configuration of PCAN? >> Sometimes it looks like it works, sometimes not. If not I see a lot of >> "write error; : No buffer space available" > > In case of that error you should retry after a small delay or increase > the TX buffer size. Search for ENOBUFS in the utitlity cangen.c for > further information. You can increase the TX Buffer size with the ip > option txqueuelen. > I'll check that. Many thanks. But it looks like these 'locally' transmitted packages are stuffing the tx queue. So they will never be sent out but block the rest of the world. Ulrich. ----- Best regards Ulrich -- View this message in context: http://old.nabble.com/On-Linux-two-applications-use-the-same-bus--tp30728796p30729332.html Sent from the Socket-CAN Users mailing list archive at Nabble.com. _______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
