You Are Here:

SOURce:SCENario:DATEtime?

Function

Query the Date, Time and Timescale of the running scenario or the start time of the loaded scenario.  The default timescale is GPS. However, the user can optionally provide a parameter to convert the current Date and Time of the running scenario to various timescales including GPS, UTC, BeiDou, QZSS, Galileo, GLONASS, EGNOS Network Time and WAAS Network Time. If no argument is provided, GPS time scale is returned. Correct time conversion to a timescale different from GPS can be performed only when a scenario is running, because timescales relation information is loaded only when starting a scenario. The special parameter RUNTIME can be used to get start time together with elapsed scenario time in seconds when scenatio is running.

Command Syntax

When scenario is not running:

  • SOURce:SCENario:DATEtime?

When scenario is running:

  • SOURce:SCENario:DATEtime? <gps|utc|bds|qzt|gal|glo|glo0|ent|wnt>
  • SOURce:SCENario:DATETIME? RUNTIME

Return

When no argument is specified, or the timescale argument is specified, returned string corresponds to one of the following formats:

  • MM-DD-YYYY hh:mm:ss.s AAA
  • NTP

…where MM=Month {01-12}, DD=day of month {01-31}, YYYY=year, hh=hours {00-23}, mm=minutes {00-59}, ss.s=seconds {00-59} with one decimal of sub-seconds digits.

The Timescale AAA= {GPS, UTC, BDS, QZS, GAL, GLO, GLO0, ENT, WNT} field supports various GNSS timescales. If AAA is not supplied, the default is GPS timescale.

NTP is returned when scenario start time is set to NTP.

When RUNTIME argument specified, returned string is a pair:

  • <date -time>
  • <elapsed -seconds>

...where date time is date and time in GPS scale as specified above, and elapsed seconds is time in seconds elaped from scenario start.

Example

QUERY:

SOURce:SCENario:DATEtime? GLO

RESPONSE:

05-07-2012 12:34:56.7 GLO

QUERY:

SOUR:SCEN:DATETIME? RUNTIME

RESPONSE:

12-31-2012 23:55:00.1 GPS, 60.1