LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

"Get Memory Status.vi" outputs zeros

I attempt use "Get Memory Status.vi" to prevent crashes due to out of memory error. The goal is to make it impossible to provide input that causes demand for memory to exceed available memory during A to D data acquisition.

 

On the computer I develop my the LabVIEW 2020 application "Get Memory Status.vi" provides usable outputs. But when the application was moved to a computer where it would be used in a lab I get a reasonable value for the "memory allocated for LabVIEW" output, but the values I get for "total physical memory", and "free physical memory", are zero. This caused my application to fail to collect data on that lab computer.

 

Why do I get those zeros? What is a reliable way to get available memory information?

0 Kudos
Message 1 of 4
(1,187 Views)

I'm guessing "Get Memory Status" was released with LabVIEW 2020 (I can't find it in my LabVIEW 2019 installation, but it is present in LabVIEW 2021).  When you say "the application was moved", are you referring to a built executable?  Do you have the proper Run Time system on the other computer?

 

Bob Schor

0 Kudos
Message 2 of 4
(1,151 Views)

The LabVIIEW application is being run as source code in both the development computer, and the lab computer, in the LabVIEW 2020 IDE. Since in body locations it is in the IDE I have to assume the appropriate Run Time system is in effect.

 

The application is not fully debugged, and so no executable has been made of it.

 

0 Kudos
Message 3 of 4
(1,138 Views)

Thanks for the added information.  Sounds like the lab computer is missing some functionality.  Can you see "Get Memory Status" when you open a VI (on the lab computer), right-click the Block Diagram, open the Application Control and Memory Control palettes, and see if "Get Memory Status" is there?  If so (and I suspect it will be there), this suggests something isn't working "as expected" on the Lab computer.  Is it possible that one machine as 32-bit LabVIEW, and the other has 64-bit?  [I'm grasping at straws here ...].

 

Bob Schor

0 Kudos
Message 4 of 4
(1,116 Views)