Dnia sobota, 1 września 2012 o 22:51:42 Alan Stern napisał(a): > On Sat, 1 Sep 2012, Marek Floriańczyk wrote: > > > It's possible that data is getting lost, but it's pretty unlikely. The > > > only way to get more detailed debugging information is to use a USB bus > > > analyzer. > > > > HI, > > > > You mean hardware device that is connected into the usb bus something > > like this: http://www.fte.com/products/FTS4USB.aspx > > Yes, that or something like it. For example: > http://www.totalphase.com/products/beagle_usb480 > > > Or do you mean some software that I can use on linux, if so could you > > please recommend any, all I can find is for windows :( > > No, not software. No Linux software will be able to display any more > information than usbmon. > > > > You could do more testing. For example, run the same program but > > > comment out the parts that talk to the device on bus 3. Or plug the > > > devices into each other's ports, or swap the serial numbers in the > > > program. > > > > I can send commands separately to each device, and then there is no > > problem. Changing serial numbers won't work, application has class > > usb-manager that during start creates objects MyUsb and each object is > > given device id vendor id and serial number, to connect to CKOZ gateway. > > You could change the order of which device you send the command to > first. HI, Debian testing, kernel 3.2.0-3 and results are the same. Order in which I call devices is important, first device I call always gives reply, second one almost never, no matter on what bus number they are. When I insert some delay between commands (500 ms) everything works fine - i got reply from both devices, always. Unfortunately I don't have usb tester, but maybe I will try to do test app on windows, so I will get some confirmation. regards Marek > > Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
