VI High 8 - More on How to Program Events with the Event Structure in LabVIEW
In this continuation of our last episode, we examine one of the most commonly asked LabVIEW programming questions: how do I use the event structure? We examine executing two events from the same event case and the basics of programming a timeout event case.
For the full video transcript, visit: http://blog.sixclear.com/post/3186138706/labview-events2
For more on learning LabVIEW, check out the Lucid LabVIEW Fundamentals Training (previously LabVIEW Fundamentals) course offered by Sixclear: http://www.sixclear.com.
You can also keep up with us at:
http://facebook.com/sixclear
http://twitter.com/#!/sixclear
http://gplus.to/Sixclear
Experience level: Basic
In the video, we mention that we don't need to place a numeric terminal in an event case tied to that numeric but we must place the terminal of a latch action Boolean in the event structure case corresponding to that Boolean. Why is that? This is taken from the LabVIEW Help topic " Using Events with Latched Boolean Controls":
"When you trigger an event on a Boolean control configured with a latching mechanical action, the Boolean control does not reset to its default value until the block diagram reads the terminal on the Boolean control. You must read the terminal inside the event case for the mechanical action to work correctly. As a reminder, a note appears in the Edit Events dialog box when you configure a Value Change event on a latched Boolean control."
Видео VI High 8 - More on How to Program Events with the Event Structure in LabVIEW канала Sixclear
For the full video transcript, visit: http://blog.sixclear.com/post/3186138706/labview-events2
For more on learning LabVIEW, check out the Lucid LabVIEW Fundamentals Training (previously LabVIEW Fundamentals) course offered by Sixclear: http://www.sixclear.com.
You can also keep up with us at:
http://facebook.com/sixclear
http://twitter.com/#!/sixclear
http://gplus.to/Sixclear
Experience level: Basic
In the video, we mention that we don't need to place a numeric terminal in an event case tied to that numeric but we must place the terminal of a latch action Boolean in the event structure case corresponding to that Boolean. Why is that? This is taken from the LabVIEW Help topic " Using Events with Latched Boolean Controls":
"When you trigger an event on a Boolean control configured with a latching mechanical action, the Boolean control does not reset to its default value until the block diagram reads the terminal on the Boolean control. You must read the terminal inside the event case for the mechanical action to work correctly. As a reminder, a note appears in the Edit Events dialog box when you configure a Value Change event on a latched Boolean control."
Видео VI High 8 - More on How to Program Events with the Event Structure in LabVIEW канала Sixclear
Показать
Комментарии отсутствуют
Информация о видео
Другие видео канала
VI High 9 - How Is Dataflow and Execution Order Determined in LabVIEW?LabVIEW Tips&Tricks Episode 3: Event driven state machineVI High 59 - Difference between the Wait and the Wait Until Next Ms MultipleComplete guide to interface instrument with labviewVI High 7 - How to Program Events with the Event Structure in LabVIEWHow to create the Simple Queue DesignLabVIEW Sequence StructuresIntroduction to LabVIEW Part 11: Event StructureUsing Cluster Type Definitions and Cluster Strict Type Definitions in LabVIEWVI High 44 - Learn How to Write to a Text File with LabVIEWVI High 36 - Conditional Loop Output TunnelsNI LabVIEW: Event structure for interactive front panelVI High 54 - How to Implement an Error Handling Strategy in a State MachineQueued State Machine QSM - LabVIEW Design PatternsVI High 49 - How to Use State Programming and State Machines in LabVIEWLabVIEW Tutorial 5 - Shift Register (Enable Integration)VI High 13 - How to Use and Install Instrument Drivers in LabVIEW (part 2)How to use Notifiers in LabVIEWLabVIEW code: Event-driven producer-consumer state machine (walk-through)