scott123

In order to automate the process of right clicking on a case structure and selecting "Case Insensitive Match" I am trying to write a VI to do this programatically. I have cast a reference to the CaseSelector Object and i do not see any methods to call or properties to set that will accomplish this. I have also examined the methods and properties of the Selector object that is tied to the CaseSelector Object, but I still don't see the appropriate metohds/properties. Does anyone know if such a thing exists?

I have two PXI systems with PXI 8106 controllers. My code is acquiring data, calculating information based off this data, running PID and open loop control, outputting values to hardware, and transfering data to a host PC via TCP. I am using LabVIEW 8.5.1 and RT 8.5.1. I have not tried a simple VI, but this is a good idea. I will allow the getmemoryusage.vi to run all by its self on a test platform to see if i can recreate this situation. I have not tried the execution trace tool kit. The system seems to run fine after the increase happens, no freeze or crash. Therefore, this does not seem like a major concern, but if another spike were to occur after it has spiked to 60% then we may not be able to guarentee(sp?) a shutdown to protect the device under test.

Hi all, I am using the rtgetmemorysummary.vi located at http://zone.ni.com/devzone/cda/epd/p/id/4952 to monitor the memory usage of a real time application. I use the total and available outputs to calculate the percent usage, and log this to file. I have seen a step change from roughly 11 to 60 percent usage on two different RT systems. After the increase occurs, the system maintains 60% memory consumption. This rare occurrence has happened twice within the course of maybe two months. National Instruments has verified that this VI is the same as the RT memory monitoring VI in the 8.6 RT package. I am wondering if anyone has seen a sudden step change in memory usage, similar to what I have described. I am not sure if calling this VI is causing the memory to spike or if this is a false report, or if the code is causing a whopping 256Mb allocation. So, does anybody have any similar experiences and possible solutions? Crosspost on NI: http://forums.ni.com/ni/board/message?boar...hread.id=410300

You should think about initializing that shift register.