LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Multi loops write data to one tcpID

If multi loops write data to one tcpID, will it be a problem.

 

In every loop, the tcp package length will add to the header.

 

Any suggestion, thanks.

0 Kudos
Message 1 of 3
(2,020 Views)

Have one loop that takes inputs from all the other loops and communicates with the network. To communicate between the network interface loop and the other loops you can use a user event, queue or notifier - depending on your exact situation.

 

Mike...


Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
Message 2 of 3
(2,011 Views)

I think if you are thinking about doing this you will need a couple of loops. One that processes and sends the TCPIP info and the other that generate the code. You may need one that takes all of the code info and parses it into one command for the TCPIP loop to send. I would also probably make it a qued system or event driven to make sure things happen when you want them to.

Tim
GHSP
Message 3 of 3
(2,009 Views)