Can't create Network Stream connections between Win and RT

[KHartley]

David,

I will be working to try an replicate the issue you and Bob have been able to post. I've been monitoring the thread all morning, sorry I didn't post sooner. I'll try to work on an explanation later today.

I see Bob was able to use LabVIEW 2010 to replicate the issue, David which version are you using? Have you tried with multiple targets? I remember I saw a cRIO model posted ealier I'll double it to see if it was yours.

[David_Staab]

Hi Kyle -

I'm working in LV 2011. Yes, I've tried on multiple cRIO models.

[KHartley]

David,

I tried out your code on one of our cRIO 9075 and I was unable to reproduce the situation that you and Bob are seeing.

I ran your code from the first post and it performed without any errors. I was able to successfully run the code atleast 5 times, just to make sure. I'm only seeing those errors when I let the network streams timeout.

Below is the settings I was using and I didn't change the code at all on the back end. I even ran my own example passing data back and forth between the rt target and the host and it worked fine.

Check to make sure you have the most up to date real-time module and NI-RIO driver. Try reformatting your controller to see if there is a newer version of the network stream engine available.

[kent.wedeking]

David,

Just ran into the same thing.  I'm trying to gin together network streams for an easy communiction protocol for passing objects between a host PC and a cRIO.  Worked great on Windows to Windows communication.  Soon as I put it to Win/RT communications its started failing.  I moved all the "active" endpoints to the Windows machine and it worked immediately.  Odd .... either way, my band-aid is till holding ...

[David_Staab]

I did the same thing, Kent. No real solution to this problem, just the workaround of always putting your passive endpoint on the RT system.

[EricLM]

David, I just ran into the same thing, but with a laptop and a PXI windows machine. I turned off firewalls on both computers and still could only put passive endpoints on the PXI.

After digging into firewall settings some more, I realized that even with the firewall turned off, I still had to add an exception for lkads.exe per http://digital.ni.com/public.nsf/allkb/BB3A4E062CE21A098625775F00710497.

Turns out that my work network firewall was being forced on regardless of what I tried to do. The PXI was not on our domain, so was not governed by those rules.

Once I added the exception for lkads.exe on my laptop, I was able to run active or passive endpoints on both machines. Don't know if it will fix your case, but would be worth a try.