debugging stand-alone application on cRIO

[davidc10]

I have deployed a stand-alone application to our cRIO as "Set as Startup".  It deploys and runs fine.

However, I am unable to debug the deployed stand-alone application - the message is "Failed to lookup debuggable applications or shared libraries".

Build settings are debug enabled, VI server is enabled on the cRIO (and on the PC), but when I try to connect the debugger through the "Operate" menu my network spy shows 96 bytes being uploaded to the cRIO on 10.x.x.2:3580, but no response from the cRIO.

The R-T System Manager works fine and connects on that port - but I close it before I attempt to debug.

 A second issue is that when I re-build and deploy as "Unset as Startup", the application still starts upon reboot.

 
Thanks,
David

[Stephen_S.]

Hi David,

What version of LabVIEW, and what operating system are you using to deploy this application? Also, do you have a firewall enabled? Try disabling any firewalls to see if you are still getting this same problem.

Regards,

Stephen S.

[davidc10]

Stephen,

I'm using 8.5.1 under XP SP2.   I should have mentioned that I already tried it with the firewall disabled.  

Thanks for the reply,

David

[Stephen_S.]

Hi David,

Make sure you are following all the steps in the LabVIEW Real-Time Help file for Debugging Stand-Alone Real-Time Applications. Especially note that the IP address of the Real-Time target (cRIO in this case) has to be entered into the Machine name or IP address field.

As far as your question about Unset as Startup, once this option is selected, the application has to be deployed for the changes you made to take effect.

Regards,

Stephen S.

Message Edited by Support on 05-28-2010 12:52 PM

[davidc10]

Stephen,

I believe I have been following those instructions very closely from the start.  It is at step 5  that I have the problem.  When I enter the IP of the cRIO a request is sent to the cRIO, but there is no response from the cRIO.

I've included some screen shots from my setup, and one showing network traffic to the cRIO on port 3580, with no response from the cRIO.

Regarding the "Unset" issue: as  I said in my original post "I re-build and deploy as "Unset as Startup" " - so I think I am also following the right procedure here.  As I uderstand it there are two distinct types of deployment - one is to deploy the built project and the other is to deploy cRIO settings, both available from the Project Explorer window.  I do both when I change any settings.

 If you want to see any more settings, or if there is a way to generate a printout without the screen shots, let me know.

Thanks,

David

[wildcatherder]

Old post but others will find it looking for help with the failure of debugger to connect to remote computer.

This may seem obvious but if you turn on debugging in the EXE build, you MUST also re-build the INSTALL.  Often, after making changes to the VI, I don't rebuild the INSTALL.  In this case the debugger seems to require additional resources not provided in any VI, so the INSTALLER must include them in its build.