<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jun 8, 2012, at 6:45:13 PM PDT Max B <span class="Apple-style-span" style="font-family: Helvetica; "> <<a href="mailto:skinkworks42@gmail.com">skinkworks42@gmail.com</a>> wrote:</span></div><blockquote type="cite"><br>As a disclaimer, I'm not a serious software/electronics engineer, but wouldn't it be conceivable to have a ROS USB device that shows up as an ethernet NIC that automagically connects to the ROS master? I don't know how different OSes handle USB NICs, but it might work with little or no configuration (you could tell it the URI of the master, if it isn't localhost:11311).</blockquote>Yea I thought of this too, and think it would work. At the very least the device then could be seen as another master with connected devices. But then you would have the whole ethernet <-> USB profile and the 802.11 stack which seems like a lot of weight.</div><div><br></div><div>Though supporting stock USB profiles might be useful, e.g. the USB storage profile could be supported to allow auto-mounting a config/settup/status/UI etc web page to be accessed just by clicking on (just making up a path) /volumes/usb/devcieXYZ/status.html . One could stash other useful files there as well, and use such things to trigger UDEV (e.g. it would be easy to have udev launch /volumes/usb/deviceXYZ/.ros_initial_launch sort of thing, at last if I recall my udev correctly). Security is an issue here too.</div><div><br></div><div> -jrg </div><br></body></html>