Shared variable library deployment error

Similar Questions

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

• Library deployment error

  Hello

  I want to use shared variables (network or a single process, does not matter), to communicate on the same PC two exe.

  Everything works fine with the development environment. Things are not so good, if you use exe.

  I found this useful link on the site OR (in french)

  http://digital.NI.com/public.nsf/allkb/67D0ED29F6FE8E6D86257538003436B2

  but when I use the method of library to deploy in the exe, I get an error 8 (you do not have the required permissions)

  Thanks for your help!

  Phil

  IT a problem with the Vista firewall...

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

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

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

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

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

• 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

• 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 variables with touchscreen of TPC-2106

  I can't work with a TPC-2106 Touch Panel shared Variables.  I am hosting a Board 9642 sbRIO variables.  I built a test VI to run from the hard drive, and I can edit and read variables that VI.  When a generation a VI to run it on the touch screen works, but he can't read or write on all shared variables.  No error is shown during the execution of the VI.

  It seems that I is not need to take special steps to install support for this version of touch panel by: http://zone.ni.com/reference/en-XX/help/372507A-01/lvtpcgsm/tpc_install_sharvar/

  I tried the "Shared Variable.lvproj" sample project that is supposed to generate weather information and then transfer it to the touch screen.  The weather data are generated and displayed by VI on my PC.  The VI on the touch screen works, but never any weather data updated.

  I use LabVIEW 8.6 with touchscreen, FPGA and real-time modules installed.

  I have the touch screen connected via an Ethernet cable directly to my PC.  I assigned an IP address to the touch screen manually.

  Problem is solved using an Ethernet crossover cable instead of a standard cable.

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

• CompactRIO RT (:-65589) error code: error or warning occurred when writing the following shared Variable)

  Hello

  is anyone know this error Code:-65589?

  This error says:

  Shared in environmental_logger.vi variable
  This error or warning occurred when writing the following shared Variable:
  CompactRIO Target\Mod2\DO1 \\RT
  \\localhost\Mod2\DO1

  My cRIO9073 has 3 modules:

  MOD1: 9203 HAVE,

  MOD2: 9472 DO,

  Mod3: 9265 AO.

  When I delete all States and run only the first "init" State where I put DO0 = true and DO1 = false, I get this error. What could be?

  I think we need more information about your project - you can take a screenshot of your project LabVIEW RT target and the location of the shared variables? What is the configuration of the shared variable? Do you use the cRIO Scan Engine or FPGA (or both?)? How you deploy your library of variables? You should also zip to the top of your project and join, if you can.

  Here are some articles about the possible causes:

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

  http://digital.NI.com/public.nsf/allkb/7B52091D2FFA01EC86257C32005DF935

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