shared variables unused and vi

I clean a project of 9 - months old. I'm the developer 3rd working on it and it became a bit disorganized. I want to clean the project directory and file before the next developer structure intervenes to support this project. What is the best way to organize an already existing project and the structure of the files to remove any unused vi and shared variables?

Paul:

In your project, you can right click on your variables and select 'Search of the appellants' to determine what (if any) screws use your shared variables. That can help determine which ones is not used.

Tags: NI Software

Similar Questions

  • Pass a reference to the shared variable

    I use two shared variables in a loop where I write one and read each other.  I need to repeat this loop 5 times, but each loop uses a different pair of shared variables.  These variables are shared between a vi on the computer and a cRio.

    It would be ideal to incorporate this loop into a Subvi where I can pass a reference to the two shared variables in and then read and write in threw these references.  Then I could just call this Subvi 5 times, instead of copying and pasting the loop 5 times.

    Is it possible that I can accomplish this?  I can't find an example that would achieve this.

    Thank you

    If I understand correctly, you can use the mode programmatic access to shared Variables and it would work.

    http://zone.NI.com/reference/en-XX/help/371361H-01/lvconcepts/sv_usingdynvarapi/

    http://zone.NI.com/reference/en-XX/help/371361G-01/lvconcepts/usingdynvarapi/

  • 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

  • VI refuses to run when the published network shared variable is not available

    I have a VI of logging data on my PC that gathers data from several sources, including several shared variable published network hosted on an RT target.

    The problem I have is that the data logger VI refuses to start if the target RT is disabled and the VI is abandoned if the network connection is interrupted.

    Is there an easy way to detect when running, be published these variable network are available and use a placeholder value, if they are not rather than the current behavior of refusing to work?

    I saw many people using data sockets, but I try to avoid the overhead of setting up and testing a loop of treatment relatively complex network on both ends when the network has published shared variables are so simple to use and works perfectly as this abnormal behavior.

    You can replace them with programmatic access (shared variable aperture and friends) and the dummy data placeholders if the variable is not accessible.

  • Shared Variable deployment error

    I need to use Variables shared in my code, and when I try to run the code I get the following error.

    My computer deployment
    Ventilation Library.lvlib\\169.254.192.23\Ventilation library of deployment deployment has failed (error:-2147220712, MAX: internal error (Hex 0 x 80040318): the customer has failed to connect on the server configuration, perhaps because the server is too busy or encountered an error of communication.) Note: the steps that you did which led to this error and contact technical support).
    Completed with errors of deployment

    The code was working yesterday with shared variables, but it won't deploy today and I can't imagine any changes that I made to do this. I tried to run the code on my cRIO and the PC. I have used amd 2015 2014 and I get the same error on all.

    Any help with this problem would be great.

    What is the IP 169.254.192.23? It looks like an auto-negotiation-to-peer (e.g., crossover) connection IP or the IP address of your computer on the network?

    Is the library with shared variables located under 'my computer '? If you right click on 'my computer' in the project - he shows here? IP address you think it correct?

    If you check the custom address 'specify' and put 127.0.0.1 (loopback IP address), it works?

    I also look in Windows Services and verify that the shared Variable service (and other services OR that it requires) are running.

  • What is the blue thing in the shared variable?

    I'm going thorough a code that has the huge set of shared variables and in some nodes, I find a blue color of brand/thing left bottom just worldwide as shown below.  What this indicates?

    Thank you

    Ajay

    I found the answers of my team member.  The blue mark indicates in fact a point and a slash ". ------"which means relative sharing Variable target."  If the shared Variable is absolute, this indication does not appear.  To learn more about the difference between shared variable absolute and Relative target, check it out here.  A Shared variable node can be established between absolute and relative assistance

    Menu popup (right click the node)-> reference mode.

    Thank you

    Ajay.

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

  • OR shared Variable engine usage example

    Hi guys,.

    using OR shared Variable engine and we try to use it with java. As we understand it, NOR shared Variables are available on the network.  So it is possible to communicate with the use of Sockets. Is there a protocol that I have to use? Any of you got an example on how to write a string to the shared variable?

    Hope this is the right forum.

    Thanks in advance.

    Greetings

    Tuney

    According to this link: http://www.ni.com/white-paper/4679/en/

    "In addition, with the network library Variable introducted in NI LabWindows/CVI 8.1 and NEITHER measure Studio 8.1, you can read and write variables shared in ANSI C, Visual Basic .NET, or Visual c#."

    There is also more information available on the following links:

    http://www.NI.com/white-paper/5484/en/

    http://StackOverflow.com/a/4597966

  • Variable shared between PC and myRIO

    Hi all

    I have a shared variable generated on a PC VI and I want to read this variable on a VI myRIO. I simplified it down to a simple generator of random numbers on my PC that updates all the 1 second and writes in a shared variable node. I then a random number (shared variable read node) receiver on my myRIO who should read this varable it updates. However when I run the two screws of the random number on the myRIO receiver does not refresh from a value of 0. Any thoughts on how to solve this problem?

    The issue only seems to happen when I try share a variable between the PC and the myRIO. If I have the receiver and random number generator communicate via shared variables nodes on the same hardware, for example on the PC or on the myRIO both the shared variable is transmitted and updated perfectly. I also made sure the shared variable engine is installed on my myRIO and the variable is set to the published network.

    I have attached a few screenshots of the dagram of block and I am happy to download the screw if this makes it easy for you guys.

    Thanks in advance!

    Ben

    Thanks for the advice natasftw, I will consider for the future.

    I managed to solve this issue this afternoon. It ends up being a firewall problem. I had previously allowed the engine variable to OR through the firewall, but that has not solved the problem. I visited this page (http://digital.ni.com/public.nsf/allkb/0D7B86F4B4D19A5E86256F9A006EECB1) and unblocked these three elements.

    C:\Windows\SysWOW64\lkads.exe

    C:\Windows\SysWOW64\lktsrv.exe

    C:\Program NIUninstaller Instruments\Shared\Tagger\tagsrv.exe

    Thank you all for your help, it is much appreciated!

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

  • SQL and shared Variable communication failure when you run an .exe application

    Salvation OR engineers,

    I'm faced with a problem. I have already tried almost everything under my bottom to solve, but I just couldn't get over it.

    I have a VI on my PC accessing a SQL database via the connection string and some share of variables in a server. Both shared variables and the SQL database are on the same server. There is a firewall between this server and my PC and the server is located in a DMZ environment.

    Design Labview environment, everything works fine. Even when I run the .exe on this computer file, everything works fine. But, when I created an application and install it on another computer, it just doesn't work.

    I'm using Labview 2013.

    Someone of you can help me with this bug?

    Thanks in advance!

    Hello world

    Back to share with you the solution:

    The problem was with the "SQL Native Client". Windows 7 doesn't have it as a default installation, if the application could not find the OLE DB provider for ODBC drivers. After installation, the connection has been established.

    As the server was within a demilitarized zone, I had to open some specific ports as follows:

    UDP/1434

    TCP / / 2343,49163

    59110-59115

    In fact, I have not experienced problems with the OAS. The error was generated when you try to connect to the database and sent to the rest of the code through the cluster of the error.

    Thanks for the support!

    Best regards to everyone.

    Luiz

  • Shared variables, analysis engine and multiple targets

    I'm looking for some general tips on my LabVIEW project structure.

    The project consists of a laptop with LabVIEW, a connected joystick and a CompactRIO connected via ethernet. I ran the cRIO mode Interface FPGA, but a change in some things causes the project to have be moved to scan mode.

    From now on, the code on the portable computer updates the shared variables on the cRIO and bed from the variables shared on the cRIO for surveillance. I want to shared variables on the cRIO because he will also need to work without the connected laptop. Before moving the cRIO for scan mode, I found that I had to first run the code of the laptop and then run the code cRIO, or shared variables would not release properly. Now that I spent to scan mode, I have to run the code cRIO first, and even then the shared vars do not properly communicate for more than a few seconds and are well laggier.

    My ideal project solution is a system that can operate with or without the connected laptop and obviously do not have these questions shared variable. I would like the autostart code on the cRIO and ask the user to execute the code of the computer laptop, if necessary, but in the past, it doesn't seem to work with shared variables.

    I'm really confused about why this is happening. I hope I explained my problem well enough. I really don't want to display the entire project here, but I can email to people if they are willing to take a look. Thank you for taking the time to read this.

    I'm under LabVIEW 2010 SP1 with FPGA, DSC modules and robotic in real time. I have the updated Feb 11 driver and NOR-RIO 3.6.0 installed and completed all updated on my RT cRIO.

    I do this kind of thing all the time...

    Move all your NSV libraries on the cRIO.  Of the project, you must deploy on the cRIO and then they are persistent until you reformat.

    Your windows GUI application, you can set static NSV tags on the block schema or use the API SV dynamic R / w.  Also you can bind GUI controls and

    indicators directly to the NSV cRIO (it's what I do) also I create a library of 'mirror' in the PC HMI that is linked to the library of cRIO.  This library has DSC Citadel

    data record enable and automatically records the historical traces of all my important data - very nice.  Libraries hosted PC can be set to autodeploy in the version of the app.

    the project also has an option of autodeploy to the development environment that normally, I turned off.  If you have a PC at the cRIO binding configuration so be careful

    on any kind of autodeployment because this will eventually force the cRIO app stop when you deploy.  To work around this problem, you can use the PSP (IP address rather than project binding

    process name) and use of the DSC deploy library s vi in your HMI application.  Once you use the scan engine, you can use the app DSM (Distributed System Manager) to view, DIF and

    each of you IOV and NSV graphic on your network.

  • cRIO and 9234 modules do not work or communicate via fpga with accelerometers, fpga, connected to the real-time application is also related to shared variables related to modbus slave

    Hello

    I have a compact rio, which has a 4 way frame this chassis is the three modules of ni9234, they are related using FPGAs for application in real time, then using shared variables in the low-speed loop associated with a slave modbus to communicate with the domain controllers, the nor 9234 accelerometers linked to them with option ac coupled iepe on c modules , my problem is the real-time application seems to work well even when power loss occurs it restarts without problem and the fpga written hard disk portable bin files very well, but without an accelerometer connected I get readings of low noise as soon as I connect an accelerometer to one of the outputs 10 it just goes to a fixed number (0.03125) as soon as you unplug it again He returned to readout noise, I ran a scan on the modules and get only a spike when I connect or disconnect the accelerometer, I tested voltage at the pins on the module and I get 22 volts CC which makes it more likely that the material is not the problem, but software is perhaps the cause to hang up, I join the project and files for your perusal. I also realized a new project which, in mode directly linked scan has the module entry in the shared variable and the scenerio even once again. Help would be appretiated.

    Thank you very much

    Jason

    Whren using waveform with the 9234 acquisition, we recommend the following FPGA and RT model.

    http://sine.NI.com/NIPs/CDs/view/p/lang/en/NID/209114

    It can be extended as a datalogger with:

    http://zone.NI.com/DevZone/CDA/EPD/p/ID/6388

    or using shared variables combined with the analytical engine

    http://zone.NI.com/DevZone/CDA/tut/p/ID/9851

    The FPGA in all this, as well as the framework of RT have used successfully by 1000s of users.  I recommend giving these a try.

  • shared variables stops when I use RT Set date and time.vi

    Hi all

    I have a problem that I can't solve. I run a project of RT on a PXI-8106 module using LV8.5. I used shared Variables to transfer data to and from my host computer for about 6 months with no problems. Recently I neeeded to the synchronization time RT with my host PC of time (to collect time-stamped data of the target RT) and I decided to use the "RT set time and Date.vi ' both before the beginning of each synchronization test.

    As soon as I started using this vi, I noticed that my shared variables would either stop updating, or slow down considerably (this includes loss of data during the transfer of data between the PXI to host PC with shared variable). I do not receive any errors or warnings from any of my shared variables, and no errors are generated when using the RT set time and Date vi, so im at a loss for where to start. Ive disabled this feature for now and my system works well again, but I want to get this to work because the timestamps generated in the data by the RT system are out and I need a method to synchronize the time with the host pc.
    Any ideas would be appreciated,

    Thank you

    David

    Thanks for the info. I'll avoid upgrading to 8.5.1 at the moment so I'll just remove the VI. Instead, I create a 'elapsed time' timestamp which should do the job.

    See you soon,.

    David

  • shared variable of mutual FUND not updated of DSC

    Hello world

    I have some problems with shared variables and the OPC Client IO server functionality in Labview 8.6.1. I have the DSC module installed as well.

    I use a lonworks OPC server a company called us. I am able to monitor my traffic lonworks successfully using this software. I set up a server of e/s of Client OPC called Lon server in my library. From there, I've added a shared variable called nvoUI [1] in a simple VI. When I run this VI, I get no errors or warnings, but I have also no output, either in the data field or the timestamp. I read a lot of documents on the forum and knowledge base, but I could not do this work.

    I have attached a picture of my setup project and in my opinion of OPC server, along with a photo of my diagram VI and the front panel. I hope someone can help.

    Thank you

    Dale Borelli

    Just to wrap things:

    I realized that my problem was multi-party.

    (1) suggestion of the cancellation of the deployment of all of my libraries deployed Charlie was a good, I got a lot of active libraries which were all referencing the same variables on my OPC server, which may have caused problems. I knew not that libraries remained deployed, a bit silly, I assumed that they were cancelled when the associated project has been closed.

    (2) I didn't know at the time, but I had several copies of my OPC server on my local machine. A copy has been started automatically in the background when I started to labview. It does not appear in the taskbar or system tray. I only found it by looking in the Task Manager.

    By cancellation of the deployment of my unused libraries and a second instance of my OPC server won't start not, I could get my shared variables to work properly. Thanks for your help Charlie.

    Dale

Maybe you are looking for