Error Message: No VIs to download from application

[LabBEAN]

Got the error message in the subject by:

Operate » Debug Application or Shared Library...

Typed in IP Address of the cRIO

Clicked Refresh

Selected startup.rtexe

Clicked Connect

Called NI and found out that the cRIO-9004 controller does not support remote debug.  There is a CAR, but due to the age of the controller NI does not plan to add debugging support.

[Matt.M]

Hello LabBean,

CAR#281651 is filed on this issue. As of right now a target version for fix has not been set.

Regards,

Matt M.

[Matt.M]

Hi Everyone,

An update on this issue.  SSE2 Optimizations were enabled on the executable. Once we disabled the SSE2 Optimizations in the build specification we were able to connect to the remote executable.

The solution is here: http://forums.ni.com/t5/LabVIEW/Startup-EXE-is-not-running-in-cRIO-9002-controller/m-p/2102462

Regards,

Matt M.

[LabBEAN · Accepted solution]

Matt is correct.  As indicated by this document, cRIO-900x targets do not support SSE2.  The "No VIs to download from application" message during attemtped remote debug AND the fact that my startup.rtexe would not run were both related to this.

It's important to note that cRIO-9004 (and maybe others) does not support remote debugging even if you disable SSE2 and connect to the startup.rtexe.  If I connect to a debuggable EXE on the cRIO and attempt to place a probe, the VI locks up.  If I then abort that VI, reconnect to the target, place a probe, and wait, LabVIEW and Windows lock up.  Recourse = bring up Task Manager and end the LabVIEW.exe process.

Takeaways:

(1) Disable SSE2 optimization when deploying to cRIO-900x targets.

(2) Don't attempt remote debugging on a cRIO-9004 even though LabVIEW allows the connection.