Error -1074118647

[gammarays]

I'm using a PCI-5122 with Labview 8.2 on a XP machine.  I have two apps using producer loop/consumer loop to read radiation detector signals.  They have identical NI-scope coding leading to the producer loop.  However one runs OK apparently - at least it delivers signal to the consumer loop which runs.  In the other the producer loop runs but the consumer loop does not and when I stop the program (a switch on the producer loop terminal) it generates an error #-1074118647, located in the ni-scope read cluster.  I cannot find this error code listed... 

What's up?

Thanks

Dave Allen

[Doug_L._Bear]

This error code seems to mean that a previous acquistion of the scope is already in use.  Are you properly closing our your driver session at the end of your code?  What is the difference between the two pieces of code that you have, you say the producer aspect is the same?  What VI is generating this error code.  The message should say error such and such occured at start.vi or something to that effect.

This discussion forum seems relevant.

http://forums.ni.com/ni/board/message?board.id=170&message.id=203539&requireLogin=False

[gammarays]

Hi Doug

Thanks for getting back to me.

The message reads as follows:

Error -1074118647 occurred at Error occurred at: niScope Read Cluster.vi:1

Possible reason(s): (Hex OxBFFA4009)

A previous acquisition is still in progress.  If you are attempting to change an attribute, note you can only change fetch attributes while an acquisition is still in progress. 

Status Code:  -1074118647

This message occurs at the Release Queu vi, which is downstream from the Read Cluster.

There seem to be two problems:  one is the fact that while it is running the consumer loop doesn't, and then this message occurs if I try to stop it at the producer loop terminal.

I've attached the vi's in question.  They are ragged because they are unfinished and modified in attampts to figure out what's going on, but maybe they'll help.  The MCA.vi is the one in which both loops seem to run, and Counter.vi if the problematic one.

Thanks.

Dave

[Doug_L._Bear]

How are you determining that your consumer loop is not running.  I would recommend you run highlight execution and see what is actually happening.  You may also want to wire up the error wires through the queueing VIs to see if errors are coming out of there.  The error you are receiving didn't make a whole lot of sense to me as there is nothing that would be changing any of the run properties while the VI was running.