On Thu, Dec 13, 2012 at 10:12 PM, Xiaofan Chen <xiaof...@gmail.com> wrote: > On Thu, Dec 13, 2012 at 6:56 PM, Mohamed HAMZAOUI <requin...@gmail.com> wrote: >> I'm developping a card which support 2CAN HS(baudrate up to 1Mb/s)/2 >> CAN LS and 2 LIN channel. >> The protocol implemented is the standard CAN layer with normal and >> extended ID support. >> >> In critical load on USB with several frame to send and receive, it's >> normal that USB protocol cannot deal with the amount of I/O data... > > Okay. it is good that you understand this situation.
On the other hand, if you have some buffering on your card and can assemble the CAN packets into USB data, then your USB side (even with full speed USB, which should reach speed like 400KB/s without much difficult) may be able to handle the CAN I/O data. >> but the libusb should not stop handling, sending, receiving and block >> on LIBUSB_ERROR_NO_MEM for all submit_transfer call and -5 for >> handling transfer ! >> >> Is this a bug on the libusb/WinUsb or a limitation ? > > I think Tim and Pete have already answer that question. You > can call it a limitation if you feel better that way. However, you > should try to follow Tim's suggestion by submit larger transfers at > longer intervals to see if that helps. > -- Xiaofan ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
