Shared variable dialog window

I want to ignore the dialog window or prevent it from coming up when there is an error in my shared variable. I am reading data from a PLC on a manufacturing machine. I am doing this on a separate server system and it isn’t monitored, so the fault does nothing but lock the Vi and prevent it from collecting data until someone happens to look at it.
I have a loop that is waiting for the variable to change and the most common error is when the PLC is turned off and there is no data available, however there are others that come up now and again.
I want to simply return to the loop and keep cycling until the data is there and readable again.
Is there a way to prevent the Shared Variable from halting on error? Can I turn off the dialog box so that it doesn’t stop the Vi?

It is coming from LabVIEW's autmatic error handler. There is also a VI option that can be changed globally for the VI to ignore the error. But I don't recommend changing that unless you have accounted for all other errors you could possibly get elsewhere in the VI. Any node that has an error output not wired to something else will have this dialog box pop up if the VI option is set to automatically handle the errors.
Another alternative is to wire the shared variable error to a tunnel on the loop, but don't do anything with it afterwards.

Similar Messages

Odd Shared Variable Dialog Box message

I came across some odd behavior in the dialog box while I was created a new shared variable.
As I was typing in the name, I kept see a warning pop up in the dialog. It would come and go as typed. I figured out that whenever I typed a space, and thus it was temporarily the last letter in the SV name, the warning popped up. Type the next letter, the warning would go away. You can see the space ending the name right before the cursor in the top picture, and the name ending with a normal character in the bottom picture.
Now it is logical to me that ending a shared variable name with a space would be a bad practice, and should be warned against. But the warning never actually states that you can't end with a space. To be more precise, it says you can't have the slash code \s in the variable name. Now I am not actually entering slash codes, but I am entering spaces. And they seem to work just fine in the variable name, just not if it is the last character.
It just seems to be a mismatch between what the warning says, and what you can and can't do.
Can you have spaces in the SV name? By my experience you can.
Also, this in in LV 8.6 on an XP SP3 machine.
Message Edited by Ravens Fan on 03-05-2009 05:02 PM
Solved!
Go to Solution.
Attachments:
SV Dialog.PNG ‏48 KB

ColeTrain wrote:
Ben, which VI did you use to create your bogus folder? Was this a specific DSC VI or just the generic Create Folder VI?
The CAR for that bug was "105656".
The desription for that CAR was "Create DB while specifying path with space on end creates illegal Windows directory".
It supposed to create then put then put hte data files in the specified folder. It does the create but has trouble putting the data in the folder.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Using shared variables in windows 7 64 bit

Hi !
I am trying to use network published shared variables (with Labview 8.6.1) in windows 7 64 bit. I have three PCs on the network. All PC's are visible to each other. I am able to remotely log on to other PCs.
But when i run my program, the shared variables are not able to read the value over the network. The same program was working with windows XP.
I am not sure whether it is windows issue or labview issue.
Please help ASAP.
Mandar Joshi

I am having the same problem with Shared Variables with LV8.6.1 and Win7 64 in a program that uses a shared variables to share in seperate loops. I was able to use a local variable instead, but would love to know if it possible to use shared variables with 8.6.1 and win7.

Order of Variable Dialog Windows

In a workbook with five queries, how do I set the order of the variable popups? I have exposed SAPBEXqueries but I don't see anything I want to fool around with. Sheet1 has all the varibles in its query, so I want that one to pop first so the others won't even appear.
Thanks,
Geoff

Raj,
I'm running 3.5 but I don't think that's the correct option. I checked it for all the queries and re-saved the workbook, but when I re-opened it, I was not presented with any variables. Instead, it re-ran the workbook with the values I had input previously. We need to present the client with the dialog from the query on Sheet1 first, or even better, one dialog that combines all the unique variables in the workbook.
I recall that the order of the popups is somehow related to the order in which they were inserted into the workbook, but I don't know what that rule is, and it would be a huge job to rebuild the workbook even if I did know it would do.
Geoff

Shared Variables vs Globals

   I started a large project recently and decided to make use of Shared Variables. :I need some network communication between LV apps, so that is the main reason, but I decided to put them to the test by also using single-process Shared Variables instead of globals. (Yeah, yeah, globals are evil. blah blah blah. I'm not really interested in dogma here. Suffice it to say that, IMHO, there are still a few times and places where globals are appropriate and useful.)
   My project is fairly modular, and the main control program launches numerous other top-level programs. The problem is that whenever one of these top--level programs (or the main program) is launched, the Shared Variable deployment window pops up and does its several second initialization.; If this happened just once, when the top level program launched, it would probably be acceptable. But having each dynamic VI go through this gets annoying.
   I'm using 8.2.1. I haven't tried 8.5 much yet, but at least in 8.0 and 8.2, you can't search for Shared Variables. That is also annoying and can lead to maintenance issues.
   So now I am considering replacing all the single-process Shared Variables with good-ole Globals. A couple of the VIs in the system will still use networked Shared Variables, so they will still cause the deployment window to pop up, but it will be much less frequent. And I'll be able to search for the globals and make sure I'm using them responsibly.
   Does anyone have any other ideas on how to minimize the deployment window? Or ideas on development patterns using Shared Variables? Preferences for Shared Variables vs Globals?
Thanks,
    Dave
David Thomson Original Code Consulting
www.originalcode.com
National Instruments Alliance Program Member
Certified LabVIEW Architect
There are 10 kinds of people: those who understand binary, and those who don't.

Ben,
   Wow, you are quick. And thanks. Good catch. Turning off the auto-deploy removes the dialog. Nice, but now I have to figure out how the SV's are going to get deployed on each installation... I haven't fully digested how SV's really work, especially how to best handle the deployment issues. This project will be installed on a number of computersand used by scientists, not LV programmers. So I need a reliable way of setting up the deployment. Perhaps it is just one more step in the installation process.. That assumes that all the SV's are defined when the program is first installed The program is very modular, so the end-user will be able to copy new modules into a certain directory and be able to use them right off the bat, no extra programming. But if a new module contained a new SV, it wouldn't be deployed...
   Any suggestions for searching? I haven't tried it yet, but it seems that deleting a SV from the project is the only way. That causes an error to occur at each instance of the SV. Assuming all the project VIs are in memory, you can then use the error finding to locate every instance of where the SV was. Of course, it isn't there anymore. Minor issue...
Graziano,
   Thanks for the ideas. I do use functional globals a lot as well. Very nice tools.
   I was really trying to transition to SV's so that I could use the Networked version. I was using Single Process SV's instead of globals just as an experiment and to potentially leverage other SV features for them in the future.
Regards,
   Dave
David Thomson Original Code Consulting
www.originalcode.com
National Instruments Alliance Program Member
Certified LabVIEW Architect
There are 10 kinds of people: those who understand binary, and those who don't.

Enable shared variable buffer

Dear all,
I'm writing on a program to create shared variables programmatically. I use the examples available in labview and DSC 8.0 as reference. I'm able to create and set the different properties such as scaling, alarms, inital value etc for the shared variable(s). However, when i wire a boolean "true" to " enable buffering", it doesnt seems to work. I checked the shared variable created in the shared variable engine, the variable is created but the buffering cant be enabled programmatically. Can anyone guide me what's the fault? thanks.

Hi,
The VI worked without any problem though I had to change the shared variable name. One thing to note about changing the properties of shared variables programmatically using the shared variable I/O is that it only affects the deployed shared variables and not the actual library file. In essence, these changes are not saved in the library. So the shared variable properties window will not reflect the current status of the "Network.UseBuffering" option. To verify that the "use buffering" is enabled, place another "Network.UseBuffering" property node on the block diagram and read the current state from it.
Attached is a modified version of the VI with the current status of the "Network.UseBuffering" property for the deployed shared variable.
Tunde
Message Edited by Tunde A on 03-05-2007 12:34 PM
Attachments:
Modified_buffering_error.vi ‏10 KB

Deploying shared variable

Is it possible to disable or hide the deploying shared variables dialog box at program start?

Hello Peter
No, it is not possible to completely disable or hide this dialog box when deploying a VI to a real time target or building an executable since this dialog box is used to report errors during the download process. The only thing you are able to do is check the Close on successful completion checkbox to close this dialog box after a successful download.
Carlos Pazos
Applications Engineer
National Instruments Mexico

Shared variable engine with pro-face touchscreen windows 2000 professional

hello,
who has some experience with the shared variable engine from LabView 8.5 and a touchpanel from Pro-Face?
We try to deploy shared variables from the touchpanel but it doesn't work. Additionally the windows service ni shared variable engine dosn't start and we can't start it manually .
The touchpanel is a PS3701A from Pro-Face with Windows professional 2000 for embedded, Pro-Face told us that we have the full service of Windows 2000 professional on a regular PC.
Many thanks in advance
derN

Hi Andrew,
Thanks for the feedback! Your feedback will help us to improve LabVIEW for our customers. This bug has been reported to R&D (#45493) and they are currently investigating this issue. For now, the best workaround appears to be using a different OS, as this seems to only occur in Windows 2000. Thanks for the feedback!

Shared Variable Engine on Windows PC w/o full install of LabVIEW

I have the NI Developer Suite (8.20) and need some conformation before I get too deep in a project.
First of all, it is my desire to become very efficient on develop compiled executables with LabVIEW 8.20 as my NI Developer Suite license allows me to deploy these programs to any number of machines without facing copyright infringement. I have been successful with this to a certain degree, but am still having problems in the testing stages of my application especially in cases where the hardware I am trying to target does not exist on my developing station. If anyone can point me to white papers that would help me get the mindset to develop in this way, I would appreciate it.
Onto the topic of this post:
I am just scratching the surface of the shared variable interface that is available in LabVIEW 8.2. My project involves two computers where both of them need to share variables back and forth from each other. I've been reading everything I can get my hands on and I am having a hard time answering my unlying question: Is it possible for both of these machines to be running compiled LabVIEW programs and still manage the shared variables between them? That is to say, can one of the machines have the Shared Variable Engine running on it as a Windows service, or compiled into my application executable.
I've read that I can access shared variables from my compiled LabVIEW application through NI-PSP. I am wondering what my limitations would be sans-LabVIEW installation other then the troubleshooting head ache you get from developing applications without direct access to the hardware.
Thank you for your time and submissions.
-Nickerbocker

I am trying to get the "Shared Variable Client - Server" project example compiled so that both the server and client vi's can be run as executables on a standalone machine.
I have created 3 build specifications:
1. "My Server" which is the compiled EXE of the server.lvib. Added that entire library to the source.
2. "My Client" which is the compiled EXE of the client.lvib. Added that entire library to the source.
3. "My Installer" which is the installation package of the vi's and NI supporting software. In the additional installers I have added:
* NI DataSocket
* NI LabVIEW Run-Time Engine 8.2
* NI Measurement & Automation Explorer 4.1
* NI Variable Engine
* NI Variable Manager
* NI-DAQmx 8.3
Some of those are added for future needs. Installed the package on my target machine and run the server executable it appears to run fine but I get various error messages from my client.exe package (which I won't go into detail here, yet). Upon stopping the server I get the message "LabVIEW: (Hex 0x8BBB0005) Unable to locate variable in he Shared Variable Engine. Deployment of this variable may have failed."
I check the services running and see that the "National Instruments PSP Server Locator" and the "National Instruments Variable Engine" are both in the list and "Started." I open up the Variable Manager that has been installed on my target machine and manually add the "waveform" and the "command" variables under a process I call "server" and start the process. After that I start my server.exe that I have compiled from the server.lvib library. The process gives no error messages until the stop button is pressed, and then I receive the message "LabVIEW: (Hex 0x8BBB0011) The connection to the server was disconnected."
The compiled programs run fine on my development machine as well as the uncompiled VIs within the LabVIEW development enviornment. Something tells me that I simply do not have the Variable engine properly configured on my target machine. Also, the process and variables should automatically be populated under "Local System" in the Variable Manager, right? I do not need to add them manually, or do I?
Thanks for your input!
-Nickerbocker

Windows XP vs Windows 7 and shared variables

I have a stand-alone app I install onto 2 different PCs. One PC runs Win XP and the other Win 7. The application must deploy 3 shared variable libraries before the executable can run. On the Win XP PC, I can be a user and accomplish this. On the Win 7 PCI must be sys admin. If I login as a user in the Win 7 PC, I must have the app set to run as sys admin otherwise the user cannot run the app. What has changed?

Faustina,
I do not know of a good way around this. However I did find several links that I think should help. First here is information about what is going on http://digital.ni.com/public.nsf/allkb/E06C1800F5AFCCBF86257236006C9F2A?OpenDocument. Next as a workaround I would suggest setting the exe to run as admin you can find instructions for that here https://technet.microsoft.com/en-us/magazine/ff431742.aspx.

Shared Variable Engine clock is consistently inconsistent

From the annals of the weird:
I noticed a while back that the DSM displays a different time than my system clock when I manually change a NSV value. I didn't think much of this, but then I noticed that it is not just wrong but inconsistently wrong. Here's the time difference, in seconds, between the system clock and the SVE timestamp for a dozen NSV value changes [the SVE clock always lags behind]:
35, 14, 1, 18, 29, 2, 21, 24, 14, 17, 29, 20
I checked these numbers in two different ways: (1) with the "Time stamp" event property node with NSV events using the DSC module and (2) manually changing values with the DSM and comparing to the displayed Windows time.
What's the deal? The timestamp is completely useless to me with a seemingly random offset from the system time; it's by far the best way to deal with this little bit of unfortunate SV event handling behavior. Filtering event timestamps against system time is fairly standard procedure and I can't see it being useful with this going on.
This should be trivial to reproduce--does anybody else see this? If so, is there an explaination--or better, a fix?
[I should note that I have seen this but I'm running Intel core 2 duo, not an AMD multicore. I'm using LV and DSC 2010 SP1]

You may have to set up the Time Synchronization Services on the computer with the DSM running.
In LabVIEW Help, look for Shared Variable Engine Page (Options Dialog Box)
In DSM Help, look for Shared Variable Engine Time Server Configuration Box
I don't know if both are necessary but I made all the computers on my system point at the same time server. The time server is configured as an Authoritative Time Server under Windows. It is in turn slaved to our DSN server which follows a Public NTP server.
JohnCS

Shared Variable Conflict with RT Startup App

I think I am running in circles trying to determine what my problem is. Please look at the screenshot I have attached.
I setup three different network shared variables (two in one library, the third in a second library) on my RT target. I have deployed them manually probably half a dozen times. I then build the executable, and tell it to make it a startup app.
I then created alias shared variables on my user computer. They are setup as PSP variables that I linked thru the dialog boxes NI provides. A sample URL of one of these variables is: \\169.254.0.2\rtDataRouter\Data
I deployed this library on my user computer. From what I was reading, I am not sure if that is the correct thing to do if I am having the RT target host the main variables (we want to be able to hook up multiple clients at remote locations, hence have the RT host them). So I tried it both ways, with the aliases deployed and without.
If everybody is still with me, when I run pure development environment, Labview 2009 SP1, deploys everything to the RT, I then run my local app, it says it is deploying items, and then it runs, shared variables seem to talk to no problem. Doesn't seem to matter if the aliases were deployed or not (I do have auto deploy turned off).
Next, I try deploying the RT startup app, it reboots, I hit the run arrow on local machine, and I get the conflict window! Again, I try manually deploying the libraries on both the RT and local machine, rebuilt the executable, reboot the RT, run the local app (still in development environment), and I get conflict window!
Part of me thinks, I am simply missing turning one thing on or off. From the tutorials on NI's site, I think I am in the ballpark, what am I missing???
My project is 99.99% done other than getting the executables done. Any insight and help you can give would be HUGE for me to get this out the door!!!
Attachments:
screenshot.jpg ‏301 KB

Make sure you have Autodeployment turned Off on your cRIO targets as well as your Windows Target.

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

I am trying to connect Dashboard shared variables to a server on a different subnet. Any ideas?

My goal is to control a device that is connected to our wired network using an Android tablet via Dashboard. I have created a vi with shared variables that controls the device as expected when it runs on a computer that is connected to the same wired network. The problem is that my Android tablet running the Dashboard app cannot connect to the shared variables on the PC running the vi on the wired network.
Our wireless network is on a separate subnet from our wired network. I am able to ping my Android tablet from the PC on the wired network but when I try to connect a variable in Dashboard, the PC running the SVE cannot be found. I tried listing it in the alternative server settings window and it still did not work. The only way I have been able to get around this is to run the vi which launches the server on a laptop that is connected to the wireless network and the wired network at the same time. My tablet can then find the server and my VI can connect to the instrument that is connected to the wired network. The laptop is somehow acting as a bridge between the subnets. I need to find a way for the Dashboard app to connect directly to the PC on the wired network. My PC IP address is 192.168.0.105. My Android IP address is 192.168.10.93.

Data Dashboard doesn't care about subnets, but it has to be able to access the server using the right ports. There is probably a firewall blocking the shared variable ports. This document explains how to configure a firewall to allow shared variables to be accessed. Your challenge will probably be to figure out where the firewall is and how to configure it.
It is also possible that the router that your Android device is connected to doesn't know how to route to the other network. Again, that is an issue with your router that you need to resolve.

How to add a new Shared Variable programmatically to an existing and deployed library?

Hi there!
I am trying to accomplish this on both LabVIEW 8.6 and LabVIEW 2010 and seems like it's not any different in this situation.
My case: A project has a library with 4 Shared Variables (SVs). The library and the variables are deployed (visible in Distributed System Manager 8.6/2010). I want to add 2 more variables into this library. It is possible to do this manually from Project Explorer window's options menu. But while running an application it has to be done programmatically. Can I provide the library reference to the one currently existing without creating a new one?
"Create Or Add Library To Project" function in the Datalogging and Supervisory Control (DSC) toolkit does not help in this case. That function, as the name suggests, just tries to create a new library in the project.
Two possible methods:
The function "Add Shared Variable To Library" (DSC>EngineControl>Libraries & Processes) needs a library reference, which could be provided via "CreateOrAddLibraryToProject" function, but this function tries to create a new library, and if I provide the path of the existing library it throws an exception that the library already exists in the project (yes, as I wrote above, I need to add new variables to an existing and deployed library).
OR
The function "Create Shared Variable" (DSC>EngineControl>Variables & I/O Servers) will add Shared Variable in a process, and not physically in a library file, and the problem (limitation) with this approach is that it doesn't allow to add complex data type Shared Variables (for example in LabVIEW 8.6 it has only 4 datatype options in input parameter, and even in LV2010 it does not have "Image" datatype that I need).
The scond method is my preferred method as it allows to work on Online Shared Variables and doesn't create them physically in libraries (and this is good as the variables' scope remains only till the Variable Engine is running). But it doesn't support advanced data types, and the first method is powerful in terms that it supports to virtually any datatype, it just seems tricky to get that reference to the library.
Any tips?
Thanks ahead!
Vaibhav

<<<<>>>>
As the above two images show, while a library does not exist, it is easy to use the "CreateOrAddLibraryToProject.vi" which will add a new library to the project (if it doesn't exist on file system, a new library will be created) and that way, using the reference (the green wire going out from the function and the Case Structure, can be used to add Shared Variables to the library. The problem was what to do when a library already exists in the project, how to add more variables to it. I was looking for a way to get a library reference, and somehow I could not see it inside a Project's property (VI Server functions). Hence I posted the question. And upon continuing my search, I found it on the Application's property list.
I hope it was useful for someone else as well. And thanks for the replies. Please share a better idea if you have.
Vaibhav

Shared variable dialog window

Similar Messages

Maybe you are looking for