Create a shared variable

Similar Questions

• "Not a valid error code" when you create a shared variable of data type custom

  I am trying to create a shared variable with a data type of a 2d double table. I created a custom control that contains a table with a numeric type for this 2d. Manager of distributed system v12 I select 'add a variable', then select 'of the custom control. Once select my control I get the following error: "invalid data type. You want to choose a different data type. Any advice as to why it doesn't work? Thank you.

  This seems to be recorded in the CAR #405941.  All this is a bit strange, but I'll try better possible workaround solutions I can.  I tested a large number of these myself, and here is what I found.

  1. make sure that the custom control you did was created in 2012 of LabVIEW or you save it in an earlier version.  If you save on an earlier version, you may also open the .ctl in LabVIEW 2012 and resave it (I needed to do).  I tried to create my own control in 2012, as well as save the control to a previous version, the two worked, but I don't end up with the same result (I don't understand this, but I wanted to mention it so that you know).

  2. it seems that you are able to make the variable shared by program by modifying the example of the community to adapt to your needs.  If you do not need to create many variables it may be the best option if it works for you.

  I would also try adding the variable of the LabVIEW project, you are working on that.  It wasn't a direct troubleshooting step but there are several ways of doing things in LabVIEW and, sometimes, one of them is working while the other does not.

  Edit: Example of community is here https://decibel.ni.com/content/docs/DOC-16863

• How can I create a shared variable to store the data of 2D image?

  I would like to store as a shared variable 2D image data, but there is no data type to do! How can I do?

  You will need to use the picture to Pixmap VI to get a set of image data that you use with a shared variable. Take a look at the other screw in the photo on the block diagram features palette.

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

• Impossible to programmatically access a shared variable

  Hello

  I am attaching a file in project where I created 2 shared variables

  When I try to access it programmatically im getting this error "error-1967362038 occurred to read Variable in Untitled 1." "vi IAK_SHARED: (Hex 0x8ABC700A) not found."

  can someone tell me where im going wrong?

  Woof...

  found the solution

  has not deployed the library file containing the shared variable

  After you deploy the library file so I was able to programmatically access a shared variable

• Can I combine global shared variables libraries?

  Whenever I add a Global Variable of shared, another library without title (lvlib) is added to my project.  I now have 11 of them!  These can be combined in a library?

  Yes.

  I don't know how you have created your shared variables.  I imagine that if you a higher level of the project, it creates a new library and a variable it contains.

  If you create a new variable by right-clicking on an existing library in the project, you will need to place the new variable within this library.

  If they are all "Untitled", this means that they have probably not yet saved.  You should be able to drag one library to another in the Project Explorer window.  Don't forget to save the final library.

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

• Can I send value cluster through the shared variable?

  Hi every1,

  I want to send a cluster through the shared variable. While creating a shared variable, there are options to choose the type of data, but there is no option to Cluster.

  But there is an option of "custom control". How to use it?

  Hi, Germain,.

  Create your control and save it as a file on your disk *.ctl. If you use the "custom control" option, and then select your control. If this does not work for your control, you can use the function 'flatten in string' to send a string.

  Mike

• How to turn RT FIFO on a shared variable for custom control

  I try to get my shared variables behave: update when I tell them of and only update once. It's the sort of 2 separate problems. Update only once should be fixed by activating RT FIFO on the shared variable. However, if you create a shared variable by using a custom control (because your data type is not available on the menu drop-down), allowing RT FIFO is not available. Why is this? Will there be an another GUARANTEED way to do this?

  Description of my goal: after having many problems with a large scale of my real-time program version, I started from scratch. My program is that the bases in order to send a signal to my goal of running on a few D/A channels, then return the data that I read A/D channels to ensure that the waveform has the same appearance. In addition, the program should be able to repeat this process without having to reboot.

  -Host is a state machine with: initialize - reset variable, check that the UI events - start target, target stop and end program, send data - to create 2 waveforms and send it to the target using the variable "data entry" (table 2D-double), data Get shared - read the entire waveform on the different channels after it ran using the shared variable "all data output" (table 2D-double) , Write to the file - (does nothing), stop - program ends.

  -Target is a loop with 2 States inside: false - target does nothing as he waits to be the host to say 'Start', True - target Gets the shared variable input data, runs on 2 D/A channels and reads the equivalent A/D channels to make sure the waveform actually ran as expected. This happens in a deterministic loop with a non-deterministic loop waiting for the command "Stop" on the host. After the written entry, the D/A signals stop and playback of signals/a. are placed in a 2D array and sent to the host via a variable shared, "all the output data".

  -J' tried to put "all the data output" in a while loop which must reiterate if he does not obtain data in the specified time-out period. I also removed the while loop but kept the specified time-out period. In both cases, data are collected twice!

  -Without specifying a time-out, the host never gets data updates "all output data" before he goes into another State.

  Summary: I need update they once when I asked to a my shared variables. I think that my program is about as simple as you can get, so I'm surprised to see why he is currently not completely reliable.

  (I have attached the vi host, target the vi and variable)

  Hi FireIce,

  To answer your questions:

  1 RT FIFOs are supported data types can be pre-allocated space. This is to keep the determinism on the RT system.

  2. reading of the variable in the loop and have the chart outside the while loop will only show the last value of the shared variable, showing actually only a single reading. Then if it works for you, it will give the same result.

  Looks like you have network buffering enabled on your shared variables. Is this true? Shared variables must always have a value, and so it will continue to contain old data to the new data is written to it. If you have buffering enabled network, new data can be added after the former, which actually look like you read the old data twice before getting the new.

• shared variable creates sound - problem, save data in crio

  Hi all

  I have a problem here...

  Why I get noise when using shared variables in my labview code...

  but when I remove these shared_varibles, the sounds are totally reduced...

  I use the shared variable for the data record. For the recording of data, I do a VI special folder under my computer. During my actual code CRIO.

  These two screws are to communicate using shared variables. Is there a better way to make the real-time recording apart from the use of shared data variables?

  I tried to record data directly to CRIO but it always fails... That's why I do a special VI under workstation for the logging of data...

  But if shared variables create sounds... my data record is no longer valid...

  Please help me...

  I downloaded some pictures... I hope that makes my problem clearly to you all...

  Hello auralius,

  Are these plots you have posted on the graph of velocity on the block diagram?

  I think that shared variables are affecting the timing of your loop and so affect the outcome.  I suggest you to add code to check if one of the iterations is late.  I suspect that the end iterations will correspond to the bad data that show you.

  You can try to enable the RT FIFO on the shared variable or you may need to add a second loop of communication and use a form any local communication to pass data to it.

  Take a look at http://zone.ni.com/reference/en-XX/help/370622G-01/TOC1.htm, including the sharing of data in deterministic Applications section for more information.

  Let me know how it goes,

  Sebastian

• 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

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

  Hi all!

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

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

  Best regards

  Marko.

  Marko,

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

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

  I hope this helps!

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

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