Sign In Now Sign in to follow this Followers 0 Go To Topic Listing LabVIEW General All Activity Home Software & Hardware Discussions LabVIEW General Calling a VI using VI Server Administrators 274 5,736 posts Version:LabVIEW 2015 Since:1994 Posted February 20, 2008 QUOTE([email protected] @ Feb 19 2008, 12:03 AM) Which is better? "Abort vi" method or the "stop" function under "Function palette->application Using queues is helpful because they have the nice property of allowing you to forcibly budge and put your message at the front of the line. Share this post Link to post Share on other sites crelf 274 I'm a LAVA, not a fighter. http://softacoustik.com/labview-error/labview-error-ni-488.php
The launched VI waits for this information (You can pass the event refnum or further via VI server before running it) and then launches the base class of the Dynamic dispatch Let me try it out. Each background process is accompanied by a statically-linked "Action Engine" which provides actions for "init", "shutdown", and whatever else is needed. What I usually do, is pass the reference to the spawned process (via Set Control Value) and let the process (explicitly) close its own reference. http://digital.ni.com/public.nsf/allkb/DE45BD35AFE818E2862565FB00592B31
If we don't know yet which VI will be called (parent or child), how do you unwrap from the queue when the code is dynamically called? Sorry for the confusion. Sign in here. Share this post Link to post Share on other sites Create an account or sign in to comment You need to be a member in order to leave a comment Create
Please Contact NI for all product and support inquiries. I'd start dropping error > indicators or probes after any property nodes and run it on > the PDS system that's failing to see where the error is > originating from. Developer Walkthrough of the Finite Measurement Sa... Both VIs share many subVIs but each one does have a few unique subVIs.
Make sure you are using\instead of/, make sure you spelled the directory names correctly, and so on. Serving Up Powerful Solutions: LabVIEW VI Server E... Error 1000 can also occur if you attempt to abort a VI that is in the incorrect execution state, either due to the VI running or being part of another VI http://forums.ni.com/t5/LabVIEW/Error-1000/td-p/3075066 What state would the callers be left in if a sub-vi Aborted!?" There is rumored to be a test case to prove the fix never gets lost again. 0 Kudos Message
That's why I try never to use hardware. :-) Share this post Link to post Share on other sites i2dx 6 The 500 club Members 6 681 posts Location:Duesseldorf/Germany Version:LabVIEW This works properly in labview 2010 SP1, XNET 1.1.1 and with the same code in labview 2014 XNET 14.0 we get the error 1000 when we want to abort the vi You also need to set the Wait until done option to FALSEto eliminate the data dependencies of this VI. I'm not sure if the version makes the difference, but anyway, the dynamic dispatch didn't work.
Related Links: KnowledgeBase 28IAHMDM: Common VI Server Errors LabVIEW Help: Programmatically Controlling VIs Example Program: Programmatically Opening and Running One VI from Another Using VI Server Attachments: Report Date: 10/15/2002 Last https://lavag.org/topic/2986-calling-a-vi-using-vi-server-the-vi-is-not-in-a-state-compatible-with-this-operation/ is this just a way of checking whether your remote hardware is on the network. My idea was to have this VI AQ is referring to within the class, in essence moving the "dynamic dispatch" part up one level. Solution: Several methods which can be invoked through VI Server have the effect of editing the VI.
I think i will contact NI for further informations .... http://softacoustik.com/labview-error/labview-error-6.php Members 187 1,036 posts Location:Milford MA USA Version:LabVIEW 2013 Since:1999 Posted October 18, 2008 Wrapping the method should work, thanks for the advice all. If the foreground code calls it with a "shutdown" action, the action engine can verify successful shutdown before returning. I have a member VI that needs to be dynamically dispatched.
do you remember the CAR, in which Labview version was this bug corrected ? 2) Does it means the method Run Vi doesn't work anymore ? Please tell us why. Share this post Link to post Share on other sites Create an account or sign in to comment You need to be a member in order to leave a comment Create check over here Debugging Techniques - LabVIEW 2011 Help - Nationa...
I have heard of weirder race conditions. Share this post Link to post Share on other sites shoneill 79 The 500 club Members 79 715 posts Posted October 17, 2008 QUOTE (normandinf @ Oct 16 2008, 05:20 Trying to run the proprety node "Make > Current Values Default" is one that will do this in a built > application. > > Though you have slightly different symptoms since
The major drawback to this however, is the greater difficulty of passing data values to the called VI. Caveat: I still find aspects of my implementation to be cumbersome. I've tried my usual way (read: only way of which I'm aware) of opening a VI reference, setting a control value, and invoking it: I expected an error here, and sure Anyway - see the attached files: unzip the zip file to a new folder and point the path control of LittleBugger.vi to that new folder - I can't understand why the
In the second case, you must configure the VI Server to give you the appropriate permissions by selecting Tools»Options (or Edit»Preferences in LabVIEW 5.x). Any idea welcome... THe VI will be aborted BUT it may hang the LV session (at least that is what happened the last time I tried it, about a month ago under LV 8.2.1) this content Have you tried specifying a time out value for the ping?
but not dynamical. Recap: "Abort VI" can have ugly side effects. Administrators 274 5,736 posts Version:LabVIEW 2015 Since:1994 Posted March 3, 2006 Hey all, I'm using VI server to load and run a VI dynamically, but I'm getting: Error 1000 occurred at My idea was to have this VI AQ is referring to within the class, in essence moving the "dynamic dispatch" part up one level.
A VI is reserved for running when a reference to it is opened using the Open VI Reference function with a strictly typed VI Refnum wired to the type specifier VI 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. Internally, it has its own rules for state transitions, but it can additionally be sent action messages asynchronously from the foreground code. Any ideas what I am doing wrong Regards KahrCertified LabVIEW ArchitectCIM A/S Solved!
Shane. in Graph Server.vi. > > Possible reasons: > > LabVIEW: The VI is not in a state compatible with this > operation. > > VI was built using lv 6.02 > Register a new account Sign in Already have an account? The way I imagine it (not tried this yet), I don't know how I can avoid ending up with the parent object type.
All rights reserved. | Cart|Help KnowledgeBase Request Supportfrom an engineer NIHome > Support > KnowledgeBase EnglishChinese(China) 13 ratings: 3.69 out of 5   Why Do It will still call the correct dynamic dispatch VI. Wiring the type specifier reserves the VI for Call and you can't Run it. Don't know if that's related to the error at hand, but in the end it didn't surprise me.
If u run this vi alone it will run without any problem. You might experience this warning with various different properties, such as Front Panel Window:Auto Center. If the response is not recived within some 10 seconds i am killing this vi (which is attached ) so that the main application will call this vi once again.I have