Jump to content
News about the LabVIEW Wiki! Read more... ×

TimVargo

Members
  • Content Count

    48
  • Joined

  • Last visited

  • Days Won

    2

TimVargo last won the day on March 19 2017

TimVargo had the most liked content!

Community Reputation

11

About TimVargo

  • Rank
    More Active
  • Birthday 12/16/1961

Profile Information

  • Gender
    Male
  • Location
    Albuquerque, NM

LabVIEW Information

  • Version
    LabVIEW 2013
  • Since
    1992

Recent Profile Visitors

1,045 profile views
  1. TimVargo

    [CR] LabVIEW Task Manager (LVTM)

    Hi Ron, I haven't actually tried this, but I can see no reason why you shouldn't be able to update both packages without breaking LVTM. Sure, the package will complain about "missing dependencies", but that shouldn't matter because by then you've already done installed it and no longer need the package. The order in which this is done IS important however. First install LVTM along with the older dependent packages, THEN (optionally) upgrade the GPower and SmartBalloon packages. >> So I've downgrade the two support packages so your Task Manager will run.<< Are you saying that after the two package upgrades LVTM wouldn't run? In what way did it complain? I have rechecked the package build specs, and both bitness of the OS and bitness of LabVIEW are set to allow both 32 and 64-bit -- so everything SHOULD be compatible, unless it is one of the dependent packages that is the problem (I've not tried this myself on 64-bit LabVIEW). When you got that error, did the error message explicitly state which "package is not compatible"?
  2. TimVargo

    [CR] LabVIEW Task Manager (LVTM)

    Eric, LVTM was built to support LV2013 and up (when developing toolkits, always best to provide backward compatibility as far back as possible). Those two libraries do indeed have more current versions available, but those more recent library versions THEMSELVES do not provide backward compatibility back to LV2013. So the answer to your question is that it depends on what version of the LV development environment you will be running LVTM under. If you are developing in LV2013 or LV2014, then you will need to stick with GPower Error & Warning = 1.2.0.14, and NI SmartBalloon = 2.0.0.2. If you are developing in LV2015 or higher, then you should be able to safely use the very latest versions of those two libraries without any compatibility problems.
  3. TimVargo

    [CR] LabVIEW Task Manager (LVTM)

    No. The tool relies on much functionality that is not available in a RunTime environment, including many VI Scripting properties. However, there is a possible solution... Probably, but it would require you to first enable this from within your own built application -- a small and simple piece of code (example provided) to invoke the LVTM on a key combination of your choice. See this post from the early days of LVTM development. There, Ravi describes a technique of invoking LVTM from LV built executables, by using a plugin. The download linked in that post was written for a much older version of LVTM, but you should be able to adapt it to the current version. All of the plugin architecture is already provided, so I would think you would only need to replace a few older LVTM folders with newer versions of the same, then rebuild it. If you do this, we would appreciate any feedback on your experience in modifying it; or maybe even post your modified plugin solution here.
  4. TimVargo

    [CR] LabVIEW Task Manager (LVTM)

    I just now edited the topic description to clarify this. I will also add it to the readme file for the next release. Invoke the LVTM tool from your dev environment menu: Tools > LAVA > LabVIEW Task Manager
  5. TimVargo

    [CR] LabVIEW Task Manager (LVTM)

    Hi dwb, No, the LVTM Control App is not about debugging a LabVIEW-built application executable -- rather it is intended to run on your development machine, alongside of the LVTM tool. If the LabVIEW code you are developing ever hangs up the UI of your LV development environment, the Control App will allow you to escape from that situation (which otherwise requires killing LabVIEW and loosing any unsaved changes). The most common cause for getting into that situation is if your code calls a modal VI that was already open (you were editing it and forgot to close it before running it's caller). Normally you could use the LVTM tool to close the front panel of any open VI; but when this frustrating circumstance occurs, the entire LabVIEW development environment UI becomes unreachable, including the LVTM tool itself -- so the Control App was created to overcome that problem. Here is the text from the Control App's VI documentation: This application helps close any open modal VIs that are not closeable otherwise. Click Refresh to get all modal VIs in memory, in all application instances. Select the VI that you want to close and click Close FP Because the LVTM Control App is itself a built executable, you can still run that, and it will call into the LVTM tool and allow you to close any open front panel, effectively releasing the deadlock. Because the Control App is a LV built executable, the LV Run-Time Engine (RTE) is required. Install the 2013 RTE onto your development machine, and create yourself a shortcut to "LVTM Control App.exe". Use your shortcut to recover from a hung LabVIEW UI the next time that happens to you!
  6. TimVargo

    [CR] LabVIEW Task Manager (LVTM)

    A new installer package, which now properly ensures that all dependent 3rd-party libraries get installed, has been uploaded. Neither the version number nor build number has changed, still at v1.10.0.71. Many thanks to postalbyke for discovering and reporting this issue, and for testing the fix.
  7. TimVargo

    [CR] LabVIEW Task Manager (LVTM)

    Thanks for pointing this out postalbyke. I may have neglected to include that unpublished package into the LVTM package. I will look into this later today.
  8. TimVargo

    [CR] LabVIEW Task Manager (LVTM)

    LabVIEW Task Manager (LVTM) v2013.1.10.0 has finally arrived!!! You can download this new version using the "View File" button at the top of this page. Of all the new features added to this version, my favorite isn't a feature at all; it's how much FASTER it now is than before, and with much smoother scrolling through the tree too! In a post above I said that the new version would contain "several modest improvements"; but I said that after I had added those improvements myself, before Ravi had added his own. Wow, his additions boosted the improvements from modest to nothing short of amazing! But don't take my word for it, see it for yourself! Hope you find it as useful as Ravi and I do.
  9. TimVargo

    LabVIEW Task Manager

    This is a very old thread, but I am going to make this one last post here to direct anyone still monitoring this ancient discussion, to the actual support page for LabVIEW Task Manager. It is relevant to do so now, because I don't want anyone to miss out on today's announcement that this tool will be featured in a NIWeek 2017 Technical Session! Here is the announcement on the support page: https://lavag.org/topic/18322-cr-labview-task-manager/?do=findComment&comment=121847
  10. TimVargo

    [CR] LabVIEW Task Manager (LVTM)

    It has been over two and a half years since version 1.7.0 of this tool was released, and today Ravi and I have an exciting announcement to make. The two of us will be presenting a technical session, Advanced Debugging With LabVIEW Task Manager, at NIWeek 2017! For those of you planning to attend NIWeek 2017, 22-25/May (yes, NI has moved it up 10 weeks earlier), please be sure to add our presentation to your session schedule -- we'd love to see you in our audience! Here are the details: Session Title: 0195 - Advanced Debugging With LabVIEW Task ManagerType: Technical SessionWednesday, May 24Time: 4:45 PM - 5:45 PMLocation: 19B Abstract: Discover both the merits and limitations of LabVIEW debugging tools, explore which situations impede troubleshooting, and view a live demonstration of the free, open-source, and community-developed LabVIEW Task Manager, which delivers new comprehensions into your running code, plus ways to dynamically interact with individual or groups of VIs. To commemorate this speaking opportunity, Ravi and I are working hard to release an updated version of the tool, including several modest improvements, to the LabVIEW Tools Network. It is our goal to complete this release prior to NIWeek 2017. Here is a sneak peak into the future: What's New in LVTM v1.10.txt Hope to see you in Austin in May!
  11. TimVargo

    Any info about NIWeek 2017 LAVA BBQ yet?

    I have my conference pass, my air travel booked, and my hotel booked. Only thing left now to complete the whole package is a LAVA BBQ ticket! I'll keep checking back here.
  12. TimVargo

    NI Week Advanced User Track

    I too thought this new track was a success! I attended quite a few sessions in Room 15, and I thought they were great. For several previous years I was one of many to give feedback that I wanted more advanced, more technical content; and I'm glad to see that NI was listening. I encourage NI to do this again in future years. Speaking of future years, remember that starting with NIWeek 2017 the conference will be held in late May.
  13. TimVargo

    LAVA BBQ 2016 - Official Information

    Just bought my ticket. I'm in, and SOOOO looking forward to it!
  14. I am ready and eager to send money (to pay for BBQ)!
×

Important Information

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