LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Losing 75% of UDP data due to design/UI/references/charts (I think)

Solved!
Go to solution

What is your underlying protocol for the data stream? What is driving the state machine of your Get UDP function? that is sitting in a loop and looks like it is a queued message handler. What is putting the Read Data state in? You haven't answered what is creating the stream and at what frequency the data is generated. I would have my base UDP Read read a large chunk of data with a very small timeout. I would ignore the timeout and simply go back to reading. The data read, as a large string buffer, is then passed to a parsing task which will do the actual parsing of the data and then forwards that for further processing or display. Your objective is to keep the underlying UDP buffer (managed by the low level OS libraries) as empty as possible.



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
0 Kudos
Message 11 of 11
(163 Views)