Solenoid Subvi

Similar Questions

• Renamed 3 variables shared on the network in Subvi to starting RT VI, now they won't write?

  Hello world

  I worked on an RT program deployed to our cRIO-9024 with custom FPGA, and I changed the way in which the data is written to these three types of DBL 1 d. I renamed the shared variables ("shvars") in the library of the RT project shvar and also changed the target to the PC for the debugging of the function of the code written for them. I used a struct of conditional compilation to turn them off and something has been corrupted along the way and the second node broken shvar (node moved directly from project, no programming style) and caused a hard compilation failure in the Subvi. I got the compile error and go after the removal of the node of shvar entirely and placing him again the project and everything seemed fine.

  Soon, I bring the Subvi RT application instance and build my RT exe and deploy it. On the host PC, this second shvar now not get written in at all. I hunt and chase and decide that something is wrong with the deployment of the shvars. I redeploy all and even delete all 3 of the nodes of these shvars in the Subvi and place them again. Now, all 3 are not be written to. My next step is to move the shvars out of this sub - VI I put them in but this is recommended? Note that sometimes they seem to get written once and then are forever silent after that. Is this because I use the nodes instead of the function of programming with shvar addresses?

  Thank you.

  Edit: Notice the same level superior RT vi successfully wrote in 19 other shvars that I have not touched.

  -Very well, I shot myself in the foot and was in fact barking the wrong tree. Put shvar nodes in a Subvi was well and not at all related to the problem.

  The problem is that I had a bug in my code FPGA in a particular case, that could get him to stop putting valid data. Once I corrected this bug, everything returned to normal. I would like to delete this thread, but a little shy is right for you.

• deployment error: unable to locate all the subVIs screws saved because a Subvi is missing or the VI is not registered in the last version of LabVIEW.

  Hello world

  I want to deploy my project Teststand and got a strange error when creating the image.

  For many additional files with the suffix as .tso, alias, lvlpb, exe, dll... deployment tool launches the error message "unable to locate all the subVIs screws saved because a Subvi is missing or the VI is not registered in the last version of LabVIEW.» (see also the attached picture).

  If I exclude the files of my distribution or set them to "include without treatment or dependencies of elements of" the generation works fine.

  After the error, I checked the Temp folder. The temporary project LV is not yet created.

  I used the deplyoment-installation in the same way within a fromer project and had no problems like that...

  I use Win7 / LV2013 SP1 & Teststand 2013 f1 (5.1.240).

  Could someone help or support? Thank you!

  Finally, I tried the construction with LV2015 & TS2014 - no problems... Everything works fine...

• Using FFT to palette spectrum Subvi Interface of FPGA functions

  Hello

  I use the card PCI-5640R and PXI-5600. I want to use the "scale" and "FFT" exspress screws to the range of functions 'Mathematical FPGA and analysis' in my VI "FPGA VI" and "FFT spectrum for '"FPGA interface"in my"host VI.

  A poster of the code examples in which these three subVIs are used can.

  Thanks in advance.

  Kind regards

  Rashid

  

  Hi rachid,.

  There are two examples of delivery here: LabVIEW 2009\examples\R Series\FPGA Fundamentals\Analysis and Control\FFT\

  Jim

• Why my Subvi freeze my main VI?

  Could someone look at this VI for me?

  What this VI is supposed to do, it's detect Excel is open, take what workbooks are available and then displayed them in a listbox. It works as a standalone program, but my problem is that I can't select any item in the listbox when the VI is called. What I'm missing here? VI is in 2016 LV.

  Just as I suspected.  Your highest level VI is set to be "Modal".  This means that it will be in front of any other screw your Subvi is 'default', which is basically the same thing as "floating".  I recommend that you change your main VI 'float '.

• reference Subvi model VI deployed

  Hi all

  We use about 50 testsequences with TestStand 4.1.1 and LabVIEW 8.5. The development is made with LabVIEW and TestStand, production uses the runtime TestStand.

  Our reference libraries vi vi: for example "C:\Program Files (x 86) \National Instruments\LabVIEW 8.5\vi.lib\Utility\error.llb\Clear Errors.vi. After development, we are deploying our testsequences on a network share, so the production of PC can run them through the TestStand Runtime. The references to "program files" are deployed in a folder... / SupportVIs for the production of PC can find these references, since they do not have the folder "C:\Program Files (x 86) \National 8.5\vi.lib.

  Some vi is reused in new testsequences and copied in the folder /NI_Labview of the testsequence. To check for errors before deploying, I run the option "compile mass" (Labview-> tools-> Advanced-> mass compile...) for the real testsequence /NI_Labview folder. The exit of the mass 'compile' contains odd messages:

  # Mass compilation of departure: make April 28, 2016 09:07:24
  Directory: "C:\Stefsvn\TESTSET55\NI_Labview".
  C:\Stefsvn\TESTSET55\NI_Labview\TESTSET55.llb\ReadConfig_DUT_parameters.VI
  -VI should happen to "S:\Teststand models\SupportVIs\Read key (U32) .vi" was loaded "C:\Program Files (x 86) \National Instruments\LabVIEW 8.5\vi.lib\Utility\config.llb\Read key (U32) .vi.
  . VI C:\Stefsvn\TESTSET55\NI_Labview\TESTSET55 (Teststand)
  -VI should happen to "C:\Program Files (x 86) \National 8.5\vi.lib\Utility\error.llb\Clear Errors.vi" has been loaded "S:\Teststand models\SupportVIs\Clear Errors.vi".
  # Mass compilation Finished: make April 28, 2016 09:07:27

  LabVIEW search references Subvi in deployments of our teststand files!

  Using the massive compilation option, I broke a teststand deployment model vi. I want to avoid this scenario not to affect production in the compilation/deployment of a new testsequence.

  If I look at LabVIEW-> tools-> Options-> paths-> VI search path, I get the following:

  \*

  \*

  \*

  \*

  C:\Program Files (x 86) \National Instruments\LabVIEW 8.5\resource

  Why prefer labview reference in lieu the deployed model vi VI in the | vilib | folder? It's because of 'S:\Teststand models\' in ?

  Can I avoid labview vi deployed SEO? Can I edit/clear ?

  Is there a built in option to view all the Subvi their paths? Or what I need to build it myself? I found this http://www.ni.com/example/27094/en/ vi which looks like a good start.

  Thanks in advance,

  Stef

  SVH wrote:
  ...

  If I look at LabVIEW-> tools-> Options-> paths-> VI search path, I get the following:

  \*

  \*

  \*

  \*

  C:\Program Files (x 86) \National Instruments\LabVIEW 8.5\resource

  Why prefer labview reference in lieu the deployed model vi VI in the | vilib | folder? It's because of 'S:\Teststand models\' in ?

  Can I avoid labview vi deployed SEO? Can I edit/clear ?

  Is there a built in option to view all the Subvi their paths? Or what I need to build it myself? I found this http://www.ni.com/example/27094/en/ vi which looks like a good start.

  Thanks in advance,

  Stef

  Hi Stef,

  your search paths are used top-down. Get your way s sought firstly, including subfolders. As your list of . VILIB is searched only after these two. On my installation, I even deleted the list, since it caused me troble on a regular basis.

  What I don't understand: do you want to change the deployed screws or you are working on a development project?

  See you soon

  Oli

• Reading from the sensor to LabView via rs232 or Subvi problem

  I'm quite new to LabView and not too experienced with instrument control so I was wondering if someone could help me to solve my problem?

  Currently, I'm using LabView 2011 and I'm trying to read pressure DualGauge of Pfeiffer (TPG 262) pressure sensor and display the readings of two pressure on LabView.  However, when I run my program, the pressure readings are not displayed - what is displayed are default 0.00 if same mBar pressure reading a reading of the display of the DualGauge probe.  To connect the sensor, I use a RS232 cable and have managed to find the device on my device manager, so I don't think that the connection is the problem (I've also seen the port appears in the Device Manager, when I connected the sensor via RS232 and USB in my computer).  I also use Subvi Pfeiffer in my code, and I suspect that the problem may be in there.

  Attached is my code and here are links to the manual of the DualGauge and the driver of the software LabView of Pfeiffer

  Double manual gauge - p. 23 and 68 are probably the only things related to the RS232 connection.

  http://www.idealvac.com/files/brochures/Pfeiffer_TPG262_Operating_Instructions.PDF

  DualGauge LabView driver - software Pfeiffer double gauge LabView driver 2009

  http://www.Pfeiffer-vacuum.com/products/measurement/activeline/measurement-equipment/OnlineCatalog.a...

  Any help is very appreciated!

  -Candice

  You have not tested really do anything. Devices and MAX Manager displays only the com port that you added to the computer. It does nothing to verify that an instrument is truly connected. You might have the wrong settings of com or the wrong type of cable serial (null-modem is required). I suggest that you start with program such as hyperterminal, PuTTY or MAX and try something simple. It seems that you will receive an acknowledgement returned by the instrument when a correct command is received. Make sure that this simple step that happens.

• Print pictures of the face before of the subvis to executables

  I have a high level vi which calls a Subvi, which has all the parcels I want to print a report.  It works as a vi I do refer to the Sub - VI I want to print the image of.  When I make an executable it no longer works and even if I change the reference for the image of the toplevel vi, so there is clearly viable (.exe) refers to print, it does not work.  Can I use the print queue window, but it does not give me the report. only the image.  All advice welcome

  We need to see your code to be sure, but I guess you found the reference VI using the path of the VI.  Well when an EXE went the way of the VI won't be the same.  You must use a static reference VI to get a reference to the VI, and then the location on the disc is not serious.

  Here is a small example that I did some time ago using replacement VITs in a similar way.

  http://forums.NI.com/T5/LabVIEW/building-an-executable-with-Vits-with-LabVIEW-2011/m-p/2384984#M7404...

• Load a component of a Subvi in secondary of a hand of Vi

  I know it's possible to load all the Subvi in the subgroup of experts, however, is possible to load a component or an individuall chart a subvi in the vi secondary main iti?

  I think you can stop it by focusing on the "sub", just put any VI in a secondary school. You can just put a VI in a secondary, nothing else.

  Your problem is maybe just for the redesign of your initial VI to also have a sup Panel which includes a VI showing that your chart VI you will be able to put in any school of different voluntary initiatives.

• I have problems with of the Subvi after the use of customized device model

  I used to start my machine personalized customized device model and I got success in the deployment until I started to do more complicated the Subvi.   I am currently trying to convert low FPGA and high ticks to the duty cycle, but for some reason when I add it to the RT VI "Data read of HW" driver, it seems to cause a downtime... ideas? Is a circuit agree? I have added a time delay but I am still having problems. It is a device online, so I'm suspicious of it hogging resources, but am not sure.

  Attached images are meant to be read like this:

  1. the case of the RT pilot ReadDataFromHW

  2. it's the Subvi calling ToDutyCycle SIMStimPWMSubVI

  3 ShiftRegister.PNG is inside the Subvi.

  As a robotician I celebrate early and often (usually by a failure or two...), but it seems that the answer was to transform fundamentally the While loop for a loop with a count of 1 and then remove the additional elements to ensure that each shift register has that one and then right click on the shift registers and convert at the Feedback node...
  I was able to deploy to VeriStand as a custom device and it runs and calculates the factor of use with no problems. WOOHOO! Where - what is celebrate button!

• FPGA Subvi Multiple Instances

  Hey,.

  It is sort of a basic question, and I don't know how at the height, I'm on the vocabulary of LabView FPGA. I did a machine States that performs a task, and I want two of these state machines is running at the same time. So, I created a Subvi with the state machine and placed two calls to them in the top level VI.

  The problem is when I run the VI of highest level in interactive mode, the initial contributions are locked, and subsequent changes to the entries does nothing. So, basically there is something I don't understand. I imagining me signals propagating VI of highest level for two instances of the subVIs instead of the initial values being stored.

  What I am doing wrong?

  Thank you

  Kevin

  Hello kevin.key,

  The difference between the two parts of the code that you fixed is that the code in the while loop will run several times until it stopped while the code without the loop will only run one and then stops.

  Your Subvi begin values based on the values of input passed your top VI. These values will be updated every time your Subvi is called from your albums VI. To do this your top VI has a loop for continuous data and your Subvi should independently of your albums looping VI. The reason why the values in your front panel are not getting updated is because there is no loop in your top VI. If you include a loop that values will update each time the loop runs, which occurs only after the entire interior of the loop ends, including the Subvi.

  If you have access to a computer with LabVIEW on it try to start live using the run culminating to see the behavior of your Subvi.

• Looking to simplify Subvi to make it reusable... Is this possible?

  I'm looking for the opportunity to make a more generic VI so that I can re-use it for multiple applications. The VI is used to write the parameters of an instrument in a configuration file (.ini). The Subvi is vipm under the library of the OpenG Variant Configuration file. Saw him take in a clustors clustor and changing their settings in a configuration file. I am wanting to make more generic for re-use so that I can use any clustor of instruments of clustors for the parameters (each insturment will be different) between projects.

  Is it possible to pass a clustor refnum and in the Subvi re - create the clustor to move to this VI?  Or should I shut up and create a new VI for each project instead of trying to do something that is reusable between projects insturment?

  

  If you think about it, very easy. Writing INI Cluster itself is of course capable of taking any cluster as input. This is why the entry is not actually a cluster, but a Variant. (Note the red dot)

  Change "Ini settings" control variant instead of cluster and your vi will be more reusable.

• The call of a Subvi without stopping the execution of the main thread

  Hello everyone, I have a rather simple demonstration VI, which opens a menu where the user can call a few screws, signal generation, reading and analysis, each contained in a Subvi and with their own front panel and chart controls. The idea is user just click a button and the required Subvi is in charge, I use a structure of the event to ease.

  Problem is, after I opened an option, said Subvi hogs the thread of execution and does not allow for new bodies until it is closed (this is inside a while loop it is so logical, I guess), the queue of events and the next before Panel charges only after that I have stop the Subvi. I would like to be able to simply open the front panels and let them run in parallel, without them in the meantime another at the end, is it possible?

  natasftw is right.

  A high school is a "hole" in your main panel.  You "insert" a separate VI in this 'hole' and then you see the Panel of VI inserted through the hole and mouse clicks through the hole of the Subvi below.

  You will need to run the Subvi separately, even if - by inserting just can't run.

  Aynchronous call will begin a Subvi running and then return to the calling thread with the Subvi running in parallel.

  You can then insert the Subvi in a secondary, or let it have its own window, as you choose.

  There are examples of both techniques.

• ???? LV eat my Subvi

  Seriously, I can hardly even how to describe the strange thing that happens to my code.

  A vi project that worked well for months, now desimated... lack key Subvi which are outside the vi.

  I checked on my PC, and all these subvis are in a library on this PC, then that's happened?

  It seems that the vi is trying to replace the vi mising with other library vi from an earlier project.

  Thanks for the review of my problem

  LV attacked and corrupted all my archived copies of this vi.

  Fortunately for me, I found a reading - single CD with a copy of my month vi bup there.

  Fixed.

• TestStand deployment error - error: unable to locate all the screws saved subVIs because it lacks a Subvi

  Hello

  I am a systems and software engineer based in Vancouver. I developed a test system automated using 2013 LabVIEW and TestStand 2013 with custom operator interface.
  I encountered problem 'lack screw' which is kind of weird because I went to analyze the sequence for the TestStand Deployment Utility and TestStand sequence editor > files broadcast tab.
  But when I tried to build the installer and reach the point ' called distribution screw, it always throws an error saying "an error occurred trying to read the error of the screw, possible because the screws are not saved in the latest version of LabVIEW. Do you want to save any changes now? ". I tried both (that is to say Yes and no) for this option, but it has not solved the problem.

  This is part of the original error message displayed in the TestStand deployment utility:
  " ***************************
  Then the treatment live...
  Error: Cannot locate all the subVIs screws saved because a Subvi is missing or the VI is not registered in the last version of LabVIEW.
  The chain of calls to missing screws:
  1 - ATE_AccelerometerTest.vi
  2 - CreateAndMergeErrors.vi (missing)
  3 - LogControl_CheckForErrorSendUpdates.vi (missing)"

  All screw missing come from userlib.

  Actions performed:
  -File of sequence analyzed by using the TestStand Deployment Utility and TestStand sequence editor
  -Checked "search directories" include all the necessary files/dependencies.
  -Mass to compile the directory of the missing screws
  -Added all the necessary files and folders in the workspace file.

  The result is always the same function according to the actions performed.

  Debugging last I did earlier, is that I tried to find the sequence and steps missing screws as shown above (for example ATE_AccelerometerTest.vi)
  and I discovered that the measure appears to be an empty action step. This would be possible even if it has already passed the analysis?

  Other considerations include:

  I'm using sp1 2013 LabVIEW and TestStand 2013. We tried the building three 3 computers and we only managed once to a freshly installed comptuer.

  Hoping to hear from you soon.

  Kind regards

  Michael Panganiban
  Engineering systems and software
  www.Synovus.ca
  [email protected]

  Hi all

  We were able to solve the problem. First of all to note is that the release notes in 2013 TestStand is obsolete and we confirmed engineer OR Austin TestStand 2013 works very well with LabVIEW 2013 SP1.

  Second, we played option deployment TestStand that solved the problem. Attached are the pictures.

  We have activated just the 'delete unused Components VI'. It could be one of the libraries (lvlib) we have included in the compilation, but we've not thought of it again because we have checked that all the screws are working. It could also be something else that I think is very hard to find from information. However, if someone had the same problem, this could be useful.

  Again, we return to using 2013 TestStand and LabVIEW 2013 SP1.

  I appreciate all comments and feedbacks. Otherwise, you can close this request for assistance.

  Thank you.

  Kind regards

  Michael Panganiban

  Engineering systems and software