c# : winform : pdf viewer : Add page number to pdf in preview SDK application project wpf windows web page UWP RS_SigGen_GNSS_Operating_en_0830-part1434

Annex
Satellite Navigation
301
Operating Manual 1173.1427.12 ─ 08
Container
Tag name
Parameter
Description
<maxyawrate>
Maximum rate of change of the yaw/heading (rad/s)
<maxyawaccelera-
tion>
Maximum second rate of change (acceleration) of the yaw/head-
ing (rad/s2)
<maxyawjerk>
Maximum third rate of change (jerk) of the yaw/heading (rad/s3)
<maxpitchangle>
Maximum pitch/elevation angle (rad)
<maxpitchrate>
Maximum rate of change of the pitch/elevation (rad/s)
<maxpitchaccelera-
tion>
Maximum second rate of change (acceleration) of the pitch/
elevation (rad/s2)
<maxpitchjerk>
Maximum third rate of change (jerk) of the pitch/elevation
(rad/s3)
<maxrollangle>
Maximum roll/bank angle (rad)
<maxrollrate>
Maximum rate of change of the roll/bank (rad/s)
<maxrollaccelera-
tion>
Maximum second rate of change (acceleration) of the roll/bank
(rad/s2)
<maxrolljerk>
Maximum third rate of change (jerk) of the roll/bank (rad/s3)
<proximity>
Specifies the maximum allowed deviation from the waypoints
specified by the user (m)
A.1.3 Antenna Pattern / Body Mask Files
The antenna patterns files are supported by instruments equipped with option
R&S SMBV-K102/103. Some parameters additionally require option R&S SMBV-K92.
Two files describe an antenna, the antenna pattern *.ant_pat file and the phase
response *.phase file.
Both files must have the same file name and must be stored in the same directory. The
*.ant_pat file describes the power response matrix of each antenna. The instrument
retrieves the phase response matrix from the *.phase file.
If the required *.phase file does not exist, a zero phase response is assumed.
Both file *.ant_pat and *.phase should have the same content but different data
section <data> (see table 1-4)
The following are two examples of the file format: an extract of the description of an
antenna pattern with three antennas and description of an antenna with four sectors.
Example: Anntena pattern with three antennas
The follwoing is an extract of the description.
<?xml version="1.0" encoding="ISO-8859-1"?>
<antenna_pattern>
<antenna_descr count="3" use_same_pattern="no">
<antenna id="1" YawAxis_Z_offset="-5.5" PitchAxis_Y_offset="0"  
User Environment Files
Add page number to pdf in preview - insert pages into PDF file in C#.net, ASP.NET, MVC, Ajax, WinForms, WPF
Guide C# Users to Insert (Empty) PDF Page or Pages from a Supported File Format
add pages to pdf online; adding page numbers pdf
Add page number to pdf in preview - VB.NET PDF Page Insert Library: insert pages into PDF file in vb.net, ASP.NET, MVC, Ajax, WinForms, WPF
Easy to Use VB.NET APIs to Add a New Blank Page to PDF Document
add and delete pages in pdf; add page pdf
Annex
Satellite Navigation
302
Operating Manual 1173.1427.12 ─ 08
RollAxis_X_offset="-11.0" Yaw_offset="0" Pitch_offset="0"
Roll_offset="0" />
<antenna id="2" YawAxis_Z_offset="5.5" PitchAxis_Y_offset="-4" 
RollAxis_X_offset="-11.0" Yaw_offset="0" Pitch_offset="0"
Roll_offset="120" />
<antenna id="3" YawAxis_Z_offset="5.0" PitchAxis_Y_offset="4"
RollAxis_X_offset="-11.0" Yaw_offset="0" Pitch_offset="0"
Roll_offset="240" />
</antenna_descr>
<az_res> 1.00000000e+000 </az_res>
<elev_res> 1.00000000e+000 </elev_res>
<data>
-179.5,-178.5,-177.5,-176.5,-175.5,-174.5,-173.5,-172.5,-171.5,-170.5,-169.5,-168.5,
-167.5,-166.5,-165.5,-164.5,-163.5,-162.5,-161.5,-160.5,-159.5,-158.5,-157.5,-156.5,
-155.5,-154.5,-153.5,-152.5,-151.5,-150.5,-149.5,-148.5,-147.5,-146.5,-145.5,-144.5,
-143.5,-142.5,-141.5,-140.5,-139.5,-138.5,-137.5,-136.5,-135.5,-134.5,-133.5,-132.5,
...
</data>
</antenna_pattern>
Example: Antenna with four sectors
The follwoing is a file decribing an antenna with four sectors.
<?xml version="1.0" encoding="ISO-8859-1"?>
<antenna_pattern>
<antenna_descr count="1" use_same_pattern="no">
<antenna id="1" YawAxis_Z_offset="0" PitchAxis_Y_offset="0"  
RollAxis_X_offset="0" Yaw_offset="0" Pitch_offset="90"
Roll_offset="0" />
</antenna_descr>
<az_res> 90.00000000e+000 </az_res>
<elev_res> 90.00000000e+000 </elev_res>
<data>
-135.0,-45.0,45.0,135,45.0,0.0,3.0,6.0,9.0,-45.0,0.0,3.0,6.0,9.0
</data>
</antenna_pattern>
The table 1-4 describes the used tags and parameters.
Table 1-4: Format of *.ant_pat and *.phase file
Container
Tag name
Parameter
Description
<antenna_pattern>
Defines antenna pattern File
<antenna_descr>
Contains the descriptions of the antennas
<count>
Number of antenna patterns. Value range = 1 to 4.
<use_same_pat-
tern>
Specify whether the same data section is used for all the anten-
nas or not.
"yes": the data section will be used for all antennas
"no": the data section has to be augmented with the data of
all antennas consecutively
User Environment Files
C# PDF insert text Library: insert text into PDF content in C#.net
pageIndex, The page index of the PDF page that will be 0
add page number pdf; add page to pdf in preview
C# PDF File Split Library: Split, seperate PDF into multiple files
If your page number is set as 1, then the two output PDF files will contains the first page and the later three pages Add necessary references:
add pages to pdf; adding page numbers to pdf document
Annex
Satellite Navigation
303
Operating Manual 1173.1427.12 ─ 08
Container
Tag name
Parameter
Description
<antenna>
Descriptions of the individual antenna
<id>
Antenna identification number
<YawAxis_Z_off-
set>
<PitchAxis_Y_off-
set>
<RollAxis_X_off-
set>
Position shift of the antenna along the X/Y/Z axis with respect to
the center of gravity of the body
Value in meters
<Yaw_offset>
<Pitch_offset>
<Roll_offset>
Angular shift of the antenna along the X/Y/Z axis of the to the
body
Value in degrees
<az_res>
Resolution of the columns in the data section
value in degrees integer divider of 360
<elev_res>
Resolution of the raws in the data section
value in degrees integer divider of 180
<data>
The file has to contain for every pattern:
[1 + 360/<az_res>] columns
[1 + 180/<elev_res>] rows
Title column and row are disregarded
If the <use_same_pattern=”yes”> only one pattern is suffi-
cient, otherwise the other patterns must be appended after each
others inside this section
If the data represents the power response of the antenna
(*.ant_pat file), the power loss values are in dB (between 0
and 40)
If the data represents the phase response of the antenna
(*.phase file), the phase values are in degrees
A.2 RINEX Files
The RINEX file format consists of three ASCII file types: observation data file, naviga-
tion message file and meteorological data file. The navigation RINEX files comprises
the Ephemeris information of all visible satellites at a control station or a commercial
receiver.
Each file type consists of a header section and a data section. The header section con-
tains global information for the entire file and is placed at the beginning of the file. The
format of the data records of the RINEX navigation message files may contain naviga-
tion messages of more than one satellite system (GPS, GLONASS, Galileo, etc.). See
RINEX Format Description for description of the RINEX file format.
RINEX Navigation Files can be downloaded from http://cddis.gsfc.nasa.gov/gnss_data-
sum.html#brdc.
RINEX Files
VB.NET PDF File Split Library: Split, seperate PDF into multiple
can split target multi-page PDF document file to one-page PDF files or PDF file to smaller PDF documents by every given number of pages Add necessary references
adding page numbers to pdf in preview; add page pdf reader
C# PDF delete text Library: delete, remove text from PDF file in
Add necessary references: RasterEdge.Imaging.Basic.dll. matchString, The string wil be deleted from PDF file, -. 0
add pages to an existing pdf; add multi page pdf to word document
Annex
Satellite Navigation
304
Operating Manual 1173.1427.12 ─ 08
A.2.1 RINEX Format Description
Records marked with * are optional
Table 1-5: Navigation message file - header section description
HEADER LABEL (Col-
umns 61-80)
DESCRIPTION
FORMAT
RINEX VERSION / TYPE
Format version (2)
File type ('N' for Navigation data)
I6,14X, A1,19X
PGM / RUN BY / DATE
Name of program creating current
file
Name of agency creating current file
Date of file creation
A20, A20 A20
*
COMMENT
Comment line(s)
A60
*
ION ALPHA
Ionosphere parameters A0-A3 of alma-
nac (page 18 of subframe 4)
2X,4D12.4
*
ION BETA
Ionosphere parameters B0-B3 of alma-
nac
2X,4D12.4
*
DELTA-UTC: A0,A1,T,W
Almanac parameters to compute time in
UTC (page 18 of subframe 4)
A0,A1: terms of polynomial
T : reference time for UTC data
W : UTC reference week number. Contin-
uous number, not mod(1024)!
3X,2D19.12, 2I9
*
LEAP SECONDS
Delta time due to leap seconds
I6
END OF HEADER
Last record in the header section.
60X
Table 1-6: Navigation message file - data record description
HEADER LABEL (Columns
61-80 )
DESCRIPTION
FORMAT
PRN / EPOCH / SV CLK
Satellite PRN number
Epoch: Toc - Time of Clock
year (2 digits)
month
day
hour
minute
second
SV clock bias (seconds)
SV clock drift (sec/sec)
SV clock drift rate (sec/sec2)
I2, 5I3, F5.1,
3D19.12
BROADCAST ORBIT - 1
IODE Issue of Data, Ephemeris
Crs (meters)
Delta n (radians/sec)
M0 (radians)
3X,4D19.12
BROADCAST ORBIT - 2
Cuc (radians)
e Eccentricity
Cus (radians)
sqrt(A) (sqrt(m))
3X,4D19.12
RINEX Files
C# PDF replace text Library: replace text in PDF content in C#.net
Add necessary references: Delete specified string text that match the search option from specified PDF page. 0
add page numbers to pdf reader; add page numbers to pdf document in preview
C# PowerPoint - Split PowerPoint Document in C#.NET
If your page number is set as 1, then the PowerPoint files will contains the first page and the Add necessary XDoc.PowerPoint DLL libraries into your created
adding page numbers to pdf documents; add page numbers to pdf online
Annex
Satellite Navigation
305
Operating Manual 1173.1427.12 ─ 08
HEADER LABEL (Columns
61-80 )
DESCRIPTION
FORMAT
BROADCAST ORBIT - 3
Toe Time of Ephemeris (sec of GPS
week)
Cic (radians)
OMEGA (radians)
CIS (radians)
3X,4D19.12
BROADCAST ORBIT - 4
i0 (radians)
Crc (meters)
omega (radians)
OMEGA DOT (radians/sec)
3X,4D19.12
BROADCAST ORBIT - 5
IDOT (radians/sec)
Codes on L2 channel
GPS Week # (to go with TOE)
Continuous number, not mod(1024)!
L2 P data flag
3X,4D19.12
BROADCAST ORBIT - 6
SV accuracy (meters)
SV health (MSB only)
TGD (seconds)
IODC Issue of Data, Clock
3X,4D19.12
BROADCAST ORBIT - 7
Transmission time of message (sec
of GPS week, derived e.g. from Z-
count in Hand Over Word (HOW)
spare
spare
spare
3X,4D19.12
A.2.2 Example of a RINEX File
The following part of a script has the ephemeris info of satellites 4 and 9 at toc = toe =
352800.
2.10           N: GPS NAV DATA                         RINEX VERSION / TYPE
teqc  2002Mar14     Lisa McCormick      20090501 01:40:41UTCPGM / RUN BY / DATE
Solaris 2.7|Ultra 2|cc SC5.0|=+-|*Sparc                     COMMENT
rnw                 Dataflow Processing 04/30/2009 00:00:21 COMMENT
END OF HEADER
4 09  4 30  2  0  0.0-7.157493382690D-05-1.523403625470D-11 0.000000000000D+00
5.100000000000D+01 9.125000000000D+00 5.024495004670D-09-3.085066632770D+00
3.930181264880D-07 8.587007410820D-03 7.828697562220D-06 5.153723627090D+03
3.528000000000D+05 3.725290298460D-09 1.098217239560D-01-1.024454832080D-07
9.410577584670D-01 2.186875000000D+02 4.847291251310D-01-8.071407635100D-09
-3.571577341960D-10 1.000000000000D+00 1.529000000000D+03 0.000000000000D+00
2.400000000000D+00 0.000000000000D+00-6.053596735000D-09 5.100000000000D+01
3.456060000000D+05 4.000000000000D+00
9 09  4 30  2  0  0.0 5.332380533220D-05 1.932676241270D-12 0.000000000000D+00
1.070000000000D+02-7.959375000000D+01 4.243748197720D-09-2.353512095310D+00
-4.012137651440D-06 2.042865683320D-02 3.149732947350D-06 5.153640602110D+03
3.528000000000D+05 2.738088369370D-07-3.071164751940D+00 9.499490261080D-08
9.762633443270D-01 3.201250000000D+02 1.469759572200D+00-7.773895242510D-09
RINEX Files
C# Word - Split Word Document in C#.NET
your page number is set as 1, then the two output Word files will contains the first page and the later three pages respectively. C# DLLs: Split Word File. Add
add pdf pages to word document; add a page to a pdf document
VB.NET PDF url edit library: insert, remove PDF links in vb.net
objects, including website, image, document, bookmark, PDF page number, flash, etc. open in a new window, blank page or tab. NET users will be able to add a url
add a page to a pdf; add page number to pdf file
Annex
Satellite Navigation
306
Operating Manual 1173.1427.12 ─ 08
1.046472161190D-10 1.000000000000D+00 1.529000000000D+03 0.000000000000D+00
2.400000000000D+00 0.000000000000D+00-5.587935447690D-09 1.070000000000D+02
3.456060000000D+05 4.000000000000D+00
A.3 NMEA Scenarios
The National Marine Electronic Association (NMEA) is a broadcasting standard sup-
ported by all navigation receivers. The NMEA files comprise information about com-
mon parameters related to the satellite constellation, navigation parameters, time,
receiver location and dynamics. The table 1-7 defines the starting acronym for a NMEA
command of a specific navigation standard. In the moment this firmware is released,
the Galileo NMEA acronym has not been defined yet.
Table 1-7: Overview of the starting acronyms for the NMEA command
ID
Meaning
AG
Autopilot - General
AP
Autopilot - Magnetic
CC
Computer - Programmed Calculator (outdated)
CD
Communications - Digital Selective Calling (DSC)
CM
Computer - Memory Data (outdated)
CS
Communications - Satellite
CT
Communications - Radio-Telephone (MF/HF)
CV
Communications - Radio-Telephone (VHF)
CX
Communications - Scanning Receiver
DE
DECCA Navigation
DF
Direction Finder
EP
Emergency Position Indicating Beacon (EPIRB)
ER
Engine Room Monitoring Systems
GP
Global Positioning System (GPS)
GL
GLONASS
HC
Heading - Magnetic Compass
HE
Heading - North Seeking Gyro
HN
Heading - Non North Seeking Gyro
II
Integrated Instrumentation
IN
Integrated Navigation
LA
Loran A
LC
Loran C
NMEA Scenarios
.NET Excel Document Add-on | Manipulate Excel File in .NET
DLL, .NET programmers also need to add .NET Basic applications deployed to an unlimited number of clients license and price details on page Purchase Product
adding page numbers to pdf in; adding page numbers to a pdf document
Annex
Satellite Navigation
307
Operating Manual 1173.1427.12 ─ 08
ID
Meaning
MP
Microwave Positioning System (outdated)
OM
OMEGA Navigation System
Example of NMEA File
$GPVTG,,T,,M,0.000,N,0.000,K,A*23
$GPGGA,215810.00,3540.00066,N,13944.99611,E,1,04,1.61,6.8,M,39.4,M,,*5E
$GPGSA,A,3,06,09,04,10,,,,,,,,,2.47,1.61,1.87*01
$GPGSV,4,1,14,29,48,312,,26,47,312,,06,35,302,47,09,18,238,47*71
$GPGSV,4,2,14,27,47,312,,13,50,118,,04,72,181,47,30,48,312,*76
$GPGSV,4,3,14,14,39,070,,10,12,050,47,31,48,312,,07,64,349,*72
$GPGSV,4,4,14,25,47,312,,28,48,312,*7E
$GPGLL,3540.00066,N,13944.99611,E,215810.00,A,A*69
$GPZDA,215810.00,28,04,2023,00,00*64
$GPRMC,215811.00,A,3540.00066,N,13944.99611,E,0.000,,280423,,,A*7E
A.4 Used Algorithms
This section provides reference information on the algorithms applied by the genera-
tion of the GNSS signal.
A.4.1 Detailes on the Smoothening Algorithm
An important parameter in the smoothening application is the proximity parameter
which specifies the maximum deviation from the user’s input waypoints. This parame-
ter also specifies the number of inserted waypoints along the great circle in case the
user’s input waypoints are far away from each other. This is done to ensure that the
smoothened trajectory will not transverse the earth’s surface.
The smoothening is based on a modified version of linear segment parabolic blend
algorithm (LSPB) to specify the motion dynamics between two waypoints and geomet-
ric blend to change the direction of motion.
LSPB provides continuity in velocity (limited acceleration) but suffers from infinite Jerk.
The modified LSPB guarantees the continuity in acceleration (limited Jerk) between
waypoints. Control points are inserted between each two waypoints and the motion is
planned between these control points using fifth order polynomial regression which
guarantees the continuity of the velocity and acceleration at the control points.
The acceleration at the starting and the reached waypoint is zero; this will guarantee
the continuity when entering a blend to change the direction of motion since the blend
is represented by a sixth order polynomial with zero initial and final acceleration. The
blend is symmetric with respect to the axis bisecting the angle formed by three way-
points.
Used Algorithms
Annex
Satellite Navigation
308
Operating Manual 1173.1427.12 ─ 08
The starting and the exit waypoint coordinates of the blend in addition to the blend’s
sixth order polynomial coefficients and velocity are determined by the proximity param-
eter mentioned before. Once the starting and exit waypoints coordinates for the blends
of all the user’s input waypoints are determined, these waypoints can later be connec-
ted using the modified (LSPB) mentioned before to form the entire motion trajectory.
In case the user specifies zero proximity value then the motion is formed entirely of
straight segments with no blends, since the starting and the exit waypoints are the
user’s input waypoints, in such a case the simulated motion will stop at every waypoint
in order to change direction of motion.
Used Algorithms
List of Commands
Satellite Navigation
309
Operating Manual 1173.1427.12 ─ 08
List of Commands
[:SOURce<hw>]:BB:BEIDou:SETTing:CATalog?..........................................................................................162
[:SOURce<hw>]:BB:GALileo:SETTing:CATalog?.........................................................................................162
[:SOURce<hw>]:BB:GLONass:ATSCenario..................................................................................................161
[:SOURce<hw>]:BB:GLONass:SETTing:CATalog?......................................................................................162
[:SOURce<hw>]:BB:GPS:ATSCenario..........................................................................................................160
[:SOURce<hw>]:BB:GPS:SETTing:CATalog?...............................................................................................162
<subsystem>:ADGeneration:<GNSS>:SYNChronize....................................................................................259
<subsystem>:ADGeneration:ACQuisition:CREate........................................................................................265
<subsystem>:ADGeneration:ALManac:CREate............................................................................................266
<subsystem>:ADGeneration:BEIDou:LOCation:COORdinates:DECimal......................................................260
<subsystem>:ADGeneration:BEIDou:LOCation:COORdinates:DMS............................................................260
<subsystem>:ADGeneration:BEIDou:LOCation:SYNChronize.....................................................................259
<subsystem>:ADGeneration:BEIDou:LOCation:URADius............................................................................262
<subsystem>:ADGeneration:BEIDou:SVID:SYNChronize............................................................................259
<subsystem>:ADGeneration:BEIDou:SVID<ch>:ACQuisition:BLOCk?........................................................256
<subsystem>:ADGeneration:BEIDou:SVID<ch>:SAData?............................................................................257
<subsystem>:ADGeneration:BEIDou:SVID<ch>:STATe...............................................................................259
<subsystem>:ADGeneration:BEIDou:SYNChronize......................................................................................259
<subsystem>:ADGeneration:BEIDou:TOAData:DATE..................................................................................262
<subsystem>:ADGeneration:BEIDou:TOAData:DURation............................................................................264
<subsystem>:ADGeneration:BEIDou:TOAData:RESolution.........................................................................264
<subsystem>:ADGeneration:BEIDou:TOAData:SYNChronize......................................................................259
<subsystem>:ADGeneration:BEIDou:TOAData:TBASis...............................................................................262
<subsystem>:ADGeneration:BEIDou:TOAData:TIME...................................................................................263
<subsystem>:ADGeneration:BEIDou:TOAData:TOWeek.............................................................................264
<subsystem>:ADGeneration:BEIDou:TOAData:WNUMber...........................................................................265
<subsystem>:ADGeneration:GALileo:LOCation:COORdinates:DECimal.....................................................260
<subsystem>:ADGeneration:GALileo:LOCation:COORdinates:DMS...........................................................260
<subsystem>:ADGeneration:GALileo:LOCation:SYNChronize.....................................................................259
<subsystem>:ADGeneration:GALileo:LOCation:URADius............................................................................262
<subsystem>:ADGeneration:GALileo:SVID:SYNChronize............................................................................259
<subsystem>:ADGeneration:GALileo:SVID<ch>:ACQuisition:BLOCk?........................................................257
<subsystem>:ADGeneration:GALileo:SVID<ch>:SAData?...........................................................................257
<subsystem>:ADGeneration:GALileo:SVID<ch>:STATe..............................................................................259
<subsystem>:ADGeneration:GALileo:SYNChronize.....................................................................................259
<subsystem>:ADGeneration:GALileo:TOAData:DATE.................................................................................262
<subsystem>:ADGeneration:GALileo:TOAData:DURation...........................................................................264
<subsystem>:ADGeneration:GALileo:TOAData:RESolution.........................................................................264
<subsystem>:ADGeneration:GALileo:TOAData:SYNChronize.....................................................................259
<subsystem>:ADGeneration:GALileo:TOAData:TBASis...............................................................................262
<subsystem>:ADGeneration:GALileo:TOAData:TIME..................................................................................263
<subsystem>:ADGeneration:GALileo:TOAData:TOWeek.............................................................................264
<subsystem>:ADGeneration:GALileo:TOAData:WNUMber..........................................................................265
<subsystem>:ADGeneration:GLONass:LOCation:COORdinates:DECimal..................................................260
<subsystem>:ADGeneration:GLONass:LOCation:COORdinates:DMS........................................................261
<subsystem>:ADGeneration:GLONass:LOCation:SYNChronize..................................................................259
<subsystem>:ADGeneration:GLONass:LOCation:URADius.........................................................................262
List of Commands
Satellite Navigation
310
Operating Manual 1173.1427.12 ─ 08
<subsystem>:ADGeneration:GLONass:SVID:SYNChronize.........................................................................259
<subsystem>:ADGeneration:GLONass:SVID<ch>:ACQuisition:BLOCk?.....................................................257
<subsystem>:ADGeneration:GLONass:SVID<ch>:SAData?........................................................................258
<subsystem>:ADGeneration:GLONass:SVID<ch>:STATe...........................................................................259
<subsystem>:ADGeneration:GLONass:SYNChronize..................................................................................259
<subsystem>:ADGeneration:GLONass:TOAData:DATE..............................................................................263
<subsystem>:ADGeneration:GLONass:TOAData:DURation........................................................................264
<subsystem>:ADGeneration:GLONass:TOAData:RESolution......................................................................264
<subsystem>:ADGeneration:GLONass:TOAData:SYNChronize..................................................................259
<subsystem>:ADGeneration:GLONass:TOAData:TBASis............................................................................262
<subsystem>:ADGeneration:GLONass:TOAData:TIME...............................................................................263
<subsystem>:ADGeneration:GLONass:TOAData:TOWeek..........................................................................264
<subsystem>:ADGeneration:GLONass:TOAData:WNUMber.......................................................................265
<subsystem>:ADGeneration:GPS:LOCation:COORdinates:DECimal..........................................................260
<subsystem>:ADGeneration:GPS:LOCation:COORdinates:DMS.................................................................261
<subsystem>:ADGeneration:GPS:LOCation:SYNChronize..........................................................................259
<subsystem>:ADGeneration:GPS:LOCation:URADius.................................................................................262
<subsystem>:ADGeneration:GPS:SVID:SYNChronize.................................................................................259
<subsystem>:ADGeneration:GPS:SVID<ch>:ACQuisition:BLOCk?.............................................................256
<subsystem>:ADGeneration:GPS:SVID<ch>:SAData?................................................................................258
<subsystem>:ADGeneration:GPS:SVID<ch>:STATe....................................................................................259
<subsystem>:ADGeneration:GPS:SYNChronize..........................................................................................259
<subsystem>:ADGeneration:GPS:TOAData:DATE.......................................................................................263
<subsystem>:ADGeneration:GPS:TOAData:DURation.................................................................................264
<subsystem>:ADGeneration:GPS:TOAData:RESolution..............................................................................264
<subsystem>:ADGeneration:GPS:TOAData:SYNChronize..........................................................................259
<subsystem>:ADGeneration:GPS:TOAData:TBASis....................................................................................262
<subsystem>:ADGeneration:GPS:TOAData:TIME........................................................................................263
<subsystem>:ADGeneration:GPS:TOAData:TOWeek..................................................................................264
<subsystem>:ADGeneration:GPS:TOAData:WNUMber...............................................................................265
<subsystem>:ADGeneration:IONospheric:CREate.......................................................................................267
<subsystem>:ADGeneration:MODE..............................................................................................................259
<subsystem>:ADGeneration:NAVigation:CREate.........................................................................................266
<subsystem>:ADGeneration:UTC:CREate....................................................................................................266
<subsystem>:ADGeneration[:ACQuisition]:DFORmat...................................................................................265
<subsystem>:APATtern:ANTenna:ID............................................................................................................168
<subsystem>:APATtern:ANTenna:LIST?......................................................................................................167
<subsystem>:APATtern:CATalog:PREDefined?...........................................................................................167
<subsystem>:APATtern:CATalog:USER?.....................................................................................................167
<subsystem>:APATtern:FILE........................................................................................................................167
<subsystem>:ATMospheric:BEIDou:IONospheric:ALPHa<ch0>...................................................................252
<subsystem>:ATMospheric:BEIDou:IONospheric:BETA<ch0>.....................................................................252
<subsystem>:ATMospheric:GALileo:IONospheric:AI<ch0>..........................................................................252
<subsystem>:ATMospheric:GALileo:IONospheric:SF<ch>...........................................................................253
<subsystem>:ATMospheric:GPS:IONospheric:ALPHa<ch0>.......................................................................251
<subsystem>:ATMospheric:GPS:IONospheric:BETA<ch0>.........................................................................252
<subsystem>:ATMospheric:IONospheric:KLOBuchar:ALPHa<ch0>............................................................251
<subsystem>:ATMospheric:IONospheric:KLOBuchar:BETA<ch0>..............................................................251
<subsystem>:ATMospheric:IONospheric:MODel..........................................................................................251
<subsystem>:ATMospheric:TROPospheric:MODel.......................................................................................250
Documents you may be interested
Documents you may be interested