I agree with Jonas suggestion re: RT Engine Info.
I beileve use need the following line in your LabVIEW.INI file to get that option.
targetmeminfo=true
I threw together a VI that tracks memory usange vs time VI that has preved quire helpful. I will attach this Vi along with a llb that I pulled down of this site somewhere. They have some supprt VI that are required.
What I suggest you do is fire this VI up and watch how your memory behaves. What you will see (hopefully) is memory useage that converges on some constant level. When you open FP via LV-RT or the web served FP's, there will be spikes in memory usage. When these remote FP are closed, the memory usage will drop-off.
If the memory usage keeps climbing, you have a problem!
NOW LE
T ME STOP and acknowledge that you may have some difficulty in trying to use the Get RT Engine info or using my utility if you really are out of memory. Let me suggest that you start by opening and running my utility first. If your code will not run and load with my utility running, don't give up! Try targeting the application and building the VI on the cFP 2000 and setting it to auto-boot. I have found that the compiled vesrions use a much smaller foot print than the development versions. Start your app by ressetting it and then target the cFP unit. You then load and start the utility I attached.
I have successfully deplyed app's that would only run as built app's on the cFP's. The cFP is very good at making you very aware of how you are using memory. THey are just a little tricky to work with. They make you appreciate the luxury of working with the cFP 2020's.
Post your code, and I'll take a look if you like.
Ben
Ben Rayner
Certified LabVIEW Developer
www.DSAutomation.com
