11-28-2006 07:22 AM
11-28-2006 12:05 PM

Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.11-29-2006 02:59 AM
Hi,
As Ed had said Datasocket also goes fine till those velocities... The question is what is your application going to work with????
If you ar working in the same vi and PC you should use queues coz are faster because they work with the memory of the PC.
If you want to exchange data within a network then u should use Datasocket (or shared variables or TCP/IP or UDP depending of your choice and version of Labview) because that is thought for sharing data around the network...
So of course datasocket is going to be slower coz it is implemented based on TCP/IP protocols for networks, while the queues are done to work inside the same PC with the memory...
Hope that helps u to understand the differences and different behaviours.
11-29-2006 11:06 AM
Thank you Ed & Jaime.
I'm going to use 4 queues and 1 DS (writer+read) per vi. I have 50 vi arranged in 2-3 computers.
Still I'm working with one computer (50 vi in one computer). When it works good I will adjust to others computers and I will distribute the 50 vi.
Exactly, I had a problem with the computer. Now works best, but I don't know if the results are goods: I've calculate (working all vi in one computer) that the transfer between vi with DS are 200-250 elements/second. This number is good?
Vicens
LV7.1 / WinXP
11-30-2006 02:21 AM
Hi,
I think that won't be a problem at all... if you ar connecting them through an ethernet (that should be 10/100 Mbps that is far more than your needings...)
The only small delay you can observe is the same one as you do if u use a TCP conection ...
11-30-2006 04:36 AM
Thanks you.
Vicens