04-21-2009
02:55 PM
- last edited on
04-18-2025
01:50 PM
by
Content Cleaner
I am trying to debug an application that runs on a RT target. I am having a problem with debugging a reentrant vi. I am following the suggestions in this article (https://www.ni.com/docs/en-US/bundle/labview/page/suggestions-for-using-execution-systems-and-priori...), but by vi is not behaving in the mannor described. In the vi's properties under execution, I have the Allow debugging check box marked and the Reentrant execution check box marked, also I have the Preallocate clone for each instance radio button selected. When I open the vi for debugging while the application is running, "Clone" does not appear in the title bar and I cannot probe any of the wires.
How do I probe the wires if I need to maintain states for each instance of the reentrant vi? And if I can't probe, how do I figure out what is going on durring execution?
I am using LV 8.5.1 with Win XP, the real time target is a cRIO-9012
Thanks for any help.
04-22-2009
01:46 PM
- last edited on
04-18-2025
01:53 PM
by
Content Cleaner
Hi,
Are you following the steps in this LabVIEW help file to debug your Real-Time application?
Regards,
Stephen S.
04-22-2009 01:51 PM
Set a break point in the re-entrant VI then when each instiance opens you can place your probes.
Ben
04-27-2009 01:14 PM
Hi,
The reason you are no being to probe any of the reentrant vis is beacause you can't. Under RT context , you cannot do the debugging of the reentrant vis as normally you would do( putting probes and all) . Move it to localhost context and you can see all the options again. Now coming to the solution of it, you might try using breakpoints inside the vis and use indicators as much as possible. Another way would be to move ur vis into localhost context and do all your debugging , where you can, and then deploy onto the target.