with ser2net and ds2480 i could reduce this problem, turning ser2net down, wait a moment and restart ser2net
ser2net is a serial-tcp program i'm running it at ARM device (android with linux 2.6.29) and at server (x86-64) i'm running owhttpd with command option: -d 172.16.0.22:5331 with some time (like you told) the ow disapear solution for me (i can't cut the cable since i can't change phisical cable path): restart owhttpd (works) restart ser2net (works, but i wait more than restart owhttpd) running owhttpd at arm device with -d /dev/ttyUSB0 give the same problem i think that's a problem with ser2net and owhttpd when using usb-serial devices at ser2net code is easy to put a 'reconnection like algorithm' (since i can close tcp port and owhttpd disconnect) but at owhttpd i don't know where to change it i don't know if you are using usb-serial-ds2480 bus master but if you are using it, could you try to run it with ser2net?? run ser2net on same computer and use -d 127.0.0.1:ser2net_port to connect with owhttpd program -------------------- > Roberto Spadim wrote: >> >>> :D i found this too with ds2480b! >> OK, I expected this! i'm using a USB-serial-ds2480b solution not serial-ds2480b (maybe a problem at USB devices and linux?) > Roberto Spadim wrote: >> >>> maybe a single workaround (ugly, but works) is a counter at device >>> for example after 10 reads, close and open device (/dev/ttyUSB0 or other >>> device) >> > I'm not an expert with the OWFS, but here my 2ct: > Why do you think anything on the Linux device can help here? > So far I've tested, the Linux device stays stable connected over all the > error stages. If you reduce the capacity / length of the cable far enough, > you can still access the 1-Wire devices forever, so I see no need to > reconnect the Linux device, it works. > > It looks like some counter unintentionally reduces the "power" of the 1-Wire > sender/receiver, so it is not able anymore to communicate with long cables. > Using short ones (below about 60m) works fine without any problems. no no it's not a problem of eletrical power and a software program, i think that's a problem at USB devices stop working without notices (maybe don't sending the BREAK command to ds2480b, or maybe just a linux problem, or maybe a problem without notices, or maybe a time problem with USB converter) the reconnection do restart ds2480 initial state that's the nice part and this works (i think the problem with usb device is the communication) > Hopefully my steps-to-reproduce and the cable-length-simulator help solving > this... yes this works but my problem is: i can't change cable path, and i don't know if add a resitor or add a capacitor could help, i must check in plant with a scope to check diferences, but your experience is very nice to check this problem (maybe it's not only a usb problem, but my cable problem... i checked statistics and it don't show shorts, but i can't see more my device, and restart works nice to get it back) > > Achim > -- > View this message in context: > http://old.nabble.com/Problems-in-owserver-with-USB-and-longer-cables-tp33213551p33214966.html > Sent from the OWFS - Dev mailing list archive at Nabble.com. > > -- Roberto Spadim Spadim Technology / SPAEmpresarial ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
