Hibernation problem due to NI variable engine

Hello,
I posted a problem some month ago that discribed a problem with hibernation since I'd installed LabView8.
The proble is still there. I hibernate my laptop and the longer I wait for waking up the machine again the longer it takes to wake up.
I found out that after I stopped the service "NI variable engine" everything is fine again.
I don't have DSC installed. So it's not the keyboard driver of DSC.
Regards.
Ronny

Hi Ronny,
We haven't heard from you in a little while, so I was wondering if
you're still encountering the same issue. One suggestion that
came up here was that if the shared variable engine service appears to
be causing the delay, we might just be seeing a large number of
libraries deployed. To clean out the variable engine, you can
open the Variable Manager from within LabVIEW by selecting
Tools>>Shared Variable>>Variable Manager. Once this
loads, right-click on Local System and select Remove All
Processes. This will undeploy and remove all shared variable
libraries and will require you to close and restart any running LabVIEW
projects. It may be the case that many unused libraries are still
being deployed, which can potentially drag down your system
performance. Give this a try and let us know if it helps.
Cheers,
Matt Pollock
National Instruments

Similar Messages

Error with the Shared Variable Engine

Hi,
I have a problem with the Shared Variable Engine,
A .doc File is attached to this message, decribing the problem with pictures.
I will be glad if anyone can help me.
Sincerely yours
Amitai Abramson
Attachments:
Question.doc ‏819 KB

Hi Amitai,
Good afternoon and I hope your well.
A member of the team from NI Israel contacted me regarding this post.
I want to provide you with extra details on how to resolve your issue - i.e. Repair (Or Re-install) the Shared Variable Engine.
If you use the MsiBlast Tool it will populate a list of all MSI NI Installers. One of these will be NI Variable Engine. On the right-hand side you can the click 'Repair'. I would also Repair the engine support for the versions of LabVIEW you have installed. Please see attachments for MsiBlast and a screenshoot of the MSIBlast screen.
If this doesn't work I would recommend re-installing LabVIEW using the following guide, which I posted on this forum. (second post by me).
Please let me know how you get on,
Kind Regards,
James.
Message Edited by Hillman on 12-03-2008 12:19 PM
Message Edited by Hillman on 12-03-2008 12:19 PM
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!
Attachments:
Repair Shared Variable Engine.JPG ‏97 KB
msiBlast.zip ‏110 KB

Shared Variable Engine not always started

I'm experiencing an intermittent problem with the LabVIEW variable engine. The National Instruments Variable Engine service is configured to start automatically with Windows but that doesn't seem to always be the case. Every now and then I'll load my application only to find red LED indicators on all of the controls accessing my shared variables. I'll bring up the variable manager and stop/start the service, restart my application and then they're all green LEDs and everything works. Any idea what might be causing this?
Thanks,
- Kevin Handy

Hi Kevin. I don't know what causes the problem, but I have seen it on our systems as well.
Our solution was to have our application stop and then start the variable engine every time
it launches. Stopping might not be ok for you depending on how your applications are
architected, but for us it is fine.
We use two System Exec.vi calls, with the following strings:
net stop "national instruments variable engine"
net start "national instruments variable engine"
Haven't had any instances of the application coming up w/o the variable engine since
we added this initialization step.
Matt

Shared variable engine memory problem

Hello,
I have a lot of problems with DSC 8. The server that worked very well in DSC 7, in DSC 8 is creating a lot of problems starting with memory leaks in tagsrv process. I have over 5000 shared variables and when I publish them the tagsrv is around 90Mb of memory. After approx. 30 min is around 130Mb and so on until the computer becomes useless. If I restart the computer the process is the same, even if I don't start the VI that updates the shared variables. I tried to uncheck different things in the variables definition like: no alarming, no buffering, no scaling, with no improvement.
Is there a way to undeploy the shared variables or processes manually, not from the labview project, or Variable Manager. To undeploy the mentioned library with the Variable Manager takes more that an hour (just to enumerate all the shared variables).
Any suggestion is welcomed,
cosmin

cosmin,
I have several thoughts for you. First, I recommend
splitting up
your 5000 variable library into a set of smaller libraries. In
contrast
with the LabVIEW DSC 7 engine, the LabVIEW 8 Shared Variable Engine is
optimized for multiple smaller libraries. I would recommend
having at
most about 1000 variables per library. You'll see some different
recommendations from different people at NI, but in my personal
experience I
think 1000 is about as many Shared Variables that can be easily managed
at
once. For your case this would mean having 1000 variables in 5
different
libraries. --Splitting up your library gives you the added
benefit of being able to
undeploy/disable individual libraries without affecting the other
libraries. Unfortunately, the SCF migration tool will not do this
for you manually so it may take a little time to get everything
organized.
Your comment about ever-increasing memory usage is
concerning. Do
you see this while deploying your library, or while writing
values? If
you write to values very fast (like in an untimed loop) for an extended
period
of time memory usage will increase as the variable buffers
increase.
Please elaborate more on this topic and let me know what happens if you
separate your variables into multiple libraries. I was not able
to reproduce this on a similarly spec'd computer using 10 libraries of
500 variables each.
You can programmatically undeploy libraries using the delete process VI
on the DSC Engine Control palette in LabVIEW. Use this VI in combination
with the get process list VI to quickly remove all currently deployed
libraries.
Also, regarding your question about why variables sometimes show up the
Published Variable Monitor window; the different utilities you described may
use different methods to get that variable list. These methods behave
differently depending on how stressed the Shared Variable Engine is. If
you're in the middle of loading a library with 5000 variables I'm not surprised
that the list won't get populated immediately in the Published Variable Monitor
window. After the library successfully loads though, you should be able
to refresh the view and see all the variables.
Regards,
Nick F
LabVIEW R&D
~~

Problems with Labivew 2013 / 14 install - Ni Variable Engine error and Labview does not close, processes do not stop when I run Vis.

Hi All,
I am hoping at all my problems are relateded to a problem I am experancing, when I look into my windows 7 (64bit) event viewer near every time I boot up I get an error regarding the NI Variable Engine which reads.
The description for Event ID 0 from source NI Variable Engine cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
C:\Program Files (x86)\National Instruments\Shared\Tagger\ni_tagger_plugin_mxs.dll: Failure to load plugin: Unexpected Error: Unable to get the Interface from the plug-in.
and a second which is the same apart fomr the last line
Unable to load the MXS configuration plugIn: Failed to get MAX Configuration interface for Tagger: 0x80040318
I have tried uninstalling all labview things and I have tried repairing all labivew programs. Along with this I got this error when I installed Labview 2013 so I thougth why not try 2014 and I still get the same problems. I also shoudl point out I use bot 32 bit and 64 bit versions of labivew. I have installed labview on many machines before but never encountered this problem. That being said this was a new clean windows install.
Along with thiese errors labview heardly ever shuts down properly when I close the program it just freezes and needs forshed shut down.
Apart form this I noticed that when I run any of my Vis which I have never had problems with in the past and I stop the program somtiems processes keep using CPU such as "lktsrv.exe"
I really need to get this sorted out because its morstly the crushing and processes not stopping which is rather annoying.
I shoudl also say that these problems are both in the 32bit and 64 bit versions of labview not difference. and no difference if its 2013 or 2014
Cheers

Hi GajanS,
Thanks for your reply sorry I havetn noticed anybody had replied as I stopped hoping for any responce before then.
I have attached a screenshot of the four processes that seems to be giving me a problem.
I have actually managed to find the program causing labivew to crash was in fact my antivirus software which I have now removed and have no more problems with labview crashing on shutdown.
After removing it I tried the repair feature again for all my labview programs but sadly the one persistant problem remaining is still the four processes using around 13% processor each. I have found out this happens sometime after booting up regardless of if I run labivew or not. So it does not directly seem related to the running of any labview applications but rather a bug in the labview software.
the processes are:
lktsrv.exe
tagsrv.exe
nidmsrv.exe
lkads.exe
as shown in the task manager.
I would relaly help if I can get this sorted out.
Cheers
Attachments:
Screenshot 2015-03-24 21.50.00.png ‏12 KB

NI Variable Engine closes on boot up.

I am new to LabVIEW and installed the 8.6 Evaluation DVD on my XP computer. Now, whenever I boot up, I get the message. "NI Variable Engine has encountered a problem and needs to close. We are sorry for the inconvenience.... Please tell Microsoft about this problem..."
Please tell me how to fix this. (If I need to execute a System Exec.vi call to stop/start the variable engine, please be explicit in telling me how to do it.)
Thank you.
Solved!
Go to Solution.

Hi Don,
Thanks for the post, I noticed you haven't had any support.
I have seen this error before. Unfortunately there is not one simple solution.
It has been resolved for some customer due to a conflict with measurement studi. Please see this forum link.
Also it seems that this is most likely due to a corrupt installation. Windows
typically gives this type of error for corrupt installs, and the fact
that both machines that installed from the same disk experience the
error compounds my belief. The error happens at start up because
LabVIEW automatically launches the Shared Variable Engine (SVE) at
start up. We have two options to stop this from happening:
(1) Re-install the shared variable engine by installing the NI DAQ driver again
(2) Turn off the feature that automatically starts the SVE at start up
Method
(1) takes care of the problem with your SVE, and will make it usable in
the future, but will take a long time to do. Uninstalling the current
version of NI DAQ that you have, and then installing it again, or
installing a newer version can take a very long time. If you feel like
doing this, here is a link to the newest version compatible with
LabVIEW 8.5:
http://joule.ni.com/nidu/cds/view/p/id/965/lang/en
Method
(2) does not fix the fact that the SVE does not work properly, but if
you are not going to use it then this is no concern. Also, it is much
quicker and easier to do. Here is a link to how to do it:
http://digital.ni.com/public.nsf/allkb/2DD852E2B9CDF7578625707E006641A5?OpenDocument
Let me know what you think,
Kind Regards,
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!

Attempting to install a compiled 8.6.1 package fails with "NI Variable Engine (higher version already installed)

This is long as there are a collection of details I thought would be useful. Please bear with me.
I have a VI compiled with LV 8.6.1 PDS. The installer ran on the development machine and it works fine there (WinXP SP3).
Was handed a laptop (another WinXP SP3) that already had LV 7.0 (academic) on it. Someone was fiddling with an old version of LV. OK.
Wanted to uninstall 7.0 so there would be a clean field for the program compiled under LV 8.6.1.
So: Start --> Control Panel --> Add/Remove Programs and uninstalled "National Instruments Software". That went smoothly. It wanted a reboot. Fine.
Ran the setup program in my package, the one I'd wanted to install. No errors. The following installers were included with the Build:
* NI LabVIEW Run-Time Engine 8.6.1
* NI Measurement & Automation Explorer 4.5
* NI DAQmx 8.8
By the way, this generated an installation package of "almost" 900 megabytes.
Connected the hardware (one ethernet-based, another RS-232 based). Started the program, "EDGAR2".
First error:
Unable to locate the LabVIEW Run-Time Engine.
EDGAR2 requires a version 8.6.1 (or compatible) LabVIEW Run-Time Engine. Please contact the vendor of EDGAR2 to correct this problem.
(This is Error1.JPG, attached).
A check of C:\National Instruments\Shared\LabView Run-Time\8.6 shows that there is only one item in that directory: a sub-directory named "errors". That's it. If the executable is looking for something in the 8.6 directory, well, there's nothing there.
Uninstalled EDGAR2 using the Control Panel. Reinstalled. Same problem.
Downloaded the standalone LabVIEW Run-Time 8.6.1 installer, Standard Edition, from NI's site, unpacked, and ran the setup.exe from that package.
There is one box with a green checkmark in it: NI Variable Engine .
Click Next. Up pops a pane and Error2.JPG is attached. It won't continue because the "detected" version of Variable Engine is of a higher revision.
The "Next>>" button is grayed out.
Uninstalled EDGAR2 again. But there was no entry in the Windows uninstall panel for uninstalling any National Instruments software. This raised a flag in my mind and NI Support was telephoned.
With the Support Guy running Google searches for relevent topics (I'd done some of that, too), a number of things were tried.. ending up with deleting everything in C:\Program Files\National Instruments while in Safe Mode, everything in C:\Documents and Settings\All Users\Application Data\National Instruments, going through the Windows Registry with REGEDIT, uninstalls and attempted reinstalls. Nope, nothing worked. That defective Variable Engine seems glued into the system
The application can't find the 8.6.1 run-time because it doesn't exist. It doesn't exist because both the standalone and built-in installers see a Variable Engine of a higher version installed and apparently won't install over it. There is no uninstall for any NI software in the Windows Control Panel --> Add/Remove pane and so I can't seem to get rid of this Variable Engine.
At this point, the Support guy says, "Time to reimage your computer. Call us for anything else.. you know we're here for you."
This is the first trouble I've had installing a compiled VI. All other packages built with 8.6.1 PDS just slid right in.
There's been a LOT of software installed on the target over the years and going on the proverbial "scavenger hunt" to locate all of the installation disks will be a time-consuming task (a week is a conservative estimate). Is there a solution to this problem? Where are the installers "looking" for the Variable Engine revision level? Is there a specific Registry key that can be adjusted?
Went looking through the WinXP Event log. No errors are popping up there.
Your time is appreciated.
Mark
Attachments:
Error1.JPG ‏17 KB
Error2.JPG ‏28 KB

Hi Mark,
I'm sorry to hear your having trouble installing the LabVIEW 8.6.1 Run-Time Engine. It sounds like there could be a few problems going on here. First, you should have more options when installing the Run-Time Engine than just the Variable Engine. If you uncheck the Variable Engine, does it try to install anything? Second, not being able to install the Variable Engine suggests that there may be something wrong with your registry. If you removed all National Instruments keys when cleaning the registry, then this shouldn't be a problem.
At this point, there are a couple things I would suggest. Unfortunately, the best solution would probably be to reformat. It sounds like some low level parts have been corrupted and this would be the quickest way to fix everything for sure. Other than that, you can try installing the full 8.6.1 Development System on the computer. This will install the Run-Time Engine on the computer. You can simply not activate the software, which means you won't be able to edit anything. You will be able to run the program, though.
Jared S.
Applications Engineering
National Instruments

Installer Builder - Install application installer error, NI Variable Engine 2.6.0

Dear All,
Good Day!
Im Shahril.
My PC have 2 version of LV, 2012 and 2013.
The application required NI Variable Engine to be installed.
When i build the installer, nothing got wrong. AKA completed.
But when tested it by install the application installer, the error occurred as attached.
I do many times reinstalling the labview 2013. Still got the same problem.
And i did run the NI Update Service. Update everthing in urgent needs to update.
Please help me.
TQ.
Attachments:
Error NI Variable.png ‏36 KB

David,
I can’t say for certain what’s going on here but I do have a few suggestions before you “recreate the installer for legacy code reasons.” First, I would delete everything from the Build Directory. This may be where the recursive issues are coming from. Lastly, in the My Installer Properties window, I would look at the Source Files and make sure everything is there and check for any broke links.
Charlie M. CLD

What causes the Shared Variable Engine to Crash?

All,
Some background info:
I am using the SVE and DSC so that I can log my data to Citadel using Data Sets. I converted a previous DSC 7.1 project that used the tag engine over. That app ran for over 18 months. Need to upgrade app and add features at my customer requests so we migrated to LV 8.0.1.
I have an app that crashes the Shared Variable Engine (SVE). I created a test app with a single SV and then created a control and bound it to the SV and it works every time until I launch the larger app. The main app only has 33 SV that are set when I receive TCP data from PXI RT system (not using SV on RT since the logged data is only a fraction of the total data streamed and I don't want to take apart the RT data and send the SV separately). I have bound front panels controls to the SV's. When I run, I get server connection has been closed. I verified that the SVE was running with the test app before launching the main app.
I deploy the shared variables in the application and have verified they are deployed by the Monitor Variables utility ... but it always shows "No Value" for the data fields. I have set logging to enabled for data only, set Value Deaband (%) to 0 and Value resolution to 0, Update Deadband is Disabled as is Alarming, Scaling, Initial Value and Description. Security is set to default. All of the variables are set to Double, Network-Published, Single Writer with Buffering and Bind to Source disabled.
I have verified that the SV deploy without error by clicking Deploy from the project. Autodeploy All is off but I get the same results with it On (checked).
I undeploy and kill the process when I close the application.
I have tried only using 1 or 2 of the SV in the main app but get the same results. Every once in a blue moon it will work after rebooting the PC (but not everytime). Once it dies I have tried running NI examples as well as the test app and they fail until I reboot.
The error code indicates that the SVE engine has crashed. I have changed the service settings on Windows to relaunch on 1st, 2nd and all times after but nothing restarts the SVE. After it crashes it is impossible to exit LabVIEW without it hanging or reboot the PC without pressing the hard On/Off switch.
Once it dies there is nothing that I can do to get it back alive without rebooting the PC (a real problem for a control and monitoring system).
Any ideas would be greatly appreciated
Thanks.
Randy

Randy
Sorry for the delay, I've been researching your issue and juggling a few other issues. :-) One thing we can check is the Windows Event Log which will give us some more details as to WHY the Shared Variable engine seems to be blowing up on us (Conttrol Panel -> Administrative Tools -> Event Viewer). Any details in there along the lines of Variable Engine or Tagger crashing will help us narrow down what's going on.
There's always a possibility of files not getting upgraded correctly; however there aren't many shared components between LV 7.1 and LV 8.0. The Shared Variable engine is entirely new and the installations of LabVIEW themselves don't share many files outside of the example finder and a few other small common components (things located in the appropriately named Shared folder) I keep both on my machine (in addition to 5.1, 6.1, 7.0, and 8.2) without any hiccups.
The SVE crashing I have seen in the past (and from internal bug reports) has been from buggered installs, so uninstalling and reinstalling DSC may be a good course of action. One good test to do in the middle is to see if the engine still crashes with DSC uninstalled.
Hope this helps.
--Paul Mandeltort
Automotive and Industrial Communications Product Marketing

Appear to lose connection with the Shared Variable Engine

Have been through the boards, but with no success regarding the specifics of my problem.
I am running a real-time application on a PXI-8108. The host software is taking care of user interface, etc. Information exchange is handled using Unbound Network Shared Variables (located on the host, though problems occur no matter where the variables are located). Everything deploys fine. Software runs swimmingly. I have backed off the DAQ/communication processes until the RT cores are at <10% busy. However, occassionally while running, I get a popup "Waiting for Real-Time Target xxx to respond..." If this message stays up for long enough, then the target's attempts to read the Shared Variables start erroring out with an error -1950679035. As the variables have already been deployed and used prior to this instant, I find this curious. If I filter out the error, eventually the real-time software comes back up and everything progresses as though nothing happened. However, this is a potential deal-breaker for the users who can be impatient with having to wait a few seconds for the software to respond.
Any idea what is happening? I'm not pumping huge amounts of data over the network, no threads should be starving. Kinda confused.
Dan M.

The shared variables are being used much like how a queue would, directing each loop to perform an action should the host require it. If no action is required, then the loops default to check their respective bus or DAQ.
Currently, I am running 13 timed loops (whose periods I have extended signficantly during debug to no detrimental effect of my software, but to no improvement in the issue in question):
RS-232/J1708 converter loop (50ms period)
CAN loop (50ms)
DMM loop (250ms)
Oscilloscope loop (250ms)
DAQ loop (50ms, includes 1 AI task, 4 DI tasks, and 6 CTR in tasks)
Switch loop (50ms)
RS-232 loops (50ms for the main, 1 additional loop at 1Hz)
RS-485 loops (50ms for the main, 4 additional loops at 1Hz)
Both cores appear to share the load, usually the aggregate load is under 15%. When the popup appears telling me that the host is waiting for a reply from the target, the PXI controller monitor output still updates the CPU loads, which do not show anything unusual, such as a spike or a freeze in loading. The target loading does spike up to about 30% total after the communication is reestablished, but that appears to be the software attempting to "catch up" with the events that occurred during the "black out".
The error reads like this:
Shared Variable in Main Target Application.vi
This error or warning occurred while reading the following Shared Variable:
\\My Computer\Host-Target Interface\RS-485 Messages to Target [<--insert other variables here]
\\192.168.1.122\Host-Target Interface\RS-485 Messages to Target
Unable to locate variable in the Shared Variable Engine. Deployment of this variable may have failed.
Are there any other drivers that would be starving the Shared Variable Engine? For example, if a VISA or NI-DAQmx driver goes to sleep, could it hold up the SVE? What execution system are they running under?
Thanks for your help!
Dan M.

Deploy Shared Variable Engine in localhost

I need to talk to multiple RTs using single computer. It seems
obvious to deploy shared variable engine (libraries) in localhost instead of
RT. However, the problem is the shared variables (read) used in localhost VIs
are not being updated from RTs. But when I am using another local VI to update
the shared variable, it is working just fine. The variable path of the RT looks
like "\\My Computer\Local NPSVlvlib\Test
Data". I think this is the problem why the values are not being updated
because RT cannot resolve the network path ("\\My
Computer\Local NPSVlvlib\Test Data"). Also, I tried to change the shared
variable path in RT but I could not do it. Help Needed!!!!
Solved!
Go to Solution.

Thanks for your reply. I found in this link http://zone.ni.com/devzone/cda/tut/p/id/9900#toc2 that host computer can host the shared variable library and RT does not need the shared variable engine. See below
If your application includes a single host computer and a single or multiple RT targets it is recommended to host the library on the host computer. This will save memory and processor time on the RT targets. Also, by hosting the library on the host computer instead of the RT target, you can reduce the software install footprint on the RT target. The RT target will not need the Network Variable Engine, but will still require Variable Client Support. The Network Variable Engine allows hosting, the Client allows communicating with libraries on other machines. You can see a RIO target with these installed in Figure 4.
That exactly what I am trying to do. Any comments?

RT Shared Variable Engine stops publishing

I have an RT system (PXI-8106) that hosts quite a few network published shared variables (NPSVs) for communicating to a Host PC. My Host and RT executables have been functioning fine on their respective systems for weeks, but just recently, I started running into problems with my NPSVs. My Host application has indicators to display DAQ data being acquired on the RT target and transferred via NPSV, and lately the application will update normally fine for several hours and then the displays will stop updating all of a sudden. If I reboot the RT target, the communication is restored...for a couple hours, anway, until we get another NPSV lockup. I can see no rhyme or reason as to why it stops updating the variables when it does; it seems to just randomly crap out.
It just happened again, so I brought my development laptop down to run the Distributed System Manager. Sure enough, the NPSVs all stopped updating (latest timestamp was about 30 min previous to my check). I know, however, that the RT system is still running (I can open remote front panels), and none of the NPSV calls use their error input clusters, so an upstream error would not be causing the issue. Also of note, I have a couple NPSVs that are aliased to PSP URLs (NI_SystemState\CPULoad), which do continue to update while the remaining NPSVs do not. So that seems to indicate to me that it is not a networking issue, nor is it a Shared Variable Engine issue.
I also programmatically deploy the NPSV library from the Host to the RT target on initialization, so I know they are deployed properly. Redeploying does not kickstart the RT SVE into updating. The only thing that seems to solve the problem (albeit temporarily) is a reboot of the RT target.
Does anyone have any ideas as to what might be causing the RT to stop updating the NPSVs? I have already check the NPSV Troubleshooting KB (http://digital.ni.com/public.nsf/websearch/6E37AC5435E44F9F862570D2005FEF25?OpenDocument), and none of those suggestions appear applicable in this case (most address networking issues that result in never being able to read the NPSVs in the first place, whereas my problem is NPSV communication dropping out arbitrarily). Has anyone else run into such a problem?
Thanks!

I think I have an idea as to why my NPSV communication was freezing. One of my NPSVs is a 2D String Array of Alarm History Data, which just published infomation about alarms that have been triggered on the RT system; each new alarm appends a 10 element string array onto the 2D string array. For the most recent testing we were running, there was a recurring alarm condition that was not applicable (i.e. did not need to be handled--it just kept adding new elements onto the history array), and I am guessing that the array may have just gotten too big. When the RT target kept updating the NPSV (at 1 Hz) with more and more 2D String Data, it may have caused a buffer overflow for the shared variable.
I will attempt to recreate the problem on another system to verify the cause.

-1950679023 Shared Variable Engine and the NI 9148

I'm running an RT application on a cRIO-9074 that calls I/O from a connected cRIO expansion chassis (NI 9148). At some point some digital input variables throw he following error
-1950679023, The connection to the server was disconnected.
What's strange is that its only some of the inputs that have this problems. Other variables on the same module work just fine. What's going on here and how can I get my system to recover from this error once throw?
I'm running RT 2011.0.1 and Network Variable Engine 1.8.1
Craig

Hi Craig,
Do you see these same problems if you place the two offending modules in the 9074's chassis instead of an expansion chassis? If you do make this switch do you then see errors on other modules?
Have you tried programmatically reading the variables instead of using shared variable nodes? You can find an example of this if you're not familiar with it here, https://decibel.ni.com/content/docs/DOC-12548.
When you see these errors does your application stop running, or do you just see the errors being carried through the variables as it continues to run? Also, just to double check, you're seeing these errors intermittently not every time you run correct? Also is there anything noticeable happening when this error occurs other than the error itself?
Finally, could you post a little bit of your code, or some screenshots of where you're accessing these variables and how often you're doing so?
Thanks,
Miles G.
National Instruments
Applications Engineer

Deploying cRIO as Shared Variable Engine

I am finishing up a project where a crio will be continuously recording data and the computer is running a program that will download the data once daily as well as comunicate with the program running on crio device over shared variables. Since the crio will be using a cellular modem to connect to the internet, connection loss is expected. For this reason we have made the crio serve the shared variables so that if connection is lost to the PC, the crio will continue to record data normally without problems when it writes to or reads from the shared variables.
The crio will be running headless. I built a real-time application and deployed it as startup successfully on the crio device without warnings or errors. I connected to it via font panel to confirm it started up and is working properly. I will eventually use the application builder to build an installer that will install everything needed to run the program on the PC side. However, when I open the 'Belle Glade System PC' and run it, it attempts to deploy the shared variables on the crio device. It warns me that it will close any applications running on the crio device. This is not what I want. The shared variable engine is already deployed on the crio device and the program is running. All the PC program (Belle Glade System PC) needs to do is run and connect to the shared variable engine already deployed. I am obviously doing something really fundamentally wrong here and I could use some help.
[will work for kudos]

I apologize for not posting the solution to the problem.
Basically what you end up having to do is create two nearly identical shared variable libraries, one on the pc and one on the crio. The library on the PC has each of its shared variables binded to the corrosponding variable in the cRIO Shared Variable library by PSP URL (ip address and variable location). To do this, open the PC shared variable library and go to the properties of a specific variable. Check "Enable Aliasing" and under the bind to drop down menu select PSP URL. Then hit browse and find the variable on the crio. Do this for each of the variables on the pc.
This option does not seem to be 100% reliable as it has trouble detecting connection problems between host PC and crio device. This is because shared variables look for a connection to the shared variable engine. However, both the pc and the crio have their own shared variable engine running as a host so there is always a connection as far as it knows, lol. This solution worked ok for me since I could not find a more relable option.
There is a better explaination on this post: http://forums.ni.com/t5/LabVIEW/cRIO-Shared-Variables-amp-stand-alone-application/m-p/797139?query.i...
[will work for kudos]

The Distribution Kit Builder is Looking for the NI Variable Engine in an old distribution, cant find it and fails to build

I am unable to build a distribution kit because the builder appears to have saved a path to the NI Variable Engine which is not valid. I appear to have the NI Variable Engine installed. There are NI Variable Engine 2.5.0 .xml files loaded in on my computer (See attached for listing of drivers loaded). I do not seem to be able to break CVI's Link to my past installers for getting drivers. I've tried creating a new installer but had the same trouble.
I am running a 64 bit Laptop with Windows 7, building a 32 bit application, running CVI 2010.
Solved!
Go to Solution.
Attachments:
ATAHM Outline.ppt ‏61 KB

The default path is the path to whatever distribution installed NI Variable Engine on your machine. For example, if it was installed from a Driver Disk, the path would probably be D:\. However, from the images you originally posted, I can see that you were being prompted to provide the path to one of your earlier ATAHM distributions. It was looking for it at this path:
c:\Users\chill\Documents\Development\AATAS\ATAHM\distributions_ATAHM\ATAHM Oct 24 2011\
Do you still have that distribution? If you can point it to that distribuiton, you should be good.
Now back to the error you were seeing... Your version of that .NET manifest file matches (except for the version number) Revision A from the Knowledge Base, so you should try replacing it with Revision B (and rename it to NI .NET Framework 2.0 Language Pack x86 Installer {F8ECD2D6-659C-49EB-8454-5F8F7B526FCF}.xml). Make sure you restart CVI after swapping the file. I would expect that to solve your problem. If it doesn't, you'll have to let me know what the new issue is, or if you're somehow still seeing the same error message.
Mert A.
National Instruments

Hibernation problem due to NI variable engine

Similar Messages

Maybe you are looking for