01-05-2007 02:36 PM
01-08-2007 05:21 PM
01-09-2007 10:12 AM
01-10-2007 08:09 PM
Hi dehrenberg,
As Jason asked, how do you know it is the GPIB that causes the problem? Is this 100% reproducible, as in, does the printcapture immediately fail when you open LabVIEW? LabVIEW has not been tested with this utility, so that is why we need this information. Does it cause any other hardware on your system to fail? Is there any other software that you have tested to see if it does the same thing? National Instruments software is designed to be fully compatible with National Instruments hardware, so what do you mean by the "software always preempts other applications..."? We need to determine if this is an issue on the GPIB side or on the LabVIEW side so we can troubleshoot further with you.
Have a great day!
01-16-2007 12:29 PM
Chris, sorry for the tardy reply, there was no email generated by your reply on the 10th.
your wrote: Is this 100% reproducible, as in, does the printcapture immediately fail when you open LabVIEW?
"Immediately fails" is difficult to determine. With enough trials, I might be able to corrupt a transfer-in-progress, but the symptoms are: screen capture works when LabView is not running, screen capture fails when LabView is running. The screen capture fails at the first LabView window (the splash screen asking for <New VI> or <Open VI>).
I was not trying to operate any other GPIB instruments during the printCapture session. The only instrument physically connected to the bus was the HP spectrum analyzer.
My test set is still manually operated and I don't have other GPIB applications running. (If I do use the GPIB, it will probably be through the LabView interface.)
The problem looks to me like a classic competition-for-resource where LabView will not release what it thinks is a dedicated resource. If the (National) GPIB card is not reference from within the GUI, is the GPIB card free to be accessed by other programs?
The trial version of printCapture is free. An instrument with a <print> command can be use to test the utility.
David Ehrenberg, dehrenberg@multiplexInc.com
01-18-2007 01:19 PM
01-18-2007 01:59 PM