DRAFT SCPI command set for Timing Generator

Responses are underscored

General purpose commands

*RST # reset, equivalent to power on values

*IDN? # who are you
SPOL TIMING_CONTROLLER 2009-8-10 v1.1 # release date, version # of software

set/fetch PRT

:XMIT:PULSe:PERiod 1.022e-3 # SCPI standard is seconds

:XMIT:PULSe::PERiod?
1.022e-3 # response from timing generator

set/fetch Long pulse mode

:XMIT:PULSE:LONG 1
:XMIT:PULSE:LONG?
1

set/fetch Test Pulse location and width

:TEST:PULSE:WIDTh 1e-6 # microseconds
:TEST:PULSE:WIDTh?
1e-6

:TEST::PULSE:DELay 9.99e-4
:TEST::PULSE:DELay?
999e-4

  • No labels

1 Comment

  1. Jim George

    Aug 10, 2009

    Would it not be better to use the natural units for time (seconds)? This would be compliant with the SCPI protocol. Thus, Joe's example would read

    :XMIT:PULSe:PERiod 1.022e-9

    :XMIT:PULSe:PERiod?

    1.022e-9

    For those not familiar with SCPI, the parts of the command that are in lower case are optional. Thus, the following are equivalent:

    :XMIT:PULSe:PERiod 1.022e-9

    :XMIT:PULS:PER 1.022e-9