You Are Here:
You are here: SCPI Guide > Command Reference > Source Subsystem > SOURce:SCENario:ADVLOG:HEADer?

SOURce:SCENario:ADVLOG:HEADer?

Function

Queries the header for the data of the specified log. This feature is effective as of firmware version 6.7.1.

This command is intended to be used together with the command SOURce:SCENario:ADVLOG?, and allows to get a line of comma-separated labels for fields of corresponding log records.

Command Syntax

SOURce:SCENario:ADVLOG:HEADer? <logID>

<logID> — Log identifier that specifies the advanced log for which to obtain the header.

Notes

The position of specific field label within the comma-separated line is the same as the position of that field’s value within a response line of the SOURce:SCENario:ADVLOG command.

In order to be compatible with future versions of the unit firmware, any user-developed software should not strictly rely on a specific order of fields in responses to the SOURce:SCENario:ADVLOG? and SOURce:SCENario:ADVLOG:HEADer? commands. Before issuing log record requests user-developed software should:

  1. first request the log header once,
  2. then determine positions of all fields of interest based on their labels,
  3. and then refer to log record fields by their determined positions.

The order of fields is fixed within one firmware version.

When the logID argument is RSG, the following fields are available:

Field label
(in response to a “SOURce:SCENario: ADVLOG:HEADer?” query)
Field meaning Possible field values (in response to a “SOURce:SCENario:ADVLOG?” query)
id Record numeric id Integer in range [0; 65535]
RSG Log identifier Always RSG
record_type Record type ANTENNA or BODY_CENTER
time Scenario time in seconds Non-negative decimal
utc_time UTC time in ISO 8601 format e.g., 2016-09-20T20:29:36.100
gps_sow GPS second of week Integer in range [0; 604799]
speed_over_ground Speed over ground, m/s Non-negative decimal
acceleration_over_ground Acceleration, m/s2 Decimal
vertical_speed Vertical speed, m/s Decimal
vertical_acceleration Vertical acceleration, m/s2 Decimal
heading Course, degrees [0 ; 360)
heading_rate Course rate, degrees/s Decimal
pitch Pitch, degrees Decimal in range [-180; +180]
pitch_rate Pitch rate, degrees/s Decimal
roll Roll, degrees Decimal in range [-180; +180]
roll_rate Roll rate, degrees/s Decimal
yaw Yaw, degrees Decimal in range [-180; +180]
yaw_rate Yaw rate, degrees/s Decimal
latitude Latitude, degrees Decimal in range [-90; +90]
longitude Longitude, degrees Decimal in range [0; +360]
altitude Altitude, degrees Decimal
pos_x ECEF X position, m Decimal
pos_y ECEF Y position, m Decimal
pos_z ECEF Z position, m Decimal
vel_x Speed ECEF X-projection, m/s Decimal
vel_y Speed ECEF Y-projection, m/s Decimal
vel_z Speed ECEF Z-projection, m/s Decimal
acc_x Acceleration ECEF X-projection, m/s2 Decimal
acc_y Acceleration ECEF Y-projection, m/s2 Decimal
acc_z Acceleration ECEF Z-projection, m/s2 Decimal
vel_e East speed projection, m/s Decimal
vel_n North speed projection, m/s Decimal
vel_u Vertical speed projection, m/s Decimal
acc_e Acceleration east projection, m/s2 Decimal
acc_n Acceleration north projection, m/s2 Decimal
acc_u Acceleration vertical projection, m/s2 Decimal

When the LogID is SAT, the following fields are available:

Field label
(in response to a
“SOURce:SCENario: ADVLOG:HEADer?”
query)
Field meaning Possible field values
(in response to a
“SOURce:SCENario:ADVLOG?”
query)
id Record numeric id Integer in range [0; 65535]
SAT Log identifier Always SAT
time Scenario time, s >= 0
utc_time UTC time in ISO 8601 format e.g. 2016-09-20T20:29:36.000
gps_sow GPS second of week Integer in range [0; 604799]
sat_id Satellite ID e.g. G11 for GPS satellite 11
pr_l1 Pseudorange L1, m Decimal
prr_l1 Pseudorange rate L1, m/s Decimal
doppler_shift_l1 Doppler shift L1, Hz Decimal
doppler_shift_rate_l1 Doppler shift rate L1, Hz/s Decimal
pos_x Satellite ECEF X position, m Decimal
pos_y Satellite ECEF Y position, m Decimal
pos_z Satellite ECEF Z position, m Decimal

As of firmware version 6.7.5, when LogID is NAVMSG, the following fields are available:

Field label
(in response to a
“SOURce:SCENario: ADVLOG:HEADer?”
query)
Field meaning Possible field values
(in response to a
“SOURce:SCENario:ADVLOG?”
query)
id Record numeric id Integer in range [0; 65535]
NAVMSG Log identifier Always NAVMSG

time

Scenario time, s

>= 0

utc_time UTC time in ISO 8601 format e.g., 2016-09-20T20:29:36.000
sat_id Satellite ID e.g., G11 for GPS satellite 11
signal_type Signal type of navigation message For GPS satellites: L1CA, L1P, L1CAP, L2P; “L1CAP” is used when the satellite has both L1CA and L1P signals enabled.
sf_id Subframe id Integer per corresponding ICD
pg_id Page id Integer per corresponding ICD
msg Navigation message data Hexadecimally-encoded binary data of navigation message e.g., 8BFFFC464C7749C005364A923E46B3001EDA4C48A6BEC14EBA60ECD324A90057186FC0133C4. String length depends on corresponding navigation message length. Please note that data length (in bits) is not necessarily multiple of 8 bits, hence the number of hex digits is not necessarily even. It can be even or odd. Usually hex dump represents some amount of bytes, each byte is represented by 2 hex digits. In this case a half byte is possible, therefore there can be an odd number of hex digits.

Currently supported navigation messages are:

  • GPS: L1CA, L1P, L2P; QZSS: L1CA; Beidou: B1, B2.

Navigation message decoding functionality is provided by GSG StudioView software.

Example:

SEND:

sour:scen:advlog:head? sat

READ:

id, SAT, time, utc_time, gps_sow, sat_id, pos_x, pos_y, pos_z, pr_l1, prr_l1, doppler_shift_l1, doppler_shift_rate_l1