# XX-LAVA-LabVIEW Task Manager **Repository Path**: douhao/XX-LAVA-LabVIEW-Task-Manager ## Basic Information - **Project Name**: XX-LAVA-LabVIEW Task Manager - **Description**: No description available - **Primary Language**: Unknown - **License**: MIT - **Default Branch**: master - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 3 - **Forks**: 1 - **Created**: 2020-05-23 - **Last Updated**: 2023-11-05 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README ## README ## ----- This code is from https://bitbucket.org/lavag/labview-task-manager/src/master/. The store is just easy for china user. ----- ![输入图片说明](https://images.gitee.com/uploads/images/2020/0524/225652_b3386e2d_91089.png "5925f97be03e6_LVTMScreenshot-Copy.PNG.a345fe65cbe713b29f505a851e0fe597.PNG") ### Latest Released Version ### The most recent version of LabVIEW Task Manager is v1.10.0, released on 24-May-2017 ### This code is **Open-Source**, and free of charge ### Authors: Ravi Beniwal, Tim Vargo LAVA Names: Ravi Beniwal, TimVargo Contact Info: Contact via PM at the LAVA site (http://lavag.org) ### What Is the LabVIEW Task Manager (LVTM)? ### _LabVIEW Task Manager_ is a debugging tool for use during LabVIEW code development. An expandable/collapsible tree diagram displays detailed information (both static and dynamic) on all VIs in memory, belonging to a selected project/target. It allows for interacting with single or multiple selected VIs at a time, and includes the following major features: + Selection of project/target + Lists all VIs in memory, grouped by class/library or disk folder, or a flat list + Searches for and enumerates clones in memory + DropIn VI for including dynamically referenced clones (Clone Beacon) + 'Refresh Now' (F5) re-reads all VIs in memory and adds new ones to the tree + Displays VI name, owning class/library, state, path, data size & code size + Displays VI FP Behavior, Reentrant?, Reentrancy Type, Paused? & Highlight? + Group by Class/Library or Folder, or display a Flat List + Sort by any column, ascending or descending + Filter out item types vi, ctl, and vit/ctt + Filter out vi.lib and global VIs + Filter out items from being displayed, per folder paths. + Tracking of, and ability to toggle, execution highlighting on multiple selected VIs + Tracking of paused VIs with ability to Pause/Resume/TogglePause multiple selected VIs + DropIn VI for pausing only while debugging + If a clone initiates a pause, a different pause symbol is used for all clones of that same reentrant original VI + Select multiple VIs and open or close their FPs or BDs + Double Click a VI from the tree to bring the BD (first choice) or FP to front, if already open + Select multiple top-level VIs and Abort them + Remotely close any VI's Front Panel ### How Do I Use It ? ### * During LabVIEW(R) code development, invoke the LabVIEW Task Manager from your "Tools > LAVA" menu * Use the "App Instance" drop-down to select which of your loaded projects/targets you wish to manage * A tree diagram will show detailed information on all VIs in memory. You may interact with single or multiple selected VIs at a time. #### Helper Functions #### There are helper functions available to assist with your debugging effort, and these are made available from Functions Palette > Addons > LAVA > LabVIEW Task Manager. * #### Pause #### The Pause function allows for optionally initiating a pause from within any VI. Just drop this function into any VI that you wish to be able to pause, on an optional condition, but only if LVTM is running (so this pause will NOT occur if not debugging). If the pause request is generated from a clone of a reentrant VI, it will pause all clones of that VI. Leaving this function in your VIs, even when deploying your application, will not effect the performance; as it has a very small footprint. * #### Clone Beacon #### Asynchronously called reentrant VIs are not automatically recognized by the LabVIEW Task Manager, because they (by design) run in their own threads, independent from the rest of the project. This function remedies that problem. Just drop the "Clone Beacon" into any asynchronously called reentrant VI, to force its clones to be seen by LabVIEW Task Manager. Leaving this function in your VIs, even when deploying your application, will not effect the performance; as it has a very small footprint. ### LabVIEW Versions Supported: LV2013 and up ### LabVIEW Versions Tested on: LV2017 LV2016 LV2013 ### Tool Installation ### To install this tool for your own use, simply download its VIPM package from [the tool's download page](https://bitbucket.org/lavag/labview-task-manager/downloads), then install the package (lava_lib_labview_task_manager-x.x.x.x) using [VI Package Manager](http://jki.net/vipm). VIPM 2014 or higher is required for installation of this tool's installer package. The latest version of VIPM is available for free from ### Known Issues: + Cannot abort SubVIs launched from remote VI Server or local Asynch Call By Ref ###### This application was originally authored by Ravi Beniwal, and now includes code contributions from Aristos Queue, James Powell, Darren Nattinger, ohiofudu, Neil Pate, and TimVargo. Packaged by TimVargo. ######