LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

datasocket VI at client side just stops

Solved!
Go to solution
Hi guys, I am trying to send microphone-captured sound to another PC (both PCs connected by cross-over cable). I tried various options like TCP, Datasocket but none worked. With TCP it always shows input buffer overflow. With Datasocket, it doesn't show any error but the VI on the remote PC just stops. I have not been able to figure out the problem. I am using LabVIEW 2009 version 9. I am attaching the two VIs for your testing. Please help. Thanks. Regards.
Download All
0 Kudos
Message 1 of 3
(2,177 Views)
Solution
Accepted by topic author rocky3015

Hi Rocky,

 

I looked at your code, and made a few changes. First, I couldn't tell why you were dividing the samples/ch by two for the read sound function. I disabled that. Also, the "Initial Data" you were feeding to the first "sound write" VI and at the default data input of the DataSocket Read function was a waveform cluster. The sound data sent over the DataSocket connection is an array of waveform clusters (one cluster per channel). This probably was causing DataSocket problems for ya.

 

I set the sound configuration values to what I found in the "Continuous Sound Input.vi" example VI. I also added a few charts for visual indications.

 

Note that you must have DataSocket Server running (on windows: Start->Programs->National Instruments->DataSocket->DataSocket Server).

 

If these don't work, I'd look at network/firewall issues. Also, if you want less latency, consider using straight-up UDP. It should have less overhead than DataSocket (and with a crossover connection, I'd guess you won't have much data loss to worry about).

Message Edited by RandyP on 03-03-2010 10:29 AM
-Randy
-=--=-=-=-=-=-=-
Nothing like a good dose of LabVIEW to cure what ails ya'.
Download All
0 Kudos
Message 2 of 3
(2,140 Views)
Thanks Randy. It is working now. Thanks.
0 Kudos
Message 3 of 3
(2,122 Views)