LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

velocity dequeue elements and insert to DS

Hi, my vi's giving me a trouble.
 
I'm working with Queues and DataSocket (DS). In a first 'vi' I do a calculation. In this 'vi' use queues because I have several 'while loops'. As I use several vi, I need DS to comunicate with them.
 
I need to work in miliseconds for a correct function.
 
I've tested mi 'vi' and don't works good. It seems I loose elements!! At first I thought the queues didn't work and therefore I created a simply example of my 'vi' to see the problem. Then I've realized that if I don't use DS the queues works excellent, but if I use DS don't work!!!!
 
Question: why the velocity of DS is lower than queues? I can resolve this problem?
 
I enclose the 2 examples, one with DS and the other without.
 
Thank you.
Download All
0 Kudos
Message 1 of 6
(3,302 Views)
I'm not sure why the Datasocket version is running slower for you. Both versions can easily run at 1ms on both transmit and receive for me.
 
It may be a network configuration problem on your machine causing the datasocket function to slow down. If you can, try running your VIs on another machine and see what happens.
 
Let us know what you come with.
 
Ed


Ed Dickens - Certified LabVIEW Architect
Lockheed Martin Space
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.
Message 2 of 6
(3,287 Views)

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. 

Regards,

Jaime Cabrera

NI Applications Engineering Spain
Message 3 of 6
(3,275 Views)

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

0 Kudos
Message 4 of 6
(3,260 Views)

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 ...

 

Regards,

Jaime Cabrera

NI Applications Engineering Spain
0 Kudos
Message 5 of 6
(3,247 Views)

Thanks you.

 

Vicens

0 Kudos
Message 6 of 6
(3,239 Views)