I have two devices that stream data to my application. A device, which continuously completes 1-packet COM1 with every 50 ms '\ r \ n' in the 9-byte data packet currents. The second device ends a 38 byte packet with '\ r \ n' with Com 3, when the device is triggered.
Each one has a completely different SerialDataReceivedEventHandler and put them in different threads in each of its own dll runs.
The COM1 SerialDataReceivedEventHandler always performs well.
If the COM3 SerialDataReceivedEventHandler does well, then any data that is streaming in COM1 will perform.
However, when COM1 SerialDataReceivedEventHandler is working and COM3 SerialDataReceivedEventHandler work, COM1 SerialDataReceivedEventHandler immediately to activate the fire when the data is available, but take COM3 SerialDataReceivedEventHandler 12 seconds when data is available.
COM1 keep COM3 SerialDataReceivedEventHandler from SerialDataReceivedEventHandler firing? Or maybe there is something happening under the serial data reassured handler hood? any idea?
By default, COM1 and COM3 both to signal when data shows, in assuming the same obstacle The real use of the line is the serial port. Can you configure a port to be COM2 or COM4? COM1 & amp; Com 3 sharing both IRQ4 Com 2 & amp; COM4 Share IRQ3 If you (you can run devmgmt.msc to start it) might be able to see this with the Device Manager.
Comments
Post a Comment