Shared Variable Not Deploying

I'm having a hard time getting the shared variable to deploy on the C root of the computer.
The following error comes up each time I try to deploy the Lib
Deploying Untitled Library 1\\192.168.0.12\Untitled Library 1 deployment failed (error: -1967362042, IAK_SHARED: (Hex 0x8ABC7006) Unable to start service.)
I've tried uninstalling and installing labview and it's components.
I would appriciate any help.
www.movimed.com - Custom Imaging Solutions

Joey,
Thanks for the response.
The service will not start. I get the following error attached.
The document suggest reinstallation of the DSC Module, problems is I do not have DSC installed. We do not have a lincense for it.
Dan,
www.movimed.com - Custom Imaging Solutions
Attachments:
Service Start Error.png ‏27 KB

Similar Messages

Modbus I/O Server Shared Variable Not Updating Immediately After Flush

Hi everyone,
Weird issue here... If I create a Modbus I/O server in a LabVIEW project, bind a shared variable to a holding register, write to the shared variable, flush, and read back, the value returned in an immediate readback is NOT the value I previously wrote. I've attached an example snippet.
In this example, PLC Command Complete is TRUE coming in. I write a FALSE to it. I flush the shared variable buffer. I read back PLC Command Complete. When I do this, PLC Command Complete will return TRUE (???), and after 100ms or so, return FALSE. How is this possible??
Some notes:
The shared variable is NOT network buffered.
The slave is NOT altering the value of this variable; only this snippet of code is.
Altering the refresh rate of the Modbus server does not affect the outcome.
If anyone has any idea as to what's going on, I would greatly appreciate it!

Couple of points.
First, your screenshot shows network shared variables, not single process!
Next, network shared variables take time to update (much longer than NI tell you!) If you knock up a little timing noddy to set a variable and then loop reading that variable until the transition comes through you get results like this (runnng from the programming environment, I've not tried with a compiled exe):
Network shared variable, no flush - approx 20ms (NI say is should be 10)
Network shared variable, flush buffer - very fast (faster than the ms clock resolution) but still took between 14 and 20 iterations of my loop before the change percolated through (certainly not what you would expect)
Single Process variable - instant (even without the flush)
This has caused me so many problems in the past (my own race conditions are bad enough without NI throwing in extra ones with this unexpected behaviour) that I try to avoid network shared variables now.
Change yours to single process and you should be fine (or do they need to be NS?)

Not able to access Network Shared Variable when deployed in PC

Initially, when we deploy a Network Published Shared Variable in PC and try to access the same (Read/Write) from RT, we get an error/warning "-1950679023". But when we access the same variable from the PC, it works fine. In the distributed system manager, we can see the variable getting deployed. Also the value changes in Distributed System Manager if we write a value from PC. The attached image "Shared variable Issue.png" will give more understanding of this issue.
The other way round it works fine i.e deploying in RT side and accessing from both RT and PC is working fine.
We also see that the network adapter settings is not loading properly in MAX, if at all we install any software in RT. With no software installed, it loads properly.
The following were the steps that we tried to solve the issue.
1.Flushing the entire NI software and Re- installing again
2.Formatting the RT(PXI).
3.Removing the EtherCAT Card and testing.
4.Checked the network properties of the RT network.
5.Checked the IP/Subnet/Gateway settings.
6.Checked Firewall Settings, If Shared Variable Engine is accessible.
Attachments:
Shared variable Issue.png ‏491 KB

First Root cause needs to be identified before any actions.
I would suggest first check if you can access the shared variable hosted in PC from RT using other ways like using SVE API (Logos and PS protocols, Datasocket etc..)
Check if antivirus or firewall is playing...
Check the same experiment with some other PC if you can.
You can also try creating another Shared Variable in RT and binding the same to the PC and try to access it...
Since you have did all the reinstallations already
Best Regards,
Vijay.

I/o server shared variable not working in deployment system ( error no-1950679034 (0x8BBB0006) (Warning))

Hello ,
am using shared variable from opc client in labview when am run a exe file at development system its working fine but when am running it in deployment system its not working am using same configuration file in opc server at development and deployment system error -1950679034 (0x8BBB0006) (Warning)

First Root cause needs to be identified before any actions.
I would suggest first check if you can access the shared variable hosted in PC from RT using other ways like using SVE API (Logos and PS protocols, Datasocket etc..)
Check if antivirus or firewall is playing...
Check the same experiment with some other PC if you can.
You can also try creating another Shared Variable in RT and binding the same to the PC and try to access it...
Since you have did all the reinstallations already
Best Regards,
Vijay.

Shared variables not updating in exe

Hi,
I've created a project with 2 vi's, they share data via Networked Shared Variables, one vi writes while the other reads.
The data is passed between the 2 vi's whilst running in the Labview 2009 SP1 development environment, but when I create an exe, the screen values in the reader vi do not update at all.
In the build specification I've tried both including the vi's which reference the shared variables and the
option to list the shared variable libaries for deployment at run time, as methods to overcome the problem.
Please, any clues why the exe should fail to allow shared variables to pass data ?
thanks,
Gary.

Hey Gary,
I've just created a project to replicate the issue you are having and indeed when I built the application, the Shared Variables were no longer working. This is because I hadn't deployed the Shared Variables in code; which I think may be the problem that you're having at the moment. When create a Network Published Shared Variable library in LabVIEW, it auto-deploys itself for the development environment; but this is definitely not the case for when you build an executable. Instead, you must deploy the library yourself in code.
In the attached zip folder, please follow the following instructions and hopefully you'll be able to fix your VI:
Unzip the folder and extract the files.
Open up the project.
Look at the project layout. Notice the SharedVariableLibrary.lvlib and inspect the Shared_Double variable.
Look at how the Reader.vi and the Writer.vi interact with the variable.
Go into the Main.vi. See that I make an Open Application Reference VI and Invoke Node to manually deploy the library in code. You'll have to change the path to this library to match the directory structure of your own computer, so just make sure it navigates to the library in the extracted folder.
Check out the Build Specifications. I've done nothing here except ensure I only include the Main VI. Finally build the VI and run the executable.
You should see that this will give you a working Shared Variable setup. The Machine Name input for the Open Application Reference is blank because you only want to communicate with the localhost i.e. Your computer. Therefore by explicitly deploying all libraries you require, your VIs should be able to communicate effectively.
Does this solve your problem?
Alex Thomas, University of Manchester School of EEE LabVIEW Ambassador (CLAD)
Attachments:
GlobalVariableProject Folder LabVIEW 9_0SP1.zip ‏26 KB

Using shared variable not in the project.

hi all
I have a project with the 2 RT targets and the development PC which were i currently deploy all my shared variables, But I need to finally deploy these shared variable in a different stand alone windows based machine. To do this I created separate application which does nothing but deploys the shared variables in this PC. but when i tried to bind to this variables (frount panel binding) from my RT targets it woudnt work, the led does not glow, it is always transperent. but when I tried to connect to these variables from my development PC it works fine. I double checked the firewall problem, that is not the case here. Can anyone tell me what am i doing wrong?
Thanx
Arun

Hi Prashanth
Thanks for the reply. I did realize that the front panle connection would not be supported in RT, now i have the shared variables on my RT machine which has te source as the windows machine. If the windows machine is my development machine the shared variables connect fine, but if its a different PC the shared variables connect for few seconds and with the error info "shared variable value 0" then the connection gets disconnected.
Also i read a note in the shared variables help, it said to subscribe and publish on a network shared variable all the shared variable which connects to this variable should be active. does this mean that if there are 2 RT targets that subscribe data and one of them is not switched on the shared variable does not work.?
Thanks again for your support.
Regards
Arun

Shared variables not working on PC

Can anyone tell from the attached screen shot, why my one shared variable is not working with the labview application I'm running on my PC. I set the variable to 48 (I thought), and yet in the NI Distributed System Manager the value doesn't changed.
Solved!
Go to Solution.
Attachments:
shared_var_not_working.JPG ‏255 KB

Its not likely to be a deadband problem if you haven't touched the settings. I would check it out just in case though. In the project window, right click on the shared variable>>properties and select Update Deadband. See attached image. If it's not this, I shall have to think some more about what else could cause this.
As for ensuring it works when setting it from DSM...from your screenshot you appear to have a VI that writes to the SV. Change the code ore create a new VI so that it reads the SV and then double check that if you change the value in DSM, the VI also reads back the updated value. It may be that the number changes in DSM but does not update the SV in the VI - this would indicate a problem with the shared variable engine or the deployed variable library...Reboot PC and retry... if the problem persists let me know or attach the SV library!
Regards,
Dave
Senior Software Engineer
www.Adansor.com
Attachments:
SV_deadband.PNG ‏8 KB

Scale cRIO NP Shared Variable AFTER Deploying an Executable

I have a project coming up that has about 140 shared variables deployed on an RT target and sharing data at 1S/s over the network. There is nothing else going on concerning the RT target, just dumping values. I would like to scale these SV's in the .lvproj to avoid having to write a bunch of scaling code in software.
My only concern is what happens when I have an executable application running (without LV 2012 installed on the computer). How would I re-scale these values without having access to the .lvproj? Distributed System Manager doesn't provide for this. Any help would be appreciated. Thanks.
Nathan - Certified LabVIEW Developer

Hy Nathan,
Your Shared Variables are within a library in you LabVIEW project. In your Application Properties make sure to include that library. This is shown in Figure 9 in the below white paper.
http://www.ni.com/white-paper/9900/en/
MJ
Application Engineer
National Instruments

Binding a shared variable to a NI-PSP data object does not work

Hi,
I want to share data between a RT-target and one or more hosts (LV 8.6.1). The network shared variables are deployed to the RT-Target. According to NI accessing shared variables from another project or host has to be done by defining a shared variable on the host and aliasing it to the NI-PSP data object on the target.
I did that and the host shared variable generated an error (0x8BBB0011) during runtime.
Next I aliased to a shared variable deployed on the host from another project. This did work.
Another thing I tried was to bind the variable from the RT-target to a display element:
This is working !!! And as you can see the path of the NI-PSP data object is exactly the same ! So what is the difference between binding a data object to a shared variable and to a display element?
Is there a bug in the SVE or am I missing something here?
The host project:
The publisher VI
Hope, someone has an answer.
Regards
Matthias Quade
Solved!
Go to Solution.
Attachments:
AliasTestWrite-RT.vi ‏8 KB
AliasTestConsumer.vi ‏8 KB

Dear Mr. Quade,
thank you for posting at the National Instruments Forum. There is a known issue with the path of the bound variable with LabVIEW 8.6.1
Please download the patch for LabVIEW 8.6.1, it should solve your problem:
http://joule.ni.com/nidu/cds/view/p/id/1255/lang/de
Best regards from Munich
MarianO

Where can I find the "Shared Variable Properties" VI to be used in my program for configuring SV remotely?

I was using the "configure Alarms" and "configure Logging" VIs to design two user interfaces to make use of these VIs when I came across a problem. In both VIs you can enable logging of alarms. So which one is valid? Which one has priority? Then I looked at the "Shared Variable Properties" built into the project explorer. Now I realize that I am spending all of this time redesigning this properties dialog (which also has two options of enabling logging of alarms (on the Alarms tab to the far right side as well as on the Logging tab). So now my question is, how do I access this "Shared Variable Properties" dialog through my program (Note: this would be on a different machine than where the shared variables are set up. The point is to configure shared variables remotely).
Thanks
Matt

Here is a VI I re-created and posted for all. I'm not sure why NI doesn't provide their VI to the developer. The only thing I can't figure out is that when reading in the "Ack Type" into a variable, it generates an error. It will work if you go into "project explorer" and right click on the library with the shared variable and "deploy" but eventually stops working. I have tried using the "undeploy library" and "deploy library" to see if this would be a work around but had no success.
Just pipe the path of the shared variable into the vi.
Mattk
Attachments:
Shared Variable Properties.vi ‏95 KB

Configuring Database for logging to citadel Database using shared variable engine

Hello All,
I have two systems with me here, one with LabVIEW 8.5 and one with LabVIEW 8.6, I'm using Shared Variables in my code and I am Logging to citadel Database. In a PC with LabVIEW 8.5, I am able to Log Data to citadel Database, but with the same code I am not able to Log Data from the PC with LabVIEW 8.6. Both the PC's have Database Installed and the connection with the Database Exists when I test connection with database through control panel. I would Like to know any configurations (in LabVIEW or in code or in Database or in PC) that have to be done for Logging to Database because the PC with LabVIEW 8.6 was added recently and the code was upgraded to 8.6.

It was due to a dll in LabVIEW, a dll named nitaglv.dll
Now I have a issue with Data Logging from the EXE, once the shared variables are deployed programatically from the EXE the Data Logging stops,
can I get any input on this issue..???

Shared variables problem

I have 2 applications runnng in different PC connected to the same network
Both applications are for testing purposes before going on with the real implementation. Written in LV 8.5 and based on Shared Variables.
While everything is fine when those application run on the same PC (in effect, localsystem), nothing seems to work when each is active in the proper PC.
Shared variables seem not to be seen from outside the PCs.
This happens also when I use Variable manager on both machines: I create a variable on PC1, defining it as published. Then I create another variable on the other machine (PC2) and try to bind it to the variable deifned in the PC1. Pressing the Browse button the list of PCs networked to mine appears. Selecting th eone I need (PC1), Variable Manager tries to populate the tree but hangs up. Or, better said, simply does not populate the tree. The ariable Manager still works but the item son the other PC are not seen.
Any suggestion?
Regards
Walter

Hi there,
I'm having a very similar issue. My set up is 2 pc's on the same network, the "server" (date generated on this pc) running LV 8.0 ip#1, the other is running LV 2010 and will only see the data, ip#2.
I have set up two test network shared variables and configured them on the server machine Ip#1 to bind to ip#2. When I run the vi's I see that the shared variables are deployed to the particular machine.
On ip#1 I included a test vi in the project to read data from the ip#1 shared variable, and I see no data. I have other local shared variables working within ip#1, but the network shared variables cannot be read even within the same project.
Any ideas as to why I cannot read the networked shared variable within the same project on the same computer?
Also the link about multiple network-adaptors is dead. I have seen strange issues when configuring the networkd shared variables if I have a VPN sessing going to an outside network on both computers, I will see both the windows computer name and the ip address.
Is there anyway to delete a computer after adding it as a shared variable potential source?
Thanks for any help, there are a couple of questions here.
Jim

Shared variables + timed loops + naming conventions + how to find all

Being almost halloween, thought I'd share some more eerie behavior I've noticed with shared variables.
1st strangeness with timed loops already mentioned here: http://forums.ni.com/ni/board/message?board.id=170&message.id=209475
2nd strangeness: If you have a shared variable that is network-enabled, it is OK to use a "?" in the name (eg, "RT_Simulate?").
However, should you decide to change that variable to single-process, or if you create it that way in the first place, you will get this dandy message from the broken arrow you now have:
"LabVIEW could not generate code for the shared variable. You must open the VI in the project that contains the library where the shared variable resides."
..............whaaa????? Loosely translated, this seems to mean "Don't use a "?" in your single-process variable names."
3rd strangeness: I don't know if this has been mentioned before....
If you have an application that references a network shared variable, and the library has NOT been deployed, the app will hang for some time (approx. 7 seconds! on my machine) before returning with an error. This seems to be the case whether or not the error ins/outs of the variable are wired. This looks bad to me, and I'm not sure what is causing it (some sort of timeout when attempting communication with the SVE I assume). Has anyone else noticed this? It should be easy to reproduce. Any ideas?
I haven't done any bug notifications yet, but will do if there are no positive solutions by next week some time.
-Have a Great Halloween Weekend

WHAVEman,
Currently (as of LabVIEW 8.20) there isn't a way to programmatically interact with the shared variable engine outside of using DSC. If you had DSC you could "hack" a way to determine if a shared variable was deployed.
I think the best way to get around your program hanging is to have an initialize state where you write a dummy value to each variable. If the variable isn't deployed, then you should get an error out of the shared variable. Problem is that there's probably going to be a timeout associated with determining if the shared variable is deployed. But at least you can use the information from your initialize state throughout the rest of your deployed application.
Chris C
Chris Cilino
National Instruments
LabVIEW Product Marketing Manager
Certified LabVIEW Architect

How do I setup shared variables between executables created in sepparate projects

Hello,
I have several sepparate projects with their own respective executable files and I would like to be able for these executable files to all share the same variable (one program controls the value of the variable, while the others read from it).
I got this setup to work on my personal computer (by being able to access variable manager, etc), but I need to deploy these executables on different computers that don't have the labview development program. What steps do I need to do in order for me to be able to put these executables on any computer (I'm assuming I need to setup a path for the shared variable that is always in the same folder, etc)
Thanks
Vlad
Solved!
Go to Solution.

Hi Vlad,
I think this article may answer some of your questions regarding shared variables in deployed applications.
http://zone.ni.com/devzone/cda/tut/p/id/9900
It sounds like you already have your executables built, but this article may answer some questions about deploying them to other machines.
http://zone.ni.com/devzone/cda/tut/p/id/3303
Jeff S.
National Instruments

Front Panel binding of shared variables very slow initialization / start

Hello @ all,
I am using a server running Windows2000 and LV 8 DSC RTS for datalogging. All shared variables are deployed on that server.
I am now facing the problem, that all front panels running on the clients using the network shared variables on the server take very long to sync on startup. First the flags on the controls bind to the shared variables turn red, after up to ten minutes they start to turn green. The panels use up to 40 controls bind to the shared variables.
All firewalls are turned off. I tried to connect the client to the same switch the server is connected to. Same problem. Does anybody have a clue?
Thx for your quick answers.
Carsten

While I can't offer any solution to your problem, I am having a similar issue running LV8.0 and shared variables on my block diagram (no DSC installed).
When using network published shared variables, it takes anywhere from 30 sec to 4 min from the vi start for any updates to be seen. Given enough time, they will all update normally, however this 4 minute time lag is somewhat troublesome.
I have confirmed the issue to be present when running the shared variable engine on windows and RT platforms, with exactly the same results.
In my case, the worst offenders are a couple of double precision arrays (4 elements each). They will normally exhibit similar "spurty" behavior on startup, and eventually work their way up to continuous and normal update rates. Interestingly enough there are no errors generated by the shared variables on the block diagram.

Shared Variable Not Deploying

Similar Messages

Maybe you are looking for