05-25-2010 12:23 PM
05-25-2010 12:41 PM
Does the event structure handle both the boolean value changes as well as the tab control value change? How much CPU time is the DAQ task using? Are there any dependencies between the loops?
Please attach your vi, if possible.
05-25-2010 12:58 PM
The event structure handles only the boolean cluster change, there is no event for the tab control change.
It looks like the data acquisition loop is running about every 2 ms (it's not DAQ, it's NI-CAN).
05-25-2010 01:10 PM
05-25-2010 01:17 PM
05-25-2010 01:31 PM
Well, a VI would be much more helpful compared to a picture. We cannot see the other cases, for example!
A big no-no is placing the event structure inside a case structure unless all other cases complete fast! Of course here "idle" is a constant, so the case structure is not even needed. 😉
05-25-2010 02:23 PM
05-25-2010 02:34 PM
I am hesitant to post much more code; I thought that maybe someone might have had a similar issue.
I did try unchecking the Lock Front Panel checkbox but it did not make a difference.
05-26-2010 01:06 PM
05-26-2010 04:04 PM - edited 05-26-2010 04:10 PM
Just curious, but why are you using the Tab Indicator and booleans to change tabs? Why not use a tab control and allow the user to click directly on the tab they want? Then you can set up an event for the tab control be clicked. With a control, if you need to change things on the tab display you can just property nodes to update the control.
________________________________________________________________________________________________
After a couple presses of a button I can usually get it to change the tab. Any ideas on how I can fix this unresponsiveness?
________________________________________________________________________________________________