07-30-2012 01:08 PM
I'm using labview 2011 real-time and on cRIO and PXI chases and when I try to debug using execution highlighting and breakpoints they don't do jack. Usually I can set a breakpoint during initialization, but if multiple loops are involved, especially timed loops nothing happens.
Now the processor is not anywhere near maxed out. I have pretty much given up trying to use these tools when this happens, but today a co-worker experienced the same problem and asked me what is going on.
So, Someone tell me what could be going on!
thanks!
07-31-2012 08:24 AM
Hi David-n-Mo, if highlight execution or breakpoints are not working, it can be that you have the debugging options disabled for that VI, or that you have a re-entrant VI. You can check the status of this 2 options in VI Properties in the execution category.
Do you have problems debugin them while if they run on your main computer? are you running the VIs as a Real Tinme Application? Are you able to place breakpoints in the VI?
Best Regards
07-31-2012 01:47 PM
In both of the cases I'm thinking of the VI was the top level with debugging enabled and not re-entrant. I also checked with my co-worker and she confirmed that her's is also top level with debugging enabled and not re-entrant.
... it occurs to me that i have had a vi that failed to debug due to insane objects detected by MassCompile.
08-01-2012 08:05 AM
Assuming the insane objects are occuring hand-in-hand with the break points not working, I would suggest we go after the insane objects. Here is a link to a knowledgebase that discusses different possible approaches to dealing wit those insane objects. http://digital.ni.com/public.nsf/allkb/AFA28DCC3DE89839862566B200594E8C?OpenDocument