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

bmoyer

Members
  • Content Count

    187
  • Joined

  • Last visited

  • Days Won

    5

bmoyer last won the day on January 9 2017

bmoyer had the most liked content!

Community Reputation

19

About bmoyer

  • Rank
    Very Active
  • Birthday 01/26/1974

Profile Information

  • Gender
    Male
  • Location
    Princeton, NJ

LabVIEW Information

  • Version
    LabVIEW 2017
  • Since
    1993

Contact Methods

Recent Profile Visitors

1,512 profile views
  1. bmoyer

    LabVIEW Not Responding

    Thanks for your reply. I have 60 different actors, some are spawning multiple instances, but not many. I had a video attached to my previous post (sorry for the poor quality), and I routinely encounter long delays when iterating (after about 5 or so iteration of running, stopping, then making edits, then re-running and so on). I have been in contact with NI support about this problem but so far they haven't come up with anything. It's been difficult to debug since it doesn't seem to be a problem with small projects, and because of IP/corporate issues, I can't just send the whole project to them. What's the longest delays you've seen? Thanks, Bruce
  2. Hi everyone, I've been developing a fairly large program using drjdpowell's Messenger Library (over 60 actors so far) and I am encountering slowdowns in the LabVIEW environment (LV2017 SP1) that I've not been able to figure out. After running my source code multiple times (in order to make edits to the code), I find that the duration of time that I have to wait after stopping the code becomes increasingly long. Sometimes it get to the point where I need to wait over a minute before I can continue using the LabVIEW environment! Is this normal/expected behavior? It makes using LabVIEW very painful, and it ruins my train of thought. Any suggestions on how to improve things? Thanks, Bruce Video.MOV
  3. bmoyer

    [LVTN] Messenger Library

    Wow, so easy! I guess when the top-level level VI isn't broken I forget that there's another way to bring up the error window beside clicking the broken arrow! Thanks for all of your help! Bruce
  4. bmoyer

    [LVTN] Messenger Library

    On various occasions I run into the problem where one of my Actors is broken and I didn't realize it (such as a Type Def needs updating, or maybe I accidentally left an Actor in an unfinished state, etc.). This causes all Actors to not be able to be dynamically launched until the bad/broken Actor is fixed. Since the Actor is dynamically launched, I don't realize this until I try running the program. Is there a good way to figure out which Actor is broken besides going through the process of opening all Actors to find out? Thanks, Bruce
  5. bmoyer

    [LVTN] Messenger Library

    Oh! That was it! I had been struggling with this for a while now. Now it only takes a couple of seconds to save! Thanks for the tip!
  6. bmoyer

    [LVTN] Messenger Library

    I'm wondering if others see a similar behavior (described below) and if it's the Messenger Library, LabVIEW, or if it's related to a possibly slow PC (my IT department is extremely overly security cautious). I have a project that has many Actors (currently about 80) and I want to change some of them to re-entrant. When I change from NR to Shared clone reentrant execution (in VI Properties), afterwards it takes anywhere from 30 seconds to over a minute to save. Is this expected? I've also noticed other slowdowns in the project (Find Project Items) that can take a long time to respond where the cursor blinks from a arrow cursor to a waiting cursor for about 30 seconds during which I can't select or do anything in LabVIEW. Thanks, Bruce
  7. bmoyer

    H.264 video file

    You need to call the command line interface version of Handbrake. HandBrakeCLI.exe
  8. bmoyer

    H.264 video file

    LV2011 in case others have the same difficulty. Call HandBrake.vi
  9. bmoyer

    H.264 video file

    You can include HandBrakeCLI.exe in the installer of your application and make calls to the exe using the command line interface. Call HandBrake.vi
  10. bmoyer

    H.264 video file

    I use the Command Line Interface of Handbrake to allow LabVIEW to convert the .avi to .mp4 but I'm sure there are better ways. https://handbrake.fr/
  11. bmoyer

    [LVTN] Messenger Library

    1.8.3.82. I'm able to create an exe from the Messenger Library Demo 2.lvproj using Top Level.lvclass:ActorNR.vi but when I try building my program (without the steps below) I get the error. Here's the steps I tried (to get it to build and run correctly): I uninstalled and reinstalled the Messenger library in VIPM but still same error. "Use Fast File Format" checked...I was able to build the exe but when I run the exe it states "LabVIEW: Resource not found. An error occurred loading VI 'Actor type2.lvclass: Get Dynamic Launch Shell Reference.vi'. LabVIEW load error code 3: Could not load front panel." Then the exe crashes. Checked "Disconnect type definitions", unchecked all "Remove unused...", the exe works now! (the culprit to step 2 was the "Modify project library file after removing unused members). Strange build quirks/confusing settings in Build Properties was the culprit. Thanks for your help! Bruce
  12. bmoyer

    [LVTN] Messenger Library

    Same here. On another note, I just started working with it (in LV2017 32-bit) and I'm having an issue with building the exe. The source works fine but when I build I get this build error: "A VI broke during the build process from being saved without a block diagram. Either open the build specification to include the block diagram of that VI or enable debugging to include the block diagrams of all VIs in the build. Report this error to National Instruments technical support." C:\Program Files (x86)\National Instruments\LabVIEW 2017\vi.lib\drjdpowell\Messenging\Action MSG\Async Execute Core.vi Any ideas? I've tried to include the block diagram of this VI and my Actor VIs in the build and also tried creating a debug executable but neither worked. So far I've really enjoyed using the Messenger library and hope to use it in many applications (if I can get past making an exe). Thanks, Bruce
  13. bmoyer

    Using LV with SVN

    I see that PushOK SVN is listed as a recommended SCC Provider in LabVIEW. Has anyone tried to use this? I tried but ran into difficulties because the initial connection when LabVIEW started was taking too long and timing out. Which Third-Party Source Code Control Providers Does National Instruments Recommend for LabVIEW 8.x and Later? http://digital.ni.com/public.nsf/allkb/41FBD516D8BC1DED862576AF007061B2
  14. bmoyer

    Trying to use JKI SMOs

    Francoise, thanks for responding! I replied to your other response: http://forums.ni.com/t5/JKI-State-Machine-Objects/Trying-to-use-JKI-SMOs/gpm-p/3592039 Bruce
  15. bmoyer

    LabVIEW Network License Problem

    The people who set up the NI network license server have to set up permissions for particular computers to get licenses. It's not an "everybody who wants a license can get one" type of system. Everytime I have a new computer I have to have my IT set up the server to allow it to grant licenses to my new computer. Your screen shot seems different than what you're describing however. People who install LabVIEW on a computer should be able to use LabVIEW in evaluation mode for a short period of time (can't remember if it's 30 days or something shorter).
×

Important Information

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