Shared variable refuses to deploy correctly!

Similar Questions

• 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

• Unexpected error from a specific shared variable in RT PXI

  Hi all

  Basically, I have 2 screws, one running on a PXI system, lets call it PXI.vi and the other on the pc, GUI.vi

  I started to test my request a few days ago and after 3 hours of running, I got the error in the picture.

  1073807339 error occurred at the VISA write to PXI.vi

  Reason: "timeout expired before the operation is completed."

  Then immediately also this error:

  "Unable to locate the variable in the shared variable engine. Deployment of the variable may have failed. »

  I restarted the PXI and started the test and it happened again after 2 hours.

  Even before the third time.

  It is always 2 items that cause this problem. They are used to pass information about the error happening on an instrument.

  So in fact they are not yet used to give the message.

  I have check them in a loop every second.

  They are not stored. I initialize them at the start of the vi

  I'm using Labview 2011 and windows 7

  I thank in advance or for your time.

  Hello

  I guess you already checked those links, which explains the source of your mistakes:

  http://digital.NI.com/public.nsf/WebSearch/E4F90AD24DEC9CC786256F4300605C02?OpenDocument

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

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

  If it is authorized by you, you could also download your code, then we can take a closer look.

  Concerning

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

• 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

• Shared variables is deployed several times

  Everyone has experienced problems with an application in development mode (LV2015) from deploy shared variables whenever it loads a VI?

  He suddenly began to arrive, and I don't know why or what I did. Now it charges 11 times before can run the application. Very annoying and I can't find where to select a VI not deply its Variables shared. Deploying them should suffice

  It was only a matter of time. I have a main VI calling several other VI that uses the same shared variables to communicate with each other. It translates the same loading variables each time the main VI called the next VI on startup.

  Solution was to right click on my computer in the project and check the option 'Disable Autodeplay Variables'.

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

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

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

• to connect to a shared variable (android)

  Hello

  I just started to learn how to use the dashboard data Labview for android.

  I made a very simple project, with a VI that generates random numbers. I also added a variable published network shared in this project, and I write the random number generated for this variable shared every second.

  I would like to read this value on my phone (Motorola Razr i, Android 4.1.2) android using the dashboard of data for an Android application.

  I have a wireless access point and both my laptop (that hosts the project, LabView, Labview 2013) and my smart phone is properly connected to the wireless router, and both gets from dynamic IP addresses.

  I start running my VI on the laptop and the variable shared within the lvlib correctly deployed and began to broadcast (I guess) its value to the network.

  I start the DD application on my Smartphone, I choose 'Connect shared variable to', I type the local IP address of my laptop, which is 192.168.0.100, and I try to connect.

  After some 'research' and waiting, I get a message "connection error".

  Do I did wrong?

  Thank you much for the help.

  Best regards

  
  

• Network shared Variable breaks rtexe

  I have a cRIO-9063 which I want to use for the control (PWM digital output for pumps signals) and measurement (temperature and voltage) of a system. In the ideal configuration the cRIO would be able to take measures and rebroadcast to a PC for monitoring and logging. The PC must be also able to change the digital output PWM on the cRIO lines. The cRIO should be able to continue to operate when the PC is not available. To do this, I use Scan interface for data acquisition and shared variables (single editor, no RT FIFO) hosted on the cRIO for network communication.

  I have developed the code for the target cRIO as well as my host PC meets my criteria. However, this code only works in development mode. When I try to build and deploy a rtexe on the cRIO, it does not work. I reinforced to the back and made a simple LED flashing user vi, ensure what I create and deploy properly. Slowly adding things to this flashing vi, I discovered it's shared network variables that break the vi once it is integrated into a rtexe.

  After flipping through other-related posts, I'll include the following:

  -There is no object on the remote VI front panel. Simply add a variable node shared is enough to break the vi (when it is deployed).

  -J' tried including my shared variable library in support of the construction directory, but what I saw there is not copied during construction or deployment. I manually copied the library to the /home/lvuser/natinst/bin/data / directory on the cRIO, then used an invoke node to deploy the cRIO variables when the software starts first. Even when you include a delay of 10 seconds after the invoke node, it did not work, just a mistake of 1043 at "the method or property is not supported in this version of LabVIEW."

  -NSV is referenced as absolute

  Some details of my configuration:

  LabVIEW 2015

  cRIO 15.0

  NOR-RIO 15.0

  Communication via ethernet, static IP

  Any help would be GREATLY appreciated. I suspect that I forget a few minor step or detail, otherwise am poorly understand exactly how and when shared network variables are deployed.

  I found shared to not be worthwhile over the years network variables.

  The RT EXE is not able to use the library to deploy to deploy the shared Variables.  See Help topic: http://zone.ni.com/reference/en-XX/help/371361M-01/lvprop/app_libdeploy_library/

  In general, SV are deployed once the project and they persist through reboots of the RT system.  In general, you should have a startup routine that checks the shared variables and expected for there to be without error on a node of the OAS and then move on to the rest of the program, defining the commissioning of values and check that they spread in the engine of the Variable is a typical method.

  See here for more information on the deployment of a variable in an application of the RT.  http://digital.NI.com/public.nsf/allkb/990508969805A7C086257619007189E7

  The section deployment of Variables shared in a real-time (RT) target running Headlessly is downstairs.  Because you are connected to an HMI PC, you should be able to use the library to deploy feature of the PC code targeting the cRIO.

  Usually, it's a faster, more scalable solution to replace your shared network Variables with a stream of network dedicated to the HMI and another for HMI - RT EXE commands.  You can send complex structures such as a cluster or even define the message as a cluster of enum and variant type to be able to use the Enum to convert the variant correctly according to the Enum value.

• There is no chance to install a standalone engine shared Variable of EVS?

  Hello!

  I wrote a small application that reads the values of a NetworkVariable created on the local computer. The address of this variable is something like \\127.0.0.1\System\test1

  That I can see, I can use this type of variable (I mean System -based) that if I installed an EVS (by Measurement Studio). But to install Measurement Studio, I need too Visual Studio...

  There is a way to work properly with NetworkVariables based on a system without having to install everything as I said before? AES is responsible for the correct operation of NetworkVariables? In this case, is there any chance to install a standalone engine shared Variable of EVS?

  Thank you!

  I found the solution to help NI MeasurementStudio 2008:

  Server deployment

  In this scenario, you must deploy the motor Variable shared to another machine that plays the role of the server. To deploy the shared Variable engine, you must run an installation on the target computer. The required Installer is installed with Measurement Studio for the [InstallDir] \ Redist\NINETVARSERV folder.

  You can view all the command-line options to run the installation program with setup.exe /? . Command line options, you can choose to run the installer in silent mode.

  You can use the Variable Manager to create and configure network on the server variables. The variable Manager is installed by default. To run the Setup program without installing the Variable Manager, run setup.exe /prop VARMANEXCLUDE=1 command. To run the installation program of engine Variable shared in silence and without the Variable Manager, run setup.exe /q /acceptlicenses yes /prop VARMANEXCLUDE=1 command.

• Properties of shared variables

  Hi all... I'm looking for a tutorial or article knowledge base explain the following:

  Use: Labview 8.6 Professional RT, none module DSC (impossible to spend right now, no funds available)

  System: PXI (called targets) communicate with various instruments and a PC (called host) by TCP/IP. operator enters variables of control through Labview program separate running on PC (XP).

  Background: development of the Labview project from version 4.3, made only another project of RT PXI, who communicated with an HMI via Modbus.

  Question about shared Variables: on my last project of RT, I had to 'read' all shared in the PXI program variables before you use them so that they would be 'available' to the HMI. I don't know that I'm creating variables properly now:

  Set up the 'network Variables' on the PXI system with the following properties - Type: network has published, the network: use buffering, the number of elements: 1, RT FIFO: enabled, the number of items: 1, FIFO type: single element

  Side host, I defined the same variables with the following properties: allow Aliasing and link to: URL of the PSP.

  It seems that I have to set the same properties as the other variables: network: use buffering, the number of items: 1, etc.

  What is the correct way to do this? I read a few posts on the problems of "deployment" variables, if the program PXI or the program host is and such. I saw one or two things 'flipped' passes, is not up to date variables. I just want if sure I do this correctly. PXI will always control if the host program does not work.

  Thanks for any help and I will continue to look for more information. And, just to remember, there is NO money available to upgrade my software now.

  
  

• Modification of the data types of the custom shared variables

  My application includes a library containing a number of shared single process variables. I use type defs to create the shared variable "of the custom control." I know that shared variables do not-automatic update since the type defs, so I'm updating shared variables (data type, do a right click, properties) whenever I update the type definitions.  However, if I make a change to a type design that does not change the data type, for example to change the labels controls, these changes will be reflected in the shared variable.  The data types of variable window shared list contains entries for each previous update, which indicates he uses the previous entries.  How can I make the window of properties of shared variables 'forget' my previous defs type wandering without deleting the variable total? Withdrawal and replacement would be troublesome because the done variable references throughout my project.

  Thank you

  Wes

  The variable is not in the Distributed System Manager, or Manager of the Variable, and cancellation of the deployment has not been resolved.  However, I found Labview from closing completely and reboot clears the memory of the previously used custom data types that sees the library.  Thus, the effective workaround I found is:

  1 make a significant change to the data type of the type (per your suggestion) FED. Record.

  2 - redefine the variable screw-notice type FED.

  3. save the project. Close and restart labview.

  4 - the old def type is now disabled.

  5. return the significant change of the def type, implement trivial change and save.

  6 redefine the variable using the type correct now def. Viola!

  Thank you!