Shared variables is deployed several times

Similar Questions

• Shared variable library deployment error

  Hello

  I'm having a problem with my variable shared library in the .exe deployment.  I installed my two individual computers to request one.  We my library is as it should be and on the other, I get an error message, as shown below:

  

  Here's the code the error occurs in:

  

  I checked the path and name, and they are the same on both computers, i.e.:

  

  The two computers are new and have had just my app installed installation I built and as I said at the beginning one of the systems very well so all that is needed is to be installed.

  Both computers are Windows 7 64 bit. My application has been developed using LEVELS and Distributed System Manager 2010 is installed on the computers.   However we have installed windows Dell and the other made by my IT department using our brand Image (which is the one that does not).

  The only thing I've tried is to disable the firewall and adds indicators on the front panel to show me what was entered for a path and a name.

  I've also attached the my library file.

  I read a few on the other posts, but there seems not to be a consensus for the resolution of the problem and they have been since 2008.  I hope someone can give me a solution to this problem.

  Terry

  It is a follow-up to the solution of my problem.  I discovered there was a problem with the installation with this computer.  In collaboration with an Application Engineer of NOR, I was asked to perform a forced relocation of my request and this has solved the problem.  Here is the link on how to do it.

  http://digital.NI.com/public.nsf/allkb/ADD22E807D5A12AD862579EC00760F79?OpenDocument

  Terry.

• How to use the shared variables to address several Watlow controllers on the same COM port

  Hello

  I am using LabVIEW 2010 to control 4 Watlow temperature controllers on a port com 3 are model 96 and 1 is a zone EZ controller. The controller has a unique modbus address and I'm trying to read from and write in the individual records (for example, setpoint closed-loop) variable shared help. I would return the data during playback (even if the data is displayed as invalid), but I am unable to change the value in the registry in writing. How can I be sure that's the Modbus server send commands to the correct controller?

  Chuck

  Hi Chuck,

  Sorry for the delay in response, I was away last week. You can create as many servers for Modbus on one COM port that you would like, the only problem you'd see is if you tried to call the port from different locations at the same time. With respect to the documentation to cross, I'd start with the tutorial below for a comprehensive manual of Modbus. There are also quite a few listed under Datalogging and supervisory control Module help topics that may be useful if you want to solve specific issues.

  Introduction to MODBUS

  Kind regards

  Peter W.

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

• Shared variable RT FIFO (multi element) - read both

  Hi all!

  I'm trying to collect data from analog inputs on my cRIO with a time step of 1 second. For this I use a timed loop and a variable shared with RT FIFO active (several table of doubles). Along with the timed loop, I also use a while loop that is significantly slower (lets say 10 sec period) who must read all the berries stored in the FIFO and write it in a .txt file (everything is run locally on target RT). Is it possible to empty the shared variable RT FIFO at the same time, and if not how can I get a number of tables that are currently stored in a shared variable?

  What is the difference between one created using the palette of FIFO of Real-Time/RT and RT FIFO created by a shared variable? I prefer to use the shared variable instead of Real-Time/RT FIFO allowing also time stamp.

  Best regards

  Marko.

  Marko,

  We recommend that the nondeterministic loop run faster than your deterministic loop and remove samples when they become available. If you don't want to do this, you can simply place your RT FIFO loop for the value to perform 10 iterations and then put that in your loop. For more information about the differences between the RT FIFO and Variables shared with RT FIFO active, please see pages 32 to 35 of the CompactRIO Developers Guide link below.

  http://www.NI.com/PDF/products/us/fullcriodevguide.PDF

  I hope this helps!

• shared - variables multi-network

  Hello

  I have problems of publication of multiple variables shared in a network configuration to the correct network. (NIC1, NIC2, wireless)

  I followed the info in Spreading of Variables shared for a specific network adapter

  For a Windows-based system:
  If one does not already exist, create a file in the C:\WINDOWS directory named logos.ini and add the following lines to the file:
  [LOGOS]
  ServiceBindTo=XX:XX:XX:XX:XX:XX
  where XX:XX:XX:XX:XX:XX is the MAC address of the Ethernet card to want to bind to.
  

  Right-click on My Computer within the LabVIEW Project Explorer, click on Properties. Under the General tab, click the Specify Custom Address checkbox, and enter the IP address of the network card that the shared variables will be deployed to.
  

  but it comes to 8.2.1 - is still topical for 8.5?

  After these changes my shared variables always deployed to the default (wireless)

  I am running XP on the computers and LabVIEW 8.5

  Hello Al,.

  I think you may need to change your default interface card just.

  Here is an article that should help you further:

  http://digital.NI.com/public.nsf/allkb/FB4B94AE226BEA2986257559006D0FF1

  And also, point number 8 on this refers to a similar route of troubleshooting:

  http://digital.NI.com/public.nsf/allkb/6E37AC5435E44F9F862570D2005FEF25

  I hope this helps.

  Let me know if the problem persists.

  Kind regards

  Michael S.
  Technical sales engineer
  NEITHER UK & Ireland

• Do not access shared variable

  Hello

  I have a host (exe) application that uses variables from shared network to read the values of an RT application on a target of cRIO (exe all built with LV2010). The host application uses a method node to deploy the shared on RT target variable library. As I run this application on the pc where I have the development system, it works fine... when I put the application on a pc with the LVRunTime only, get a strange behavior: node library method does not return an error with the Distributed System Manager, I see shared variables actually deployed on the target... BUT the application of the RT is unable to update the shared variables!

  At first, I thought there was a problem because the target RT boots until the library is deployed by the host application, but it works on my development pc. So what don't understand me?

  Thank you for any clue,

  I'm sure that you can not deploy the hosted cRIO SV programmatically. This must be done by the project.

  Try to start over again, cancel the deployment of all libraries in the project and redeploy it manually.  Remove your method "deploy".

  and then check that your RT code is updated the NSV using DSM.  Then, try to read or write of NSV from the host application.

• shared variable LAN configuration

  Hello everyone,

  I have a problem with deployment variable published network share and I hope that the experts of Labview in this forum could help me.

  I'm contacting a compactRIO (IP 192.168.10.100) via the published network shared variable. 32-bit LabVIEW version 2014. CompactRIO is AES.

  On the target, computer laptop, there is a port LAN (the usual) and it is used to connect to the internet with the IP (for example 10.115.22.200). There is also a USB adapter to ethernet, and it is used to connect to the compactRIO using IP 192.168.10.10. I am able to ping the compactRIo of the laptop.

  I called up the Manager of distributed system, but I couldn't see the compactRIO. I could see all the other devices on the 10.115.22.200 network.

  My question is, is it possible to set up a laptop with two IP addresses (192.168.10.10 and 10.115.22.200) with different subnets? I suspect that this is not possible and this is the reason why I do not see the compactRIO.

  Thanks in advance for your advice.

  chati

  Yes, shared variables are deployed.

  There is a solution. Apparently affecting USB) 1 Ethernet adapter to the network of 'Home' and 2) gateway defaults to the IP address of the cRIO, solves the problem.

  Thanks for the suggestions and the entries of Sam and natasftw.

  Your

  chati

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

• Deploy shared Variables

  I'm having a problem with the help of EVS. I use LV 8.6 (impossible to pass to 2010 at this hour, must "make it work").

  I used before shared variables with a GUI and PXI, but my setup is different now:

  PXI (called target) that "speaks" to the different controllers via Modbus TCP/IP. Separate interface for PXI PC to provide a user interface (called my host).

  I ran across messages spoken by calling the library method to deploy in the first level VI of the application. I want the PXI to deploy variables shared, because it will run constantly and the PC is optional. "Manually" transfer the shared variable library, in this case called the NetworkVars, for PXI so the PXI application can find? PXI will run independently once the program is fully developed.

  I have used Labview for a long time but have never had to do a lot with networking and sharing.

  Thanks for any help.

  I ended up upgrading to Labview 2010 and now everything works as it should. I will mention that it was a complete horror show trying to upgrade... including duty reload WinXP on my development computer, because the files have become corrupt. Now, I have to charge a ton of programs, at a later date, because they are there but are not related. Fun stuff.

  Thanks for all the help.

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

• Deployment of shared Variables failed

  Hello

  I can't deploy a shared variable.

  I get the following error when executing my exe.

  Initializing...
  Calculating dependencies...
  The checking for conflicts. This may take some time...
  Prepare the items for download. This may take some time...
  My computer deployment
  Deployment deployment failed shared Variables.lvlib\\192.168.1.109\Shared Variables (error:-1967362042, operating system and Network Services: (Hex 0x8ABC7006) could not start service.).
  Completed with errors of deployment
  You want to run the application in any case or abandonment of execution?

  I tried to google the error code, but my search has been unsucsessful at the moment. Has anyone encountered this particular error? It would be useful if he said what service especially could not be started!

  Any help would be greatly appreciated!

  Thnaks for the research,

  Iain

  Welcome to the world of partially useful LabVIEW Error Messages (even if they usually Microsoft beat by a mile here).

  What version of LabVIEW you run?  It is the only version that has been installed on your PC?  [The reason for seeking it is me and others, have experienced the installation, say, LabVIEW 2015 on a system that has already LabVIEW 2014, something that is "legal" and should work, but during the Installation, OR HHT are stop and restart not.]  [A single Service, necessary for the operation of shared Variables, is the Variable Service NOR].

  In fact, while composing this Post, I went to my Services (because I wanted to be sure to specify the correct Service), to see that the Service is missing (again) and (again), the shared Variable engine isn't available.  Indeed, I get exactly the same error message.

  So here's how I'm going to (try to) fix.  I will go to the Panel, programs and features, National Instruments and will repair LabVIEW 2015 (32 bit).  I expect this process to take about 30 minutes (if I'm lucky) - I'll post my results here...

  Bob Schor

• Receive 2147220696 error message when you deploy shared variable library to cFP-2200

  Does anyone know what is this error and how to solve the problem?  I have LabView2010SP1 on my laptop and FieldPoint 6.0.7 with WIF as ADDon-Aug2010 on the CFP. Attached is a snapshot of the error screen.

  I have worked with Kellis Application Engineering and she determined that the shared variable engine had not begun on the CFP.  She had me reformat the CFP, reconfigure and reload the software of the PSC.  After that, I was able to deploy my variable library shared to the CFP.

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

• Shared variable refuses to deploy correctly!

  My problem looks like one that has been met before, but without good answers on the documents OR or the forums. When you try to run a VI that deploys shared variables, I get an error that the shared variable engine was not found. This seems to be almost at random, because I was able to deploy perfectly shared variables. He could have when I rebooted my computer this problem started to occur.

  I tried to disable the firewall, which had no effect. LabVIEW 2009 reports the following when I try to start my VI:

  "LabVIEW: (Hex 0x8BBB0005) Impossible to locate the variable in the shared Variable engine."  Deployment of this variable may have failed.

  This error or warning occurred when writing the following shared Variable:
  \\.\fake_data\flow_sh
  \\.\fake_data\flow_sh".

  I will include all relevant files so that you can see exactly what I'm doing. The purpose of the fake_data program is just to practice using shared variables, very simple. Thanks for any idea that you can offer!

  my shared variables work once again, I just open cmd.exe and typed:

  net stop "national instruments variable motor.

  followed by

  net start "national instruments variable motor.