Network Streaming data acquisition (PC-cRIO)

[glovato]

Hello,

I have written some code using Labview's network streaming option to transfer data from the cRIO to my computer and then save this data in a .csv file. I wanted to test it but I'm confused on how to run or deploy it.

Right now I have the code divided into two VIs, one for each endpoint. I'm assuming the writer endpoint corresponds to the cRIO and the reader to my PC. 

So my questions are:

- Where exactly in the project explorer am I supposed to add these files? (please check the attachment and tell me if it is correct).

- What do I need to deploy into the cRIO? and How do I run the whole application?

- Can I build a UI for both VIs (writer and reader)? or because the writer is running in the cRIO I could only see the front panel of the reader?

Thank you very much!

[crossrulz]

It looks like you have the files in the right place.  Just try to run each VI in their proper context.  If you are connected to your cRIO, it will deploy and run for you.

[glovato]

Do you mean open up the VI with the active endpoint, I mean the one that stablishes the connection and click run? it doesn't work. The connection is never stablished, I get no error and it seems like it can run forever.

I have attached screenshots of both VIs if it helps...

Thanks

[Bob_Schor]

Network Streams have a "listener" and a "connector".  The Listener should be started first -- it "listens" for anyone trying to connect to it.  The Connector then should be started -- it's the one that need to have an IP (that of the Listener) as part of its argument.  Note that either can be a Reader or Writer.  I typically put the Listener on the RT side, as that is usually "always running", hence "running first".

Once the Connector can find the Listener, the connection will be established.

Bob Schor

[glovato]

Hi Bob,

Thanks for your reply. The only listener I can find in labview is "TCP listener" and I'm using the network streaming Labview feature not the Internet protocol. I don't know if maybe you were refering to another listener.