Labview Error 1122
I do use force destroy, however. The queue was destoryed, so you get error 1 and 0. It assumes that the second while loop can process the data in the time it takes the first while loop to acquire it. Ben Share this post Link to post Share on other sites John Lokanis 75 The 500 club Members 75 786 posts Location:Seattle, WA Version:LabVIEW 2015 Since:1993 Posted August 30, 2008 http://jvmwriter.org/labview-error/labview-error.html
Click here to get the free tool. Did you upgrade OS's. not only would you have to allocate millions of queues, you'd have to have them all continuously in play in order for the refnums to ever hit up against each other. The Wait has it's Timeout set to -1 so it will not Timeout.
Top contributing authors: Name Posts matt198717 4 user's latest post: why do i get error 1122 at... Share this post Link to post Share on other sites mprim 0 Active Members 0 19 posts Version:LabVIEW 2009 Since:2009 Posted September 24, 2008 Your vi makes a number of Sign in to follow this Followers 0 What can kill a queue? I don't rule out the possibility of a bug in something, but not that.
I do not 'obtain' an existing quene anywhere because I am using unnamed queues. It assumes that the second while loop can process the data in the time it takes the first while loop to acquire it. Your cache administrator is webmaster. Share this post Link to post Share on other sites Neville D 6 The 500 club Members 6 751 posts Version:LabVIEW 2011 Since:1996 Posted September 3, 2008 QUOTE (jlokanis @
Are you sure your CPU is fast enough to acquire and process the data simultaneously. The stop button is read as F and the loop waits at the Dequeue node. I have a large number of reentrant VIs running and I create a lot of unnamed queues that I pass inside a cluster to sub VIs. https://forums.ni.com/t5/LabVIEW/Release-Queue-error/td-p/203122 Maybe I should stop doing that, even though in this case it should not matter.
If it does not the number of elements in the queue will grow very quickly. Just not the VIT that reported the error. Even if the VIT was stopped by an external VI, this error would never happen and the code that logs the error to the event log would also not execute. Your consumer loop should be using the Dequeue Elements. 2.
It stopped abrupty popping up a message " Error 1 occurred at release Queue in my file, Possible reasson: An input parameter is invalid" So what could have gone wrong? It's easy! I think there is a bug in the code that manages refnums. Share this post Link to post Share on other sites Aristos Queue 537 LV R&D: I write C++/# so you don't have to.
All rights reserved. his comment is here Example_VI.png 4 KB 1 Kudo Message 10 of 11 (2,760 Views) Reply 1 Kudo « Previous 1 2 Next » All Forum Topics Previous Topic Next Topic Privacy | Terms of That's going to be the best way to get NI to push further on this. And I use the Force Destroy feature to stop the background DAQ loops.
This report page is a snippet summary view from a single thread "why do i get error 1122 at dequeue element in consumer loop when i hit stop button", located on Have you tried debugging the built executable? I have error logging throughout my code that shows multiple references going invalid at the same time in unrelated VIs (all of these use 'private' unnamed queues). http://jvmwriter.org/labview-error/labview-error-7.html Please tell us why.
Also, since I only see this error from the EXE version of the code and only after 100's of units are tested (many days of testing), I suspect it would be What is wrong with it? I handled with the problem.
That was the other thing I was going to say ...
Primary Software: Primary Software Version: 1.0 Primary Software Fixed Version: N/A Secondary Software: N/A Problem: When I use an Enqueue Element, Enqueue Element at Opposite End, Preview Queue Element, Preview Queue Your consumer loop should actually be releasing the queue in the STOP case. 3. Enable Debugging when building the exe and try it out. When we replaced it with a while loop we hadn't any problems any more.
Egemen Producer-consumer to txt.png 106 KB 0 Kudos Message 1 of 5 (697 Views) Reply 0 Kudos Re: Why did I get error 1122? I am at a total loss. But I am not. http://jvmwriter.org/labview-error/labview-error-ni-488.html Always ensure to close the reference only after all other functions needing it have executed.
Search Advanced search Search everywhere only in this thread Thread: why do i get error 1122 at dequeue element in consumer loop when i hit stop button Started 1 Wire the release queue function out of the loop where you generate the events instead of the consumer loop. Is there a way? I have contected NI for support on this so we will see what they say.
I suspect that the 'shared clone' reentrant mode and queue refs have some latent bug. The error text describes what happened fairly clearly, I think. Cart|Help KnowledgeBase Request Supportfrom an engineer NIHome > Support > KnowledgeBase EnglishSpanishJapanese 13 ratings: 2.61 out of 5   Why Do I Get Error 1122 Seems to have Repaired it, thanks x” Angelo- 1 Month Ago “You are an absolute legend!
Scenario Example: Create Queue in a VI Put Queue refnum in LV2 Gbl Launch (asynchronously) other code that need the Queue (other code call LV2 Gbl) Create Queue VI stops --> I have never done something like that before? There is also no need for the polling to see how many elements are left in the queue. 4. http://lavag.org/old_files/monthly_08_2008/post-2411-1220050049.jpg' target="_blank"> The Dequeue element gets an error stating the reference has become invalid while waiting.
My guess is that Labview is not dequeing the elements fast enough. So, there is no way that cleanup VI could execute before the VI that is waiting. Also, this is not the only reference that does invalid. I don't have LV here, so this is off the top of my head, but doesn't LabVIEW's producer/consumer template rely on this error to stop the consumer loop when the producer
I notice that when this problem occurs, the whole app also starts to slow down AND memory usage starts to increase. Also, I have over 15 queues, not just the one shown here.