shared Subvi FPGA, variable functions

Similar Questions

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

• Shared data varying variable published network write error

  In my project in real time, on the VI host running on my Windows PC, I try to write in a number of published network shared variables.  All these write operations are successful (which means that I can read them on the RT target, then a cRIO-9012), except for these shared variables network-published with data type defined as Variant.  I'm not sure what is causing the problem.

  I take the table of clusters shown here...

  

  .. .and going through one "in Variant' VI and then subsequently in writing to the shared variable (data type: Variant).  Diagnosis of the failure of the VI in real-time to read the data, I found that variable writing shared on the host VI produced the following error:

  Error - 2147467259 appeared to Variable shared in the PC host TTS CTRL.vi

  Possible reasons:

  LabVIEW: Unspecified error (Hex 0x80004005).
  =========================
  System OR Configuration: Various operating default (Hex 0x80004005).

  This error or warning occurred when writing the following shared Variable:
  Shared \\My Computer\Network Variables\TC trust Array Group - network
  Shared \\128.144.90.143\Network Variables\TC trust Array Group - network

  .. where 128.144.90.143 is the IP address of the PC.

  Any thoughts?

  Sean

  I saw this post, and when I found myself with no other option, I have redefined the variables in question to the string data type and replaced all the "to variant" and "given Variant of ' functions with functions 'Flatten channel' and"The string Unflatten"respectively.  Initially, it did not work - functions "Chain Unflatten" would produce error 74, until I realized that the "data includes array or string of size? (T)"input on each 'string Unflatten" function must be set to FALSE. Wiring a constant false for each instance of "Unflatten to the string" seems to have corrected the problem.

  I have still no idea why wouldn t Variant.  Shared variables Editor allows to define a variant data type, so I guess it's supposed to?

  Sean

• Getting a shared list of variable references

  I'm working on a project of data acquisition that will use AES. This is really my first foray in EVS, and I hit a stumbling block.

  I'll use a loop for distributing the waveforms acquired at their appropriate variables (DAQmx read Nsamples, Nchannels, 1 d of DBL waveforms, each waveform of the GET it's own variable.) "Get Shared Variable List" returns a list of variable names, but the Variable 'write' requires a reference to a variable. How can I go from one to the other?

  I've posted an excerpt of what I have so far.

  -Ian

  It seems that you're dealing with two categories of variables.  The origin of the palette of DSC function and returns what looks like an array of labels of DSC.

  The purple thread says it's a network variable (tag BV), but the hook upwards a property to that node and the class is SharedVariable IO.

  Your other function leaves the Variable Communication/Shared Data palette and just says it is a variable.

  I'm not sure it would work as I have no way to test it.  But if you use the node name property of the SDC tag and use it to open a reference to a shared variable, the son all connect without errors.

  

• global variable functional to read and write data from and to the parallel loops

  Hello!

  Here is the following situation: I have 3 parallel while loops. I have the fire at the same time. The first loop reads the data from GPIB instruments. Second readers PID powered analog output card (software waveform static timed, cc. Update 3 seconds interval) with DAQmx features. The third argument stores the data in the case of certain conditions to the PDM file.

  I create a functional global variable (FGV) with write and read options containing the measured data (30 double CC in cluster). So when I get a new reading of the GPIB loop, I put the new values in the FGV.

  In parallel loops, I read the FGV when necessary. I know that, I just create a race condition, because when one of the loops reads or writes data in the FGV, no other loops can access, while they hold their race until the loop of winner completed his reading or writing on it.

  In my case, it is not a problem of losing data measured, and also a few short drapes in some loops are okey. (data measured, including the temperature values, used in the loop of PID and the loop to save file, the system also has constants for a significant period, is not a problem if the PID loop reads sometimes on values previous to the FGV in case if he won the race)

  What is a "barbarian way" to make such a code? (later, I want to give a good GUI to my code, so probably I would have to use some sort of event management,...)

  If you recommend something more elegant, please give me some links where I can learn more.

  I started to read and learn to try to expand my little knowledge in LabView, but to me, it seems I can find examples really pro and documents (http://expressionflow.com/2007/10/01/labview-queued-state-machine-architecture/ , http://forums.ni.com/t5/LabVIEW/Community-Nugget-2009-03-13-An-Event-based-messageing-framework/m-p/... ) and really simple, but not in the "middle range". This forum and other sources of NEITHER are really good, but I want to swim in a huge "info-ocean", without guidance...

  I'm after course 1 Core and Core 2, do you know that some free educational material that is based on these? (to say something 'intermediary'...)

  Thank you very much!

  I would use queues instead of a FGV in this particular case.

  A driving force that would provide a signal saying that the data is ready, you can change your FGV readme...  And maybe have an array of clusters to hold values more waiting to be read, etc...  Things get complicated...

  A queue however will do nicely.  You may have an understanding of producer/consumer.  You will need to do maybe not this 3rd loop.  If install you a state machine, which has (among other States): wait for the data (that is where the queue is read), writing to a file, disk PID.

  Your state of inactivity would be the "waiting for data".

  The PID is dependent on the data?  Otherwise it must operate its own, and Yes, you may have a loop for it.  Should run at a different rate from the loop reading data, you may have a different queue or other means for transmitting data to this loop.

  Another tip would be to define the State of PID as the default state and check for new data at regular intervals, thus reducing to 2 loops (producer / consumer).  The new data would be shared on the wires using a shift register.

  There are many tricks.  However, I would not recommend using a basic FGV as your solution.  An Action Engine, would be okay if it includes a mechanism to flag what data has been read (ie index, etc) or once the data has been read, it is deleted from the AE. 
  
  
  There are many ways to implement a solution, you just have to pick the right one that will avoid loosing data.
  

• Flush () ing shared object to a function

  I seem to be unable to hunt/save to file "data elements" of an object shared from a function, any ideas please people?
  
  I can get the code works of the "body" of the script, BUT if I try the same or similar thing within a function it does not play! would it be because of some considerations regarding the scope of variable (I have a little understand - and a little not?)
  
  

  Try:

• How a shared single process variable be FIFO and single element?

  How a variable shared unique process can we both FIFO and the only element at the same time?

  I read the NOR recommended for communication between a loop deterministic and non-deterministic loop.  He is said to use SVariable ingle-process Shared FIFO and single element.  OK I can't have something... because in my mind these two things must be mutually exclusive.  How do you have a single item 1?

  

  What 'RT FIFO activé' means, that when you use the variables shared in a timed loop it actually is written to a RT FIFO created automatically.

  The key here is that generally shared variables are shared resources and can add jitter to deterministic tasks if another loop uses the variable at the same time as your loop of deterministic.

  So here's the takeaway, when shared with RT FIFO active Variables using:

  • Normal loops read and write the shared variable in the same way as they always do.
  
  
  • Call loops read and write a FIFO RT rather
  
  
  • The data is automatically passed between the RT FIFOs and shared in a nondeterministic loop variable

  RT FIFOs exist because their architecture referred to as non-blocking so that when the timed loop trying to access it is guaranteed immediate access to a memory space.

  Does that answer your question?

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

• subVIs does not function when it is called by main secondary to vi

  Hi all

  I have a main.vi that loads the façade into a secondary four subVIs when selected. Like most applications, everything works fine up to come to build the project (.exe). Program works as expected when run it from .exe but when all the vi.lib functions (for example reading png Subvi) is included in one of the subVIs called, the façade is loaded correctly, but the Subvi is not running and the invoke node (perform a VI generates error 1003).

  I've included the subVIs in 'Always include' in the specification to build under the heading Source files.

  Help, please

  Thank you

  I made a significant change to your "called" sub - VI (I created an icon for it - you'll see why it's important in a minute) and again your main VI.  This code snippet is saved in LabVIEW 2015, but it is simple enough that you should be able to recreate it in any LabVIEW version you are using.

  

  I like to use references static VI (the first thing on the block diagram) because, especially if they are associated with a Subvi with an icon, they provide a mnemonic, robust and easy to get a lot of useful sub - VI 'properties' (for example the path) without worrying about the execution environment.  In particular, they work very well with the Start function Asynchronous Call, I think it's much simpler to use than the VI server method.  I'll walk you through it...

  1. Start with a static reference of VI to the Subvi to run asynchronously.  If your Subvi has an icon, it will appear (as shown here) in the body of the static VI reference, which makes it slightly better documented.  Notice the Red Star on top of the static reference - which indicates a reference strictly - type (right click and choose strictly typed), you need to the asynchronous call start.
  2. This reference gets first wired to a property node - the unusual appearance of the node ('VI Interface Type 2') comes from the strictly typed reference.  We choose the Path property.
  3. The path gets plugged into an open VI reference function.  Because we use asynchronous Start Call (Forget), we specify Option 0 x 80 (glance using reference VI open for further explanation).  We also wire the Strict Type of step 1 at the entrance to this function Type.
  4. The VI reference resulting is wired to Start Asynchronous Call, which starts the called sub - VI.
  5. We also spend it to Insert Secondary VI method, which shows the sub - VI running in the Sub panel.
  6. Now, we interact with the sub - VI in the Sub panel as much as we want to.
  7. In the main routine, we now run the while loop, waiting simply Stop pressing.  I placed a 100 msec waiting here to give priority to the Subvi.
  8. When leaving us, we remove the sub - VI of the Sub panel, he abandoned and get out.  I see no need to put a function exit here - if you want to automatically close the main façade, just do it.

  Bob Schor

  P.S. - I've tested (LabVIEW 2015) and it works fine.

• 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

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

• Shared STM vs variable

  From what I saw on the forum so far, it seems to me that, compared to a shared variable, STM is better with different data and larger size data type. The only thing that makes the slightly better shared variable that the STM is to be a little more simple.  If this is the case, why use a variable shared at all?  Are there applications where the shared variable is much better than the STM?

  We used the variables shared/datasocketfor for 5 years and they work well. In the simplest form, they are extremely easy to use. I strongly recommend wrapping it in a logic to give you the ability to detect the connection state and to reestablish the connection if it is lost (simple implementation will raise an error and not reconnect)

  The biggest risk in using this Protocol is that NEITHER has all the cards. You have no guarantee that they will not introduce critical bugs in the next update or eliminate entirely (aka datasocket). In addition, when you identify obscure bugs/features with the Protocol, NOR will be adapted, but, chances are, you will not be able to get a concrete timetable on the fix. It is not very cool if it's the backbone of your system.

  Because of the risks above, I started studying using TCP/IP primitives to make the set of our communication network. I have a theory that they are very stable and little evolutionary (except maybe for ipv6). Can someone save me from this?

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

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

• call shared the actor object function

  I run a large application using the Framework of the actor on the cRIO-9068.  LabVIEW 2013 SP1f2.

  One of my players must call a function from a .so shared object file that I created.  I also created a vi wrapper that contains the node of the library call.  The vi wrapper is not part of a library or a category.

  When I add the wrapper vi to one of the methods of the actor's and deploy the application; I get an error for the B indicating actor Core.vi actor charged with errors on the target and has been closed.  Here's where it gets interesting.

  If I remove B actor of the project, the error becomes actor C.

  If I remove the wrapper vi of the actor, the error disappears and my application runs as expected.

  If I have only the wrapper that VI on the target, the shared object function runs as expected without error.

  I'm out of ideas.  I will try to reproduce this problem on a small scale, but any help will be appreciated.

  Thanks in advance,

  Kevin

  Looks like I solved the problem by moving the .so to/usr/lib and by running chmod 0755 /usr/lib/libfoo.so

  would have been easier to repair if assigned deployment error to the actor actually using the library