Variable engine

Hello,
I met the following problem: when I was trying to deploy shared var library, Labview dropped down before deploying starts. Variable manager shows nothing under Local System (icon for Local Syatem became the cross). Attempts to start new process in Local System return error - cannot connect to target: \\localhost. How to fix it? Is it possible to reinstall Shared Variable Engine separately?

Hi Err,
Thanks for contacting National Instruments. I'm glad you appear to have solved your problem. Ensuring that the Configuration Manager is started is always a good troubleshooting step. It looks like you might have already seen this, but I am including a link that you will be able to look at in case you have any more problems that may have something to do with the Database Connection Error in MAX. Thanks!
http://digital.ni.com/public.nsf/allkb/B9107A7F281F9B408625720B0078E5A8?OpenDocument
Regards
Noah R
Applications Engineering
National Instruments

Similar Messages

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

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

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

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

Shared variable engine with pro-face touchscreen windows 2000 professional

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

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

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.

Executable won't re-connect to shared variable engine when it breifly goes offline

Hi,
I have shared variables that are hosted on a field-point controller. I read these variables from executables that run on a PC. When the shared variable engine on the field point controller goes offline and then comes back online (for instance, if I cycle the power to the controller), the executables on the PC don't automatically reconnect. I need to restart the executables in order for them to re-connect and read the shared variables.
Any ideas on how to have the executables automatically re-connect? I don't want to have to restart the execuables when the power cycles on the controller,
Thanks, Derek.

Hi Derek,
It is my understanding that the variables should reconnect, even after your FieldPoint has been power cycled. I found a few articles that could be helpful; read through these and let me know if you are still having issues.
http://digital.ni.com/public.nsf/allkb/7BA64956A475405F862570ED007B2A88?OpenDocument
http://digital.ni.com/public.nsf/allkb/04D9A85B6967EE87862571140065EEC6?OpenDocument
http://digital.ni.com/public.nsf/allkb/AA97FF29D0B3C748862572F600055B22?OpenDocument
Cheers,
Marti C
Applications Engineer
National Instruments
NI Medical

How many clients subscribed to shared variable engine

Hi,
I have shared variable engine deployed on RT and want to know how many clients get access to the shared variables. Is it possible? Thanks!
Tom

Theoretically there is no limit for the number of clients (maybe there is a 2^32-1 limit somewhere I don't know about).
However, more clients create more threads and the CPU usage will increase.
So you shouldn't use that much clients or host the SVE at the host computer if possible.
Christian

How do I install Shared Variable Engine on a computer not having Labview?

Hi,
I am trying to communicate with a real time program running on Compact RIO through shared variables. I have an executable of the host vi that runs on a Windows computer. If I run this executable on the computer that has Labview installed on it, it functions fine. I want to be able to run this executable on a computer with Labview. I learned that I have to first install Shared Variable Engine on this computer.
How do I do that? Where to install it from? Is that going to be sufficient? Please provide the solution or point me to the right resources.
Thank you.
Anmol.

When you built the installer for the executable, you have a choice to include additional installers. One of them is the "NI Variable Engine". Have you tried including it?
LabVIEW Champion . Do more with less code and in less time .

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).

NI Visa - Shared Variable Engine

Hi,
I am using labview Shared Variable Engine to create variables on my workstation and bind them to variables on my server.
I have labview 8.2 installed on my workstation and labview 8.5 installed on my server.
The communication between them worked perfectly and I was able to use the variables created in the workstation.
In my application I need yo use NI visa to take serial input. So I installed the NI Visa on my workstation and the NI visa worked.
However, the Server was not able to see the variables I have created in my workstation.
Does this mean that NI visa do not work in parallel with the Shared Variable Engine, or does the NI visa change some of the settings parameters that would stop the Shared Variable Engine from working properly.
Thanks in Advance

This information helps me get a better idea of what you are doing, but I need much more information in order to help pinpoint what is happening in your application. You should absolutely be able to use VISA as well as the Shared Variables concurrently. What is the device that you are using for data acquisition? I'll need the model of the device. What kind of data are you acquiring? How are you using VISA to communicate with your instrument?
One other item is to look in the distributed system manager to see if your shared variables are actually getting updated
Any code you could post here would help as well.
National Instruments
Applications Engineer

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

Variable engine

Similar Messages

Maybe you are looking for