error -826 occurred at timed loop

[eximo]

I am getting the LabVIEW Error #-826 occured at Timed Loop in (*calling VI*)

Possible reason(s):

LabVIEW: A time-critical VI contain a timed structure.

_________________________________________________________________

I checked to make sure the execution properties were set correctly for this VI and they were.  Standard execution and normal priority.  But the error is still occuring.  What else can trigger this error?  

-JW

[ogk.nz]

From the sounds of that error I would say that there is something inside your timed-loop that is causing the problem not the timed loop itself. Do you have any waits or other timing based VIs within the timed loop?

Would you be able to show the VI or maybe just the timed loop? It would definitely help with finding the root of the problem.

[eximo]

ogk,

There are a million moving parts in this timed loop, it would not be useful to upload the vi nor would it be useful to view it, and would mostly likely be a frustrating waste of time for you.  Through standard debugging procedures I have acertained that the loop itself is what is triggering the error.

I had experieced the problem the week before the posting of this message because the VI's execution was set to a time critical priority, which is a no-no when using timed loops apparently, I though I had disposed of the error message by changing the execution to standard priority as was recommended.  That was not the case as the error message either came back upon the next time I opened the VI for editing, or I was mistaken about fixing the bug and it is still present.

I am able to get rid of the error message by changing the timed loop to a normal while loop, doing so without making any other changes.  However this is not as desirable, since I am interested in the properties of the timed loop.

I have not upgraded to sp1 or the f1 patch for LabVIEW 2014. This error occured as soon as I upgraded to 2014 and since this is a new error message that did not exist in LabVIEW 2011 is it possible there was a bug in the initial release of 2014?

-Regards,

JW