LabView enters some sort of deadlock after writing to the Rohde & Schwarz UPL audio analyser

[Julien van Brussel]

It sometimes (pretty often) happens that after a write commando to the UPL (through GPIB), LabView enters some sort of deadlock. The LabView Program indicates as executing, but nothing happens. The fault enters in my complex program, but also in very simple examples. When I boot the UPL from default (factory setting) and run a very simple program, the fault happens as well. So I suggest that it�s not any UPL user made device-setting that causes the problem.
The problem appears the most in the following vi�s:
- RSUPL Send Trigger
- RSUPL Measure Single Channel
(Common used vi�s, I should say)

I hope someone can give me some hints for solving the problem.


Additional Information about used hard- / software:
- UPL firmware v2.03
- LabView version 5.1
- Instrument driver library �rsupl_lv5.zip� - Rev 3.0 - 8/1999

With kind regards,

Julien van Brussel.

[Ryan_M]

What do you mean by deadlock? If you get an infamous Windows BSOD, the error may be documented in the National Instruments Knowledge Base at http://search.ni.com/search/?layout=KB

If you are unable to find a description of the crash, I might suggest using NI-SPY to log the code (set the option to log to file) and submit a response the National Instruments' Ask an Engineer page (http://www.ni.com/ask).

If the program only seems to freeze and not crash, there may be something else causing this. What setting do you have specified as the timeout? If you have disabled the timeout then the writes or reads my seem to hang the system.

One thing I'd suggest trying is to isolate a sequence from within IBIC to reproduce the problem.