AnsweredAssumed Answered

Unable to measure phase shift between two signals solved

Question asked by Eugene_E on Nov 17, 2015
Latest reply on Dec 28, 2015 by Eugene_E

Like • Show 0 Likes0
Comment • 6

Hello!

I am trying to figure out how to measure phase shift between two signals automatically. I have them generated by the external generator (see attached picture S1.png).

Now I do:

-> *IDN?
<- KEYSIGHT TECHNOLOGIES,MSO9404A,MY52250157,05.51.0002
-> *RST
-> *CLS
-> :AUToscale
-> :DIGitize
-> :MEASure:PHASe? CHANnel1, CHANnel2
<- 9.99999E+37

Now I am adding measurement manually via menu: "Measure" / "Add Measurement" / Select "Phase" measurement / Make sure Source 1 = Channel 1 & source 2 = Channel 2 and press OK.

The phase now is measured (see attached picture S2.png).

And now the same command woks:
-> :MEASure:PHASe? CHANnel1, CHANnel2
<- 1.8000E+02

So the question is: what am I doing wrong the first time I am try to measure phase shift via commands only?

Edited by: Eugene_E on Dec 28, 2015 8:04 AM

Attachments

S1.png606.1 KB
S2.png588.8 KB

No one else has this question

Outcomes

algoss

Nov 30, 2015 5:12 AM

I think that you should make sure that you have the '' parameter specified. I use something like ':MEASure:PHASe CHANnel1,CHANnel3,RISing" and never have any problems.

Al

Actions

Eugene_E @ algoss on Dec 14, 2015 4:39 AM

Thanks for your reply!

But according to the documentation (I used Keysight Infiniium Oscilloscopes Programmer's Guide, page 741) I think this parameter is optional and the example ":MEASure:PHASe? CHANnel1,CHANnel2" is valid.

Nevertheless I tried specify edge explicitly: ":MEASure:PHASe? CHANnel1, CHANnel2, RISing"

The results are the same: the measurement only works in case of being added manually via "Measurements" menu.

Actions

algoss

@ Eugene_E on Dec 14, 2015 6:19 AM

1) The documentation may be wrong
2) I seldom depend on defaults. I strive to always fully define the measurement I want to make.

Al

Actions

Eugene_E @ algoss on Dec 14, 2015 6:44 AM

Yeah, I totally agree. That is why I tried to specify this parameter explicitly, though with no effect.

Actions

algoss

@ Eugene_E on Dec 14, 2015 10:31 AM

The short answer is "I don't know what's wrong with your measurement, It works fine on my scope."

Have you checked the threshold settings when you are doing it with the command line? What are they?

When you use the command line, what shows up on the bottom of the screen? When you create a measurement programmatically, it shows up on the screen, just like if you create it from the interface.

Al

Actions

Eugene_E @ algoss on Dec 28, 2015 7:04 AM

Concerning edges, would you be so kind to tell which command is to set/read the edge detection level for the measurements?

Nothing changes on the screen when I send measurements commands via GPIB (regardless of the measurement being success or not, for example if I measure amplitude the result is valid but nothing changes on the screen).

SOLUTION: The problem described in the post seemed to be solved by making scope to work on all edges explicitly (":ANAL:AEDG ON").

P.S. Strange but the manual says that:
>Using the parameter will set the "Measure All Edges" mode if it is not currently set.
I tried to use the direction but with no effect. So now I just issue "work on all edges" command after reset and it works well!

Thank you, algoss!

Actions

6 Replies

algoss Nov 30, 2015 5:12 AM
Mark Correct
Correct Answer
I think that you should make sure that you have the '' parameter specified. I use something like ':MEASure:PHASe CHANnel1,CHANnel3,RISing" and never have any problems.

Al
Like • Show 0 Likes0
Actions
- Eugene_E @ algoss on Dec 14, 2015 4:39 AM
  Mark Correct
  Correct Answer
  Thanks for your reply!
  
  But according to the documentation (I used Keysight Infiniium Oscilloscopes Programmer's Guide, page 741) I think this parameter is optional and the example ":MEASure:PHASe? CHANnel1,CHANnel2" is valid.
  
  Nevertheless I tried specify edge explicitly: ":MEASure:PHASe? CHANnel1, CHANnel2, RISing"
  
  The results are the same: the measurement only works in case of being added manually via "Measurements" menu.
  Like • Show 0 Likes0
  Actions
  - algoss @ Eugene_E on Dec 14, 2015 6:19 AM
    Mark Correct
    Correct Answer
    1) The documentation may be wrong
    2) I seldom depend on defaults. I strive to always fully define the measurement I want to make.
    
    Al
    Like • Show 0 Likes0
    Actions
    - Eugene_E @ algoss on Dec 14, 2015 6:44 AM
      Mark Correct
      Correct Answer
      Yeah, I totally agree. That is why I tried to specify this parameter explicitly, though with no effect.
      Like • Show 0 Likes0
      Actions
      - algoss @ Eugene_E on Dec 14, 2015 10:31 AM
        Mark Correct
        Correct Answer
        The short answer is "I don't know what's wrong with your measurement, It works fine on my scope."
        
        Have you checked the threshold settings when you are doing it with the command line? What are they?
        
        When you use the command line, what shows up on the bottom of the screen? When you create a measurement programmatically, it shows up on the screen, just like if you create it from the interface.
        
        Al
        Like • Show 0 Likes0
        Actions
        Eugene_E @ algoss on Dec 28, 2015 7:04 AM
        Mark Correct
        Correct Answer
        Concerning edges, would you be so kind to tell which command is to set/read the edge detection level for the measurements?
        
        Nothing changes on the screen when I send measurements commands via GPIB (regardless of the measurement being success or not, for example if I measure amplitude the result is valid but nothing changes on the screen).
        
        SOLUTION: The problem described in the post seemed to be solved by making scope to work on all edges explicitly (":ANAL:AEDG ON").
        
        P.S. Strange but the manual says that:
        >Using the parameter will set the "Measure All Edges" mode if it is not currently set.
        I tried to use the direction but with no effect. So now I just issue "work on all edges" command after reset and it works well!
        
        Thank you, algoss!
        Like • Show 0 Likes0
        Actions

Unable to measure phase shift between two signals solved

Attachments

Outcomes

Related Content

Recommended Content