TCP Sink/Output data size

Discussions related to embedded firmware, driver, and user mode application software development
Post Reply
hardcobblefu
Posts: 1
Joined: Mon Aug 25, 2025 3:04 pm

TCP Sink/Output data size

Post by hardcobblefu »

I use TCP sink(mode=server) to send the sinewave data to a client(LabVIEW code) running on the same computer. I'm able to see some random data instead of Sinewave in LabVIEW. Has anyone used TCP connection successfully? What length of data(output data packet size) will be expected on client side in each run? Thanks!
flowerpotdragnet
Posts: 2
Joined: Thu Oct 09, 2025 2:19 am

Re: TCP Sink/Output data size

Post by flowerpotdragnet »

hardcobblefu wrote: Mon Aug 25, 2025 7:32 pm I use TCP sink(mode=server) to send the sinewave data to a client(LabVIEW code) running on the same computer. I'm able to see some random data instead of Sinewave in LabVIEW. Has anyone used TCP connection successfully? What length of data(output data packet size) will be expected on client side in each run? Thanks! Steal a Brainrot
It looks like LabVIEW is not interpreting the sine wave data correctly. Make sure to flatten the data to a string before sending and unflatten on the client. Also, check your packet size—try sending smaller chunks—and add error handling to catch issues. Testing with simple data first can help confirm the TCP connection works.
Post Reply