to connect to a shared variable (android)

Similar Questions

• shared variable Android

  Hi all

  I have a problem with the shared variable and labview android app.

  I create a basic while loop IV and a random number with the shared variable. Now I deploy all the variable and I have this message:

  Initializing... Calculating dependencies... The checking for conflicts. This may take some time... Prepare the items for download. This may take some time... Deploy my computer deployment Untitled library 1. lvlib deployment Untitled library 1. lvlib1\DDVariable1 DVariable1\\10.211.55.6\Untitled library deployed. Deployment completed successfully

  now I open android app, select "connect to the shared variable" and insert the IP 192.168.0.2 (ip address of my pc where run labview), but the connection fails... why?

  my ip address of the router is 192.168.0.1 and my smarthphone is connected via wifi in the same network.

  
  

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

• Executable does not connect to the hosted PXI shared Variables

  Hello

  I'm developing an application to run with RTE 8.2.1 on Windows XPe machine. Data are passed through network shared Variables in a target RT PXI. I developed on a laptop with the top Suite Developer Pro and everything works wonderfully here. When I create a program installation (and an EXE version) and on the port to the XPe machine, variables don't connect with each other (as seen to drag the control to the public Service, view the small arrow to the right to the status of the connection). I think it's due to not having the right drivers on the target XPe. Do you have any suggestions as drivers that I should include in the installation properties? I currently have:

  OR LabVIEW 8.2.1 RTE

  Engine OR Variable

  And NI-DAQmx is already installed on the machine (I think... a previous installation, the wizard sees a newer version about this than what I'm trying to install). I have also included the library with the shared variables in the properties of the EXE in the part of the Support files.

  I know this is a very old version of LV, but if you have ideas, or things to check, I would be very happy to help.

  Thank you!

  I understand the problem!

  In the structure of the Project Explorer files, I had included the buttons under the heading of the library (HMIvariables.lvlib), with the rest of the variables. I guess when you try to deploy by programming, he's trying to deploy the control files and get the dreaded error 1. I moved out of the library control files in Project Explorer and it fixed the issue and deployed the library, as verified by the Manager of shared Variable.

  I got 1 Core 3, and on the RT 1 and 2. Nobody never mentioned against it and could not find any documentation talking about do not do. I hope it helps someone else!

  Thanks for your help.

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

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

• Update of address of the card "shared Variable.

  Hello Experts!

  I have a question about shared variables:

  Now I create a variable Shared (81O_G01) in the library, and it is related to:

  My Computer\SVCREATION.lvlib\Modbus1\410611

  Question is: How can I change this address SV (410611) when tha variable has already been opened?  is this possible?

  Thanks in advance!

  Anibal

  Hey Anibaldos,

  Looks like you're trying basically change the binding of a /A1 to /A2 variables at run time. I think that there are a few options for this:

  (1) in LabVIEW DSC, you can access a hosted variable and change the link address by using a property node. If you run the server modbus on a windows machine, this is the best option. Otherwise, I'm guessing you don't have a DSC. If this is the case you can always edit links by editing the library manually, but it seems that this will not help you.

  (2) it may be possible to open a variable connection shared using pallets (Data Communication > shared Variable) to this specific address, to which cases you have no need to use the shared variable. You can simply open a connection to two addresses different modbus and read one or the other as needed.

  (3) if #2 does not work, then I think you can still use datasocket API to perform such an operation. There is a bit of research you need to do to use it (for example, URL editing and UI thread problems), but it does not work. In my opinion, this is the approach taken by this document: https://decibel.ni.com/content/docs/DOC-13508 (I know from experience, you have to dig a little to find the screw, but they are there).

  (4) you can use the Ni Labs library: http://ni.com/labs

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

• Question about different types of shared variables

  Hello

  I'm trying to use shared variables to pass data between several screws but I do not understand the types. Like, what is the difference between unique process and publish shared network variable?  Also between absolute and relative target.

  I've been thorugh all the post, PDF files, and links. But everything seems vague, at least for me. Anyone can share ideas in a simple way? I mean the absolute basics. What I'm trying to do is move some data to host VI to myRIO VI.

  (I won't use the global variable because I might need to transfer data over the network in the future.)

  Thank you.

  Absolute run on the target in which you created the shared variable.  So if you created on your myRIO, then everyone should point towards the myRIO to access this variable.

  The target always connects to the variable on the target your VI is running.  Target-parent can only connect to the variables on the same target.  So if you put the variable on the myRIO, your host will not be able to access.

  So in conclusion: you want a variable absolute shared on the network.

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

• Delay weird read shared variables

  Hello

  I'm working on a project were I am followed a few lines of production. I use an OPC server on the DSC module to connect to PLCs on the production line and I created variables related to my labview tags of the PLC project.

  On my project, I have a main VI were I show information on production lines and I can access several subVIs were I see more information on these lines. Then I a VI that runs in the background were I read about 50 shared the PLC variables and where I save data in a MySQL database, data entry of data on the database of the Citadel and the recording of alarms.

  The problem I have is that I noticed a delay read variables that read weight of containers from the production line the VI that runs in the background. It seems that all shared variables suffer no delay, only the variables weight start to make some delay when the values are on the rise. It also seems that when I run only one VI, without running the main VI, there is no any kind of delay. I read shared variables shared as variable nodes.

  Can someone help me understand what is happening and how can I fix this delay? The VI that runs in the background is time critical and a strange delay like that messes up my data.

  Hi Mateus23,

  The shared variable has various capabilites buffering, including integration with real-time FIFO functionality in LabVIEW Real-time.

  I guess that buffering settings are causing the unexpected behavior.

  Check out these resources:

  Buffer Network-Published static Variables (white paper)

  Properties shared Variables dialog box

  - Network Page

  - Page FIFO in real-time

• Support of the shared Variables in the third part XP embedded based of PTC?

  I sent a request in an embedded XP touch function (third party). The application works very well, but hosted on a RT (sbRIO Board) shared variables are not getting updated in the app on PTC

  1. the PTC is part of the project as a Windows XP Embedded Touch Panel

  2 NI TPC Service has been installed on the PTC and the application can be deployed remotely from the PC development via ethernet. (Where network connections and communications are OK)

  3. using distributed in the development computer systems manager, I can see that the shared variables are getting updates on the network

  I think that the problem can be solved if the following programs are installed on the TPC

  A. Support for variables that are shared for XPembedded

  B. shared Variable engine

  I tried to install the support of variables shared Program Files > National Instruments > Labview 8.6 > PDA > utilities > Variables > x 86 - but I get an installation error "cannot find the application for the Pocket PC applications Manager.

  Shared variable engine was installed from the ve220 folder. The program is installing. But the engine Variable is not start Control Panel > administrative tools > Services, Xpe, the service is stopped and cannot be started. When I try to start the service, I get the following error on PTC

  "Cannot start Service engine of National Instruments Variable on the local computer."

  Error 1053. Service has failed to demand launch or timely control.

  Please suggest solutions to the addresses above or another of the following:

  1. support of variables shared for XP built-in PTC

  2 Installer engine Variable shared.

  Thank you

  Krish

  Problem solved!

  Update for interested people working on XP Embedded PTC

  Just to ensure that shared Variables were indeed accessible to the TPC, I wanted to install Distributed Systems Manager 8.6 on the TPC. However given that the TPC was only 1 GB of DOM (disk on memory) and with all the software that I had tried, there remained only a few megabytes on the system. I had to add an another DOM of 2 GB.

  All products in the Installation went well, with the exception of the Logos NOR (Version 5.0). Logos OR installation has failed repeatedly.  I tried to install NI Logos separately, with the same results. Then I had this intuition that NI Logos had anything to do with the question.

  Then, I downloaded the new version of NI DSM 2009 SP1. Even if it were to settle on any fresh system without Labview, the installation would not proceed beyond the stage of configuration. I tried to install NI Logos of the folder on the download of new products separately and it worked magically!

  Once the new Logos (Ver 5.5) installed, the Shared Variable engine starts automatically and the shared Variables are finally unleashed - free stand up and shine! I thank Almighty God!

  On the lighter side, come to think of it - to run an application about 400 KB, we need NEITHER of Run Time, XP embedded, DSM, Logos...  (around 900 MB). Can make us everything simpler?  Invite your comments...

  Thank you

  Krish

• network Publish shared variable

  I'm hosting the OAS of a sbRIO engine, developing with LV10.  I share an array of Boolean values on the sbRIO and I need to be modified by (1) the sbRIO by programming the control array, and (2) a LV GUI running on PC graphically (i.e. option boxes).  I share the table and PC HMI can connect and view the States of the button as established by the sbRIO, but when I try to click on one of the radio buttons, the sbRIO seems to outweigh demand and turn the reverse button (I know demand is through, I see a very rapid change in the State of button/table on a temporary HMI connected through the sbRIO project).

  Do I need a separate shared table for applications for PC/HMI that I must then analyze via w/Combinatorial logic and find the changes then send updates until the sbRIO to write in the "master" control programmatically array?  Or is it a type of feature for arbitration to a shared Variable NP?

  THX

  Hey Atlas,

  This looks like a problem that arises from the conditions of competition, access to shared variables. You always read or write variables in a loop on each application? If the Boolean values are poised to the HMI, you must use a "send" or the "write" button that writes to the shared variable. If the HMI application is constantly reading and writing to the shared variable, you can overwhelm network variable motor and see problems like these. If you still have problems, feel free to post your screws or block diagram screenshots so that we can see what you're doing.

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