Jump to content

Search the Community

Showing results for tags 'abort'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Software & Hardware Discussions
    • LabVIEW General
    • LabVIEW (By Category)
    • Hardware
  • Resources
    • LabVIEW Getting Started
    • OpenG
    • GCentral
    • Code Repository (Certified)
    • LAVA Code on LabVIEW Tools Network
    • Code In-Development
  • Community
    • LAVA Lounge
    • LabVIEW Feedback for NI
    • LabVIEW Ecosystem
  • LAVA Site Related
    • Site Feedback & Support
    • Wiki Help

Categories

  • *Uncertified*
  • LabVIEW Tools Network Certified
  • LabVIEW API
    • VI Scripting
    • JKI Right-Click Framework Plugins
    • Quick Drop Plugins
    • XNodes
  • General
  • User Interface
    • X-Controls
  • LabVIEW IDE
    • Custom Probes
  • LabVIEW OOP
  • Database & File IO
  • Machine Vision & Imaging
  • Remote Control, Monitoring and the Internet
  • Hardware

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Personal Website


Company Website


Twitter Name


LinkedIn Profile


Facebook Page


Location


Interests

Found 2 results

  1. Hi, I am trying to abort a timed loop in order to quickly stop the VI that contains it without having to wait for the next iteration to wake up the loop. The example that ships with LabVIEW works fine, but when I do what appears to be the same thing, the loop itself returns error -816: "Timed structure aborted or attempted to execute another iteration of the following aborted Timed Loop.", and the Wakeup Reason left data node is "Normal". When I run the example, there is no error and the Wakeup Reason is "Aborted". Does anybody know what could be different in my code? It's a complicated VI with a lot of code inside the loop, but I believe all that code is unrelated... One difference with the example is that the Abort function is in the same VI as the loop in the example, whereas in my case it's inside a separate VI, but that should still work, right? Thanks for your help!
  2. Un-abortable from VI Server: Start Asynchronous Call Prepare to call and forget 0x80 I'm trying to abort call and forget VIs that don't get shutdown properly. I'm launching using 0x80 (call and forget) Problem is, I can't seem to find them in memory using VI server. If I "trick" labview and just start opening a VI by name, and put in the correctly (guessed) clone name i.e. dameon.vi:3 and it just so happens to be the right name I can find it. Why isn't it appearing in all VI's in memory? Is there any way to find clones of a VI through server? Stranger still: the name of the VI when i hover over the abort button is something like dameon.vi:Hostdaemon:ProxyCaller.234908238:3 wtf? how can I abort call and forget VIs problematically? Lastly, I'm aware of Abort.vi which I forget who programmed. I got it off lavag at some point, see attached. ~Jon Oh yeah, even if I get the right clone name from VI server through my educated guess, I still cant abort it problematically with the abort method. Showing the front panel with an invoke node does work however (wtf? why?) I can then hit the abort button on the front panel of the daemon, and it does stop. ~Jon Abort_LV82_v100.zip
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.