No, I don't think w1 is the optimal way to use the USB adapter. The snipet you show suggests a USB disconnect and then rescan and reconnect. A 1-wire short shouldn't cause this (though I've never done the test) but perhaps shorting out the 5V line might. Or a loose connector.
Can you give more information about your setup? Paul On Mon, Apr 5, 2010 at 11:31 AM, Sven Geggus <li...@fuchsschwanzdomain.de> wrote: > Paul Alfille <paul.alfi...@gmail.com> wrote: > >> Speed improvements for the w1 subsystem > > Hm, is this the recommended way to use a 2490 USB Adapter? > > I recently had some trouble with communication failures and bus > resets using libusb. > > Unfortunately I don't know if these are hardware or software problems: > > DEFAULT: ow_ds9490.c:DS9490_reconnect(594) Found USB DS9490 bus master after > USB rescan as [004/027] > DEFAULT: ow_reconnect.c:TestConnection(58) DS9490 bus master reconnected > DATA: ow_ds9490.c:DS9490_reset(942) start > DATA: ow_ds9490.c:DS9490_reset(995) ok > CALL: handler.c:SingleHandler(264) sem_timedwait timeout time=0.100 > (timeout=100 ms) > CALL: data.c:DataHandler(126) Presence message on /12.9B6E45000000/PIO.A > bus number=0 > CALL: data.c:DataHandler(109) DataHandler: parse path=/12.9B6E45000000/PIO.A > CALL: ow_parsename.c:FS_ParsedName_anywhere(93) > path=[/12.9B6E45000000/PIO.A] > CALL: data.c:DataHandler(137) Write message > CALL: ow_parsename.c:FS_ParsedName_anywhere(93) > path=[/12.9B6E45000000/infobyte] > DATA: ow_ds9490.c:DS9490_reset(942) start > DATA: ow_ds9490.c:DS9490_reset(995) ok > CALL: ow_parsename.c:FS_ParsedName_anywhere(93) > path=[/12.9B6E45000000/infobyte] > DATA: ow_ds9490.c:DS9490_reset(942) start > DATA: ow_ds9490.c:DS9490_getstatus(854) Status byte[0]: 4 > DATA: ow_ds9490.c:DS9490_getstatus(854) Status byte[1]: B0 > DATA: ow_ds9490.c:DS9490_getstatus(854) Status byte[2]: FE > DATA: ow_ds9490.c:DS9490_getstatus(857) short detected > DATA: ow_ds9490.c:DS9490_reset(975) short detected > CONNECT: ow_reset.c:BUS_reset(29) 1-wire bus short circuit. > DATA: ow_ds9490.c:DS9490_reset(942) start > DATA: ow_ds9490.c:DS9490_reset(962) error sending reset ret=-71 > DATA: ow_ds9490.c:DS9490_reset(942) start > DATA: ow_ds9490.c:DS9490_reset(962) error sending reset ret=-71 > CONNECT: ow_ds9490.c:DS9490_close(776) Closed USB DS9490 bus master at > 004/027. ret=0 > CONNECT: ow_ds9490.c:USB_next(626) Bus master found: 004/027 > CONNECT: ow_ds9490.c:DS9490_sub_open(551) Failed to set configuration on USB > DS9490 bus master at 004/027. > CONNECT: ow_ds9490.c:DS9490_redetect_low(696) Cannot open USB bus master, > Find next... > DEFAULT: ow_reconnect.c:TestConnection(52) Failed to reconnect DS9490 bus > master! > CALL: handler.c:SingleHandler(264) sem_timedwait timeout time=0.100 > (timeout=100 ms) > CALL: handler.c:SingleHandler(264) sem_timedwait timeout time=0.100 > (timeout=100 ms) > DATA: ow_ds9490.c:DS9490_reset(942) start > DATA: ow_ds9490.c:DS9490_reset(942) start > CALL: data.c:DataHandler(109) DataHandler: parse path=/12.9B6E45000000/PIO.A > CALL: ow_parsename.c:FS_ParsedName_anywhere(93) > path=[/12.9B6E45000000/PIO.A] > CALL: handler.c:SingleHandler(264) sem_timedwait timeout time=0.100 > (timeout=100 ms) > CALL: handler.c:SingleHandler(264) sem_timedwait timeout time=0.100 > (timeout=100 ms) > CALL: handler.c:SingleHandler(264) sem_timedwait timeout time=0.100 > (timeout=100 ms) > DEFAULT: ow_reconnect.c:TestConnection(52) Failed to reconnect DS9490 bus > master! > CALL: handler.c:SingleHandler(264) sem_timedwait timeout time=0.100 > (timeout=100 ms) > CALL: handler.c:SingleHandler(264) sem_timedwait timeout time=0.100 > (timeout=100 ms) > > Usually this starts to work again after I try to send the command for several > times. > Thus a short circuit on 1-wire bus is nearly impossible. > > Regards > > Sven > > -- > "Those who do not understand Unix are condemned to reinvent it, poorly" > (Henry Spencer) > > /me is gig...@ircnet, http://sven.gegg.us/ on the Web > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Owfs-developers mailing list > Owfs-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/owfs-developers > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
