Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Porter last won the day on September 21 2019

Porter had the most liked content!

Community Reputation


1 Follower

About Porter

  • Rank
    Very Active

Profile Information

  • Gender
  • Location

LabVIEW Information

  • Version
    LabVIEW 2017
  • Since

Contact Methods

Recent Profile Visitors

3,017 profile views
  1. Just tested beep VI on its own and again I get the same run away ram consumption of audiodg.exe (+5MB/s). I've got a bleeping memory leak! RAM remains reserved by audiodg.exe even after exiting the application. When using the sound VIs to play a WAV file, there is no such memory leak behavior. LabVIEW 2018 SP1 32-Bit Windows 10 Home 10.0.17763 Realtek Audio PNP Device ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0255&SUBSYS_10280855&REV_1000\4&3675F7D0&0&0001 Driver: rtkvhd64.sys (, 5.83 MB (6,111,680 bytes), 2019-04-28 1:27 AM)
  2. I had a labivew application crash yesterday due to the PC running out of memory. Looking at the windows 10 system logs, it was audiodg.exe that ate up all of the memory. Re-launching the application again and triggering the beep sound caused audiodg.exe memory usage to shoot up at 10s of MB/s. I suspect that this is a realtek audio driver bug because I can't reproduce this behavior on my development machine. Has anyone else come across this kind of behavior before?
  3. Are you talking about right click during edit time or during runtime? Does this explain the random right click of doom that freezes LabVIEW after right clicking on an item in project explorer?
  4. Trying to create a child of a class that is within a packed project library produces Error 1562 This is because CreateChildClass is trying to add the new class to the parent's library. I propose that it should instead add the new class to My Computer. To do this, just change "CCC Main.vi" to look like this: vi.lib\addons\_LAVA\lvoop_assistant\_create_child_class.llb\CCC Main.vi
  5. I'd be happy to work on it in my free time... when I have free time (newborn baby girl waiting for me at home)
  6. It would be nice to be able to modify .mnu palettes with the GCode manager. This way you don't need to add the palette to your palette set just to edit it (as you have to do with the built-in palette editor). Shouldn't be too hard to implement 😜 There is a Palette API that ships with LabVIEW.
  7. Thanks @Michael Aivaliotis for taking the time to do this.
  8. As someone contributing code on LAVA, I would like to see the certified LAVA repository packages made available through the GCentral package search tool.
  9. Be sure to double check the ASCII/RTU mode setting. Make sure that you are specifying the starting address in hex format. The PV value is supposed to be at holding register 0x1000. You could also try increasing the timeout value to 1000 or 2000ms (instead of the default 300ms). A screenshot of the dwyer communication setup and the Plasmionique Modbus Comm Tester setup would be useful.
  10. When you say Love Controller, do you mean a Dwyer "Love" Temperature Controller? They definitely work with this library. For configuring the USB-RS485 adapter, I have never used labview to specify 2-wire or 4-wire mode. That is usually done via hardware (dip-switches or jumpers) or the driver (device manager). I have never used the Tripp-Lite adapter though. I typically use USB-Serial converters from Moxa or Sealevel Systems. They have proven to work very will with labview. If you can provide the model number or user manual of the Love controller, maybe I can give you some example commands to try.
  11. I finally had a moment to take a look at this. Nice job! I particularity like the conditional auto-indexing tunnel vim and the delete elements from array vim. I will have to tell our developers to start moving away from the openG array VIs. Are you going to put this up on github or the NI Tools network?
  12. It is solved now. I unchecked the exclude PPLs and DLLs in the build spec of LF.lvlibp And moved the resulting LF.lvlibp to the same directory as the other PPLs.
  13. I have been transitioning my framework's core libraries to packed project libraries. Unfortunately, the higher level PPLs depend on lower level PPLs, but i think that I've managed to sort out all of the broken connections. Now the issue that is bothering me is that whenever I open a project containing a higher level PPL, I get a bunch of "VI cannot be found on disk errors" that refer to VIs within the higher level PPL. My initial thought was that the file paths were too long, but that doesn't seem to be the case. Has anyone else come across this behavior when using PPLs?
  14. I wonder if they will also release a community edition for Linux.
  15. It would also allow open source developers to maintain their projects after they have changed jobs. I'm glad to hear that NI is moving in this direction. How are they going to prevent companies from just using the community version though?
  • Create New...

Important Information

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