Do I have to Bind Shared Variables in Executables?
I want to have shared variables work between two executables that will be installed on seperate machines. I've managed to get the code working, but am not satisfied with the approach.
Attached is a .zip file with my project files that contain what I've been able to get to work.
What I don't like, is how I need to have double the amount of network variables. Right now I have a program that is a publisher and another is a subscriber (based on an example provided on this forum at some point). The Publisher has its own shared variables inside a library, and the subscriber has its own shared variables inside a different library. The Subscriber's shared variables are "bound" to the Publisher's shared variables in the project file and is a concrete physical network path that cannot be changed.
Once the executable is made and installed, this works. I've tried getting it to work w/o one of the executables using a shared variable library that contain bound shared variables through a concrete physical network path but I obviously do not know what I am doing. Ultimatly, I would like to have a single shared variable library that both the publisher and subscriber use. I want the publisher executable to post the variables to the variable manager running on the publishers machine, and then have the subscriber program running on the subscriber's machine to consume the shared variables from the variable manager on the publisher's machine.
Please help me!
-Nic
Hey Nic,
I am going to try and answer those questions for you.
If you use the DataSocket API to connect to a variable that resides on another machine, is your local machine's variable engine involved at all?
No, it should not be involved at all.
If the Variable Engine is not used locally, does it need to be included with your application installer?
Yes, it is going to need to included with the installer.
If I'm correct, whats better? To use the variable engine locally, or to connect directly to a remote variable engine?
Can you please give a little more information here? I'm not quite sure if I understand your question.
The default time-out on the DataSocket Read vi is 10 seconds. If you are doing multiple DataSocket reads in the same polling loop, one variable may update but the other datasocket read is waiting for its timeout before allowing the loop to itterate. This creates a really laggy scenario (see progmatic subscriber.vi in the attached .zip). Setting the timeout to something low, say 10msecs, reduce the "lag" but...
Having the ability to set a decent time-out is a really nice performance feature that isn't availabe to you when you Bind to a shared variable (I don't think). It may make performance since to not do any loop iterations until the data from the host has changed.... how to manage this w/o seperating each read into its own loop however is my question.... ???
Can you please explain this a little more as well? If I understand you correctly, it sounds like you have many datasockets open in one while loop. Are you using one datasocket per variable?
Is there any unseen advantages with using the National Instrument's Shared Variable API over the DataSockets API?
Shared variables are in general more easier to use, and provide a simple way to implement the idea of passing data between machines. Obviously, using TCP, you can create more control using your own protocol to exchange information, but in general, Shared Variables are normally just easier to use.
Feel free to post any questions or dicussion issues here.
Regards,
Kevin H
National Instruments
WSN/Wireless DAQ Product Support Engineer
Similar Messages
-
Binding shared variable in executable across network
I can't seem to get a shared variable to bind from an executable on another computer back to a source variable on the main machine.
I can get the remote variable to change with programmatic access. Is it possible to have shared variables in an executable bind to a PSP URL on another computer? This is labview 2011.
I can see everything with NI Distributed System Manager, and the programmatic access changes the remote variable, so it's not a network issue.
Thanks for any insights. This just doesn't seem to work the way NI's online white papers say it shoud.What I don't understand is why after binding to a specific URL, the "Shared Variable Deployment" screen of the application builder makes the target "my computer".
I probably could get this to work if I changed the network address of "my computer" in the ini file created in Application Builder?
This seem a strange way for this binding process to work. If the absolute target (for shared variable bound to another variable and referencing "absolute") was retained when the VI goes through the application builder, it would make for sense.
I can't get this to work any way with using bound variables. The only way this works is using programmatic access to shared variables in the built app, and I don't consider this the same thing.
My conclusion is that shared variable binding and appropriate absolute references to deployed variable libraries do not survive passing through the application builder with their absolute references intact. -
Bind shared variable to multi-channel item
How do i bind a shared variable (array) to a Fieldpoint multi-channel item?
When i configure the shared variable, and click browse to select the network item to bind to, i can select individual channels but there's no "All" tag.Actually I suspect that the problem is in the National Instruments OPC Server.
DataSocket can read array data types from an OPC Server, but National Instruments' OPC Servers do not publish data in an array format.
Probably the easiest solution is to publish your shared variable in your network but don’t bind it trough the opc server, instead you have to use it like a standard global variable (bind to source method).
Give a look to this document may lead you to a better solution.
http://digital.ni.com/public.nsf/websearch/FA610367EC62574186257118005089F2?OpenDocument
Hope these two tips can help you
FiloP
It doesn't matter how beautiful your theory is, it doesn't matter how smart you are. If it doesn't agree with experiment, it's wrong.
Richard P. Feynman -
Programmatically bind shared variable
Hi,
I'm trying to bind a control to a shared variable, if I clic on properties=>Data Binding, everything is set up correctly, but I get a red flag. Then if I add a white space after the variable path then clic OK. everything is fine and working properly.
My problem is I have to bind hundreds of shared variables so I don't want to modify every single control properties...
Anyone has any clue on what's happening?
Rodéric L
Certified LabVIEW Architect
Attachments:
properties.JPG 34 KB
method.JPG 18 KBLooking at some similar code that I had developed to set FP bindings, I included single quotes in the url, for example:
\\My Computer\IO\'PU.Heater_Power'
Maybe the space is satisfying the need for a delimiter of some sort? -
Binding Shared Variable to Source
Dear all,
I'm currently working on a project that requires the use of shared variables. The shared variables will be network published and programmatically created using properties nodes. However I encounter one error and one problem in the process of doing so.
1) I programmatically bind the shared variable directly to the fieldpoint channel (data item) by writing the URL \\10.0.0.1\FP\1AIO\00 when i create the shared variable. The shared variable can be created successfully but when i deploy it, it generates an error which seems to tell me "it is out of range". Can anyone help me to rectify this problem?
2) The 2nd question will be, as my fieldpoint is connected to a DHCP server. At the start when i create the shared variable programmatically, i could bind the shared variable directly to the data item by writing the URL to its property. However, during the process of deployment, the dynamic IP address assigned to my fieldpoint may change . How can I ensure that the shared variable continue to bind to the right fieldpoint channels respectively? even though the IP address changes?
- Or is there any method that I could view all the network data items in a table? a list? or an array? so that I can link them to the URL.
I tried using the data socket URL.vi, I can only select the data item one by one.. this will be tedious for 100 or 200 I/O points..
Will greatly appreciate for any advice and help. Thanks in advance.Try this.
Give your fieldpoint controller a computer name through MAX. Then instead of referencing it by 10.0.0.1 in the URL's of the shared variables reference it by computer name. So \\MyFPmachine\FP\1AIO\00 instead of \\10.0.0.1\FP\1AIO\00.
Dynamic IP's can definitely cause headaches, and it would be best to use static IP's if possible, but doing this method should help. It seemed to work for me. I found when you browse for the channel in LV, it wants to give it the IP address by default, but it was possible to edit the string and paste in the computer name.
Message Edited by Ravens Fan on 01-10-2007 11:01 AM -
How do I setup shared variables between executables created in sepparate projects
Hello,
I have several sepparate projects with their own respective executable files and I would like to be able for these executable files to all share the same variable (one program controls the value of the variable, while the others read from it).
I got this setup to work on my personal computer (by being able to access variable manager, etc), but I need to deploy these executables on different computers that don't have the labview development program. What steps do I need to do in order for me to be able to put these executables on any computer (I'm assuming I need to setup a path for the shared variable that is always in the same folder, etc)
Thanks
Vlad
Solved!
Go to Solution.Hi Vlad,
I think this article may answer some of your questions regarding shared variables in deployed applications.
http://zone.ni.com/devzone/cda/tut/p/id/9900
It sounds like you already have your executables built, but this article may answer some questions about deploying them to other machines.
http://zone.ni.com/devzone/cda/tut/p/id/3303
Jeff S.
National Instruments -
Network shared variables lose binding
Hello,
I am developing an application in LabVIEW that uses network shared variables to transmit data between two PC's on the same subnet. The shared variables work fine when running the VI's in development mode, however, when i build the vi's into an executable I find that they no longer work. Here is what I have found so far:
I deploy the shared variable library on the publisher machine (also happens to be the development machine) through an invoke node in the executable. NI distributed system manager confirms that this does deploy and indeed updates as it should.
For the executable on the subscriber PC I created a second shared variable library (same project) with the same shared variables and bound them to the respective shared variables from the first library by selecting enable aliasing, then bind to PSP URL and browsing to the shared variable I wish to bind it to (e.g. \\hallnet-ellm2\shared variable library\serial Number). The machines listed under browse were listed by name so when I tried this initially and it did not work I manually changed the name of my machine in the URL box to the IP address of the publisher hoping that would fix it in case the subscriber could not resolve the publishers machine alias. So now my bind URL read \\192.168.0.1\shared variable library\serial Number.
As part of the executable on the subscriber I deploy this second shared variable library. NI distributed system manager confirms that this deploys but under quality for an individual variable it has a list of issues (see attached) and the bound variable is not updating. At this point the publisher shared variables are still functioning fine. By clicking on 'edit variable' I can see that the variable on the subscriber is still bound but the PSP URL is now \\localhost\shared variable library\serial number. Changing the PSP URL on the subscriber to \\192.168.0.1\shared variable library\serial number enables the variable to update as expected.However by this time my executable has already picked up the error and does not function.
I think that the issue lies with the bind URL used on the subscriber as for some reason it does not keep the binding configured in the project and instead changes to 'localhost'. Why is this? Should it not stay bound to the address specified in the project?
I have tried changing the IP addresses in the aliases file so that
[My Computer]
My Computer=localhost
becomes
[My Computer]
My Computer=ip of local machine
This did not help.
The shared variable libraries are included in the build spec to go into the support files directory and they are successfully deployed from there on both publisher and subscriber.
I am using LabVIEW 8.6 on Windows XP
Thanks for any help you may be able to offer,
Lee
Attachments:
distributed system manager.JPG 74 KBHi Lee,
I hope you are well. Thank you for your post. Your application sounds very interesting.
Looking at your issue I was wondering, have you tried lowering your firewalls, as this may be causing the problem.
Also, another option would be to setup a private network. Do you have access to any routers that you could use to link the two machines independent of your IT's infrastructure?
The other thing to try is two other computers entirely. Again, it would be ideal to take them off the network you are on, but it's something to try if my prior suggestion doesn't work. It should work on the original two machines though, and it's likely that different computers won't solve your problems because I suspect the network.
Remember that the client variables must know the location of the variables on the server, so you can't move the server exe around without changing this value.
Make sure to set the network location in the "Bind to Source" option for the client variables.
It is also possible to write a separate piece of code to install on every machine that is responsible for deploying the library and by doing so eliminate the need for programmatically deploying the variables in the original application. However, this won't really help you, because the variables you use in the application have to be the same as the ones deployed in the library, so if you change the library, they'll no longer be linked and they won't receive data. You'd have to create a separate exe for every binding source you wanted to link to, and then have a second, known library for the sake of communication locally on the computer between the ‘deployer’ and the actual application. The main application could then be assigned the responsibility of launching the correct ‘deployer’' if it sees it needs to switch to a different variable binding source. This method is not the most streamlined or effective, but it might work.
Just to let you know, you will need to use the DSC toolkit.
Please find below some knowledge base links that I think you will find helpful in your application.
Using Shared Variables in Executables
How do I Programmatically Change the Data Binding Source for Shared Variables?
I hope this information helps and if you can give these suggestions a go and let me know how you get on, that would be great.
Kind regards,
Prashant M
Applications Engineer
NI UK & Ireland -
Problems with communication across a network using shared variables
I have two programs(projects) running on two different computers connected with a LAN. I am using LabVIEW 8.0, and the DSC-module. The program on one of the computers have measurements that I want to collect and show on the program running on the other computer on the network. I choose the indicator where I want to show the data, select ''Properties'', ''Data binding'', ''Shared Variable Engine (NI-PSP)'', ''Network Items'' and then browse for a Network...but the problem is that in my ''Network Neighborhood'' There is only one computer...and that is the one I am one...not the computer on my Network that I want to communicate with....
Have anyone any suggestions on how to solve this?
Kind regards MariMari,
Check this link regarding trouble shooting network-published shared variables:
http://digital.ni.com/public.nsf/websearch/6E37AC5435E44F9F862570D2005FEF25?OpenDocument
This might be a firewall issue, so I would check that first.
Frode -
CFP-1808 shared variables timestamp
Hi,
I need to control and acquire data from a cFP Ethernet module (cFP-1808) to a PXI RT system. I have tested two ways of doing it:
1. Bind shared variables to the Fieldpoint channels. Works great except for the fact that I have to record the timestamp of every single channel in all Fieldpoint modules. I have to avoid this. The reason I have to record all timestamps is that sometimes two consecutive reads are the same in value and in timestamp; so even if I make sure I get a value every 100ms in my real time application I cannot trust that the shared variable engine will give a real new value every 100ms, because sometimes one read is the same as the previous one. My
understanding of the technology is that the cFP network interface checks for an
updated value of the channels of each module at the Advise Rate. If there’s a
new value the cFP transmits it to the Shared Variable Engine running in the PXI
controller, but if the value has not changed it doesn’t transmit anything, so
more efficiency is achieved in the network communication. This would explain the
timestamp behavior of the shared variables bound directly to Fieldpoint
channels; since there is no new value the shared variable is not updated so the
timestamp of two consecutive reads is the same.
2. Create a Modbus server and then create shared variables bound to the Modbus server channels. With this method any time my RT application asks for a new value the shared variable engine provides a real new value with an updated timestamp, and all timestamps in the same module are equivalent (in 1usec range). Therefore, it looks like using the Modbus solution I only have to record one timestamp per module.
So option 2 probably fixes my problem, but I'd like to understand why. Both methods use the shared variable engine, shouldn't they behave the same way? There's one downside in option 2, which is having to deal with Modbus addresses and not having the ease of use of option 1 that just browses to find the Fieldpoint channel.
Any comments?
A final note, it'd be great to be able to use the Fieldpoint VIs in LV Real-Time! Can this be achieved?
RaimonHi Raimon,
How are you binding to your shared variables? This KB reviews three methods:
http://digital.ni.com/public.nsf/allkb/FA610367EC62574186257118005089F2?OpenDocument
I don't believe using FieldPoint VIs on a PXI RT target is possible because FieldPoint is not a driver that you are able to install on the PXI RT target. We do have the cFP-2xxx line of RT controllers for FieldPoint, which can communicate directly to the FieldPoint modules, ensuring determinism.
Trey B
Applications Engineering
National Instruments -
Modbus ip shared variable network failure
I am using lab view 8.6 DSC module to communicate to a watlow system which contains five watlow 96 controllers and an EM gateway. I have created shared variables for the process temperatures and setpoints for each of the five controllers using watlow modbus register Numbers with a 400001 offset. I have also created shared variables for Updating,CommFail,UpdateNow,and UpdateRate which where predefined. I have error when starting the VI if the SV has been dragged and dropped into the block diagram. The message is Error -1967353902 (The Modbus I/O server failed to receive any response from the Modbus slave device.) occurred at SV in vi. If I bind a variable in the VI to this same SV the error does not occur but the variable cycles between Good, Network Failure, No known value, and device failure as stated in the variable manager watched variables. The Updating, CommFail and UpdateRate all have a consistent Good in the quality column of the variable manager. UpdateNow has X in value, type, timestamp, and quality columns. CommFail and Updating does cycle between true and false randomly. I have tried a third party software called SpecView 32 demo to see if the commincation with the modbus system is not working and I can create five watlow controlers on my screen and direct them to the ip address along with a unit address and the system works without faults. This leads me to believe the commincation bewteen the SV Engine and the IP address is not correct. HELP Please.
Robert Jensen
UND EERCIf your application can deal with it I would recommend staying clear of the 'Networked Published' option.
When I started my Modbus development on cRIO....I left it enabled, and with ~100 shared variables on a 9074, the CPU was railing, and I saw a buffering behavior on the shared variables (which was not desirable in my application).
In my application I am using the old modbus library (as apposed to the new API) for cRIO to slave comms, the cRIO being the master.
I am also using the IOserver making the cRIO a slave to an external SCADA - and it passes essentially the same data arrays as I use on the modbus library for my local HMI [Not an NI product].....Which is two full Modbus frame writes (@ 120 words each, and about 60 words more for ~300 words outbound from the cRIO).
The IOserver slave was a recent addition and did not add much to the CPU load - although only 16 bytes is high speed, the balance of the total word package is at either 1 second or 3 seconds.
So, in my experince, the 'Networked Published' option adds significant CPU loading (on entery level cRIOs) YMMV.
I am huge fan of the shared variable engine (some at NI were pusing the CVT, and TCE etc...). However most of my shared variables are not the Networked Published variety (excepting local module channels) those have remained networked published for DSM (Distributed System Manager) use. -
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] -
Error Reading a Shared Variable Array
Hi,
I am having a problem reading an array of 20 unsigned integers from an Allen Bradley ControlLogix PLC with Labview.
I have set up a shared variable for this purpose. I have set the Data Type of the shared variable to ArrayOf Unit16. The Variable Type is Network-Published, and I have check the Bind To Source checkbox. I think my problem is in the shared variable path. I have tried the following with no success:
MyComputer\ControlLogixTags.lvlib\RsLinx\ProjectX\Online\Faults\Faults
MyComputer\ControlLogixTags.lvlib\RsLinx\ProjectX\Online\Faults\Faults[0]
MyComputer\ControlLogixTags.lvlib\RsLinx\ProjectX\Online\Faults\Faults[]
MyComputer\ControlLogixTags.lvlib\RsLinx\ProjectX\Online\Faults\
MyComputer\ControlLogixTags.lvlib\RsLinx\ProjectX\Online\Faults
I have created a simple vi for testing. I have wired the shared variable to an indicator which is an array of UInt16 items. When I run the vi, I get an error which says "Error 91 occurred at Variant to Data in Text.vi. Possbile Reason: The data type of the variant is not compatible with the data type of the input."
Does anyone have a suggestion as to what I am doing wrong?
Thanks in advance for your help,
PhilPhil,
In order to determine that you can correctly communicate with your OPC server, I would suggest creating a shared variable bound to a single tag. It sounds as if you already have an RSLinx I/O Server in your project library. Now you can create a new shared variable and use the browse option to browse the items of your I/O server. Be sure to select a tag that has a known value such that you can verify successful communication.
Also, does your VI utilize a dynamic data conversion? The error code mentioned (error 91) is normally associated with this data type. Our next step will be to look at this VI once we can establish successful communication. I hope this was useful for you. Please let me know if I can be of further assistance.
Mike
National Instruments
Applications Engineer -
I have 2 applications runnng in different PC connected to the same network
Both applications are for testing purposes before going on with the real implementation. Written in LV 8.5 and based on Shared Variables.
While everything is fine when those application run on the same PC (in effect, localsystem), nothing seems to work when each is active in the proper PC.
Shared variables seem not to be seen from outside the PCs.
This happens also when I use Variable manager on both machines: I create a variable on PC1, defining it as published. Then I create another variable on the other machine (PC2) and try to bind it to the variable deifned in the PC1. Pressing the Browse button the list of PCs networked to mine appears. Selecting th eone I need (PC1), Variable Manager tries to populate the tree but hangs up. Or, better said, simply does not populate the tree. The ariable Manager still works but the item son the other PC are not seen.
Any suggestion?
Regards
WalterHi there,
I'm having a very similar issue. My set up is 2 pc's on the same network, the "server" (date generated on this pc) running LV 8.0 ip#1, the other is running LV 2010 and will only see the data, ip#2.
I have set up two test network shared variables and configured them on the server machine Ip#1 to bind to ip#2. When I run the vi's I see that the shared variables are deployed to the particular machine.
On ip#1 I included a test vi in the project to read data from the ip#1 shared variable, and I see no data. I have other local shared variables working within ip#1, but the network shared variables cannot be read even within the same project.
Any ideas as to why I cannot read the networked shared variable within the same project on the same computer?
Also the link about multiple network-adaptors is dead. I have seen strange issues when configuring the networkd shared variables if I have a VPN sessing going to an outside network on both computers, I will see both the windows computer name and the ip address.
Is there anyway to delete a computer after adding it as a shared variable potential source?
Thanks for any help, there are a couple of questions here.
Jim -
Shared 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,
cosmincosmin,
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
~~ -
Shared variable no longer updates
All,
I have an RT Systems 2011 and have been using shared variables between the RT and Host. Working for months. Then I renamed a shared variable and it no longer updates. When I try to look at the variable in the NI Distributed System Manager, it reports that it does not exist.
I changed the name back to what it was, it is seen by the System Manager but the current value is not displayed.
I did a remote debug into the RT code and the variable is being updated.
Any ideas\comments\etc would be appreciated?
ThanksWhat hardware are you using as your real-time target? When you mentioned that you are using "RT Systems 2011", are you using LabVIEW 2011 and the Real-Time Module?
After you updated the shared variable, did you re-deploy it? I highly recommend reading through the “Deployment and Hosting” section of the DeveloperZone Tutorial linked below:
http://www.ni.com/white-paper/4679/en/#toc3
Regards,
Cameron F
Applications Engineer
National Instruments
Maybe you are looking for
-
The Mail system has memorized email addresses that are out of date or that I don't want to use. When I type in a name or group list, it defaults to the wrong address. In one case I have a group name in my address book that I cannot get it to default
-
My music on itunes doesn't have the markers anymore, how can i fix this? So my songs should be listed like this: A Advice B Bang C Chinter's will K KannaZuki No Miko L Lights
-
Why Does My MacBook Air Make Random Sounds That Sound As If Am Getting Random Facebook Messages?
HelP!
-
First of all, my goal is to return an array that I've defined back to C#. Here is the type that I've defined: create or replace type EMPARRAY is VARRAY(20) of VARCHAR2(30)here is the function I'm trying to call create or replace function getEmpArray
-
Disabling pop-up screens on/off....
Hello all, I was wondering what would be the best way of disabling a window that creates a pop-up window and after the pop up closes, it then re-enables using AWT Frames (not a dialog). I hope this clarifies my problem: myApp mySection = new myApp();