I have been confused by the entries for (example) /bus.0Finally figured out this describes the connection relative, essentially, to the connection made in OW_init
My system may host several One Wire adapters. Presently in testing these are two serial adapters via two USB to serial converters. When attached, the converters show in dmesg as ttyUSB0 and ttyUSB1.
What my application would like to know is, for a specified device (such as a temperature sensor), to which of these ports is it attached?
Each adapter has a single DS2408 switch and provides a powered bus. As each adapter can be physically marked with the serial number of the DS2408, I suppose this could be traced back by the user, but ideally I'd like this information available by my application. If, for example, a sensor should fail, the application can report which physical port and segment is at fault.
Is this data brought out anywhere? /m
------------------------------------------------------------------------------ FREE DOWNLOAD - uberSVN with Social Coding for Subversion. Subversion made easy with a complete admin console. Easy to use, easy to manage, easy to install, easy to extend. Get a Free download of the new open ALM Subversion platform now. http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
