From: Mayur P. <may...@gm...> - 2018-03-28 11:38:44
|
Thank you for your reply and Extremely sorry for replying late. Yes, We use libusb-Win32 driver. When we debugged the application, noticed that these errors are getting thrown from driver layer. Even we tried to change the driver to libusbK however it was always giving me the invalid parameter error. On Thu, Mar 22, 2018 at 7:49 PM, Xiaofan Chen <xia...@gm...> wrote: > On Thu, Mar 22, 2018 at 10:14 PM, Xiaofan Chen <xia...@gm...> wrote: > > On Mon, Mar 19, 2018 at 11:17 AM, Mayur Purandare > >> We observed that after some time. (One hour approximately), the > >> communication gets disconnected with following error. > >> > >> Win32Error: DeviceIOControl Code 00222058 failed. The device cannot > >> recognize the command. > >> LibUsbIO 22: The device cannot recognize the command. -16367. > >> > > This is strange. The IOCTL code for libusb0.sys is defined here. > https://github.com/mcuee/libusb-win32/blob/master/ > libusb/src/driver/driver_api.h > > Are you using the libusb-win32 device driver? > > -- > Xiaofan > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Libusb-win32-devel mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel > |