On 21.01.2011 16:02, uprinz wrote: > > 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. >
Hi Ulrich, additional to have separate filter capabilities for each open socket the idea is that you can have multiple (multi-user) CAN applications on your Linux box. To ensure all the CAN applications have independently the correct view on the real CAN bus the locally generated massages are looped back into the local host once they are sent on the wire, see: http://lxr.linux.no/#linux+v2.6.37/Documentation/networking/can.txt#L176 So with SocketCAN having two or more applications independently using the same CAN bus is the standard behaviour. Have fun! Oliver _______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
