Best Practices for Using Embedded Controllers for Development

Updated Oct 15, 2018

Issue Details

I would like to use my embedded controller to develop my LabVIEW code, but I am having space and performance issues.


National Instruments does not recommend using Embedded Controllers for Development.

However if your circumstances require software development on embedded controllers such as cDAQs or cRIOs, controllers, there are a few obstacles to overcome.

1. You will probably have issues with running out of memory space. Check these articles to see if you chassis is compatible: cDAQ, cRIO. If your controller is compatible, add an SD card and add it as mapped memory to increase the space on your system. One thing to keep in mind is that your SD card may have limited read/write cycles which is not ideal for long-term storage.

2. You may have more issues troubleshooting your applications. The more complex your windows installation is, the more difficult it will be to pin down certain issues with your application.

3. Your controller may run slower than intended. Due to the small form factor, the hardware included in controllers is usually designed to run single LabVIEW applications. By adding in more software, it may reduce the performance of your controller.


Not Helpful