Error -1950678945 (I/O variables)

[henriquegpo]

Hello there!

I´m trying to use the Shared Variable Functions to acess the data read by a cRIO 9148. Unfortunately, when I use those functions the same error keeps showing up.

Here´s a part of my VI:

And everytime I run the application, this error pops up:

Error -1950678945 occurred at Open Variable Connection in tilt sensor.vi

Possible reason(s):

LabVIEW: The URL specifies a host name that does not correspond to the local host, but LabVIEW only supports the specified operation on the local host. You cannot perform the specified operation on a remotely hosted variable or stream endpoint.

Does anyone know why this is happening?

I´ve read that I should change my ethernet adapter setting to "Home" or "Work" instead of private. But since I´m doing this project in my corporation network, I´m not able to change such configurations.

Please, it´s kind of urgent!

Thanks in advance,

Henrique

[Cory_K]

This is the only article I could find about that error code.

Problem:
I am using network streams in my application, what are the recommended firewall settings?

Solution:
Windows can lock down security that blocks access of protocols that LabVIEW uses. In order to use network streams properly, there are certain processes that need exceptions in your firewall settings:

• lkads.exe - NI PSP Service Locator
• LabVIEW.exe - When running a VI that uses network streams in the LabVIEW development environment
• <standalone application>.exe - When running a standalone executable that uses network streams.

Alternatively, you can open up the range of ports that LogosXT uses for communication. See KB 3T9B75XL: Using Lookout, LabVIEW DSC and Network-Published Shared Variables with Firewalls for more information on this.

Note for Windows 7 users: Make sure that each Ethernet adapter you use is set to a "Home" or "Work" setting. If your network is set to Private, it will throw this error:

Error -1950678945 occurred at Create Network Stream Writer Endpoint in Host Side.vi

Possible reason(s):

LabVIEW:  The URL specifies a host name that does not correspond to the local host, but LabVIEW only supports the specified operation on the local host.  You cannot perform the specified operation on a remotely hosted variable or stream endpoint.

[henriquegpo]

Hey Cory,

I´d already seen this article, and it did not solve my problem. As I said, I´m not able to change the network configurations, nor the firewall permissions. I think that the firewall isn´t the problem, but maybe the network actually is.

What is strange is that when I drag and drop the variable into the block diagram, it reads without any problem, but when I try to use those shared variable functions (which I´m doing only to acess the variables as controls from the front panel), it doesn´t work.

I really don´t know what is going on... But thanks for the article, Cory.

If someone else could help, it would be great!

Thanks,

Henrique

[tmatos]

Hello Henique, even in this situation it is possible that your firewall and connections settings are blocking the communication, and you should make sure that the settings are set like in the article.

If you have any doubts, just ask.

[Jed394]

1) Make sure your I/O variable are Network published using the multiple variable edit tool. 

2) I believe if this is running on a host and not on the CRIO then you need to programatically access networked shared variables using a PSP variable not an I/O variable.  Trying changing your URL to ni.var.psp//xxx.xxx.xx/mod3/ai0

Edit: 

This page might be some help too 

https://www.ni.com/docs/en-US/bundle/labview/page/reading-and-writing-shared-variables-programmatica...

[henriquegpo]

Thiago and Jed,

I´ve tried using a personal computer instead of a corporation one, and it seems that tha same error keeps going on.

Fortunately, I´ve managed to implement a code in which I don´t use those Shared Variable functions anymore, so the error no longer occurs.

Jed, I think that in this case I had to use I/O variables instead of PSP because I´m using a cRIO target based on the Scan Engine feature.

Thanks for the advices,

Henrique