LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabView enters some sort of deadlock after writing to the Rohde & Schwarz UPL Audio Analyser

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 probl
em.

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.
0 Kudos
Message 1 of 6
(2,971 Views)
It sounds like one of the VIs is stuck in a loop, probably waiting for something to happen. When you run the VI and it gets stuck you can go to the diagram and select the "Highlight Execution" button, then you should be able to see where the program is "stuck". If you see a subvi that has a green arrow in it then that vi is running and may be holding you up.

Brian
Message 2 of 6
(2,971 Views)
I have experienced a similar problem with my Rohde and Schwartz AMIQ. I have found that the instrument likes more simplified command sets. The question is have you stepped through the VI's in debug mode to see if there is an error being generated inside the VI? If so, what was the indication when in debug mode and where exactly was it hanging up at inside the VI? It sound like the instrument is erroring out when you execute the VI and if it is like my experience with Rohde and Schwartz equipment, the error is internal to the instrument and is not recognized by labVIEW so it locks up at that point waiting on a response from the instrument which it never gets. You can try to run the instrument manually using the software that was provided with it (not labVIEW)
to see if it will accept the commands etc. to illiminate the instrument from the problem solving process. I have also found that the instrument needs more time to process the trigger so you might want to add a waite state before the trigger VI is executed.That is all I can offer without more detail on the chain of events happening. Good Luck.
Message 3 of 6
(2,971 Views)
The other possible problem should not be overlooked: There could be a bug in the instrument itself. It used to be fairly common to have LV programs run considerably faster than the GPIB interface on instruments (Even with LV1 running on a MacPlus!). If you are trying to talk to the instrument too fast, it can cause problems because the instrument doesn't end up in the logical state the software is expecting.

I once had a HP spectrum analyzer that had a protocol where you had to send it a command and then check a status byte to determine when it was ready to respond. Occasionally, the code would error out because when it went to check on the instrument status, the byte read "awaiting command" instead of "busy" or "waiting to respond". I finally figured out
that I was sending a command and then asking the instrument its status before it had a chance to see the command in it's command buffer. Inserting a 10msec wait fixed the problem. Wierd things can happen.

Following the execution highlighting as has been suggested by a couple folks should get you into the right part of the code. Then it's a matter of figuring out why the code is hung: Your fault or their fault--and if its their fault: how do you work around it...

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
Message 4 of 6
(2,971 Views)

Hi I need help to set up my AMIQ device by Labview, does any one can help me to startup with my device. my exact problem at now is that I do not know how I should provide a suitable signal for my device. I should mention that I can control and initialize the device.

where can I find some example for control my AMIQ by Labview???

thanks in advance

0 Kudos
Message 5 of 6
(2,503 Views)

Please contact the R&S customer support customersupport@rohde-schwarz.com. They are pleased to help you with your issue!

0 Kudos
Message 6 of 6
(2,493 Views)