Memory is Full on my Embedded cDAQ Controller

Updated Dec 22, 2023

Reported In


  • CompactDAQ Controller

Issue Details

  • I'm using an embedded compactDAQ controller, and after installing LabVIEW and the needed drivers I see that there's almost no space left in the memory of my controller. This results in applications hanging, not responding and not being able to do more things with the cDAQ. What can I do to reduce the memory usage of my controller?
  • After installing LabVIEW, there is little to no room left on my cDAQ controller. The Windows OS and NI folder is taking up a lot of space. Is this normal? I can't even install some drivers now. How can I free up memory?


  • If you are using the development environment for LabVIEW and complete versions of NI drivers in the embedded controller, it would be recommended to instead use the Run-Time Engine versions of the software components and executables, as this would considerably lower the amount of memory needed by the required software.
  • Also, if NI software is installed and no future revisions will be needed, the NI Downloads folder can be removed from the OSDisk (C:) drive.
  • Check the (C:) drive for hidden folders that may contain unnecessary files. 

Additional Information

The embedded cDAQ controllers are designed to be used ideally as systems for deploying applications and not as development systems. The Run-Time Engine software is designed for the deployment of applications and reducing the memory footprint in the system.

To debug and test applications in an embedded system without the LabVIEW development environment, Remote Debugging can be used.