Closing references

Similar Questions

• Closing references ActiveX

  Hi all

  I'm just starting to work with ActiveX controls.  The attached graph shows a loop that opens different spreadsheets Excel in a workbook, based on the user's selection.

  My questions are:

  1 - is the 'Data Variant' create a new refnum whenever it runs?  If so, then I have to move the function of 'Closely Reference' associated inside the loop, Yes?

  2. is there a better way to select different worksheets?

  Any help would be greatly appreciated.

  Thank you

  FB

  

  Yes, you must close the reference inside the event, immediately after, you have finished using it.  You could run away references the way that you do now.

  I see no problem with this method of selecting a worksheet - is there a reason any you don't like it?

  EDIT: Also, is there a reason you have the Excel._Worksheet as a control rather than a constant of type?

• Closing references ActiveX correctly in the Simple user interface

  Hello

  I am currently editing the user supplied with Teststand 2013 Simple interface in order to access the global variables of the station through LabVIEW.  A simple test, I'm trying to access the value of username.  When I run the VI for the first time after the opening of LabVIEW, I get no error message and the program works as required.  Stop the running VI will return no error, but when I try to run the VI and rerun the Teststand, stalls the execution sequence and I get a wait status.  I then have to close running VI by killing all threads in Teststand, I think that the PropertyObjects do not come out properly and I find the structure of the event quite confusing to deal with.

  My attempt to close the references in the while loop looks like this:

  

  The rest of the program is exactly as expected with Teststand 2013.

  Any input on how to close properly references ActiveX and extracting station globals in LabVIEW would be much apreciated.

  Thank you for your help,

  Christian

  Christian,

  Doug is correct if you open references in a loop, you should also be closing them in the loop. For example, this code open a reference to the engine and the Globals PropertyObject. Two of these references must be closed each time that the loop is executed with the current code.

  You might be able to improve this code is to put your username querying code elsewhere. This username appears as something that would happen only when a user connects or disconnects, then perhaps that this code could be registered as a reminder of the event UserChangedevent. Follow these steps in the VI of reminders set up event of the user interface.

  If you do not need this code to update constantly, you can put in the structure of the event time-out event in your screenshot and fix a reasonable (maybe 100 to 200 ms).

  Hope this helps and let us know if you have other questions about this!

• closing references - what

  Hello

  I have a small question on the fence of the references.

  When writing some programs I open usually refers to a single store location in a shift register or fgv and the usewhen I need as in case 1. Then I close the reference to the output of the application so leak memory will not happen.

  I wonder why the case 2 works fine. I opened reference used and then closed. So property where I write 1 shouldn't return error?

  Implicit references close not really until the owner VI is closed.  To close an implicit reference won't hurt.  Implicit references to the same control will use the same reference.

• Close the reference (for a more specific class)

  I'm feeding a control reference to the node "to a more specific class.  When I finished, I understand that I have to close the order, but what I also close the reference that is the output of the node "to a more specific class?

  This is the same reference... There is no need to close the two.  And if you approve the automatic cleanup of references LabVIEW, you really do not need to close, as the references control must never be matched and will be automatically cleaned when your VI is inactive.

  For more information, here is a blog that just now, I wrote that talks about closing reference.

• FP. Closing does not close application.

  When I use FP. Close in my main vi, which is the last step in my code, it stops the program, but does not close the front panel.  Although the program has stopped running, the front remains open.  I would avoid this because operators think it is still ongoing.

  -Thank you

  Well, I can not help with you feel, but you have to QUIT LABVIEW in an application.

  No matter HOW you exit you should not do before closing references, files, connections, etc.

  Once you have done all that, then it's time to LABVIEW to quit SMOKING if you are in an application.

• Should I close the reference?

  Hello

  I would ask... should I close the reference of the workbook in the following code?

  

  In fact, I have little idea whether to close a reference or not, because I thought that LabVIEW will automatically close all references after the execution.

  I also found that someone says that the activeX references must be closed on mine.

  Could someone correct my understanding of the closure of reference?

  In this case I'm fairly certain that cleaning screws will close these references, so I don't think that you should close your self.  One way, usually, I test this is I put the code in a while loop, or use the continuous run button.  It's basically the only time wherever I never use only and I have on small subVIs like that.  Then, I run my code over and over again and look at the Task Manager to see how much memory is using LabVIEW.exe.  After a few seconds if there is a leak of memory then memory will continue to increase.  If the memory goes up and down a bit, but overall does not continue to grow, then all the references that should be closed are closed.

  There is a white book NOR on the reference Server VI of closing which is exactly what you are doing, but has relevant information.

  http://www.NI.com/white-paper/14393/en

  And an exchange of views on this subject.

  https://lavag.org/topic/16443-closing-references-in-LabVIEW-new-documentation-published/

• Sorensen XG 60-14 error

  Hello

  I have a problem with a programmable power recently bought Sorensen XG 60-14. In my application (LabView 2012), I use this power to fuel a cooler through regulation PID Peltier. My code sets the current performance of the PSU to the all the 1 sec. My application works without any problem for days, until like 4-5 days, and then I get a crash.

  The first problem is that, when I get the error, the LabView gives a pop up window asking continue so or stop? This is really not good, since my code should stop completely in case of error (I wrote my code in a way if there is error, he must close and stop all other material, like other power supplies). I used the official "lvlib" Sorensen to make my own screws, see set in the zip file.

  In my code, I first tried to use the "configure Output.vi" Sorensen VI official with very little modification, but usually, I got errors and accidents after 2 or 3 days. So I decided to get rid of dish-sequence-structure and also unnecessary allow exit on every play, so I set it too.

  Now I use the Output_Sorensen_XG.vi 'configure', and I call it the "Sorensen_XG_psu.vi." So in my high level VI, I call these screws with 1 Hz frequency.

  First, I here insert the photo of the first error that I consider a pop-up error:

  

  After clicking 'continue', I get the following error, but I guess that the first error above is one, as the following is generated due to closed resources?

  

  What can be the problem? I created leak memory somehow? I should close some refnums in the Output_Sorensen_XG.vi 'configure' after each iteration, there is a lot of property nodes?

  I hope someone can help me... thanks a lot!

  EDIT: actually, I realized that the second jpg is the info error relevant, since the first is just a mistake of a Subvi, where I try to shut down the power supply in case of error, and that the part is not connected via wire error.

  So the relevant error is second, the "refnum zero or removed ' a. But how the refnum evaluates to null?

  Martins wrote:

  In fact I see only two references: 'Out' and 'system '. The reference called "AmetekXGLib.IAmetekXG" is available as an entrance tunnel and is also in the exit tunnel that you see. When I call the "Sorensen_XG_psu.vi" in init mode, I get this ref, and eventually I simply store in a shiftregister as you can see...

  (1) IAmetekXGOutputs

  IAmetekXGOutputChannel 2).

  IAmetekXGSystem 3).

  4.) IAmetekXG - which you reuse via the shift register

  No closed references cause Excel to continue running in the background that's why I notice them.

• Sorry for the inconvenience.

  Help!

  I have an application that works ok for a while now and this morning it failed with LabVIEW to crash and burn.

  The error message was the dialogue where it says "LabVIEW 8.6 development system has encountered a problem and needs to close..." »

  I've seen this error message before (instead of stangest), but exclusively in development mode. This error has occurred during the March and after several hours to do the same thing (if something was borked in the s/w that he should have not much earlier). Can a doubtful driver / DLL call give this type of error message? As it happens if I particularly trust PC and PCI single board industrial basket because there are a lot of strange behavior, he.

  Any ideas?

  Thanks for all the suggestions everyone!

  I come from the client and the problem of debugging. It was a really weird error message actually come on the screen while another VI was running (and has continued to work very well, with me able to probe the pattern-block etc.!).

  The culprit was... a TDMS writing! In another loop I closing the file reference and you try to write to the TDMS file using the now closed reference.

  In hindsight, I've seen these types of errors a lot with PDM, when there is a mistake is not exactly a stop appropriate!

• Change the topology without reference to closing

  Hi all

  I was wondering if I should be able to change the topology of a MUX (reset) without closing the reference?  I have an application that performs a loop on the base initialization, connect, disconnect the sequence for functions OR-Switch and the topology changes for each loop.  I think that my reference is lost, because it becomes invalid after several loops.  I have to close the reference before I reset with the new topology?  I'd rather not have to close every time, because I 'cleansing' steps that close of references outside of the loop. In collaboration with the PXI-2527, LV 2013 and 2013 TS.  Thanks in advance.

  GSinMN

  Ali GSinMN,

  This knowledge base Article should answer your question. The last line reads, "during the change of topology, you close the current session if one is open and reset the map with the selected DriverSetup new.»

• control/references file closed and re-used

  See attached example.  I realized that you can reuse a reference control, even after it is closed, and it is not applied to the file reference.  Why is this?

  Only the need of refs dynamice closed, see here.

  Ben

• The reference must be closed on a reading-file error or not?

  Dear users,

  When I read a file, a reference is created one should close, when no longer used, should I? Here is a minimal example to my next serious question: should I close the benchmark on reading-file error or not? Is there a created in the case of "the file does not exist"?

   

  See you soon,.

  No, when used in this way, the references created by the file read and write functions should not be closed - thought that he would have no negative effect if you did.

  In addition, you do not want or need the structure case around a reference close the function.

  Mike...

• Reference to the control on the main façade fails the Subvi front is closed?

  Hi all

  I meet a strange bug. In my code, I use a Subvi to control a piece of hardware. The Subvi has commands for all functions of my hardware.

  I changes the value of one of these controls in my main façade by running a reference to a button on my main façade in the Subvi, grabbing the value of the button with a property node, then update the value of the Subvi control using a node property signage.

  This works very well when my Subvi front is open, but does not work the Subvi front closing.

  I am new to labview, so any help is appreciated.

  Thank you

  Rachid

  This event triggers a series of writing for the real hardware. The material is sent only a command when something changes.

  My code is made up of handlers inside functional global variables. In this way, I can send different parts of code of different orders (example: reset and reset) with the events generated by programming.

  The value of the wheel of the page main itself, according to my probes, getting through. It's the Subvi button that is having a problem.

  I work under a certain pressure of time pretty important, so I managed to convince the boss that the front panel of the Subvi open does not violate the requirements of the application. I guess this has solved my isse.

• Get References.vi of ActiveX and references - closing Excel grrr

  I'm new to ActiveX stuff, but eager to learn!

  The 'grrr' in my subject line is a reference to how I feel about LabVIEW documentation from time to time.  I'm a dinosaur coming from textual programming and did a fair amount of coding in C, so sometimes with LabVIEW, I find myself with this terrible feeling in the pit of my stomach, like ' Good grief!  The amount of memory must LabVIEW be hogging space in the background when I use this vi? ' or 'what happens to these variables (son) in this sub - VI, when it ends, but does not close?  What are their articles when I come back in the next time? ' or ' what if I put a lot of elements in this array, the first time and then started from 0 the second time and just put in some?  What happened with the memroy that has been allocated when there was a lot of elements? »

  Today I am steaming on the subject 'Excel get ActiveX References.vi', and what happens to the "ActiveX references" it generates whenever I call the Subvi in which lives «Excel get ActiveX References.vi»  I think at least one of the"ActiveX" it generates when I call it is of type Excel._Application.  It then seems to be an Excel._Workbook and others.  You see, I used "Excel Report.vi easy" to put some data in an Excel spreadsheet, and I want to tell Excel to do a 'save' on the worksheet open.  I think that ActiveX is (a) the right way to do it, so I'm wading into the fray ActiveX...  But this "Excel get ActiveX References.vi" said in its help file, "do not close references ActiveX opened with references to ActiveX Excel Get VI. The references should stay open until the report is closed. If not, will the 3001 error. "Well, these Excel workbooks to be created by my VI could stay open until after my LabVIEW VI ends!

  So (finally), here are some of my questions:

  (1) when I go through my sub - VI once, pointing to a workbook, I'll take a set of references 'created' or 'open' or whatever you call when ActiveX references spring into existence.  Now, when I leave the Subvi, it will automatically try to 'close' these ActiveX references?  I don't think that, since the stay of Subvi in memory until the appellant VI closes.

  (2) now, I'm back in my Subvi a second time.  New workbook is created, if I receive new references.  Okay, all right.  Uh oh!  What happened to these old references?  I suppose that if I did not save somehow off, I probably lost the possibility to recover them (maybe I'm wrong, but I don't need their return), but is LabVIEW go to 'close' the old refers (from times past through the Subvi) because I can't go to them more?  Which will not cause the dreaded error 3001?  LabVIEW is wrong to 'close', what in tarnation is happening (the old C programmer in me creeping back)?  Now, it is some oddball, reference an orphan, floating there, hogging memory, until we do something to crash intermittently and be a nightmare to debug?

  (3) now, here's the real fear.  I think I could dodge the bullet "error 3001" questions) 1 and 2), but now we will tell the user closes my LabVIEW application that Excel is always open.  All of these workbooks are still open.  Without doubt, all these ActiveX references that I shouldn't have to close are still open.  I really hope that LabVIEW is honest enough to close/delete/remove/blow-away (no matter what the right word) all of these ActiveX references that were opened/created by 'Excel get ActiveX References.vi' when my program ends.  But, oh no!  The 3001 error only then will come along?  I guess I can just discharge it in the stop error handling.

  Oh well, thanks for reading my novel.  I don't know what can be done with LabVIEW documentation to make it more satisfying to people like me, but maybe someone can weigh in on my questions ActiveX here.

  Thank you in advance,

  Steve Brady

  Here is the diagram of Excel get ActiveX References.vi:

  

  No matter how many times you call this VI, returned references are always the same. So call this VI in a loop has no effect on memory, performance, etc.

  The reason that you are not supposed to close these references is they are stored internally to your reference report (as part of the data class) and are used by the other screws in the API report generation. These references must stay open until you're appealing report Gen screws, how you must call Report.vi have as the last VI in your 'chain '. Have Report.vi looks like this (for the Excel application):

  

  That's where these references are closed. You should always call Report.vi has to ensure that all references ActiveX used by this particular report object are closed. If you do not, then it is the possibility for them to be kept in memory by LabVIEW, although the VI will idle. LabVIEW is capable of auto-éliminer certain types of reference when screws become inactive, but I don't think the ActiveX references are one of these types.

  Let me know if you still have any questions. Generally speaking, the report Gen screws should provide all the features you need to handle your report... the screws Get ActiveX references are only for the case where you need to do something the report Gen screws do not allow you to do.

• high school: when closing the reference?

  Hi, just a quick question if anyone can it clearify I thank so much.

  I found the secondary example called "Simple Subpanel.vi" and he put an inactive during the loop to "hold" the front of the called vi, here, is the "plugin1.vi". (Sorry I am still not very clear why it must be slowed down while loop here.)

  

  However, if we put the vi 'close' after the while loop, like the one I changed, is there a chance that the vi will overflow from the memory of the PC after the long period of running? What is the difference between these two methods?

  

  Lets say, I load my VI in a secondary, then after it's in high school I want to show or hide the menu bar.  Can I use a node property to show or hide the menu bar of the VI in the secondary, but I can only do this by using the reference to the VI, if it has not yet been closed.  In this case, you don't want to close until you are done with it.

  You do not leave open indefinitely in both cases that you have demonstrated, so there is no memory problem with both methods of references.