Jump to content

Search the Community

Showing results for tags '2 event structures'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Software & Hardware Discussions
    • LabVIEW Community Edition
    • LabVIEW General
    • LabVIEW (By Category)
    • Hardware
  • Resources
    • LabVIEW Getting Started
    • GCentral
    • Code Repository (Certified)
    • LAVA Code on LabVIEW Tools Network
    • Code In-Development
    • OpenG
  • 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


Location


Interests

Found 1 result

  1. Hey guys, I am trying to debug a project developed by another developer and I see 2 event structures in the Main VI with UI. They both have different timeout values set and one of the ES is sending commands through User Events to the other ES which is part of a QSM. Since I've never come across a design with multiple ES, I wanted to understand the design before I proceeded. I did a little search regarding this matter but the conversation usually drifted and it was a bit confusing for a developer like me Suppose we limited 1 event structure per block diagram? Using multiple (2) event structures in 1 VI What I got out of it was Advantages -able to capture and process multiple events in parallel so that a single event that might take some time to complete won't freeze other events -able to compartmentalize events into different categories -different timeout values mean different polling frequency Disadvantages -a bit more maintenance required than a single ES design Is there a thread or resource that summarizes and describes this design?
×
×
  • Create New...

Important Information

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