Jump to content


  • Posts

  • Joined

  • Last visited

LabVIEW Information

  • Version
    LabVIEW 2020
  • Since

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Austin's Achievements


Newbie (1/14)



  1. Was this a custom CVT library or the standard NI one? I spent most of yesterday trying to figure out the issues with packaging the NI one, with no luck.
  2. @drjdpowell thank you for your time and what you shared. Nice to confirm what I was thinking, but in a more coherent way.
  3. That seems perfectly reasonable, thank you. I created a new project to package up the CVT library so I could include this in my other project. When I try to load the PPL it also loads the original vi.lib CVT library and throws an error that Template_Read.vi could not be loaded because it could not load the front panel. When I look in the library itself all of the VIs in the Internal/Template Functions/ folders are missing except a few. This seems to be preventing me from building the main project, as it throws a file missing NULL error. I've gone back to the CVT PPL project and tried adjusting the exclusion settings to include everything but it still removes them. Any idea how to deal with this?
  4. I recently ran into this issue and wanted to know what the community has to say about it. I have a main program that is a QMH that can launch a single actor (picked by the main program and loaded through PPL) to perform a task. I want to have that actor update a CVT for the main program to monitor. I set up the CVT in the main program and had the actor write to CVT. When that call happens I get an error that it can't find that tag in the CVT. I have a CVT viewer that shows that exact tag, though. For testing, I setup the CVT in the actor with the exact same tag list and it finds it just fine. This leads me to believe that the QMH main program lives in a different memory space from the actor. (Maybe things loaded through a PPL live in different memory?) The current work-around is to send the value back to the main program. I don't really like doing that but it is what it is. My next option will be to convert the main program to an actor and see if the child actor can see the CVT setup by the main actor. Any thoughts on this? Maybe I'm doing something wrong? Edit: Tested a QMH with an actor called directly, instead of through a PPL and the actor can see the CVT without error. Next up, trying a packed actor called directly instead of loaded dynamically. Edit 2: Created a trivial PPL actor and called it directly from the main program and it could not see the CVT. Is there a good workaround for this?
  • Create New...

Important Information

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