10-09-2014 04:19 AM
Hi, I have posted this error before as well. Most replied that the queue reference is invalid. But why does the error always occur randomly after 5-6 hours of switching on the hardware. Otherwise this subVI as well as the main VI works perfectly. (This subVI controls the status of an Electric Vehicle depending on the status obtained from the charge controller of a charging station).
Solved! Go to Solution.
10-09-2014 04:39 AM
The error first points to the dequeue element of the main VI and then finally points to the dequeue element in the subVI. The status vehicle letter has to be available both in the main VI and subVI, is there a better way of implementing it, to avoid the error?
10-09-2014 04:57 AM
Where else is that cluster going? Where would those queued be destroyed? 99% of the time I have seen these errors is because some other process destroyed the queue, making the reference invalid.
10-09-2014 05:00 AM
Are you using paralell vi:s that are spawned dynamically?
It might be that the queue that becomes invalid, hence returns error 1, was first obtained in a vi hierarchy other than the one were the error occurs.
If the top-vi in that hierarchy becomes idle (i.e. stops), it will kill the queue as it was the one that created it (even if no release queue is called). Then if that queue is referenced in another, paralell running herarchy, the error will be generated.