Deploy shared in localhost Variable engine

I need to talk to several RTs using the same computer. It seems
easy to deploy shared variable engine (library) in localhost instead of
RT. However, the problem is the shared variables (read) used in localhost screws
are not updated to RTs. But when I use a different local VI to update
the shared variable, it works fine. The variable path of the RT
as "\\My Computer\Local NPSVlvlib\Test
Data '. I think that this is the problem, why the values are not updated
because the RT cannot resolve the path network ("\\My
("Computer\Local NPSVlvlib\Test Data"). Also, I tried to change the shared
variable path in the CR, but I couldn't do it. Need help!

I think I found the problem. Firewall was the culprit. I disabled the firewall and it started working like charm.

Tags: NI Software

Similar Questions

  • new variable networked shared in my computer, but not in the shared variable engine list

    I have a Variables.lvlib shared on a cRIO target and test algorithms when I don't have access to material cRIO. Thought I could do a new project, add the library to the windows target (workstation). I need to add a few additional variables, I did in the original (i.e., while the library was the target in real time). Then create a new project and added the lvlib to the project (under my computer), and then wrote a VI to write in these SVs. When I let fall a constant Variable Refnum shared on the block diagram and browse for objects variables under 'Variable' Motors > ni.var.psp > localhost > shared Variables, list of variables shows everything except the 6 new variables. When I switch the view 'Current project', I get the same variables for new list WITH THE 6. However if I select the variables in the list and run the VI I get an error-1950679035 impossible to locate the variable in the shared Variable engine. Of course, I forgot something, anyone out there set me straight?

    Thanks for your time - lmd2

    Hello Lawrence,.

    Looks like you'll have to maybe just to deploy the new variables - refer to this document:

    LabVIEW Help: Making static Variables available on a network

    http://zone.NI.com/reference/en-XX/help/371361K-01/lvconcepts/sv_deploying/

    Hope that helps!

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

  • How to deploy shared to the PC remotely variables programmatically

    Hello

    I am facing a problem of programmatic deployment of SVs generated to a PC remotely (not a real-time target). Now, I have tried two approaches:

    1."add the variable to library.vi' and that the"Library Library.Deploy"method where I pointed the remote IP (I tried multiple address formats). If I have the target value IPAddress localhost or I type in local IP variables are deployed successfully.

    2. with the help of DSC: "Create shared variable.vi" and then defining SharedVariableIO Network.URL property at different addresses. However, it did not work either. In general I like this approach more because it deploys no doubt without creation of a library.

    Is there a way to do this? I looked everywhere on the internet and there aren't any examples how to do on the network.

    Another problem is I can not set the initial value of a table previously deployed with one of above approaches. But I found this option (below) on the site of NOR, so I guess I must first deploy, then connection open Variable, write variable,...?

    Thank you for the help

    Planko dear,

    You can also do is to create some kind of service on the server, which would be able to create the SVs locally, after receipt of applications by others, already deployed shared variable or same TCP message.

  • Deploy shared in the installer Variablie

    I'm having a problem with a variable shared in my application.  This application is integrated with a Setup program must be installed on a machine without labview.  After looking around, I came across this link and think it is close to what I need.  The only difference is that the link refers to an executable file, and the next step is what throws me:

    1. Use the entry path of the library to invoke node to point to the library (s) containing your shared variables. If the library (s) have been included in the support directory of the executable as indicated above, the (s) library will be copied to the folder data the executable.  The point of the entry path to the (s) library.

    Because I do not use an executable file, I don't have not a folder 'data' to point the invoke node to.  I'm sure that other people must have experience this problem and am very curious to hear how it was resolved.

    See you soon!

    As a follow-up, I found this link which can clarify the situation a little more.

    Shared variables and stand-alone Applications or shared libraries

    If you plan to distribute a stand-alone application that uses shared variables, do not include the file .lvlib in a LAW degree or the executable file. Use the page settings of the Source file of the Application Properties dialog box to change the Destination of the file .lvlib to a destination outside the executable or the LLB. You can deploy shared variables in two ways:

    • Write the application so that it deploys programmatically variable shared at the start time. Call the library to deploy method in the first level VI of the application. In the entrance to the library path of the method, use the relative path to the .lvlib file that contains the shared variable.
    • Deploy the variable shared on the computer or target engine shared Variable before running the application built manually.

    If you plan to distribute a shared library that uses shared variables, do not include the .lvlib file in the shared library. Use the dialog box properties of the shared library File Source settings page to change the Destination of the file .lvlib to a foreign destination to the shared library.

  • 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

  • Shared in Teststand variable: error-17500

    Hello

    I'm trying to deploy a shared library that contains shared variables that I use inside step (screws). But I have error-17500 poping up-to the top whenever I'm trying to deploy it (see attached photo).

    It says that I need the module "the remote execution..." Why is this?

    I tried to access all users of remote machines (as advised in TS Reference Manual) but I have error-17502 poping up-to the top (see photo 2). Is there a reason for this?

    Hello

    This problem is now known by us on TestStand 4.2.1.

    One solution would be to circumvent the TestStand step by:

    -deploy the variables shared by using a LabVIEW LabVIEW VI is installed on the computer

    -creating an application (Installer with LabVIEW Run-Time, OR Variable engine) for this purpose that will deploy the variables so there is no LabVIEW software installed on the computer.

    Best regards

  • Deployment complete with static Variables cRio-9074 network errors, pc with executable file

    Hello.

    I am building an application runs on a machine without LabVIEW development system and connect via the network shared a cRIO Varibles (RT FIFO). I can successfully create an installer and EXE for PC and a RTEXE for the cRio. When I run on my development computer, the application is able to communicate using variables shared without a problem.

    But, when I install my application on another computer and connect the cRIO, I get the following error when you deploy shared variables when the application starts:

    Initializing...

    Calculating dependencies...

    The checking for conflicts. This operation can take a long time.

    Preparation itesm by download. This operation can take a long time.

    Deployment 169.254.84.198

    Deployment VariableLib.lvlib\\169.254.84.198\VariablesLib (:-2147467259,)

    LabVIEW: Unspecified error (Hex 0 x 800004005).).

    Completed with errors of deployment

    I created an exception in the Windows Firewall configuration. I have included the library of VariableLib on the EXE of RT, outside and inside the exe file to c:\.

    I am downloading the SP1 for LabVIEW and Module RT and decided to reinstall all the software on my cRio.

    Any help will be appreciated.

    Hello Luis.

    Thank you very much for your help. The Variable engine OR has been and should be included in the intallation.

    I was able to get the application running. I installed the System Manager distributed on the PC without LabVIEW to control if the library has been get deployed. Using what I found that another device on the network use the same IP address as the cRio and so the IP address has been lying to the deployment, but the device has returned an error. I just changed the IP address on the cRio and I was good to go. I have not reproduced on both devices such as network shared Variables suggests on some positions, nor I needed to modify the ALIAS files on devices.

    Best regards and thanks again for your time.

  • Best method for updating CompactRIO data to Server "National Instruments.Variable Engine.1"

    Hi all, I have an OPC Client of third-party I want to use for testing with the CompactRIO. Can I specify 'National Instruments.Variable Engine.1' in the OPC server, create a new item of the mutual FUND, go to a variable and then see its value. I use a CompactRIO and I want to send the updated data that I am acquisitionning of for third-party Client OPC, then, what is the best method? Currently, what works, is that I created a shared variable published to network on the LabVIEW host that I dragged in the CompactRIO project. I've created a small loop increment value every 500ms. I then created on the host computer, a little VI, who issued this national value to "" Instruments.Variable Engine.1". Now, is there a better way to do his? Is it something that can automatically fill in manually the Variable of the CompactRIO motor without publishing the shared inside a LabVIEW application variables? Thank you for your time, best regards!

    Thanks a lot for your replies, Drew,.

    I downloaded the OPC UA API and it will next week.

    Thanks again!

  • Global variables or shared unique process variables?

    Normal
    0
    21

    fake
    fake
    fake

    MicrosoftInternetExplorer4

    / * Style definitions * /.
    table. MsoNormalTable
    {mso-style-name: "Table Normal";}
    MSO-knew-rowband-size: 0;
    MSO-knew-colband-size: 0;
    MSO-style - noshow:yes;
    "mso-style-parent:" ";" "
    MSO-padding-alt: 0 cm 0 cm 5.4pt 5.4pt;
    MSO-para-margin: 0 cm;
    MSO-para-margin-bottom: .0001pt;
    MSO-pagination: widow-orphan;
    do-size: 10.0pt;
    do-family: "Times New Roman";
    MSO-ansi-language: #0400;
    mso-fareast-language: #0400;
    mso-bidi-language: #0400 ;}

    Given that the
    introduction of shared variables, whenever I needed a global variable, I have
    use shared unique process variables. But I started now return to
    using the old global variable because I think that there are some significant drawbacks
    to the single shared variable. Here is the ability to search for
    case of variables and also the ability to view or change the value of
    the variable (OK, we have the variable Manager, but I found slow and)
    unstable). My question is, are there reasons to use the new single
    process variable actions on old global variables?

    Dear Terje,

    As you use only the variables on a single system. There is no advantage to the use of unique process shared on Globals variables.

    Infact a global variable uses a little less processing power that a global variable as the implementation of a shared variable single-pocess effect is a global variable with the timestamp feature.
    If you use a shared variable single process, if you don't need the timestamp feature, then disable it to use less processing power.

  • Deploy the shared target rt variable fails (crio-9073)

    I use a cRIO 9073 with LabVIEW 8.6. I have some variable published to my PC network I want the cRIO host read. However when I try to deploy the variables on the cRIO, I get the following error:

    Initializing...
    Calculating dependencies...
    The checking for conflicts. This may take some time...
    Prepare the items for download. This may take some time...
    Variables variables.lvlib\\129.186.159.84\robot robot deployment deployment has failed (error:-2147220721, (Hex 0x8004030F) the configuration database cannot be opened, perhaps because of corruption.) Note: the steps that you did which led to this error and contact technical support).
    Completed with errors of deployment

    I tried to reinstall the software on the cRIO, which includes the network Variable 1.5.0 engine and tried hosting variables on the cRIO. I still get this error.

    Everyone knows about this problem? What should I do to use variables shared on the 9073?

    I tried stubborn MAX, who did not work. Then I reformatted the cRIO and the problem is solved.

  • Causing problems of custom data type to deploy the shared target RT variable

    I seem to have some difficulty in using a shared variable published network created from a customized data type when it is deployed as an executable on a target of cRIO RT.  I'll start by describing why I think that this is the rub.  I created my RT VI in the LabVIEW (LV 2012) development environment and everything works fine.  This VI is quite simple, because these were quickly devolved into an exercise in debugging.  The RT VI begins by simply flashing the LED to a couple of times and then starts a loop simple acquisition to read some values out of the material using the analytical engine (while still flashing the LED of the user).  After reading the material, the values are grouped in a cluster and written in a shared variable published to the network defined by a custom control type def.  The custom control contains five floats double precision.  If it's important, the RT cRIO system hosts the shared variable in this case.

    So I have that deploy in the development environment, and everything works fine.  The LED flashes merrily along, telling me that the program runs correctly.  Running a VI host who reads the shared network has published variable gives the desired result.  Everything is good.

    Now, I want the cRIO system to run this simple program by itself at startup.  I build, set it as start VI, deploy it, and then restart the cRIO target.  The LED never flashing... the VI doesn't seem to work.  I'll spare you the major part of the work of debugging and access to the end.  I basically "diagram Disabled" various sections of the code up to the VI began to run correctly in an executable file.  I kept reducing the size of the disabled code until something has been disabled: the writing in the shared variable for the custom data type.

    So, I guess my question is this: are custom data types defined by type def would be personalized orders authorized executables to RT?  I read through the cRIO Developers Guide, my book of development in real time course of NOR and the white paper using shared Variables and I see nothing that forbids it.  I know that there are things not allowed in the executable files that are allowed in the development environment (property nodes façade, dialogue live, operating system specific calls, etc.), but no mention of the shared variable type custom data.  Any ideas as to why my VI is running in the development environment, but does not update unless I have delete the entry on the published network variable shared?

    Thank you in advance for your help!

    You must disconnect the data types of variables and then recompile. You can find it useful to keep on disk, a copy of the original lvlib.

    Don't know if this is a bug or not. It was suggested by someone in the forum that putting the ctl files in the right position (the disk? in the draft?) would allow the rtexe start; I did a quick check and it didn't work then I dropped the tests more far.

  • 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 library error Variable deployment-2147220735

    I had to reinstall my whole LabVIEW installation, where my SSD was about to fill. I uninstalled everything and freshly installed everything on a larger hard drive. Unfortunately, I now get an error message and am wondering what I have to reinstall.

    When I want to deploy a library shared in LabVIEW 2014 32-bit Variable, it returns an error:

    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 test.lvlib\\10.0.10.45\test failed (error:-2147220735, MAX: internal error (Hex 0 x 80040301): the specified class is not found in the configuration database.) Your installation may need to be repaired.).
    Completed with errors of deployment

    Any suggestions?

    Have you tried a repair, which sometimes works but sometimes a completely uninstall and reinstall is necessary. Have you tried to repair only the proposed below KB file?

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

    As you can see the same error in Distributed System Manager the quickest solution would probably be to uninstall LV and the drivers and reinstall them just. If the KB above does not work.

  • Cannot connect shared variable engine

    Hi all

    LabVIEW 2009 + DSC

    We have a test laptop computer on our LAN. Other developers read the values of some variables of this laptop. We now have a new developer and the computer. When we try to go the laptop computer network test, it can be found, but we can not see all the libraries. This is done by using the Distributed System Manager. PING is ok, and there is 'none' firewall or virusradars. Other developers can connect this laptop well and there is no problem. Does anyone have good advice for this problem?

    BR, Jim

    Reinstalling solved this problem.

Maybe you are looking for