Shared Variable programatic access error -1967362038

I am trying to read/write about 300 tags from a AB ControlLogix 5561 processor from Labview 2011 on windows XP SP2 through RSLinx Classic OEM OPC Server.
At first, I tried to do everything through front panel data binding through Datasocket, but I've seen that it becomes slow/unreliable when the bound control count reaches beyond 100 tags or so. Wrong values are read/written, some controls just won't bind intially or lose thier binding...it's really odd. So, I've put all of my faith in Labview's DSC module to solve all of my problems.
I installed it on a development system, played around with the programmatic access VI's using the NI's test OPC server and everything worked great. It really looked like the answer to all of my problems but upon installing it on the target system I can't get it to work the same way!
I've created a library of simply 3 bound variables to the PLC through an IO server pointing at the local instance of RSLinx. I am able to browse the PLC tag structure, so at least the link through RSLinx is working to some extent.
Fairly often, when running the seach variable container vi on that library, I get error -1967362038 with explaination "IAK_SHARED". When this error occurs, the same error shows up in the distributed system manager and the shared variables can no longer be read. I can't seem to pin down a pattern but happens every few minutes or roughly ever 3rd or 4th time I start the vi. When it happens, the only way I've found to get things working again is to undeploy and redeploy the library, while watching it in the distributed system manager, then continually loop the search variable container VI for a few seconds and eventually, the variable comes back to life.
Does this sound like an issue with RSLinx? One of the previous posts related to this error mentioned that it may be due to some corrupt files in MAX?
Other network published shared variables (non-OPC) seem to be OK so I think this is a problem related to the DSC module.
I rebooted twice immediately after the DSC installation.
I have uninstalled SQL Server 2005 and the DSC module and reinstalled both. Twice.
What could be causing this error?
Would it be worth while to port over to the NI OPC Server?

Hi pjrose,
First, I notice that this post is pretty similar to a service request that one of my colleagues has been working on. Are you working with another NI Applications Engineer on this issue?
That said, the issue could very well be related to the DSC module. I doubt that the error is a MAX corruption error, at least at present. One thing that would be worth checking would be the connections on your network. Additionally, what are the types of variables that you are accessing, and how specifically are you coding the access to them? If you could post an example of how you're accessing them, that would be helpful.
Best,
Dan N
Applications Engineer
National Instruments

Similar Messages

Can not read shared variable on cRIO, error -1950678968 nitaglv

Hardware setup:
Laptop
Laptop connected via USB to a frammer garber.
Laptop IP: 192.168.0.2
NI vision calculating a diameter and setting a network varaible
cRIO
cRIO connected to the laptop
cRIO IP: 192.168.0.1
Project has the shared variable in the cRIO library
NI vision writes to the variable on the cRIO. I can see the variable properly updating in system manager on the cRIO. I can also run a VI in my computer that shows the variable properly updating. But...... When I read the variable with a VI running on the cRIO, I get the folowing error and the variable never updates:
Error -1950678968 occurred at Shared Variable in Main.vi
Possible reason(s):
LabVIEW: Failed to load nitaglv, which is required for Network-Published Shared Variables.
This error or warning occurred while reading the following Shared Variable:
\\NI-cRIO-OASIS\cRIOVariableLib\BubbleDiameterFromVision
\\192.168.0.1\cRIOVariableLib\BubbleDiameterFromVision
(I do not get any errors at deloyment)
So everything (NI Vision, a VI deployed on the laptop, NI Distributed System Manager) can see the variable on the cRIO being updated by the NI Vision.... Except for a VI running on the cRIO.
I have verified that I have Network Variable Engine and Variable Client Support for RT installed on the cRIO. I have tried reinstalling all s/w on the cRIO. Tried rebooting all. And talked in a nice, positive, reassuring voice to the chassis.

Hi!
I just had the same issue with my cRIO 9073 using NI RIO 3.6.0.
The problem is not caused by a corrupted project, but the improper installation of the OS on the target. There is nothing you can do using the SW installation wizard in MAX, as it does not matter if you intall a full RIO SW, minimal or custom.
You have to install the full install or a custom one with Shared Variable support. Then you have to FTP to the cRIO, and manually edit the "ni-rt.ini" file located in the root of the controller.
Make sure you have a line in the "[MODULE VERSIONS]" section which shows the version of the nitaglv.out file. (The problem is caused because this dll is not loaded when you try to access a SV) Mine looks like nitaglv.out=6.3
Then you have to insert "nitaglv.out;" without quotes to the [LVRT] section's StartupDLLs key's value. I did it after the taggerrt.out name. So my key entry now looks like this:
[LVRT]
StartupDLLs=nisysapirpc.out;NiViSrvr.out;NiRioRpc.out;taggerrt.out;nitaglv.out;sysstatepublisher.out;
memoryChecking=False
LABVIEWRTDir=/c/ni-rt/system
PATH=/c/ni-rt/system/;/c/ni-rt/;
CDIntervalTicks=55
WebServer.Enabled=FALSE
RTTarget.VIPath=/c/ni-rt/startup
RTTarget.IPAccess=+*
RTEnetRcvMode=2
RTCPULoadMonitoringEnabled=True
RTTarget.ApplicationPath=/c/ni-rt/startup/startup.rtexe
server.tcp.access="+*"
RTTarget.LaunchAppAtBoot=True
RTTarget.EnableFileSharing=True
server.tcp.serviceName="Main Application Instance/VI Server"
After you are done with the editing, you have to save the file, and overwrite the original one. You have to reboot the controller for the modification to take effect.
After this you will be able to host your variables on the cRIO and also read/write them from the application running on that same target.
I hope this will help for you too.
Regards,
Peter

Slow performance to read/write shared variables programatically

We are using datasocket read and write functions to read and write shared variables programatically (in the same machine) but we only achieve a performance of aprox. 200 reads/writes per second. We are using Labview 8.6 with DSC.
Is possible to get better results? That performance is normal?
Any help would be appreciated. Thank you in advance.

Hi MMCDAT,
I think this value can
be normal as you can see in this link:
http://zone.ni.com/devzone/cda/tut/p/id/5037
As you can see, the
limit for datasocket depends on your Ethernet limitations, even if you as using
it just in one PC:
http://digital.ni.com/public.nsf/websearch/6AC9E65734E53F9A8625672400637ECC?OpenDocument
You can improve the
performance changing the update mode or Vis configurations:
http://digital.ni.com/public.nsf/allkb/F8F7DE98856B50588625672400648045?OpenDocument
http://digital.ni.com/public.nsf/allkb/2D9C6D73A160537986256B290076456E?OpenDocument

DSC: Importing Shared Variables results in error -1950679010

This post is more of an "FYI" rather than a question. I am using LV DSC 8.2.
ASIDE: I ran into this problem because I was trying to solve a related problem with Deploy Library.vi (I had dependant libraries that deployed manually, but not programmatically). Eventually, I found the answer in http://digital.ni.com/public.nsf/allkb/8EF71E1DDDC36C908625716900594B50 (not a very satisfactory answer however, IMHO).
During my solution search, another hint was provided with http://forums.ni.com/ni/board/message?board.id=170&message.id=177268&requireLogin=False which hints that using a "Network" defined SV, as opposed to a "Project" defined SV, could help. Then I discovered the difference between NetworkrojectPath and Network:URL in the SV property definition. Then I realized that NetworkrojectBinding is exposed in the Import fields (using the Multiple Variable Editor to do the importing of course), and this gave me the idea of being able to define a Network SV using the Import function.
Unfortunately, it does not work. In the csv file I set NetworkrojectBinding to FALSE, Network:UseBinding to TRUE and provide a valid Network SV path, but this results in error -1950679010: "Shared variable is bound but path or URL is not specified", which occurs when trying to save the LVLIB. It would be nice to know why this doesn't work, as I think it should. I think it is a problem with the SV import mechanism.
David Moerman
TruView Technology Integration Ltd.

Yes, you can do this programatically. I've attached a small chunk of example code (LV 8.5) that creates just 1 variable, as well as an image of it in case you are using an earlier version of LV. If you want to create multiple variables for the same library just put the "AddSharedVariableToLibrary" in a loop, of course.
David Moerman
Attachments:
Create Library and SV.PNG ‏48 KB
Create Library of SVs - BASIC.vi ‏24 KB

Shared Variable Read Access Denied from Fieldpoint

I've posted this in the Fieldpoint forum, but I think I may get more responses here:
I've created a shared variable bound to a single analog input (AI) channel on my fieldpoint 2120. When I attempt to read from this variable in my VI, I get the error: "Read access is denied to the shared variable."
BUT, when I view the variable in the shared variable manager, the analog signal is updating correctly and continuously.
Anyone know what I may be doing wrong?
Thanks!

Link to post in Fieldpoint forum.

Change/ scale shared variable programatically

hi!
well, i am creating lot of shared variables using labview, but my question is, have i got any item or something to scale them or, change the properties of the shared variables i created??
for example, rate max/min, color.....
have you got any idea?

Hi kazak,
see this link:-
http://zone.ni.com/reference/en-XX/help/371618G-01/lvdscconcepts/chang_svpro_prog/
Thanks as kudos only

Shared Variable Initial value not licenced error with cRIO

Hello Everyone,
I've a project that will be deploed on cRIO. This project was created on a different machine and didn't have any error regarding the shared variables. when I transfered the project to the computer connected to the cRIO, I have this error with all shared variable. The error message says that:
1. Initial Values: Not Licenced or can't be edited outside of LabVIEW.
2. Logging: Not Licenced or can't be edited outside of LabVIEW.
attached are two images for the error i have.
Can I have help with this issue?
Thanks in advance
Attachments:
1.png ‏134 KB
2.png ‏142 KB

Good day,
Sounds like you are using the DSC module features on your code and you forgot to activate the runtime system on that machine. If you have access to the NI License Manager, please check the status of the license.
We need an active license for the second message but, for the first one you can try to program your own initial values for all of your network-published shared variables by initializing whenever the PC is started. During the initialization portion of your code, you can just write a constant value to the shared variables so the values are the same initial values every time it is run.
Regards,
Alejandro | Academic Program 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

Creating and loading 4000 shared variables

I need some help laying out the design of this system. The data is coming over reflective memory. I've written a dll and a simple server to do the interface between the reflective memory and shared variable engine. Everything seems to be working. The problem I am having is with scaling the application up to handle approximately 4000 variables. I have a spreadsheet to manage the reflective memory allocation and can use it to import the shared variable definitions with the names from the system that is writing the data.
I am having trouble deciding on the best way to proceed. I would like to read a buffer from reflective memory instead of reading 4000 times. I also would like the server to read in a file that defines the association between the shared variable and reflective memory address. The problem I am having is getting the data out of an array into each of the shared variables. I don't see a way to load the value of a shared variable using the property node (so that I can do this inside a loop). I also can't setup an alias that would access an array element. I don't want to manually create 4000 variables.
Any ideas would be appreciated. Thanks.

I have never had to resort to creating Shared variables programatically so I will leave that for others.
I would cheat.
In LV 7.1 DSC i could import my tag config from a csv file. After importing and saving in LV 7.1 I could let LV create the SV's when the code is updated.
THat all assumes I will only have to do that one.
I have used the interupts fired when SCRAMNet locations update to "steer" the value to appropriate code which could then in turn update the SV using a datasocket write since I can compose the URL for the SV dynamically.
Just sharing ideas,
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Programatic Access to network published shared variable - Knowlege Nugget

Wanted to Share a coding problem I have just resolved:
I have been trying to debug the code above.
It worked for one device and not the other (Identical devices: DevA,DevB)
It has been throwing an error, unable to access variable.
I resolved the problem by changing by changing the timeout to something > zero
Hope this helps future travellers
This seems onlt yo be a problem during the first connection to the variable,
Subsequent reads don't seem to need it.
It is almost as though it needs time to troll through the project shared variable database to finde the reference the first time through.
iTm - Senior Systems Engineer
uses: LABVIEW 2012 SP1 x86 on Windows 7 x64. cFP, cRIO, PXI-RT

Ben wrote:
Since I don't use shared varibales I have to ask...
Is there a timestamp returned that reveals the state of the variable?
Ben
The timestamp is only available on the reads. It returns the timestamp of when the variable was written to.
One more thing to watch out for (we recently got bit by this). The NPSV is actually written to a buffer (8kB?). The variable is published either when the buffer is filled or 10ms has passed. There is a command to flush the buffer to avoid this 10ms delay.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Error -1950678991 saving LV8.2 library of shared variables

I used to be able to programmatically save my library of shared variables using "ProcessToLib.vi" (set to Process mode) after changing properties of some or all variables. Now, and I don't know what has changed, I get this error:
Error -1950678991 occurred at property node (arg 1) in NI_Variable.lvlib: SetRawCluster.vi -> PRC_SVsToLib.vi -> PRC_DumpProcess.vi -> ProcessToLib.vi.
The explanation suggests that an Engineering Full Scale is the same as an Engineering Zero Scale value, but I have checked all variables that use scaling (not all do) and I can't find any such fault. Since these low-level VIs have protected diagrams, I can't trace the source of the error. I have tried the same thing on other libraries and they work fine.
I have attached my library for anyone to verify or duplicate the problem and maybe find out what is causing this error.
I have recently installed the DSC patch, but this should not be related to the problem.
Thanks,
Mike
UK
Attachments:
Krystallon Variables.lvlib ‏142 KB

Hi Mike,
I think something has become corrupted in your library. When getting the names of all the shared programatically I get multiple entries for a couple of the X-GPS variables. I deleted all the X-GPS variables and WS-116 and it saves fine. I think you might need to delete and recreate these variables.
Regards
Jon B
Applications Engineer
NI UK & Ireland

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.

RT cRIO: Shared Variable Engine Errors

This is an app written in LV2011 running on a cRIO-9076 (Scan mode), with the August release of software installed on it.
I have gown to great lengths to try an optomize my code, I have reached an impasse. The VERY FIRST TIME I run the code on the target (be it via a self-starting EXE or targeting from my Windows development machine I am able to read and write to several shared variables, but then when I access them again (possibly when I am starting a couple timed loops and the processor is very high) I get this:
Error -1950679023 occurred at Shared Variable in targetIdleLoop.vi->ZDAQ_cRIO_Target_Main.vi
Possible reason(s):
LabVIEW: (Hex 0x8BBB0011) The connection to the server was disconnected.
This error or warning occurred while writing the following Shared Variable:\\ZeeAero-RIO1\variables - network - RT (separate)\RTStatus\\10.10.10.10\variables - network - RT (separate)\RTStatus
If I go back to the Dev machine and restart the code, I don't get this error; it only happens after a reboot.
BUT on this second run (or subsequent VI starts), when we get to that same point, a client priogram running on Windows and reading a network variable successfully suddenly gets:
LabVIEW: -1950679035 (Hex 0x8BBB0005) Unable to locate variable in the Shared Variable Engine. Deployment of this variable may have failed.
Which lasts a minute or so, then goes away. The code is made to loop, and when it loops back through this point there are no errors at all.
So, to recap:
1st Run after reeboot, 1st loop :Error on Target (0x8BBB0011), connection to server disconnected
Subsequent Runs, 1st loop: Error on Windows Client (0x8BBB0005) Unable to locate variable in the Shared Variable Engine. Deployment of this variable may have failed.
Subsequent Runs, 2nd+ loop: No error
Here is a link to a screenshot of the installed SW on the Target:
EDIT: I should mention that there are three loops running in parallel on this app; 1 is a Timed-loop (at the moment) set to a period of 10ms with 100 priority, #2 is also a timed loop and is set to 3ms with priority = 50 and the third is a WHILE loop with a 50ms wait. The error occurs during the WHILE init phase, which happens once per run, not repeatedly.
Solved!
Go to Solution.

This is killing me. It's obviously something to do with when the Timed loops start AND when I access the network variables.
See the screenshot below.
Note that I read and write to several network variables in Subroutines to the left of this screenshot at startup. The starting of the timed loops causes the issue with the shared variables. (also note that the periods are set to 100ms and 99ms in my testing after the initial 1st loop.
Now look at the Wait at the bottom set to 10 seconds. In this case, it will work. There is no error at breakpoint 37 if I wait around 10s. If I DON'T wait the 10 seconds, there is an error after the check on the BOOL "stop - Network" variable that NEVER GOES AWAY. If I look at the CPU monitor, there is an initial bump in the cpu when starting the loops, and then it drops to about 15%. But if I don't have that 10s wait, there is ERR 0x8BBB0011 and the CPU spikes to 75% every 5 seconds and it never goes away.
And that's only the 1st loop after reboot. The 10s makes this work, but I still have an issue with it once I start doing individual runs (loops).

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.

Can't open/access Shared Variable Properties Dalog Box

I've just upgraded to LV 8.6 from 8.5. Now I can't open up the Shared Variable Properties Dialog Box. In the Project Explorer, I expand the shared variable library, select the shared variable, right-click on it to get the pop-up menu, select Properties, nothing happens. The same is true when I right-click on the shared variable library or My Computer and select New>>Variable.
On another computer that I upgraded to LV 8.6, I can do the same things and get the dialog box, albeit it looks different in 8.6 than it did in 8.5.
There were no errors reported in upgrading these computers. Any ideas as to what is wrong?

I've tried re-installing LV 8.6 from the DVDs sent to me. I get the following errors:
Error 1335. the cabinet file 'mib.cab' required for this installation is corrupt and cannot be used. This could indicate a network error , an error reading from the CD-ROM, or a problem with this package. - I responded with 'ignore'
The NI Assistant Framework LabVIEW Code Generator 8.5 installaion has failed with the following error.
Internal Error 2350.
Continue? - I responded with 'yes'
LabView installs but I still can't get access to the dialog box.

Shared Variable programatic access error -1967362038

Similar Messages

Maybe you are looking for