Dsc 8.2.1 cannot write to shared variables error 1950679035

I am getting error 1950679035 ni_tagger_write when I try to write to my shared variables. I recently upgraded from labview 8.2 to 8.2.1. I also upgraded to DSC 8.2.1. During the install, I had to upgrade my computer to SP2 (windows xp), which installed mdac 2.8 sp1 for use with dsc 8.2.1.
I have the windows firewall turned off, I checked with our IT dept and no upgrades were completed overnight (as the program worked yesterday using 8.2). I checked and MAX will get a connection with the fieldpoint unit. Everything is deployed from my machine, currently running under the dev environment.
I have looked at this thread, but I was not able to get anywhere, http://digital.ni.com/public.nsf/websearch/0D7B86F4B4D19A5E86256F9A006EECB1?OpenDocument and here.
Even though I have windows firewall turned off, I added all of the execptions to the windows firewall list.
It appears that the shared variable library is deploying correctly, as the the windows says that it has (when you run a vi). I am progmatically deploying the vi.
I looked at the variable manager and I attached a screenshot below. I am not sure if that means that it did not deploy correctly or not.?? (I was only watching a couple of the variables, I have about 20 total)
thanks
Kenny
Attachments:
variable manager.jpg ‏55 KB

It appears that my problem has been solved. Apparently our network had an internal error for a quick second and my nic did not like it. So after I restarted again (fourth of the morning) it started working now.
Kenny

Similar Messages

Problema di polimorfismo con Read/Write delle Shared variable

Salve,
Cercando di modificare l'esempio di progetto "Shared Variable Client/Server" in un progetto dove sono i diversi client a mandare dati al Server ( ovvero l'esatto contrario di quello che fa )
mi sono inbattuto nel problema illustrato nelle due figure che seguono.
Ovvero, sostituendo "Writable PSP Variable" ad "Readable" nella scheda "Connect"(FIGURA 1) mi da un errore nella scheda "Read/Write" (FIGURA 2), ovviamente anche qui ho sostituito a "Read Variable" un "Write Variable".
Mentre utilizzando il Data Socket funziona, ma non mi sono chiari i vantaggi e gli svantaggi nell'utilizzare quest'approccio.
Qual'è la strada migliore tra Shared Variable e Data Socket per creare un sistema Client/Server così costituito, ovvero con un cospicuo numero di client da servire ( destinato a crescere )che mandano simultaneamente un discreto quantitativo di dati ( circa quelli di una seriale a 115200bps ) ad un server
FIGURA 1
IMMAGINE 2

Translation
Hi,
Trying
to modify the sample project "Shared Variable Client / Server" in a
project where different clients to send data to the server (ie the
exact opposite of what it does)
I untapped in the problem illustrated in the two figures that follow.
That
is, replacing "Writable PSP Variable" to "readable" in "Connect"
(Figure 1) gives me an error in "Read / Write" (FIGURE 2), and of
course here I replaced "Read Variable" a "Write Variable.
While using the Data Socket works, but I have clear advantages and disadvantages of using this approach.
What
is the best route between Shared Variable and Data Socket to create a
client / server system so constituted, or with a large number of
customers to serve (to grow) that simultaneously sends a fair amount of
data (approximately those of a serial to 115200bps) to a server
The images points to a gmail location. It is not properly attached.

Shared variable error 1967362044

Hi everybody,
I am using shared variable in one of my project to communicate between RT program and my PC program. FOr very first time I run the program in my PC. I am facing the error 1967362044. Can anyone tell the reason for this error and solution to get rid of this error. I have also searched in ni.com but I didnt find any solution regarding this. So, I request you to provide me a solution.
Thanks and Regards
Giridhar
Idesign

Hi Giridhar
From what I've seen this error can occur if the connection between computer and target was suddenly lost while the shared varible was written to. In that case rebuild the shared Variable.
Another instance were this can occur is if the project was developed on a computer with a localized version (i.e. non-english) version of Windows AND LabVIEW. Is that the case for you?
Best Regards
David
NISW
Message Edited by DavidEk on 07-31-2009 08:25 AM

String to Shared Variable error

Hi all
I created a small example.
Why is in Shared Variable "Da 5" - "a" not upper ?
Regards.
Iskander
Attachments:
Examle.vi ‏8 KB

Hi Cole R.
Thanks for attention.
I am using LV-2010 and Win XP.
I have the same ERROR "Da5" in SVE. (See example) .
Although I created in project "DA5"
Picture is added.
Best regards
Iskander.
Attachments:
SVE.png ‏9 KB

Shared variable error

HI,
I get this error,
LabVIEW: (Hex 0x8BBB0005) Unable to locate variable in the Shared Variable Engine. Deployment of this variable may have failed.
This error or warning occurred while reading the following Shared Variable:
\\RT Single-Board RIO\temp1_lib\Temperature1
\\192.168.1.140\temp1_lib\Temperature1
What do I need to do?

Are you deploying the variable? Right click on the library>deploy.
PaulG.
"I enjoy talking to you. Your mind appeals to me. It resembles my own mind except that you happen to be insane." -- George Orwell

LABVIEW 2012 - shared variable error during programming of NI CRIO 9023 and TPC 2212

HELLO,
i am using CRIO 9023 with TPC 2212 and LV 2012. I want to develop a stand alone app which has a front panel on TPC. at first i am building a simple app with two controls variables, one is a sliding bar on TPC Vi and the other one is the while loop variable "i" on CRIO VI. i used shared variables.
first i creat shared variable on CRIO side and access this on TPC Vi. I COMPILE both Vi,s and they are working fine. But when i created the slide bar control in TPC VI, compiled and deploy the TPC Vi, it get deployed in TPC. But when i start compiling the CRIO VI an error mesage occured as follows;
I have tried every option to best of my understanding like formating crio then installing all softwares including Network variable engine etc. i also go in properties of the executable file of TPC Vi and go in properties-shared variable- then check the "deploy variable in application" option . below is image displayed.
I am in despirate need for solving this problem as i have to develop the final app for testing soon. can some one help me regrarding this.
REGARDS

I would not recommend using shared variable engine. It is supposed to make things easier, but in fact, you will spend more time troubleshooting why it is not working than you will actually coding an alternative solution.
Try the Simple TCP Messaging instead.
http://zone.ni.com/devzone/cda/epd/p/id/2739
Machine Vision, Robotics, Embedded Systems, Surveillance
www.movimed.com - Custom Imaging Solutions

URGENT DSC: I can write to shared variables but CANNOT read them?

hello everyone,
I'm using DSC to communicate with a DELTA DVP28SV PLC. I managed writing to a coil to to turn a fan on, and I also wrote to a register.
However, when i tried to read the coil (same coil i just turned on) or when i tried to read a register that im very sure has values (the register where i configure the modbus parameters), it would return ZERO, even when i tried to read the register that i just wrote into the reply was zero (I am sure that writing to the register was successful because i made the specific value that i wrote to the register a condition to turning a light on).
So, anyone knows why this could happen?? the Registers are Read/Write. I thought it could be that the scan time in the PLC is too short so i added delays but anything i read still gives zero back. ideas? can anyone help me with this?
here's the PLCs application manual in case it matters : http://www.delta.com.tw/product/em/control/plc/download/manual/DVP-PLC-Program_O_EN_20120416.pdf
Solved!
Go to Solution.

here: capture.png shows the results i get
Attachments:
diagram.PNG ‏32 KB
Capture.PNG ‏10 KB

Cannot access a shared folder Error code: 0x80070035

Hello Experts,
I have been working on this issue for like three days without a solution. I am truly desperate.
My company just purchased a new Cloud Server that we will use as our development environment for a software project. In order for all the developers (which are all over the US) to access the development environment, we need to have a few shared folders on
that new server.
As soon as we got the server I did the following:
1) Installed Active Directory
2) Created a directory and made it shared - yes IT IS shared.
3) I created a few new users on the new active directory domain
THE PROBLEM:
I can't access the shared directory.
Other developers have been successful in connecting to the shared folder (so the share is working) - all except me.
when I open explorer and type \\IPADDRESS\SHAREDFOLDER instead I get this error (I am not even asked for credentials)
Network Error
Windows cannot access \\IPADDRESS\SHAREDFOLDER
Error code: 0x80070035
The network path was not found.
Things I have already tried:
a) Enable NetBIOS over TCP/IP - on all adapters - still did not help
b) Disable IPv6 - I am not sure how to check if it truly disabled
c) Turned off all firewalls - did not help
d) Mapping a Drive using different credentials - I just get asked for credentials over and over
e) Ping - yes I can see the server
f) My credentials are correct because I can Remote Desktop with the credentials with no problem ( I am administrator)
My Machine:
Brand New Asus G Series
Windows 7 Home Edition
Any ideas?
Sorcerdon

In my case it was that the OU that my system was in did not have firewall rules for network file and printer sharing enabled. I enabled all of the rules for Domain policy and that fixed it.
I noticed a lot of comments about turning off the firewall not working. I can't be 100% sure, but in my experience with Server 2008 and Windows 7, if you want to configure a service that uses the network the base filter engine and the firewall HAVE to be
turned on while you configure. You can turn the firewall off after configuration, but they have to be active during configuration.
Good luck!

Shared Variable Error -1950679023 (Connection to Server Disconnected)

There seem to be several questions but few answers regarding this error, which appears to be related to the NIVE (National Instruments Variable Engine) service dropping out.
One solution:
I noticed:
When I opened DSM (NI Distributed System Manager), I saw processes listed that I know I had manually removed previously from DSM.
NIVE service timed out when I manually tried stop it.
So, I:
Closed out of everything, re-opened DSM, and removed all processes (except for "System", of course)
Restarted the PC
Verified that DSM had no processes listed
Ran my software (which programmatically deploys libraries)
Error -1950679023 is gone!
Apparently something was clogged up with my deployed processes (didn't check whether Variable Manager also displayed the issue), which was causing the NIVE (i.e. SVE, "tagger") to hiccup.
Certified LabVIEW Architect
Wait for Flag / Set Flag
Separate Views from Implementation for Strict Type Defs

There seem to be several questions but few answers regarding this error, which appears to be related to the NIVE (National Instruments Variable Engine) service dropping out.
One solution:
I noticed:
When I opened DSM (NI Distributed System Manager), I saw processes listed that I know I had manually removed previously from DSM.
NIVE service timed out when I manually tried stop it.
So, I:
Closed out of everything, re-opened DSM, and removed all processes (except for "System", of course)
Restarted the PC
Verified that DSM had no processes listed
Ran my software (which programmatically deploys libraries)
Error -1950679023 is gone!
Apparently something was clogged up with my deployed processes (didn't check whether Variable Manager also displayed the issue), which was causing the NIVE (i.e. SVE, "tagger") to hiccup.
Certified LabVIEW Architect
Wait for Flag / Set Flag
Separate Views from Implementation for Strict Type Defs

Shared variable error 0x8ABC0011

I was getting this error on a simple test VI that I made. I am also getting this error when running the Heat Exchanger example. All of the controls and indicators have the red status light and this error. I am using 8.2.1, but I know I ran this example without any problems using 8.2. Any ideas what could be wrong?

I got it. Once I followed the instructions in the upgrade readme file about the database differences, it worked.

Modbus Ethernet read and write to a Eurotherm 6180XIO Modbus server using LV8.2 shared variables

I am having EXTREME difficulty trying to establish communications with a Modbus device using LV8.2 shared variables. The device is a Eurotherm 6180XIO Datalogger configured as a Modbus master. The PC and a cFP-1804 are slaves. All IP addresses are set correctly. This approach using shared variables would seem simple, but I can't find any examples or proper guidance on how to get it working. I am trying to avoid having to mess around with TCP/IP, OPC, or any other old-fashioned method.
I have read many threads on related topics but none directly apply to this situation. I have created a library containing a Modbus I/O server and shared variables bound to read and write holding registers. I have followed all recommended tips for creating such variables but I can neither read or write data. All data types are U16 due to Modbus protocol limitations. I have also applied the LV x10 factor in the most significant digit in the register offset (6 digits instead of 5).
I have a cFP-1804 on the same network which reads into the datalogger OK. The registers I use are 31000 (for CH0 on module 0, 31002 for CH1, etc) and the data can be read as FLOAT32. I have updated the firmwate on the 1804 to the latest level. I cannot even get shared variables to read SGL values. Using registers 301001 for CH0 and 301002 for CH1 I can only read U16 values, and not a 2-word SGL.
Third party Modbus simulation software is able to write to and read from registers very easily, but not LabVIEW.
Some questions are:
- do I use a Modbus master or slave as an I/O server in the library as a target for binding the shared variables?
- is there some other wierd translation in register offsets between LabVIEW and traditional Modbus?
- is this actually possible using shared variables or am I wasting my time?

Sending the whole 60-character string using a string or array would be the most efficient. I have tried both methods, and these only cause the datalogger to flag a message log but no text is displayed.
For a string variable, I have used the following binding "My Computer\Modbus Test.lvlib\ModbusServer6180\442305", where ModbusServer6180 is a Modbus I/O server configured with the logger IP address, and 42304 is the register offset at the start of the text block in the logger. I need to write to 30 consecutive registers starting with this one. I am not using buffering and have not enabled single writer.
Can anyone confirm whether this method should work in 8.2?
Does the string need a special termination character?

LV7.1 DSC tag engine VS LV8.6 DSC shared variables

I'm currently running LV7.1 with DSC and RT. To handle communications and logging RT variables I'm using the init / read / write publish.vi's on the RT side and datasockets on the HMI side (Windows XP). This has worked out great - new tags can be programmatically created in real time with the publsih vi's and then I go to the the .scf file and use the tag configuration wizard to add them to my scf file and handle data logging. This worked very well - the wizard would organize all of the memory tags into folders by block name used by the init publish vi. I could also select entire groups of tags and add hundreds at a time to the .scf file. Hardware Tag also worked in a similar fashion, organizing tags by controller and module folders. Now - looking at LV8.6.I found I can still use the init / read / publish vi's on the RT side - great. However there is not tag configuration editor as in LV7.1 to let me add large numbers of tags through a wizard. The closest thing I've found is to create a library to represent each block name from the RT init publish.vi then use "create bound variables" option under the library to bind the new shared variables to the RT memory tags. I can browse to the tags on the controller by network items, but when I add them it doesn't bring the block name of the tag as it did in 7.1, only the item name. I use a lot of PID loops that share the same tag names (i.e.: P,I,D, mode, output), so not including the block name represents an organizational problem. The problem with this is, it's very labor intensive compared to the wizard in LV7.1 DSC, especially talking about creating systems with thousands of RT memory tags. Also, there is a similar problem with hardware channels (I'm using compact FieldPoint). To log channels via DSC do I have to create a shared variable for each channel to access the DSC logging capabilities? Again how do I add all of the hardware channels in some organized fashion? I hope I'm missing some tool that is an analog to the tag configuration wizard to bring in these channels and organize them. Any help or suggestions would be appreciated. Thanks,Brad

Hi lb,
We're glad to hear you're upgrading, but because there was a fundamental change in architecture since version 7.1, there will likely be some portions that require a rewrite.
The RTE needs to match the version of DSC your using. Also, the tag architecture used in 7.1 is not compatible with the shared variable approach used in 2012. Please see the KnowledgeBase article Do I Need to Upgrade My DSC Runtime Version After Upgrading the LabVIEW DSC Module?
You will also need to convert from tags to shared variables. The change from tags to shared variables took place in the transition to LabVIEW 8. The KnowledgeBase Migrating from LabVIEW DSC 7.1 to 8.0 gives the process for changing from tags to shared variables.
Hope this gets you headed in the right direction. Let us know if you have more questions.
Thanks,
Dave C.
Applications Engineer
National Instruments

Upgrade to 8.5.1 on all computers using shared variables?

Hello,
We are currently using DSC 8.5 and hosting the shared variable engine on one 'server' computer with other computers subscribing to network shared variables. Some of the computers are Windows XP and others are RT.
When we upgrade to DSC 8.5.1 can we just upgrade the 'server' computer and leave all other computers at 8.5 or do we need to upgrade all systems to 8.5.1 at the same time? Will computers running 8.5 be able to read/write network shared variables hosted on the DSC 8.5.1 system? Is such a progressive upgrade not advised? Thank you in advance.
- Chris White
ThinkG Consulting LLC

Hi Chris,
The variables pass through the Shared Variable Engine on your server before they are read by other subscribers. Therefore, you do not have to upgrade the DSC on all your subscribers. I hope that answers your question. For further reference on how network pulished shared variables operate as well as the role of the SVE, please refer to this link.
Ipshita C.
National Instruments
Applications Engineer

How to use shared variables with native c programs

Hello
What is the way to use shared variables with native c programs?
I have a c/c++ program that uses the NIDAQmx C-API to perform measurements. Now I want to communicate to a LabVIEW program via shared variables.
Is there a C-API for shared variables as there is for the NIDAQmx functionality? Where can I find further documentation? The document "Using the LabVIEW Shared Variable" mentions that one "can read and write to shared variables in ANSI C", but there are no hints about how and where to look.
Thanks in Advance

Hi user42,
with CVI 8.0, you cannot create or configure shared variables. However, you can read or write to an already configured LabVIEW 8.x shared variable from CVI using the DataSocket API.
In order to do this you need to have and DataSocket 4.3 or higher installed.
Here's a forum post about using the DataSocket functions a LabVIEW Shared Variables:
http://forums.ni.com/ni/board/message?board.id=180&message.id=24569&requireLogin=False
With CVI 8.1 and Measurement Studio 8.1 it's possible to use Shared Variables via the Network Varaiable Library (check out the end of the "Network-Published Shared Variable" section within the "Using the LabVIEW Shared Variable" documentation and the following link).
Datasocket with LabWindows/CVI and LabVIEW Real-Time:
http://digital.ni.com/public.nsf/allkb/CC4343488413A2F586256E6200099638?OpenDocument
Daniel
NIG

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.

Dsc 8.2.1 cannot write to shared variables error 1950679035

Similar Messages

Maybe you are looking for