AnsweredAssumed Answered

Oscilloscope hangs on some commands.

Question asked by vikebo on Jun 26, 2012
Latest reply on Jul 5, 2012 by vikebo

Like • Show 0 Likes0
Comment • 2

Hello

I'm trying to log two channels from a DSOX3014A to a file on a USB device using the Command Expert.

My problem is that the oscilloscope hangs on some commands, the buttons does not respond to new commands or buttons/switches and needs a power cycle to work. Agilent Connection Expert also looses the connection. In some (1 of ~8) hangs, a power cycle of the oscilloscope doesn't help and the PC must also be restarted.

From my debugging so far it seems like commands like
:TRIGger:SWEep NORMal
or
:TIMebase:RANGe 5

makes the command
:WAVeform:DATA?
fail with the message
VI_ERROR_TMO: A timeout occurred | SCPI connection attempt timed out

I updated the firmware a few days ago, but I'm new to this way of controlling the oscilloscope, so I may have some "obvious" fault in Command Expert...

Have attached a screenshot of Command Expert.

Eivind

Attachments

error.jpg109.8 KB

No one else has this question

Outcomes

algoss

Jun 26, 2012 10:41 AM

First, I may be missing something, but I don't see anywhere in your script that you actually tell the scope to "run" or "digitize". If you don't tell it to run, there's no data to get with the ":WAV:DAT?" command, so it will time out.

Second, if you just want to save the data to the USB, then you don't need the ":WAV:DAT?" commands at all. Those tell the scope to offload the data to the controller (PC).

Al

Actions

vikebo @ algoss on Jul 5, 2012 3:34 AM

Thank you very much for your reply.

I removed the digitize command since it was the first which made the oscilloscope hang, but it was probably in combination with the trigger:sweep normal command.

Based on your reply, one of your matlab scripts and a few python scripts I found I managed to do what I needed using python (easier to debug than commandexpert).

Eivind

Actions

2 Replies

algoss Jun 26, 2012 10:41 AM
Mark Correct
Correct Answer
First, I may be missing something, but I don't see anywhere in your script that you actually tell the scope to "run" or "digitize". If you don't tell it to run, there's no data to get with the ":WAV:DAT?" command, so it will time out.

Second, if you just want to save the data to the USB, then you don't need the ":WAV:DAT?" commands at all. Those tell the scope to offload the data to the controller (PC).

Al
Like • Show 0 Likes0
Actions
- vikebo @ algoss on Jul 5, 2012 3:34 AM
  Mark Correct
  Correct Answer
  Thank you very much for your reply.
  
  I removed the digitize command since it was the first which made the oscilloscope hang, but it was probably in combination with the trigger:sweep normal command.
  
  Based on your reply, one of your matlab scripts and a few python scripts I found I managed to do what I needed using python (easier to debug than commandexpert).
  
  Eivind
  Like • Show 0 Likes0
  Actions

Oscilloscope hangs on some commands.

Attachments

Outcomes

Related Content

Recommended Content