Network Shared Variable: Aliasing not working

Hello!
I am running a cRIO 9075, which is publishing network shared variables.
I can see and modify them within Distributed System Manager.
Unfortunately I am not able to read/write the variables through labview.
What I have done so far:
Tools -> Shared Variable -> Register Computer, using the IP of the cRIO
Adding a Variable to the project. Type = Network-Published, Enable Aliasing, choosing "Browse" to select the variable (all published variables from cRIO are shown there), Access Type = read/write. The PSP-URL is: \\192.168.10.70\WaveformManager\Op
Trying to read the variable results code -1950679034 and the result is always the default value for that data type.
BUT this works: using the VIs Data Communication / Shared Variable / Read/Write Variable and typing in the same URL the Distributed System Manager is showing is showing (in my case: \\192.168.10.70\WaveformManager\Op)
So, what am I doing wrong? Did I forget something or misunderstand how "Aliasing" works?
Thanks!

hi,
in which way to you read your shared variable? If you read it before you write a value "into" the variable it may couse this waring.
Have you tried this?
http://digital.ni.com/public.nsf/allkb/7DBC2C3E95AFD85C86257442005CF74C?OpenDocument

Similar Messages

Shared variable does not work in executable

In editor mode, the shared variables update fine. When I build the executable, the shared variables no longer work.
See attachment.
Attachments:
TestCitadel.vi ‏30 KB

I found this note in the LV2010 help, I wonder if this could be related to your problem...
Note You can use scaling only for network-published
shared variables, I/O variables, or I/O aliases. When the shared
variable you want to scale is a network-published shared variable, it
must have a data source. Configure a network-published shared variable
to have a data source by placing a checkmark in the Enable Aliasing checkbox on the Variable page of the Shared Variable Properties dialog box.

Shared variable does not work between two computers

I am using LabVIEW 8 on Windows XP computers.
1. On one computer I have created two projects, writeProject and readProject.
2. In the writeProject I have a shared variable, writeData, which is "network-published" double. In this project I have a writeData.vi which in while loop assigns a random value to the writeData variable.
3. In the readProject I have a shared variable, readData, which is "network-published" double and is bound to the writeData variable. This is on the same computer as the writeProject.
4. I run both the writeData.vi and the readData.vi and all works fine.
5. Now, I create a readProject on a diferent computer. Perform all the steps as described above and also in tools/shared variable/register computer, I have entered the IP address of the target computer on which the writeData shared variable exists.
6. Binding the readData variable fails in the following way. When I browse for the source, in the "Select Source Item" dialog, I see <IP> <Populating Node...>, where <IP> is the IP address of the source computer (on which exists the writeData shared variable). A very long time later it is still "Populating Node...". Neddless to say, this readData.vi does not work!
What am I doing wrong? Or, perhapse what else do I need to do to make it work?

Hi,
I would suggest checking out the two KnowledgeBases I have linked below for common issues with Network Shared Variables. Let me know the results. Thanks!
Troubleshooting Network-Published Shared Variables
Why Are My Network Shared Variables Taking Very Long to Initialize?
Stephanie

Shared variable clusters not working as intended

Hi All,
I've been using shared variables to communicate between a host computer and a crio real time target. This works well as simple variables. I configured a cluster of shared variables to try and clean up the code a bit.
I have a couple of problems. If I write to a single element, using bundle, the other elements in the cluster that I do not want to write to are overwritten with some unknown default value. Second, when the host computer program is stopped, the cluster on the RT host writes what appears to be default values to all the variables in the cluster on the RT. The idea is to keep the RT program running in it's current state until the host computer recovers. Of course this is impossible, if it resets all the data to default.
It appears that I can only write to a cluster on one side and read on the other side. I cannot read/write to the same cluster at different points on the host and target machines. With a single shared variable, I can read/write to my hearts content on any process. I haven't been able to find a way to solve this.
I will post the code, but you will need a cRIO to run it. If anyone is using clusters in shared variables, I'd be curious to see how you are doing it.
Thanks,
John
Solved!
Go to Solution.
Attachments:
host cluster test.vi ‏25 KB
rt target cluster test.vi ‏25 KB
Params 1.ctl ‏6 KB

That makes some sense, what I can think of is you are writing to the same cluster in two different places. Each place updates both values so if the host writes B1=False and B2=True then the Rio Writes B1=False and B2=False then the variable will have the latest value of both being false.It's a loop condition.
Even though you are only setting one value in the bundle by name the other value is coming from the cluster input to the bundle by name.
To handle this you will need remove the input cluster to the bundle by name and replace with the shared variable read. This is where you may need a delay to ensure the variable has the most recent updated value.
Also you still have the coercion dots. For the shared variable try linking it to the custom control instead of a undefined cluster (Next choice below in the SV setup)
Robert Fogg
Certified LabVIEW Architect
Attachments:
host cluster test.vi ‏27 KB

Need help getting networked shared variables on compact fieldpoint to work

I'm still a newbie and am trying to get Networked Shared Variables to pass from a VI running on a PC to a VI running on a Compact Fieldpoint. I created a VI that sends a message via a Networked Shared Variable and a VI that receives it. I have them both in the same project. If I run them both on the PC, it works, I can send a message string from the first VI to the Networked Shared Variable and read it in the second VI. I have the second VI turn the LED "A" on and the LED "B" off if I send the string "a", and turn the LED "B" on and the LED "A" off if I send the string "b", and turn them both off if I send anything else. It works as expected if both the VIs are running on the PC. The second VI also continuously blinks the LED "C" so I can verify that it's running.
I "deployed" the second VI to the Compact Fieldpoint as follows:
In Project I dragged the VI from My Computer (under Project: name.lvproj) down and put it under the Compact Fieldpoint name.
I right clicked on Compact Fieldpoint name and verified it was set to "Connect".
I right clicked on the second VI and selected "Deploy".
I started both VIs with the "Run" arrow. At this point I know second VI is running since the LED "C" keeps blinking. But, when I try to send an "a" or "b" nothing happens, so the VI on the Compact Fieldpoint must not be receiving the messages in the Networked Shared Variable.
I also right clicked on Compact Fieldpoint name and selected
"Disconnect". The second VI continued to run since the LED "C" keeps
blinking, but I still can't get messages to pass.
Any help will be greatly appreciated.

I got this to work. I moved the library (.lvlib) containing the Networked Shared Variable to down under the Compact Fieldpoint name. Now it works.

Network shared variables lose binding

Hello,
I am developing an application in LabVIEW that uses network shared variables to transmit data between two PC's on the same subnet. The shared variables work fine when running the VI's in development mode, however, when i build the vi's into an executable I find that they no longer work. Here is what I have found so far:
I deploy the shared variable library on the publisher machine (also happens to be the development machine) through an invoke node in the executable. NI distributed system manager confirms that this does deploy and indeed updates as it should.
For the executable on the subscriber PC I created a second shared variable library (same project) with the same shared variables and bound them to the respective shared variables from the first library by selecting enable aliasing, then bind to PSP URL and browsing to the shared variable I wish to bind it to (e.g. \\hallnet-ellm2\shared variable library\serial Number). The machines listed under browse were listed by name so when I tried this initially and it did not work I manually changed the name of my machine in the URL box to the IP address of the publisher hoping that would fix it in case the subscriber could not resolve the publishers machine alias. So now my bind URL read \\192.168.0.1\shared variable library\serial Number.
As part of the executable on the subscriber I deploy this second shared variable library. NI distributed system manager confirms that this deploys but under quality for an individual variable it has a list of issues (see attached) and the bound variable is not updating. At this point the publisher shared variables are still functioning fine. By clicking on 'edit variable' I can see that the variable on the subscriber is still bound but the PSP URL is now \\localhost\shared variable library\serial number. Changing the PSP URL on the subscriber to \\192.168.0.1\shared variable library\serial number enables the variable to update as expected.However by this time my executable has already picked up the error and does not function.
I think that the issue lies with the bind URL used on the subscriber as for some reason it does not keep the binding configured in the project and instead changes to 'localhost'. Why is this? Should it not stay bound to the address specified in the project?
I have tried changing the IP addresses in the aliases file so that
[My Computer]
My Computer=localhost
becomes
[My Computer]
My Computer=ip of local machine
This did not help.
The shared variable libraries are included in the build spec to go into the support files directory and they are successfully deployed from there on both publisher and subscriber.
I am using LabVIEW 8.6 on Windows XP
Thanks for any help you may be able to offer,
Lee
Attachments:
distributed system manager.JPG ‏74 KB

Hi Lee,
I hope you are well. Thank you for your post. Your application sounds very interesting.
Looking at your issue I was wondering, have you tried lowering your firewalls, as this may be causing the problem.
Also, another option would be to setup a private network. Do you have access to any routers that you could use to link the two machines independent of your IT's infrastructure?
The other thing to try is two other computers entirely. Again, it would be ideal to take them off the network you are on, but it's something to try if my prior suggestion doesn't work. It should work on the original two machines though, and it's likely that different computers won't solve your problems because I suspect the network.
Remember that the client variables must know the location of the variables on the server, so you can't move the server exe around without changing this value.
Make sure to set the network location in the "Bind to Source" option for the client variables.
It is also possible to write a separate piece of code to install on every machine that is responsible for deploying the library and by doing so eliminate the need for programmatically deploying the variables in the original application. However, this won't really help you, because the variables you use in the application have to be the same as the ones deployed in the library, so if you change the library, they'll no longer be linked and they won't receive data. You'd have to create a separate exe for every binding source you wanted to link to, and then have a second, known library for the sake of communication locally on the computer between the ‘deployer’ and the actual application. The main application could then be assigned the responsibility of launching the correct ‘deployer’' if it sees it needs to switch to a different variable binding source. This method is not the most streamlined or effective, but it might work.
Just to let you know, you will need to use the DSC toolkit.
Please find below some knowledge base links that I think you will find helpful in your application.
Using Shared Variables in Executables
How do I Programmatically Change the Data Binding Source for Shared Variables?
I hope this information helps and if you can give these suggestions a go and let me know how you get on, that would be great.
Kind regards,
Prashant M
Applications Engineer
NI UK & Ireland

Distributed application: Networked Shared Variables, Named Services (Raw TCP/IP) or Other?

Happy New Year NI forums!
I am working on a project involving mobile interacting robots. In the future it is likely the application's components may need to run on different PCs (Targets). Note: at this point in time all the components are seperate but all running on the localhost machine. Thinking towards the future I want to pick the 'best' architecture to allow all these components (VIs performing various functions) in multiple locations. For example, several VIs on the Robots, VIs on serveral PCs.
I am currently aware of using Server/Client TCP/IP using named services. My mock up works well, but is it time efficient (my time coding) I wonder.. ?
Whereas I am aware of networked shared variables which handle connections and all the parsing for the underlying tcp/ip communication. But will this be difficult the manage? I am unsure if I can associate shared variables with a VI similar to named services. I suppose I could pro grammatically create the variable upon initialization of the server component - and the client could just search the list of avaiaible variables to connect too. Downside this would require DSC module.
As you can see, I am rather unsure. Any advice would be great!
Kind Regards,
James
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!

Hi Jason,
Thanks for your reply. I hope your enjoying NI UK as much as I did.. fun times!
I have seen the link you posted a few times before. But today, I took a better look at it.
My issue is I need several multi-client severs, i.e. many servers which allow multiple clients to connect to them.
Now the STM does have an example of this - STM mutli-client Example - Server.vi (used with the STM mutli-client.vi)
However, when a make copies of these code (to have my second server) - it refuses to run. As in , it just stops itself.
I DID change the port number, on the lister aspect of the server code. But I Am unsure what else I would need to change to get this setup to work?
One thought I had was, the FIFOs all having the same name - this probably isn't a good idea between servers.
Any suggestions would be grateful!
*please could you provide me email support
Kind Regards,
James Hillman
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!

The shared variable does not exist????

This seems really strange!!
I already use several shared variables within my whole project without any problem. At this point, I created a new one (a boolean network published) and everything seemed just fine (no errors were detected in my VI and it runs normally). However, when the VI on my host computer tries to use the shared variable, it generates an error message saying "LabVIEW: (Hex 0x8BBB0005) The shared variable does not exist." (see attached screenshot).
What is going on? I can't find any help online about that... Can anybody help me with this please?
Thanks!

Hello,
This error can occur if you have an incorrect Path specified under your Bind to Source section for the shared variable - this could be as simple as a typographical error in the defined path. Double-check that portion of your shared variable definition, and hopefully it'll be as simple as finding a typo in your path. You should be able to browse for your variable/path by clicking Browse and then selecting Network Items if your shared variable is on the network. Can you find it by browsing?
I hope this helps!
Best Regards,
JLS
Message Edited by JLS on 10-05-2006 03:54 PM
Best,
JLS
Sixclear

Inconsistent Network Shared Variables

I will eventually be implementing a controls program on a machine using cfp. Before the cfp gets here, I am getting practice in network shared variables by trying to pass shared variables between two VIs on my computer. I have attached the two VIs and a screen shot of my project. I run a queued state machine and after the initialization routine is done, I run the control portion of the program. The control program is titled 'The4Mprocedure2.vi' and the QSM is titled '4M_QueueDrivenStateMachine'. In the initialization routine of the QSM, 'FALSE' is written to the boolean network shared variable, 'Run_4M_Procedure'. After the initialization routine is done, and a set of certain parameters are met, the QSM writes the value 'TRUE' to 'Run_4M_Procedure'. Ideally, The4Mprocedure2.vi would read the shared variable, and when the value is 'TRUE' The4Mprocedure2.vi would run. The4Mprocedure2.vi has a case statement that causes to run the program when 'Run_4M_Procedure' = TRUE. The4Mprocedure2.vi does not run when the variable is FALSE.
The problem that I am having is that The4Mprocedure2.vi does not always recognize that the value of my shared variable has changed. When the QSM passes the value of 'TRUE' to the controls program, The4Mprocedure2.vi will sometimes still read the network shared variable as FALSE. Sometimes, I have to restart the controls program several times while the QSM is running to ensure that 'TRUE' is passed to the controls portion. Why does my controls program not recognize when the network shared variable changes values?
Message Edited by tquintana55 on 07-14-2008 11:04 AM
Attachments:
The4MProcedure21.vi ‏87 KB
ProjectScreenShot1.JPG ‏68 KB
4M_QueueDrivenStateMachine1.vi ‏131 KB

Hi tquintana55,
I believe your Issue is related to the methods that LabVIEW subscribes to the shared variables. Here is a link to a related article:
How to Avoid the "0" Value at First Read of a Shared Variable in LabVIEW 8.5.x?
To resolve this you can move your Run_4M_Procedure inside the while loop.
Sappster

Network shared variables reconnecting network dropout

I've got a cRIO unit communicating with a Laptop using Network Shared Variables, with one of them being a 21 index array that is buffered.
The system connects and communicates fine, but occassionally the wireless card in the laptop is losing the signal from the WAP attached to the cRIO.
When this happens the Network Shared Variables never "reconnect" and start receiving values again once the Wireless link is restored. Is this an expected behavior?
When I tried using another industrial WAP instead of the laptop wireless card I do not get the drop-outs.
Ryan Vallieu
Automation System Architect
Solved!
Go to Solution.

Hello Ryan,
Thank you for contacting National
Instruments! I have looked into the issue you are experiencing and
wanted to ask you a few more questions. First of all, do you have a
time frame in which you allow for the reconnect? I believe that the
Shared Variables should regain connection after a short period but it
will not necessarily be a very quick process. It may take a few
minutes for the Shared Variables to reconnect.
The other
thing that may be happening is if you have error wires being passed
through the Shared Variables, it is possible that the error is not
being cleared and so it will always see the error and therefore never
reconnect. In this case you will have to filter this error out and
then clear the error in order to utilize the shared variables again.
If
you have any more specific information about your program that may help
us determine the reason for this behavior. Also a screenshot of your
code would also be helpful. Please let me know if you have any further
questions and I will be happy to assist you. I hope this helps!
Thanks!
Bob H
Applications Engineer
National Instruments

Network-Shared Variable - read string with CVI

I need to read an NSV string with CVI. I have been digging into accessing and writing NSV with CVI, but they are all scalar value. What should I do with strings, clusters and arrays?

'm an employee at National Instruments and I wanted to make sure you didn't miss the Network Variable API that is provided with LabWindows/CVI, the National Instruments C development environment. The the Network Variable API will allow you to easily communicate with the LabVIEW program over Shared Variables (http://zone.ni.com/devzone/cda/tut/p/id/4679). While reading these links, note that a Network Variable and a Shared Variable are the same thing - the different names are unfortunate...
The nice thing about the Network Variable API is that it allows easy interoperability with LabVIEW, it provides a strongly typed communication mechanism, and it provides a callback model for notification when the Network/Shared variable's properties (such as value) change.
You can obtain this API by installing LabWindows/CVI, but it is not necessary to use the LabWindows/CVI environment. The header file is available at C:\Program Files\National Instruments\CVI2010\include\cvinetv.h, and the .lib file located at C:\Program Files\National Instruments\CVI2010\extlib\msvc\cvinetv.lib can be linked in with whatever C development tools you are using.
Thomas N.
Applications Engineer
National Instruments

I have upgraded to Lion Os but my Network storage (Iomega Home Media Network hard drive) does not work with Time Machine. Are there any solution available?

I have upgraded to Lion OS only to find that my NAS (Iomega Home Media Network hard drive) does not work. It tells me that it is not configured. Are there any solutions . Have Iomega sorted out the problem?

Same issue here. Based on what I can tell, iomega still has not developed a solution to the problem. See below:
https://iomega-na-en.custhelp.com/app/answers/detail/a_id/28327/kw/Mac%20OS%20X% 20Lion

Variable Text not working as dynamic header in Crystal report

Dear Experts,
I'm working Crystal report that connected to Query BEX SAP BW trough SAP integration kit,
currently i have case that need report dynamic header using variable text from BEX query, but seem the variable text not working in Crystal reports. the header in Crystal report shown as Desription\technical name, not result from the variable text in Query BEX in SAP.
In https://wiki.sdn.sap.com/wiki/display/BOBJ/Crystal%20Reports%20and%20BW%20query%20elements stated that the "Text variable" with "replacement path" is supported, but i don't know in my query is not working.
i already set in Database -> options-> table and fields -> Show Both, but the text variable still not working.
can you help me
Crystal Reports 2008 12.2.0.290
SAP Integration KIT 12.1.0.890
Thanks
Luqman

Post your question BEX and B1 and classic SAP data source issues to the Integration Kit forum

TS1559 hello guys i wanted to ask u about my ipad wifi is not turning on and i have tried to reset the network but still is not working please i need ur help

hello guys i wanted to ask u about my ipad wifi is not turning on and i have tried to reset the network but still is not working please i need ur help

Thank you. I will try your tip. And if it works, I'll give you 10 points . But now its been charging for hours and its still the same . But thank you!

RT Network Shared Variable and Visa Serial Instr class

Hi,
I'm using Labview 2009 SP1 with the RT module. I've had no problems creating a RT Target application and a Host PC application which are interconnected using Network Shared Variables, until I came to the COM ports fitted to the RT Target (PXI Embedded Controller and 2 x 4 port COM cards).
I can configure and use the COM ports in the RT Target application providing I use constants to define which COM port to use, i.e. VISA OPEN function accepts hardcoded "COM2" , (VISA Serial Instr class).
But I want to pass the COM Port resource name from my host application.
Is there a suitable Network Shared Variable I can create ? or how do I change the string value (COM Port name) of the VISA Serial Instr class variable in the RT Target application ?
thanks,
Gary.

Hi there Gary,
Thanks fot the post. I think I have found something that may be if use to yourself.
http://labviewwiki.org/Functional_global_variable
This is the functional global variable.
Take a look at it and let me know what you think!
Many thanks,
Liam A.
National Instruments
Applications Engineer

Network Shared Variable: Aliasing not working

Similar Messages

Maybe you are looking for