Hi paul, dear list ;) as i am currently in duty of defining a general purpose sensor library and i want to incorportate owfs - i have a question for specifying the usb adaptor to use ...
but, let me first explain some internals ... my sensorlib utilizes dbus/hal to query for interfaces connected via serial or usb and installs drivers to communicate with the sensors on demand - and of course on startup ;) however in my design i have: "Interface"s - which map to one or more "physical interfaces" (i.e. device-files or the like) and "Sensors" which belong to some "Interface" however - currently i have no problem, as i have either one of the following scenarios: 1 interface - 1 sensor 1 interface - n sensors so in the case of unplugging one interface at runtime i can easily mark the sensors belonging to this interface as "missing" ... but in the case of owfs - with multiple usb adapters - i would have: n interfaces - n sensors and i can not distinguish which sensors are connected to which adapter. ... or am i wrong with this - havent tried it tough ... ;) before you start asking why we want to do it this way, as 1wire definitely is a bus ... well, this is desired, as we want to connect one sensor via one interface with one usb port to the pc - so that there is no "single point of failure" - e.g. when the 1wire bus master dies - all sensors connected to it are also gone ... anyway ... now to the question & idea belonging to owfs: currently it is not possible to force the use of a proper usb adaptor to talk to - only "-u" (the first), "-u2" (the "second") and "-uall" (all found adaptors) are possible ... and in fact i am wondering if i can also specify this in owcapi ... havent tried this either ;) so, the question is, will it be possible (technically) to modify owfs to specify the usb device to use in some manner - i am thinking of an additional parameter to specify all needed values for libusb initialisation ... ... *AND* it must be possible to specify this not only on the commandline but also via owcapi ... as pyowfs uses this ;) so, paul et. al ... does this sound feasible ?!?! or are there any other ways i havent seen until now ... ?!?! paul, if you find this a good idea - and propably could give me some hints on how to start, i am definitely willing to get my hands dirty on this ... ;) - and it would definitely improve my sensorlib's design :) many thanks, marcus. ------------------------------------------------------------------------------ _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
