![]() ![]() ![]() I assume using this PCIe AddOn Card is the shortest (direct) way, of connecting USB3 Ports to the Chipset/CPU.Īt Maximum i have connected to each of this 4x USB3 Ports a Hub with extends to 16x USB3 Ports (ExSys EX-1116HMVS).Įach of this 16 Ports is connected to one STM Device which can send up to 300 Packets per second (see my second post). So, I decided to use this AddOn Card in hope to have more reserve in Bandwith. Inspecting with USBView shows additional internal USB (Root?) Hubs which shares bandwith with possible other connected devices to other OnBoard USB Ports. In the past (other project) I ran into problems, when connecting 4x FTDI FT4232HL to a single OnBoard-USB2-Port (randomly dis-/reappearing COM Ports in device manager). Unfortunately i could not find a newer driver than 3.0.23 (08 / 2012). Yes, there is an ExSys (EX-11494-2) PCIe to 4x USB3 Adapter card in the PC. Knut function TCommO.CommReadA(var aBuf aBufLen: Cardinal aTimeOutMS: DWORD): Cardinal īytesInBuf := CommBytesInRxQueue() // Windows BufferĪBufLen := 1 // if buffer empty, wait for the first char (continue reader thread does not make sense), but receive complete in next call 150 Bytes.Ĭurrent bluescreens happens with only few packets per second.Īs far i know, only the *.inf file is STM specific. It maybe some packes per second but also some hundred packets per second. The program is a recording app, which receives and stores data, which comes from several sensors (STM32 board, O2 / CO2 sensors). Just a (overnight) running process and sometimes in the morning bluescreen is presented.īut I also had the bluescreen, when running my program in debugger and just waiting for specific sensor data. The bluescreen comes without any user action. The data istself is a properity protocol. When enough bytes are received, the data protocol (CRC or else) will be checked and payload extracted. Reading data is done by asynchronous file i/o (using overlapped struct) to let the thread sleep (WaitForSingleObject), when no data is received from device. It is a thread, which waits for data from USB-VCP and, depending from the protocol, it tries to read more or less (aBufLen) data bytes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |