AnsweredAssumed Answered

Timeout setting for :DIGitize

Question asked by bret on Jul 23, 2013
Latest reply on Oct 12, 2013 by ysspatil

Like • Show 0 Likes0
Comment • 4

Hey folks,

This might sound silly, but is there a golden rule on how much timeout to put before performing a :DIG?

Is (2 * timeRange) sufficient for a continuous signal?

Thanks,
bret.

No one else has this question

Outcomes

4 Replies

algoss Jul 23, 2013 11:52 AM
Mark Correct
Correct Answer
Which scope?

I usually set an overall timeout for everything, like 10 or 20 seconds.

Al
Like • Show 0 Likes0
Actions
- bret @ algoss on Jul 24, 2013 7:21 AM
  Mark Correct
  Correct Answer
  The 3000 X-Series.
  
  I see. Would that be enough if I am acquiring at 1s/division scaling? I've tried 1s * 10divisions * 2buffer, but occasionally the :DIG still timeout early. Weird. Not every time though, so there's no point showing my steps, hence my question on a generic range,
  Like • Show 0 Likes0
  Actions
  - algoss @ bret on Jul 25, 2013 5:58 AM
    Mark Correct
    Correct Answer
    I guess my short answer is, "I don't know". I don't have any scopes that can sample that slowly, or for that long. I generally only worry about timeouts in data transfers, where I want to move millions (or hundreds of millions) of points to the controller.
    
    Al
    
    Disclaimer: For more reliable response, you should consider calling your local Agilent Technical Call Center. The Agilent Forums are monitored on an "as available" basis, and aren't necessarily the fastest way to get technical questions answered.
    Like • Show 0 Likes0
    Actions
  - ysspatil @ bret on Oct 12, 2013 5:22 PM
    Mark Correct
    Correct Answer
    Have you accounted for the trigger time? Even with your settings, if the trigger is delayed, you can face this issue.
    Like • Show 0 Likes0
    Actions

Timeout setting for :DIGitize

Outcomes

Related Content

Recommended Content