Shared Variable Open accidents executable function

Similar Questions

• Why it takes so long to open a connection to a shared variable, the first time?

  Hello

  I have an application to large scale developed with LabVIEW DSC, which covers multiple computers on a LAN.  In one of the VI I open variable connection shared by using the "open Datasocket' VI.  I notice that after restarting my computer and execution of this VI into the source code (I have not tried with an executable file yet) it takes about 20 seconds to get a successful connection to a variable share located on another computer.  The later 'Datasocket Open' claims the same computer to the same shared variable takes much less time, about 100 ms.  I reproduce this with 3 different computer, so the behavior seems to be reproducible, but it's not to do it every time but very often.  This scenario may occur also when I did not open a connection to another computer for awhile.

  Anyone have this experience? Is there something I can do all this to avoid this 20 seconds delay problem? Anyone have an explanation?

  All of my computers running Windows 8.1.  I'm using LabVIEW 2012.  All my firewalls are 'off '.

  Thank you

  Michel

  Here is a picture of my open VI.

  Recently, I did this for another client. You can emulate a timeout (and actually connect faster) by using the function "open in background" and then checking the variable.connected? property.

• published RT cRIO-9030 with network-a project of shared variables cannot communicate with host VI when compiled and deployed as executable startup.

  I have a project including a VI RT running on a cRIO-9030 and a host VI running on a desktop computer.  The two programs communicate via shared variables that are hosted on the cRIO.  As shows, when I run the screw of the project, everything works as expected.  When I compile the RT VI in a start-up executable can deploy for the cRIO, as well as the libraries of shared variables (the record of support in the build specification-oriented), I am unable to connect to the executable running in real time.

  

  I have 'Disable Autodeploy Variables' checked on the cRIO target, if I no longer get the prompt to stop the currently running application to deploy the variables.  The host VI opens and appears to run, but has no connection with shared variables (data does not update).  Compilation of the host VI as an executable file and it works outside the project result in the same behavior.

  I read some relevant posts / knowledge base articles related to this problem, but still can't seem to find a way around it.  I note a number of articles on the series in double bond of variables, but this is in contradiction with my possible behavior for this system: I finally have a number of cRIO controllers identical all runnning the same executable RT and want to be able to have a single host VI which allows the user to select from a list of available controllers (using the screw system configuration) and extract the host name of the controller selected, that would be later used for programmatic addressing of the variables on the host of part VI.

  In any case, I want to start with the simple fact of being able to get that first controller running without an open connection to the RT VI project.  With the deployed executable start, I checked via programmed behavior of LED application of the RT and FPGA are running on the cRIO.  The problem, I think, has to do with shared variables, but I'm not sure where to go from here.  I want to connect to RT executable running from the VI to the host (in project) to verify that the compiled executable of RT works as expected and then the subsequently compile host VI in an executable that can be run from any desktop on the local subnet.

  Thoughts?

  It seems that the error has now been corrected.  There were three things, I changed: the file startup.aliases in the startup on the target directory (Home: / lvuser/natinst/bin) put in 'localhost' as an alias for the controller.  I changed it to the IP address of the controller.  Then, I got some features of IO files in my application RT relative paths using the path obtained by the 'current path VI' VI.  As this path changes according to the location / delivery system, I had to create a VI that has used the Application property: type with a case properly structure band / build railroads desired regardless of the runtime system data files.  This may have broke my RT request.  Finally, I got a property node in one of my RT SubVIs, who attempted to change an indicator in the Subvi, which is not taken care of in an RT compiled executable.  I can't do this for debugging purposes somewhere along the way, but in any case, I removed it, and after a recompilation and the deployment of the executable of RT, everything seems to work as expected today.  The host VI on the desktop can connect to the application of the RT project, and when it is compiled into an executable file, which also works.

• Shared variable of subjects with the executable in real-time

  We have a PXi target running Labview time real 8.5 and we use a series of shared variables for communication between the target and the client software. The code was developed (and used) in the last 2 years, and presented no problems with the shared variables when they are deployed since the Project Explorer (for the target and the laptop based client software). However, when you try to run an executable version on the system time PXI real target of exactly the same engine code variable shared seems to fail during the initial loading. Since it is an executable, it is difficult to display errors, but it seems that the accident occurred at the beginning of the program when we try to initialize a number of shared variables. Sometimes it loads but probably only 10% of the time. When you plug the tool to debug for code and restarting the executable, runs without any problem. However, once we managed to capture and error (error-1950678982 the shared variable client side read buffer is full).

  I checked a number of messages in the Knowledge Base (e.g. how to deploy Variables of a compiled executable shared network?), but it still has not solved the problem. Thoughts and suggestions?

  Adrian

  I tested it for a few hours now and I can't make it fail again. The big difference in my implementation was to use your suggestion, and no wire the error cluster through the method since the error it generates caused a number of questions later. So let me summarize the final configuration that seems to work then:

  -during the execution and executable on a target time real 8.5, startup not connected to a client. Library of shared variable hosted on the target and should load by itself.

  -J' added a flat structure sequence on the vi 'main' (top of page vi executable) with a node (as shown above) Invoke method in the first structure with a timer to 10 seconds and the rest of the code in the second part of the structure. The shared variable library has been copied to the target in a data directory and the path provided to the method (the same way as above) and the IP address is that of the target.

  I discovered that it takes about 8-9 seconds for the shared variable engine and library to start (I don't remember is that past exactly that) and it is important to wait this time to initialize shared variables or the behavior is unpredictable. The method always generates the error 1043 (function not supported) but I simply ignore it now, and it seems to work.

  Thanks for your help! I will let you know if there is some instability in the future, but everything looks good from here.

• variable shared unique process - build executable

  I have two applications on the same computer. Single process variable using shared with both applications. When generating executable writer updates the shared variable but the VI read the shared variable does not read the values. The question is only when you create and run executable files. How to build two executables on the same computer (and both are in the same project) using shared variables unique process?

  The use of the network shared variable is not necessary that both applications are on the same computer but when building executable with network shared variable that it works, only the shared variable unique process does not work?

  TIA

  Only shared process Variables work in the same application context.  When you are developing and the two screws are in the same project, they are in the same application context.  But two executables will be different application context.  So to communicate between two executables, you use shared network variables.

• Shared variable between 2 LabVIEW executables via the network

  Hello, I need to create a number of network shared variables by two (built with LabVIEW 8.6) executables running on two different computers on a local network. The library to invoke node returns an error when you use a different IP than localhost. even more, it is not clear to me what exactly I have to do (what executable deploys the library, on which targets, activate the link or not, so on...). Thanks for any help, if you have already managed to make this communication works properly...

  Thanks for the replies. I've found the last two documents, but the first one is the most interesting: if I can't put the sources of two applications in a single project, I will move to another solution (data as suggested by Mike sockets or TCP). The two original projects are larger, and their merger would lead to such a huge thing!

• Executable does not connect to the hosted PXI shared Variables

  Hello

  I'm developing an application to run with RTE 8.2.1 on Windows XPe machine. Data are passed through network shared Variables in a target RT PXI. I developed on a laptop with the top Suite Developer Pro and everything works wonderfully here. When I create a program installation (and an EXE version) and on the port to the XPe machine, variables don't connect with each other (as seen to drag the control to the public Service, view the small arrow to the right to the status of the connection). I think it's due to not having the right drivers on the target XPe. Do you have any suggestions as drivers that I should include in the installation properties? I currently have:

  OR LabVIEW 8.2.1 RTE

  Engine OR Variable

  And NI-DAQmx is already installed on the machine (I think... a previous installation, the wizard sees a newer version about this than what I'm trying to install). I have also included the library with the shared variables in the properties of the EXE in the part of the Support files.

  I know this is a very old version of LV, but if you have ideas, or things to check, I would be very happy to help.

  Thank you!

  I understand the problem!

  In the structure of the Project Explorer files, I had included the buttons under the heading of the library (HMIvariables.lvlib), with the rest of the variables. I guess when you try to deploy by programming, he's trying to deploy the control files and get the dreaded error 1. I moved out of the library control files in Project Explorer and it fixed the issue and deployed the library, as verified by the Manager of shared Variable.

  I got 1 Core 3, and on the RT 1 and 2. Nobody never mentioned against it and could not find any documentation talking about do not do. I hope it helps someone else!

  Thanks for your help.

• shared variables does not

  Hello, I'm writing because I'm having a problem with the use of shared variables. I am doing a project for College and I use the DSC for his shared variable function. The problem im having is that shared variables do connect it no more. I followed a document "Getting started with LabVIEW Datalogging and supervisory Control Module" and managed to build an IOServer and shared variables in accordance with the document to deploy successfully. It was a few days ago. Today when I opened the project file even shared variables would not connect. IM also having the same problem with other projects that I made over the weekend that worked, but do not work now.

  Does anyone else have this problem?

  Hi Justin,

  I am pleased to see that you are able to work with your LabVIEW installation now. 0x0000002A error message reported only in what concerns the communication between the shared variable engine and part mutual FUND of the DSC module is blocked.  This was usually resolved by inspecting the security settings Windows for the firewall, as discussed earlier.

  As for your second question, it might be better to start a new post.  However, please specify what files you want to move and what wisely win. Where would you like the directory that is to be held and for what benefits?  If you are hoping to achieve a gain of performance or similar, there may be different approaches other than moving files.

  Kind regards

• shared variables crio RT does not not after compilation

  I have a cRIO project that uses static variables. There are variables located on the host computer and a double set of variables on the RT.  While the project is open, everything works fine. I can DL the FPGA VI for flash, deployment and execution, the value of the RT VI car can run my desktop VI in EXE application.

  Once that I close the project window and close labview, the office program (host VI) will work but doesn't get over all values of the shared variable. I have read all the FAQs and have contacted technical support (which was told the fair questions).

  Apparently I'm supposed to add code to the RT VI to deploy the shared variables in the RT the RT VI executing. When I try to do, the variable deployment method requires a path. I don't know which way to turn in.

  Any ideas?

  
  

• datasocket read stop but shared variable can be updated

  Hello

  I program with datasocket open/read, sometimes stops playing and after some time, maybe 10 seconds, it go on reading, I compare with variable shared (DSC) and found

  the shared variable can be updated, I don't know what happens to my program.

  (the reason why I want to use datasocket is that I need to dynamically change the ULR, I have several OPC tags to read (automata 100 times 80 labels per PLC))

  Thanks for your help!

  Hi ~

  The reading function is expecting that the items to be updated, and 10 ms is the default time for this expectation. Affecting false wait the update value will probably solve this problem.

  PS: Variables URLS could be changed programmatically, see this document if you wish.

  Nice day

• Update of address of the card "shared Variable.

  Hello Experts!

  I have a question about shared variables:

  Now I create a variable Shared (81O_G01) in the library, and it is related to:

  My Computer\SVCREATION.lvlib\Modbus1\410611

  Question is: How can I change this address SV (410611) when tha variable has already been opened?  is this possible?

  Thanks in advance!

  Anibal

  Hey Anibaldos,

  Looks like you're trying basically change the binding of a /A1 to /A2 variables at run time. I think that there are a few options for this:

  (1) in LabVIEW DSC, you can access a hosted variable and change the link address by using a property node. If you run the server modbus on a windows machine, this is the best option. Otherwise, I'm guessing you don't have a DSC. If this is the case you can always edit links by editing the library manually, but it seems that this will not help you.

  (2) it may be possible to open a variable connection shared using pallets (Data Communication > shared Variable) to this specific address, to which cases you have no need to use the shared variable. You can simply open a connection to two addresses different modbus and read one or the other as needed.

  (3) if #2 does not work, then I think you can still use datasocket API to perform such an operation. There is a bit of research you need to do to use it (for example, URL editing and UI thread problems), but it does not work. In my opinion, this is the approach taken by this document: https://decibel.ni.com/content/docs/DOC-13508 (I know from experience, you have to dig a little to find the screw, but they are there).

  (4) you can use the Ni Labs library: http://ni.com/labs

• error in the terminal of a shared variable

  I read in the help of Labview entry 'Error In' to a shared variable provides a feature of "type error in. What I am unclear on the subject, is that if an error occurred before the shared variable, it will cause the shared variable NOT to do what it is supposed to do? If an error is passed to the entry 'Error In', the variable node still shared read/write as normally?

  Lol mistake-type functionality means that when an error is passed, the node will not run.

  (You can check yourself by writing a simple VI.)

• shared variable Android

  Hi all

  I have a problem with the shared variable and labview android app.

  I create a basic while loop IV and a random number with the shared variable. Now I deploy all the variable and I have this message:

  Initializing... Calculating dependencies... The checking for conflicts. This may take some time... Prepare the items for download. This may take some time... Deploy my computer deployment Untitled library 1. lvlib deployment Untitled library 1. lvlib1\DDVariable1 DVariable1\\10.211.55.6\Untitled library deployed. Deployment completed successfully

  now I open android app, select "connect to the shared variable" and insert the IP 192.168.0.2 (ip address of my pc where run labview), but the connection fails... why?

  my ip address of the router is 192.168.0.1 and my smarthphone is connected via wifi in the same network.

  
  

• cRIO, shared Variables & stand-alone application

  Hello!

  I developed an application very simple acquisition of analog (NI9215) and the activation/deactivation of outputs signals digital (NI9472) using a cRIO (9012). Data are transmitted to the host through shared variables program.

  I created an executable of the code to be run by the cRIO, set it to the "launch on startup" and it worked.

  I did the same thing with the hosting program and created an exe installer. As I use variables shared the result of acquisition of pipes, I have them placed in the support directory (data) when you generate the executable file (Distribution.exe).

  This executable works perfectly on my computer.

  I used the Setup program to install the program on another computer. This computer as its IP address in the same subnet as my computer. But shared variables ever offer data other than their default values so I guess there is a problem of communication...

  Can someone help me?

  Hi zyl7,

  Thanks for the post!

  This is a common problem - I think...

  The problem is that you need to deploy two seté variables shared by two of the llb. You need 'real' variables on the cRIO - and deploy manually (see link) and a second llb on the host pc, which are related to real variables on the cRIO. This is because the local computer get variables shared, which of course are not those with the cRIO data locally.

  Perhaps in clearer terms.

  When you make an exe of a project using shared variables, you must have a local copy of the variables on the deployment computer which are then related to the 'real' shared variables stored on the target - cRIO, in this case.

  This means that in the view of your project:

  (1) Create static variable in the normal Manor on the cRIO.

  (2) create variables shared on the host PC - llb under the Pc host in the project and then select the aliasing and how to link to YOUR PSP.

  Let me know how it works,

  Kind regards

• Delay weird read shared variables

  Hello

  I'm working on a project were I am followed a few lines of production. I use an OPC server on the DSC module to connect to PLCs on the production line and I created variables related to my labview tags of the PLC project.

  On my project, I have a main VI were I show information on production lines and I can access several subVIs were I see more information on these lines. Then I a VI that runs in the background were I read about 50 shared the PLC variables and where I save data in a MySQL database, data entry of data on the database of the Citadel and the recording of alarms.

  The problem I have is that I noticed a delay read variables that read weight of containers from the production line the VI that runs in the background. It seems that all shared variables suffer no delay, only the variables weight start to make some delay when the values are on the rise. It also seems that when I run only one VI, without running the main VI, there is no any kind of delay. I read shared variables shared as variable nodes.

  Can someone help me understand what is happening and how can I fix this delay? The VI that runs in the background is time critical and a strange delay like that messes up my data.

  Hi Mateus23,

  The shared variable has various capabilites buffering, including integration with real-time FIFO functionality in LabVIEW Real-time.

  I guess that buffering settings are causing the unexpected behavior.

  Check out these resources:

  Buffer Network-Published static Variables (white paper)

  Properties shared Variables dialog box

  - Network Page

  - Page FIFO in real-time