1. Manuals
  2. Brands
  3. Orolia Manuals
  4. Test Equipment
  5. GSG-6 Series
  6. User manual with scpi manual

Orolia GSG-6 Series User Manual With Scpi Manual

Gnss simulator
Hide thumbs
1
2
3
4
Table Of Contents
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
Table of Contents

Advertisement

Quick Links

Download this manual
GSG-5/6 Series GNSS Simulator
User Manual
with SCPI Guide
Orolia Part No.: 4031-600-54001
Revision: 27
Date: 22-Oct-2019
orolia.com

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the GSG-6 Series and is the answer not in the manual?

Questions and answers

Summary of Contents for Orolia GSG-6 Series

  • Page 1 GSG-5/6 Series GNSS Simulator User Manual with SCPI Guide Orolia Part No.: 4031-600-54001 Revision: 27 Date: 22-Oct-2019 orolia.com...
  • Page 3 Orolia reserves the right to make changes to the product described in this doc- ument at any time and without notice. Any software that may be provided with the product described in this document is furnished under a license agreement or nondisclosure agreement.
  • Page 4 Blank page. User Manual GSG-5/6 Series...

  • Page 5: Table Of Contents

    CHAPTER 1 Introduction 1.1 Quick Start 1.2 Welcome 1.3 Key Features 1.4 Typical GSG Applications 1.5 Intended Use and Operating Principle 1.6 Compliance & Legal Notices 1.6.1 About this Document 1.6.2 Declaration of Conformity 1.7 Technical Specifications 1.7.1 RF Output Specifications 1.7.2 Rear Panel Outputs and Inputs 1.7.3 Time Base 1.7.4 Optional Antenna...
  • Page 6 2.5.2 Transmit Power Level CHAPTER 3 Features & Functions 3.1 Front Panel 3.1.1 Description of Keys 3.1.1.1 Power 3.1.1.2 Start 3.1.1.3 Exit 3.1.1.4 Cancel 3.1.1.5 Menu 3.1.1.6 View 3.1.1.7 Enter 3.1.1.8 Arrows 3.1.1.9 N/S 3.1.1.10 E/W 3.1.1.11 Numeric Keys 3.1.1.12 +/– (format) 3.1.1.13 [.] (hold) 3.2 Rear Panel 3.3 The GSG Main Menu...
  • Page 7 3.5.5.3 User-Uploaded Ephemeris 3.5.6 Leap Second 3.5.7 Event Data 3.5.8 Antenna Settings 3.5.8.1 Antenna model 3.5.8.2 Lever arm 3.5.8.3 Elevation mask 3.5.9 Advanced Configuration Options 3.5.9.1 Multipath Signals 3.5.9.2 Interference signals 3.5.9.3 Base station 3.5.9.4 Environment models 3.5.9.5 Atmospheric model 3.5.10 Satellite Configuration 3.5.10.1 Satellite Systems 3.5.10.2 Number of Satellites...
  • Page 8 3.6.6 Restore Factory Defaults 3.6.7 Calibration CHAPTER 4 Frequent Tasks 4.1 Working with Scenarios 4.1.1 Scenario Start/Stop/Hold/Arm 4.1.2 Running a Scenario 4.1.3 Holding a Scenario 4.1.4 Configuring a Scenario 4.2 Locking/Unlocking the Keyboard 4.3 Setting Transmit Power 4.4 Accessing the GSG Web Interface 4.5 Using the CLI 4.6 Performing a Receiver Cold Start 4.7 Creating a One-Line Trajectory...
  • Page 9 4.9.12 Playing RSG Scenarios in StudioView 4.9.13 Configuring a Scenario 4.9.13.1 Defining Events in StudioView 4.9.13.2 Adding a Jammer Signal in StudioView 4.9.13.3 Spoofing a Signal in StudioView 4.9.13.4 Using SBAS in a Simulation 4.9.14 Record and Playback 4.9.14.1 Standard Workflow 4.9.14.2 Installation of the OPT-RP Software 4.9.14.3 Usage Notes 4.9.14.4 Recording Data with StudioView...
  • Page 10 5.14 GSG Series Model Variants and Options 5.14.1 Which GSG Model & Options Do I Have? 5.14.2 GSG Models & Variants 5.14.2.1 GSG-51 Series 5.14.2.2 GSG-5 Series 5.14.2.3 GSG-6 Series 5.14.3 List of Available Options 5.15 Problems? 5.15.1 Technical Support 5.15.1.1 Regional Contact 5.16 License Notices...
  • Page 11 6.3.3.2 SOURce:POWer? 6.3.3.3 SOURce:REFPOWer 6.3.3.4 SOURce:REFPOWer? 6.3.3.5 SOURce:ABSPOWer 6.3.3.6 SOURce:ABSPOWer? 6.3.3.7 SOURce:RELPOWer 6.3.3.8 SOURce:RELPOWer? 6.3.3.9 SOURce:EXTREF 6.3.3.10 SOURce:EXTREF? 6.3.3.11 SOURce:PPSOUTput 6.3.3.12 SOURce:PPSOUTput? 6.3.3.13 SOURce:EXTATT 6.3.3.14 SOURce:EXTATT? 6.3.3.15 SOURce:NOISE:CONTrol 6.3.3.16 SOURce:NOISE:CONTrol? 6.3.3.17 SOURce:NOISE:CNO 6.3.3.18 SOURce:NOISE:CNO? 6.3.3.19 SOURce:NOISE:BW 6.3.3.20 SOURce:NOISE:BW? 6.3.3.21 SOURce:NOISE:OFFSET 6.3.3.22 SOURce:NOISE:OFFSET? 6.3.3.23 SOURce:ONECHN:CONTrol 6.3.3.24 SOURce:ONECHN:CONTrol?
  • Page 12 6.3.3.42 SOURce:SCENario:CONTrol? 6.3.3.43 SOURce:SCENario:PROPenv 6.3.3.44 SOURce:SCENario:PROPenv? 6.3.3.45 SOURce:SCENario:LOG? 6.3.3.46 SOURce:SCENario:ADVLOG? 6.3.3.47 SOURce:SCENario:ADVLOG:HEADer? 6.3.3.48 SOURce:SCENario:OBServation 6.3.3.49 SOURce:SCENario:OBServation? 6.3.3.50 SOURce:SCENario:NAV 6.3.3.51 SOURce:SCENario:NAV? 6.3.3.52 SOURce:SCENario:SATid[n]? 6.3.3.53 SOURce:SCENario:SIGNALtype[n]? 6.3.3.54 SOURce:SCENario:SIGNALtype? 6.3.3.55 SOURce:SCENario:NAVBITS 6.3.3.56 SOURce:SCENario:FREQuency[n]? 6.3.3.57 SOURce:SCENario:FREQuency? 6.3.3.58 SOURce:SCENario:POWer[n] 6.3.3.59 SOURce:SCENario:POWer[n]? 6.3.3.60 SOURce:SCENario:POWer 6.3.3.61 SOURce:SCENario:POWer? 6.3.3.62 SOURce:SCENario:FREQBAND:POWer 6.3.3.63 SOURce:SCENario:SVmodel? 6.3.3.64 SOURce:SCENario:SVmodel[n]?
  • Page 13 6.3.3.82 SOURce:SCENario:RTCMCFG 6.3.3.83 SOURce:SCENario:RLM 6.3.3.84 SOURce:SCENario:DUPlicate 6.3.3.85 SOURce:SCENario:DUPlicate[n] 6.3.3.86 SOURce:SCENario:DUPlicate? 6.3.3.87 SOURce:SCENario:DURATION 6.3.3.88 SOURce:SCENario:DURATION? 6.3.3.89 SOURce:SCENario:MULtipath[n] 6.3.3.90 SOURce:SCENario:MULtipath[n]? 6.3.3.91 SOURce:SCENario:DELete[n] <TIME> 6.3.3.92 SOURce:SCENario:DELete <TIME>,<satID>[,<satID>] 6.3.3.93 SOURce:SCENario:DELete[n] <TIME>,<satID> 6.3.3.94 SOURce:SCENario:CLKMDL 6.3.3.95 SOURce:SCENario:CLKMDL? 6.3.3.96 SOURce:FILe:TYPe 6.3.3.97 SOURce:FILe:NAMe 6.3.3.98 SOURce:FILe:LENgth 6.3.3.99 SOURce:FILe:CHECKsum 6.3.3.100 SOURce:FILe:DATA 6.3.3.101 SOURce:KEYLOCK:PASSWord 6.3.3.102 SOURce:KEYLOCK:PASSWord? 6.3.3.103 SOURce:KEYLOCK:STATus...
  • Page 14 6.3.6.6 STATus:QUEStionable[:EVENt]? 6.3.6.7 STATus:PRESet 6.4 Sensors Command Reference 6.4.1 Supported Sensor Types 6.4.1.1 Accelerometer 6.4.1.2 Linear Accelerometer 6.4.1.3 Gravimeter 6.4.1.4 Gyroscope 6.4.1.5 Odometer 6.4.1.6 Odometer 3D 6.4.2 Sensor Commands 6.4.2.1 SOURce:SCENario:SENSor:REGister 6.4.2.2 SOURce:SCENario:SENSor:REGister? 6.4.2.3 SOURce:SCENario:SENSor:UNREGister 6.4.2.4 SOURce:SCENario:SENSor:DATa? 6.4.2.5 SOURce:SCENario:SENSor:NORMalize SENSOR_TYPE 6.4.2.6 SOURce:SCENario:SENSor:NORMalize? SENSOR_TYPE 6.4.2.7 SOURce:SCENario:SENSor:MAXrange SENSOR_TYPE 6.4.2.8 SOURce:SCENario:SENSor:MAXrange? SENSOR_TYPE...
  • Page 15 6.5.3.17 SOURce:SCENario:VSPEed TIME 6.5.3.18 SOURce:SCENario:VSPEed? 6.5.3.19 SOURce:SCENario:ENUVELocity TIME 6.5.3.20 SOURce:SCENario:ENUVELocity? 6.5.3.21 SOURce:SCENario:ECEFVELocity 6.5.3.22 SOURce:SCENario:ECEFVELocity? 6.5.3.23 SOURce:SCENario:ACCeleration TIME 6.5.3.24 SOURce:SCENario:ACCeleration? 6.5.3.25 SOURce:SCENario:VACCel TIME 6.5.3.26 SOURce:SCENario:VACCel? 6.5.3.27 SOURce:SCENario:ENUACCel TIME 6.5.3.28 SOURce:SCENario:ENUACCel? 6.5.3.29 SOURce:SCENario:ECEFACCel TIME 6.5.3.30 SOURce:SCENario:ECEFACCel? 6.5.3.31 SOURce:SCENario:PRYattitude TIME 6.5.3.32 SOURce:SCENario:PRYattitude? 6.5.3.33 SOURce:SCENario:DPRYattitude TIME 6.5.3.34 SOURce:SCENario:DPRYattitude? 6.5.3.35 SOURce:SCENario:PRYRate TIME 6.5.3.36 SOURce:SCENario:PRYRate?
  • Page 16 6.6.2 Trajectory FILE Format (.traj) 6.6.3 Trajectory Two-Line Element Format (TLE) 6.7 Revision History (SCPI Guide) APPENDIX Appendix 7.1 Lists of Tables and Images 7.2 GSG User Manual Revision History INDEX User Manual GSG-5/6 Series • TABLE OF CONTENTS...
  • Page 17 Introduction The following topics are included in this Chapter: 1.1 Quick Start 1.2 Welcome 1.3 Key Features 1.4 Typical GSG Applications 1.5 Intended Use and Operating Principle 1.6 Compliance & Legal Notices 1.7 Technical Specifications User Manual GSG-5/6 Series...

  • Page 18: Quick Start

    1.1 Quick Start Quick Start The following procedure is a brief outline on how to get started with your GSG-5/6 unit. The minimal setup steps are: 1. Unpack the unit (see "Unpacking and Inventory" on page 14), and place it on a desktop or install it in a rack, as described under "Mechanical Installation"...

  • Page 19: Welcome

    1.2 Welcome Welcome About Orolia's GNSS Simulators The GSG-5™ and GSG-6™ Series of GNSS Constellation Simulators provide a wide-range of capabilities for in-line production testing and development testing, including navigational fix and position testing, while offering ease-of-operation. GSG-51 is a single-channel GPS L1 RF generator, capable of emulating a single GNSS sig- nal.

  • Page 20: Typical Gsg Applications

    1.4 Typical GSG Applications Up to 64 independent satellite channels can be simulated. Supported signal types: GPS L1, L2, C/A and P-Code; L2C and L5 GLONASS L1, L2, C/A and P-Code Galileo E1/E2 and E5 BeiDou compatible Support of different types of SBAS simulation: EGNOS, WAAS, MSAS, GAGAN Generation of white noise, multipath and interference signals Receiver sensitivity testing with accurate, variable output levels ranging from -65 to -160 dBm...

  • Page 21: Intended Use And Operating Principle

    RINEX, WAAS and EGNOS data from official websites, as needed. The GSG-6 Series can be controlled via an Ethernet network connection, or USB or GPIB. A built-in web interface allows remote operation of the instrument. With the optional GSG StudioView™...

  • Page 22: Compliance & Legal Notices

    1.6 Compliance & Legal Notices Compliance & Legal Notices Orolia’s GSG-Series GNSS Simulator products meet all FCC and CE Mark regulations for operation as electronic test equipment. Note: For more information about Signal Power Emissions , see "Signal Power Level Considerations" on page 24.

  • Page 23: Technical Specifications

    1.7 Technical Specifications Technical Specifications 1.7.1 RF Output Specifications Constellation Signal for GPS, GLONASS, Galileo, BeiDou, QZSS, IRNSS Connector: Type N female Frequency: L1/E1/B1/SAR: 1539 - 1627 MHz L2/L2C: 1167 - 1255 MHz L5/E5/B2: 1146 - 1234 MHz E6/B3: 1215 - 1303 MHz Number of output channels: 1 to 64 Channel...

  • Page 24: Rear Panel Outputs And Inputs

    1.7 Technical Specifications Limits: Altitude: 18240 m (60000 feet) Acceleration: 4.0 g Velocity: 515 m/s (1000 knots) Jerk: 20 m/s Extended limits: Altitude: 20200 km Acceleration Velocity: 20000 m/s (38874 knots) Jerk: No limit White noise signal level: -50 to -160 dBm 0.1 dB resolution down to -150 dBm 0.3 dB down to -160 dBm ±1.0 dB accuracy...

  • Page 25: Time Base

    1.7 Technical Specifications Minimum PW: 10 ms Active Edge: Falling 1/10/100/1000 PPS Output Connector: BNC female Output signal level: approx. 0V to +2.0 V in 50 Ω load Accuracy: Calibrated to ±10 nSec of RF timing mark output 1.7.3 Time Base Standard OCXO Ageing per 24 h: <5x10...
  • Page 26 1.7 Technical Specifications Transit Drop Test: Heavy-duty transport case and soft carrying case tested according to MIL-PRF-28800F Reliability: MTBF 30000 h, calculated Safety: Designed and tested for Measurement Category I, Pollution Degree 2, in accordance with EN/IEC 61010-1:2001 and CAN/CSA-C22.2 No. 61010-1-04 (incl.

  • Page 27: Setup

    Setup The following topics are included in this Chapter: 2.1 About Your Safety 2.2 Unpacking and Inventory 2.3 Mechanical Installation 2.4 Electrical Installation 2.5 Signal Power Level Considerations User Manual GSG-5/6 Series...

  • Page 28: About Your Safety

    2.1 About Your Safety About Your Safety The following safety symbols are used in Orolia technical documentation, or on Orolia products: Table 2-1: Orolia safety symbols Symbol Signal word Definition Potentially dangerous situation which may lead to personal DANGER! injury or death! Follow the instructions closely.

  • Page 29: Basic User Responsibilities

    (for example: Best Practices in ESD prevention.) Do not modify the equipment, and use only spare parts authorized by Orolia. Always follow the instructions set out in this guide.

  • Page 30: Unpacking And Inventory

    (ESD). Observe all ESD precautions and safeguards when handling the unit. Unpack the equipment and inspect it for damage. If any equipment has been damaged in transit, or you experience any problems during installation and configuration of your Orolia product, please contact your closest Orolia Customer Service Center (see: "Technical Sup-...

  • Page 31: Mechanical Installation

    This support can also be used as a handle to carry the instrument. Figure 2-1: Fold-down support Single-Unit Rack-Mount Installation With the optional Orolia 22/90 rack-mount kit (P/N 9446-1002-2901) one GSG unit can be installed in a 19-inch rack (2U). The kit comprises:...
  • Page 32 2.3 Mechanical Installation Figure 2-2: Rack-Mount-Kit (the GSG housing shown in the center is not part of the kit) In order to prepare the GSG unit for rack-mount installation, the housing needs to be opened, in order to remove the bottom feet (otherwise the assembly will not fit in a 2U slot.) DANGER! Do not perform any work on the internal components of the unit,...
  • Page 33 2.3 Mechanical Installation push out the foot. Figure 2-3: Preparing the GSG unit for rack mounting 6. Gently push the unit into its housing again. 7. Re-assemble the two rear feet. 8. Install the ears that came with the rack-mount kit.
  • Page 34 11. Complete the electrical installation. Side-by-Side Rack-Mount Installation With the optional Orolia 22/05 rack-mount kit (P/N 1211-0000-0701), two GSG units can be installed side-by-side in one 19-inch rack (2U). The kit comprises: 4 x Bracket, rear (1211-1000-0706) [Item 1]...
  • Page 35 2.3 Mechanical Installation DANGER! Do not perform any work on the internal components of a GSG unit, while the housing is removed, unless you are qualified to do so. Before removing the cover, unplug the power cord and wait for one minute to allow any capacitors to discharge.
  • Page 36 Rack-Mount Installation with an Agilent Power Meter GSG units are frequently installed adjacent to an Agilent Power Meter, using one 19" slot (2U). This can be accomplished with the optional Orolia 22/04 rack-mount kit (P/N 9446-1002-2041). Also required is the Agilent rack-mount kit.
  • Page 37 2.3 Mechanical Installation 4. Grip the front panel with one hand, while pushing at the rear with the other hand. Pull the unit out of its housing. 5. Remove the four bottom feet from the housing, as shown in the illustration below: Use a screwdriver or a pair of pliers to remove the springs holding each foot, then push out the foot.

  • Page 38: Electrical Installation

    2.4 Electrical Installation Figure 2-9: Front assembly plate installation Agilent unit (shown left), GSG unit 10. Install the rear assy plate, Agilent, and the rear assy plate, GSG, and assemble them, as shown in the illustrations below. Figure 2-10: Installation of rear assembly plates 11.
  • Page 39 2.4 Electrical Installation line voltage. The maximum power draw is 40 W. Fuse The secondary supply voltages are electronically protected against overload or short cir- cuit. The primary line voltage side is protected by a fuse located on the power supply unit. The fuse rating covers the full voltage range.

  • Page 40: Transmit Power Level

    2.5.1 Compliance: Using an Antenna Orolia’s GSG GNSS Simulator products meet all required regulations of the FCC and CE Mark for operation as electronic test equipment. However, when using the GSG signal gen- erator with an RF antenna (instead of an RF cable), additional regulations controlling the...
  • Page 41 For additional information on path loss, see e.g., this third- party reference http://en.wikipedia.org/wiki/Path_loss This link is provided for reference purposes only. It leads to a web page that is not maintained or supported by Orolia. User Manual GSG-5/6 Series Rev. 27...
  • Page 42 2.5 Signal Power Level Considerations BLANK PAGE. User Manual GSG-5/6 Series Rev. 27...

  • Page 43: Features & Functions

    Features & Functions The following topics are included in this Chapter: 3.1 Front Panel 3.2 Rear Panel 3.3 The GSG Main Menu 3.4 "Start" Menu 3.5 "Select" Menu 3.6 "Options" Menu User Manual GSG-5/6 Series...

  • Page 44: Front Panel

    3.1 Front Panel Front Panel All GSG-5/6 simulators have similar front panels. On the right side are the controls used for managing scenario execution and for display navigation. At the bottom are the numeric keys used to input scenario parameters and other configuration.

  • Page 45: Exit

    3.1 Front Panel 3.1.1.3 Exit When editing a field, press exit to end the editing process, and save your changed field value. The field label will be highlighted. When editing a field, press exit return to the previous display, and save the changes you applied to the current display.

  • Page 46: Arrows

    3.1 Front Panel 3.1.1.8 Arrows Press any of the arrow keys to navigate in displays. When editing an integer value, press the UP/DOWN arrows to incrementally increase or decrease the value. 3.1.1.9 When editing latitude, press to toggle between north and south latitude. During scenario execution, press to open the transmit power...

  • Page 47: Rear Panel

    3.2 Rear Panel Rear Panel As a means for communication, GSG supports GPIB, and Ethernet. Only one con- nection can be active at a time. The active connection is selected under Options > Inter- face. The default setting is Ethernet. The illustration below shows the connections available on the back side of the unit: Figure 3-2: GSG rear panel...

  • Page 48: The Gsg Main Menu

    3.3 The GSG Main Menu 10. Fan: The fan speed is controlled via a temperature sensor. Normal bench-top use means low speed, whereas rack-mounting and/or installed options may result in higher speed. Type Plate: Indicates model number and serial number. The GSG Main Menu The main menu of the GSG user interface is shown on the GSG display when the unit is started.

  • Page 49: Start" Menu

    3.4 "Start" Menu ARM: the unit is waiting for a trigger to start the scenario HOLD: the movement along the trajectory is paused "Start" Menu To start the currently loaded scenario (as previously selected using the ""Select" Menu" on page 38), highlight the main menu option Start by pressing the arrow...

  • Page 50: Scenario Execution Views

    3.4 "Start" Menu of the scenario data). During this wait time, press the [.] (hold) key if you want to prevent the scenario from begin- ning to run before you are ready. This is called "arming" (the text icon will display in the upper right corner of the display, and the armed status indicator...

  • Page 51: View 1/X

    3.4 "Start" Menu To display the views in successive order, press the view key. In the lower right corner e.g., View 2/6 may be displayed, indicating the current view/total number of views. The total number, and content of views depends on the number of signals used in the scenario. Note: When you press the exit...
  • Page 52 3.4 "Start" Menu view: Shows the abbreviation of each satellite system, followed by its number of satellites in view/GSG channels reserved. Satellite system abbreviations are: GP: GPS GL: Glonass GA: Galileo BD: BeiDou IR: IRNSS QZ: QZSS 2. PRN: Pseudo-Range Number (satellite identifier). The identifiers are: For GPS: Gxx For Galileo: Exx For GLONASS: Rxx...
  • Page 53 3.4 "Start" Menu iSg, for sweeping GPS interference iSr, for sweeping Glonass interference iSe, for sweeping Galileo interference iSc, for sweeping BeiDou interference iSj, for sweeping QZSS interference iNg, for noise GPS interference iNr, for noise Glonass interference iNe, for noise Galileo interference iNc, for noise BeiDou interference iNj, for noise QZSS interference 4.

  • Page 54: Last View

    3.5 "Select" Menu Changing the Transmit Power setting becomes effective immediately, and also impacts noise generation levels (if in use – available with GSG-5, GSG-55, GSG-56 and GSG-62, 63, and 64). E x a m p l e S135 The example above illustrates two GPS signals ( ), one SBAS signal ( ), one multipath signal (...
  • Page 55 3.5 "Select" Menu can re-configure to adapt them to your needs. You can also create your own scenarios using the optional GSG StudioView Software. Prior to running a scenario, you have to select it from the list of scenarios installed on the GSG unit: 1.

  • Page 56: Start Time

    3.5 "Select" Menu "Trajectories" on page 43 "Ephemeris" on page 47 "Leap Second" on page 53 "Event Data" on page 54 "Antenna Settings" on page 59 "Advanced Configuration Options" on page 61 "Multipath Signals" on page 61 "Interference signals" on page 64 "Base station" on page 67 "Environment models" on page 68 "Atmospheric model"...

  • Page 57: Revision

    3.5 "Select" Menu GPS time and leap seconds Start time is based on GPS time, i.e. the displayed time is always GPS time. Unlike UTC time – which is frequently displayed by GNSS receivers – GPS time does include leap seconds. NTP real time and downloaded Ephemeris Using NTP as start time in conjunction with Ephemeris...

  • Page 58: Duration

    3.5 "Select" Menu get into a conflict with the GLONASS time stamps and in this case the receiver will not out- put any solution. This issue, especially with combined GPS+GLONASS scenarios, can be avoided by simulating future dates. 3.5.2 Duration The duration of the scenario replay can be set to a number of days, hours and minutes.

  • Page 59: Trajectories

    3.5 "Select" Menu degrees-minutes-seconds ECEF (Earth-Centered, Earth-Fixed) format. 3.5.4 Trajectories Note: This feature is not available in GSG-51/52/53. In the context of GNSS testing, a trajectory is the predefined path a receiver is traveling during the execution of a scenario. GSG-5/6 can be used to simulate virtually any user tra- jectory.

  • Page 60: User-Created Trajectories

    : “The UE [User Equipment, (Orolia)] moves on a rectangular trajectory of 940 m by 1440 m with rounded corner defined in figure 1. The initial reference is first defined fol- lowed by acceleration to final speed of 100 km/h in 250 m.
  • Page 61 Even if the RSG Option (OPT-RSG) is not installed on your GSG, and you can therefore not run scenarios in real time, you can still use the Orolia-proprietary RSG format by up-loading RSG trajectories onto your GSG unit. The RSG format is further described under "RSG...
  • Page 62 3.5 "Select" Menu incorrect checksum (because incorrect checksums can be useful for manually correcting the contents of an NMEA file). Date, time, position, speed, heading Date and time along with longitude, latitude, speed over ground, and heading will be extrac- ted from the RMC message (NMEA’s Recommended Minimum), in order to build the tra- jectory.

  • Page 63: Ephemeris

    3.5 "Select" Menu If you start a scenario that uses an NMEA file with more than 12000 epochs, GSG will ini- tiate a dialog upon start of the scenario, asking you to either cancel the simulation exe- cution, or to truncate the NMEA trajectory file down to its first 12000 epochs. Making a One-Line Trajectory As the GSG unit uses the heading and speed information of the RMC sentences, only one (!) NMEA sentence is actually required to describe a simple, continuous movement.

  • Page 64: Default Ephemeris

    3.5 "Select" Menu Figure 3-6: Ephemeris selection 3.5.5.1 Default Ephemeris CDDIS GNSS archive The default RINEX data for GPS and GLONASS is based on the using the brdc files. The non-redundant brdc file merges the individual site navigation files into one, and thus can be used instead of the many individual navigation files. This data is complemented GLONASS almanac data downloaded from...

  • Page 65: User-Uploaded Ephemeris

    3.5 "Select" Menu 1. The GSG unit must have access to the Internet. 2. The correct DNS address must specified, either by setting Options > Interfaces and Reference > Network > Obtain IP autom. = Yes, or—when using a static IP configuration—by manually entering the correct DNS address.
  • Page 66 3.5 "Select" Menu If a satellite system (e.g., GPS, or Galileo) is selected (i.e., number of satellites selected is not 0) and no navigation files are selected for that particular satellite system, then GSG will use default data for that satellite system. The RINEX format support includes version 2.x and 3.0.
  • Page 67 3.5 "Select" Menu sidered valid for ±3.5 days from the TOA value (Time-of-almanac) listed in the YUMA almanac. The scenario is restricted to start times within this range. If a scenario runs beyond this range of time, no new satellites will be added. If the user specifies a start time outside this range, a dialog will advise the user that the ephemeris and almanac are dates are mis- matched.
  • Page 68 These can cause the GSG to generate signals that are deemed ‘bad’ by a receiver and may not be used in a fix or for navigation. This data is not maintained by Orolia and is not guaranteed. Note:...

  • Page 69: Leap Second

    3.5 "Select" Menu 3.5.6 Leap Second Configuration of leap seconds include two parameters: initial GPS-to-UTC offset (due to accumulated leap second events) and future leap second event. To set a leap second event, navigate to Select > [Select Scenario] > Configure [selec- ted scenario]:...

  • Page 70: Event Data

    3.5 "Select" Menu Alternatively, the user can also specify any desired offset value. This is configured under the scenario menu: Advanced > GPS to UTC offset, or by using the scenario file para- meter GpsToUtcOffset. The allowed values are: Auto: In this setting, the initial offset is determined by scenario start time Rinex: determined by information taken from navigation data files attached to a scenario <Fixed Offset in...
  • Page 71 3.5 "Select" Menu satellites use the scenario keyword. Events which apply to a specific satellite indicate this by specifying channel NUMBER or prn SATID values. For relpower and abspower events, it is possible to apply the event to each satellite of a specified constellation: use the keyword followed satellite...
  • Page 72 3.5 "Select" Menu The units for the event parameters are: TIME in seconds since scenario start time SATID is a satellite ID. The format explained in protocol documentation. NUMBER is the channel number. Range depends on GSG model. RELPOWER relative change in power settings specified in dB ABSPOWER absolute value for power settings specified in dBm RELRANGE is the relative range delay in meters.
  • Page 73 3.5 "Select" Menu PAGEID is a page ID (with GPSL1 and L2P signals) 0 (not relevant) when the subframe ID is 1-3 0 (not relevant) with L2C and L5 signals a string idID (with Glonass). STARTBITPOS, ENDBITPOS are positions of bits in a navigation message. HEXSTRING is a bit pattern to be set in the message.
  • Page 74 3.5 "Select" Menu 9.0 system GLO relpower +3 10.0 prn G9 duplicate 30.0 -0.01 -8.3 0 10.0 channel 6 duplicate 30.0 -0.01 -8.3 0 11.0 channel 6 multipath 35.0 0.01 1.0 0.0 0.0 0 -10.0 0.0 0 11.0 prn G9D multipath 25.0 0.01 1.5 0.0 0.0 0 -15.0 0.0 0 12.0 prn G1 navbits L1CA 1 0 77 77 1 0 0 170.0 channel 6 delete 180.0 channel G9D delete...

  • Page 75: Antenna Settings

    3.5 "Select" Menu At 11.0 seconds, the multipath settings of the newly created duplicate, identified by its SATID ‘G9D’, are modified: The satellite will have a 25 meter range offset, increas- ing with 1.5cm/s. It will have its power attenuated by 15 dB. After 12.0 seconds, the MSB is set to 1 in 6-bit health (bits 77-82) in the first GPS L1CA message with subframe ID 1 sent by satellite G1.

  • Page 76: Antenna Model

    3.5 "Select" Menu 3.5.8.1 Antenna model antenna gain pattern can be specified for each scenario, using a set of pre-defined antenna models, or by utilizing a user-specified file. The built-in antenna models assume an omni-directional gain pattern where the maximum gain is to be found towards the zenith.

  • Page 77: Elevation Mask

    3.5 "Select" Menu For more information on vehicle modeling, see "Environment models" on page 68. 3.5.8.3 Elevation mask elevation mask specifies how low GNSS satellites will be simulated. The elevation mask is set to zero by default. Figure 3-8: Elevation mask A receiver typically has a higher elevation mask and it will not use any satellite below the elevation angle of its set mask.
  • Page 78 3.5 "Select" Menu Figure 3-9: Multipath signals in urban environment To configure a multipath signal, navigate to Select > Select Scenario > Configure Scen- ario, View 2/3: Advanced, and specify a number greater than zero for Multipath signals. Note: Your GSG unit requires free channel(s) available, in order to allow for the creation and configuration of a (several) new multipath signal(s).
  • Page 79 3.5 "Select" Menu be in the scenario. ‘1’ would mean that we will duplicate the satellite in the first pos- ition when scenario starts. Range Offset: The Range (or: Code) offset in meters. For a multipath signal this value should typically be positive, meaning that the travelled distance of the signal will be longer than that of the original or line-of-sight (LOS) signal.

  • Page 80: Interference Signals

    3.5.9.2 Interference signals Note: The Interference feature is only available with GSG-5, GSG-55, GSG- 56 and GSG-6 Series products. Some features are only available when OPT- JAM is enabled in the unit (see "List of Available Options" on page 205). Orolia GSG- Series simulators can generate GNSS interference signals to test GNSS receiver performance.
  • Page 81 3.5 "Select" Menu Figure 3-11: Interference configuration view The following parameters can be configured: Signal type You can configure any signal type your GSG unit is licensed for (un-licensed signal types are grayed out). Figure 3-12: Interference signal type configuration view The interference signal type can be: GPS: L1CA, L1P, L2P, L1P(Y), L2P(Y), GPS carrier, SBAS GLONASS: L1, L2 or GLONASS carrier...
  • Page 82 3.5 "Select" Menu Note: Noise interference is not available if wide band noise is set to ON under the Options > Transmit power menu. Satellite ID/Frequency slot For GPS, SBAS, Galileo, GLONASS, BeiDou, IRNSS and QZSS signals, the Satellite ID must be specified.

  • Page 83: Base Station

    3.5 "Select" Menu Figure 3-14: Configured sweeper signal 3.5.9.3 Base station This feature allows you to configure a Base station, as it is typically used for high-precision positioning, e.g. in surveying applications: A receiver in a fixed and known position tracks the same satellites the mobile receiver ("rover") does, and in real-time transmits corrective positioning data to the receiver in the rover via a radio transmission stream.

  • Page 84: Environment Models

    3.5 "Select" Menu Figure 3-16: Base station configuration dialog The following Base station settings can be reviewed/configured: RTCM version The RTCM SC-104 version currently supported is Ver. 3.2. This cannot be changed. www.navipedia.net/index.php/RTK_ For more information on RTCM standards, see: Standards Message type Message types 1002, 1004, 1006, 1010, 1012 and 1033 are supported.
  • Page 85 GSG can successfully handle vehicle models with up to 130 triangles. Models should be optimized for a low polygon count. The triangle count is limited to a total of 300 for the combined environment and vehicle models. For additional information, see the Orolia Technical Note Vehicle Modeling Propagation Environment Models Built-in signal propagation models can be used to simulate multipath propagation in rural, sub- urban and urban areas.
  • Page 86 3.5 "Select" Menu Figure 3-17: ITU multipath propagation model Satellites above the Open Sky limit are not affected by multipath propagation. Satellites in the Multipath Zone (elevation angle between Obstruction Limit and Open Sky Limit) are considered LOS signals, but affected by multipath propagation. The ITU model for LOS situation is used for these satellites.
  • Page 87 3.5 "Select" Menu Environment Open sky limit Obstruction limit NLOS probability Suburban 40° 30° Urban 60° 40° The Propagation environment model is taken into use by setting an event scenario propenv. If stated without parameters, the default parameter values given above will be used.

  • Page 88: Atmospheric Model

    3.5 "Select" Menu Valid ranges for the parameter values are: OPENSKYLIMIT: 0.0 to 90.0 (degrees) OBSTRUCTIONLIMIT: 0.0 to OPENSKYLIMIT (degrees) NLOSPROBABILITY: 0.0 to 1.0 It is possible that all multipath taps cannot be created because of limited number of channels available. The Tap number defines the precedence of tap creation (direct path first, and then second tap etc.) The maximum number of satellites to be simulated should be set to a fixed value.
  • Page 89 3.5 "Select" Menu Tropo model A number of tropospheric models are supported by the device. These are: Saastamoinen model. The model is based on Saastamoinen, J., 'Atmospheric Cor- rection for the Troposphere and Stratosphere in Radio Ranging of Satellites,' The Use of Artificial Satellites for Geodesy, Geophysics Monograph Series, Vol.

  • Page 90: Satellite Configuration

    3.5 "Select" Menu Figure 3-18: Tropospheric delay vs. elevation angle 3.5.10 Satellite Configuration Depending on the model and configuration of your GSG unit, and the scenario chosen, sev- eral satellite systems can be simulated in a scenario, each of which you may want to con- figure in accordance with the requirements for your receiver-under-test.

  • Page 91: Satellite Systems

    3.5 "Select" Menu Figure 3-19: GPS satellite configuration To access the first satellite configuration view, navigate to Select > [Select scenario] > Configure scenario: View 3/3. The following satellite-relevant settings can be configured: Satellite System, e.g., GPS, Glonass (see "Satellite Systems" below) Number of satellites simulated for a given satellite system (see...

  • Page 92: Number Of Satellites

    3.5 "Select" Menu GALILEO Europe; globally operating system; yet, not fully operational as of summer 2015; high-quality signals, multiple uses BEIDOU China; regional system (Asia); planned global expansion; open system QZSS Japan; regional system IRNSS India; regional system 3.5.10.2 Number of Satellites The maximum number of satellites to be simulated by GSG in a given scenario is specified separately for each available GNSS system.
  • Page 93 3.5 "Select" Menu … are transmitted on frequencies close to each other, yet they do not interfere with each other … can be decoded by one receiver (if supported by the receiver manufacturer) … can be grouped into four main bands. These four frequency bands are: Frequency Bands Constellation...
  • Page 94 3.5 "Select" Menu For BeiDou: For QZSS: SAIF Active Signals Frequency bands can be turned ON/OFF separately, so as to configure which types of RF signals specific to each supported satellite system shall be active/inactive when a scenario is running. Depending on the configuration of your GSG unit, all of the frequency bands listed above can be turned ON/OFF.

  • Page 95: Satellite Constellations

    3.5 "Select" Menu 3.5.10.4 Satellite Constellations Once existing GNSS satellites of a satellite system in orbit are being replaced by new, more modern satellite types, the satellites are often categorized by their generation, or historic constellation. In the case of the GPS system, these constellations are named by their block numbers, e.g., "IIA".
  • Page 96 3.5 "Select" Menu Figure 3-21: GPS Constellation configuration (StudioView) This functionality may be required for the configuration of scenarios taking place in the past, or 'What-if' scenarios. Consider the following when configuring satellite constellations: The selected satellite constellation will impact the navigation message to mimic the type of simulated satellite.

  • Page 97: Encryption

    3.5 "Select" Menu (default) For Glonass: Glonass-K1 Glonass-M (default) 3.5.10.5 Encryption Next to the unencrypted L1 band Coarse/Acquisition Pseudo-Random Noise code (C/A PRN code), the Precise (P), but encrypted Pseudo Random Noise code is used to mod- ulate both the L1, and the L2 carriers. While GSG cannot replicate the encryption, it can emulate, and thus represent the P(Y) code, so as to allow for commercial GPS surveying receivers to be tested for their ability to derive the carrier in a codeless fashion.

  • Page 98: Sbas Satellites

    3.5 "Select" Menu Considerations: For most L1/L2 GPS receivers, there are two valid configuration modes: 1. Enable L1 C/A, L1P, and L2P only: The L1P and L2P will be transmitted without encryption. 2. Enable L1 C/A, L1P, and L2P, and Pseudo P(Y): P code will be scrambled to mimic a realistic P(Y) signal for use in receiv- ers that can make use of L1/L2 P(Y) signals for codeless applications, or to...
  • Page 99 3.5 "Select" Menu Figure 3-23: GNSS SBAS systems GSG can simulate SBAS satellites at frequency bands L1 and L5. Each scenario defines the number of SBAS satellites that should be simulated. There can be 0, 1, 2, or 3 SBAS satel- lites per scenario.
  • Page 100 3.5 "Select" Menu the SBAS messages. These messages comprise different Message Types, one of which— MT9—is used to update the satellite’s position and speed. You can also select up to 3 specific satellites to simulate. The SBAS satellites transmit their signals utilizing Coarse/Acquisition Pseudo-Random Noise (see also "Encryption"...
  • Page 101 3.5 "Select" Menu Considerations If a scenario needs SBAS messages that cannot be downloaded from these FTP sites, the scenario continues, but the GSG unit transmits null- messages (SBAS message type: MT63). An SBAS-compatible receiver should still be capable of seeing the SBAS signals, but it will not find any useful information (range corrections, time offsets, etc.) in these mes- sages.

  • Page 102: Options" Menu

    3.6 "Options" Menu QZSS L1 SAIF The QZSS satellites transmit also a SBAS signal, called L1 SAIF. The GSG unit can emulate this signal. The signal is enabled by setting the value of “QZSSL1SAIF” to ”1” in a scenario file. If the user does not specify a file containing the messages for transmission, the unit will transmit only the default (MT63) messages.
  • Page 103 3.6 "Options" Menu Note: When the power settings of individual channels are changed during scenario execution (via the > Events menu, or protocol) the power range will be further limited so that the maximum difference between the strongest and the weakest signal is never more than 72 dB.

  • Page 104: Adjusting Transmit Power

    3.6 "Options" Menu Table 3-2: Transmit power offsets Constellation Signal Power offset, dB L1 C/A L1 P -3.0 L2 P -3.0 +1.5 GLONASS -2.5 -8.5 +1.5 +3.5 Galileo +3.5 Beidou -4.5 -4.5 QZSS L1 C/A L1 SAIF -2.5 3.6.1.1 Adjusting Transmit Power The term Transmit Power refers to the satellite signal power (signal level) transmitted by...
  • Page 105 3.6 "Options" Menu you modified the power configuration, it will be saved with all other settings when the unit is turned off. To configure signals power: 1. Navigate to Options > Transmit Power. 2. Adjust the GPS L1C/A band Ref. power.

  • Page 106: Adjusting External Attenuation

    3.6 "Options" Menu Orbit type Absolute power Relative power Signal name name (dBm) (dBm) GPSL1P -131.5 GPSL2P -131.5 GPSL2C -128.5 GPSL5 -127 +1.5 SBASL1 -131 -2.5 SBASL5 -127.9 +0.6 GLOL1 -131 -2.5 GLOL2 -137 -8.5 GALE1 -127 +1.5 GALE5A -125 +3.5 GALE5B -125...

  • Page 107: Adjusting Noise Generation

    3.6 "Options" Menu The range is: 0 … 30.0 dB Resolution: 0.1 dB. To adjust External Attenuation, navigate to Options > Transmit Power. Figure 3-26: Adjusting external attenuation 3.6.1.3 Adjusting Noise Generation GSG-5/6 has the capability to simulate noise on the GPS L1 band. Noise simulation can be a powerful tool for receiver testing, since it allows for a strong signal to be submitted, without jamming the receiver.
  • Page 108 3.6 "Options" Menu General considerations International regulations keep the L1 band practically clean from disturbing signals, so the only noise source is the natural background noise, as expressed in the following equation: = kTB Where k is the Bolzmann’s constant, T is the ambient temperature (in Kelvin), and BN is the bandwidth (in Hertz).
  • Page 109 3.6 "Options" Menu 1. Set the External Attenuation 2. Set the Transmit Power 3. Set the Noise Bandwidth 4. Set the Carrier-to-Noise Density 5. Set the Noise Offset (this can be done at any time without affecting the other set- tings) Adjusting Power/Noise via SCPI command If you use the SCPI protocol to change the power/noise settings, use the order above to...

  • Page 110: Signal Generator

    3.6 "Options" Menu strong signal (for example: -100 dBm, C/N 44 dB-Hz), and narrow noise bandwidth. Then increase the noise bandwidth until the C/N value shown by your receiver sta- bilizes. It is a good idea to use the narrowest bandwidth needed. Note: The receivers use different methods to calculate C/N SNR), so the value given by the receiver may be different from the...
  • Page 111 Note: The SBAS signal type is only available with GSG-55, GSG-56, and GSG-6 Series units. Note that in signal generator mode (unlike in constellation simulation mode), GSG will always attempt to download SBAS data. If such data is not available, then MT63 (i.e., “null messages”) will be transmitted.

  • Page 112: Satellite Id

    3.6 "Options" Menu nominal frequency. With GSG-6 series simulators, it is possible to generate car- rier signals for L1 and L2 at the same time. Prn: Pseudo-random noise 3.6.2.2 Satellite ID Satellite ID field is used to specify the GPS PRN, Galileo PRN, and the GLONASS satellite ID, therefore it is limited to (the highest GLONASS satellite ID).

  • Page 113: Frequency Offset

    3.6 "Options" Menu 3.6.2.4 Frequency offset Frequency offset applies to ALL of the simulated signals in the signal generator mode, i.e. once you set an offset, the code phases of the simulated signals start to shift com- pared to each other. 3.6.2.5 Start time Start time...

  • Page 114: Interface And Reference

    3.6 "Options" Menu Figure 3-30: Signal Generator running All signal parameters are stored to non-volatile memory and are set when the unit is star- ted. 3.6.3 Interface and Reference GSG interface options can be configured via the Options > Interface and Reference view: Figure 3-31: Interface/Reference Configuration...

  • Page 115: Network Configuration

    3.6 "Options" Menu 3.6.3.1 Network Configuration To access the Network configuration view, navigate to Options > Interface and Refer- ence > Select Interface Type: Ethernet. Highlight the menu item Network, and press enter; the Network configuration screen will be displayed: IP Configuration Figure 3-32: Static IP address configuration...

  • Page 116: Proxy Configuration

    3.6 "Options" Menu NTP client unable to set time In the event that GSG cannot resolve the NTP server address, upon start-up, the error mes- sage NTP client unable to set time will be displayed: 1. Confirm the message by pressing enter, and navigate to: Network configuration view, Options...

  • Page 117: Manage Files

    3.6 "Options" Menu 2. The Proxy address must be the address of the proxy including the http:// -prefix, and a port number after the address separated by ‘:’. Optionally, a username and pass- word for the proxy can be given. If in doubt, consult your network administrator about the Proxy server settings.
  • Page 118 3.6 "Options" Menu Figure 3-35: Choosing a file and an action Copying and renaming files When copying renaming a file, a keyboard is displayed for entering a new file name. Use the arrow keys and the ENTER key to select letters for the file name. LEFT/RIGHT arrow keys move the cursor.

  • Page 119: Show System Information

    3.6 "Options" Menu To exit the viewer, use the EXIT CANCEL keys. Figure 3-37: Viewing file content 3.6.5 Show System Information System Information view displays information about the GSG model, serial number, firmware version, oscillator type, and installed options (if any). In addition, the amount of free storage space available for scenarios and other user files is shown.

  • Page 120: Calibration

    Calibration Note: This chapter describes the Calibration menu items. Calibration itself should only be attempted by qualified technicians. Alternatively, you can send your GSG unit to Orolia to be calibrated. Via the Calibration view, you can: calibrate the unit’s maximum output power, and OXCO frequency view the results of a previous user calibration.
  • Page 121 3. Regardless of which oscillator option is installed in your GSG unit: If you are testing GPS timing receivers and are testing the precision of the 1 PPS output, comparing it to the 1 PPS output from your device under test, Orolia recommends calibration every year.
  • Page 122 3.6 "Options" Menu OCXO DAC value is adjusted according to the frequency measured by the GSG unit from the 10 MHz output at the back panel. Using a frequency counter, adjust the OCXO value until the GSG shows 10 MHz. PPS delay is essentially an “equipment delay”...

  • Page 123: Frequent Tasks

    This list is constantly being updated. Should you miss a task that is currently not included in this list, please let us know: techpubs@orolia.com . Thank you. The following topics are included in this Chapter: 4.1 Working with Scenarios 4.2 Locking/Unlocking the Keyboard...

  • Page 124: Working With Scenarios

    4.1 Working with Scenarios Working with Scenarios The tasks described here are frequently performed in the context of scenario execution and configuration. 4.1.1 Scenario Start/Stop/Hold/Arm See under: ""Start" Menu" on page 33. 4.1.2 Running a Scenario During scenario execution, you can ... Press view to display up to 6 different...

  • Page 125: Holding A Scenario

    4.1 Working with Scenarios 4.1.3 Holding a Scenario Holding a scenario means to temporarily prevent your GNSS receiver from continuing to move along its scenario trajectory (i.e., halting the trajectory), while the simulation con- tinues to run otherwise (time continues to elapse). This can be done manually, by pressing [.] / hold key, or by using the SCPI command SCENario:CONTrol...
  • Page 126 4.1 Working with Scenarios navigate between fields, first press the UP/DOWN arrow keys to select the field label. Then press enter or the RIGHT arrow key, to begin editing the values. To move to the next field on the same line, press enter, or the RIGHT arrow key.
  • Page 127 4.1 Working with Scenarios Third Configuration View The third Scenario Configuration View allows you to configure the satellites to be sim- ulated. Note: Some of the functionality shown is optional and may be grayed out. For more information on GSG Options, see "GSG Series Model Variants and Options"...

  • Page 128: Locking/Unlocking The Keyboard

    4.2 Locking/Unlocking the Keyboard Figure 4-4: Types of GPS (Glonass) satellites simulated Note: For a list of all configurable scenario parameters, see ""Select" Menu" page 38. Note: For the different options on how to start a scenario, see "Scenario Start Variations" on page 33.

  • Page 129: Setting Transmit Power

    4.3 Setting Transmit Power Open the , and then the command line interpreter (CLI) by clicking the MONITOR icon: Ensure that the CLI is connected to your GSG unit (see "Using the CLI" on page 116). Enter the following command: write SOURce:KEYLOCK:PASSWord [wxyz] The keyboard lock code [wxyz] can be changed at any time.
  • Page 130 4.3 Setting Transmit Power numeric keys to adjust the value, and then enter to confirm. This sets the Reference Power which is used to control the absolute power level of the GPS L1 C/A signal. You can also adjust the default relative power offset for each individual signal type other than GPS L1 C/A by selecting Sig-...

  • Page 131: Accessing The Gsg Web Interface

    4.4 Accessing the GSG Web Interface Note: Pressing the ± (format) key while dBm is highlighted changes the frequency band to be adjusted: L1 > L2 > L5 > ALL. Contrary to option 2., this will only adjust power for the selected satellites in view , not for new satellites coming into view later.

  • Page 132: Using The Cli

    File types of uploaded observations navigationData will not be veri- fied. Figure 4-5: Example GSG Web UI, showing a logged GPS almanac file STUDIOVIEW: Opens the Orolia website/StudioView web page: https://www.orolia.com/products-services/gnss-simulation/gpsgnss- simulators DOCUMENTATION: Opens the Orolia website/StudioView web page: https://www.orolia.com/support/spectracom/gsg-series-gps- simulators-support http://register.spectracom.com/...

  • Page 133: Performing A Receiver Cold Start

    4.6 Performing a Receiver Cold Start 2. Click the Globe icon. The Connections window will open. 3. Click the green PLUS icon in the top-left corner, and enter the name of the new con- nection, and its IP address (which can be found under the GSG menu Options >...

  • Page 134: Creating A One-Line Trajectory

    4.7 Creating a One-Line Trajectory Creating a One-Line Trajectory As the GSG unit uses the heading and speed information of the RMC sentences, only one NMEA sentence is actually required to describe a simple, continuous movement. For example, the following one-line trajectory specifies a continuous north-bound tra- jectory (as the heading field is set to 0.0 degrees) at a...
  • Page 135 4.8 Leap Second Configuration receivers must correctly implement the leap second at the proper time. To configure a leap second for a scenario, Select the scenario, then navigate to the con- figuration View 2/3: Figure 4-6: Leap Second field Alternatively, the leap second can be configured in StudioView. The leap second field can be set to -1, 0 or 1, and indicates a future change in the leap second value.

  • Page 136: Studioview Tasks

    ® GSG StudioView™ software for Windows enables you to create and edit scenarios, and perform file management tasks with Orolia's GSG series GPS/GNSS simulators. While GSG simulators are capable of configuring and running scenarios without the need ® for an external computer, StudioView Windows...

  • Page 137: Studioview Functionality Overview

    4.9 Studioview Tasks 4.9.1.2 StudioView Functionality Overview File Management and Control StudioView's File Manager allows you to upload or download scenario files to or from your ® GSG unit: Connect your Windows PC running StudioView to the GSG unit via its net- work, USB, or GPIB interface.

  • Page 138: Installing Studioview

    4.9 Studioview Tasks 4.9.2 Installing StudioView A free 30-day demo version of StudioView can be downloaded from the Orolia website, see the link below. After the 30-day trial period you need to purchase a StudioView license to activate all fea- tures, with the exception of the Uploader, which does not require a license.
  • Page 139 4.9 Studioview Tasks 1. On the GSG unit, navigate to Options > Interface and Reference: 2. Select the Interface type that matches your hardware configuration, i.e. the con- nection between the GSG unit and the StudioView computer: TCP/IP, USB, or GPIB (note that SCPI-Raw does not work with StudioView).

  • Page 140: Updating The Gsg Firmware Via Studioview

    GSG unit is V4.05 or lower, several updates must be performed in the correct sequence. It is possible, albeit not recommended, to back out a firmware update by installing the previous version on top. To obtain the firmware updates 2.03, 2.04, and 4.07 please contact Orolia Support at https://www.orolia.com/support/spectracom/request-service- product-support In order for the instrument to communicate with the PC Software the NI VISA runtime software is required.

  • Page 141: Uploading Studioview Files

    4.9 Studioview Tasks 4.9.5 Uploading StudioView Files GSG StudioView's Uploader tool is used to upload scenario files and firmware updates from your StudioView PC to a connected GSG unit, and vice versa. (For more information on firmware upgrades, see "Updating the GSG Firmware via StudioView" on the pre- vious page.) Note that...
  • Page 142 4.9 Studioview Tasks To obtain your GSG's IP address or change the interface type, select Interface and Reference from the GSG Options menu: Note: This screen may vary, based on your installed firmware version. 4. Click the Test button to verify the connection: Uploading Firmware 1.

  • Page 143: Transferring Files With Studioview

    4.9 Studioview Tasks 2. Click the Start button to start the transfer. The unit will first transfer the file, and then update the firmware. Uploading a Scenario 1. In order to upload a scenario, first ensure that the scenario file (.scen file) and any trajectory, event, or navigation file associated with the scenario are stored in the Stu- dioView repository.

  • Page 144: Accessing Gsg Remotely Via Studioview

    4.9 Studioview Tasks 2. Establish a connection to the GSG unit by clicking . (For details, see "Connecting StudioView to GSG" on page 122.) 3. Once a connection has been established, you should see GSG's file/folder tree in the left window, and StudioView's file list in the right window: 4.
  • Page 145 4.9 Studioview Tasks To open the Web UI in StudioView: 1. Navigate to Tools > Web interface, or click the icon. 2. Click to open the Connections Manager tool (for details, see "Connecting Stu- dioView to GSG" on page 122.) 3. After setting up the connection, a visual representation of the front panel will appear: You can control the unit as if physically pressing the buttons on the unit.

  • Page 146: Creating A Trajectory In Studioview

    4.9 Studioview Tasks 2. Click to open the Connections Manager tool (for details, see "Connecting Stu- dioView to GSG" on page 122.) 3. The following generic commands are supported (to display this list in the console window, type list.): clh – clear commands history cls –...
  • Page 147 Trajectories generated by means other than (a.) should always realistically reflect the dynamic capabilities of the type of vehicle in motion e.g., car, aircraft, ship. To this end, Orolia recom- mends using ‘smooth’ methods to describe the movements, i.e. changes in acceleration, head- ing or altitude should be gradual, not sudden or ‘hard’.
  • Page 148 4.9 Studioview Tasks GSG supports the following trajectory-related workflows: 1. NMEA trajectory files, generated with the StudioView Trajectory Editor 2. NMEA trajectory files, as recorded by a receiver under the live sky, then imported into and converted by Studioview 3. .traj format, as generated with the RSG trajectory editor in StudioView (supports 6 DoF) 4.
  • Page 149 4.9 Studioview Tasks Note: A little blue box indicates that a feature is active (except "Export ..."). Some features cannot be active at the same time. Table 4-1: The Trajectory Editor Toolbar Hover Icon Usage Tooltip Waypoints Parameters Display/hide the table on the right side of the screen. panel Speed and Altitude Charts...
  • Page 150 4.9 Studioview Tasks 1. In the StudioView Trajectory Editor, click the Route Builder icon . (See also "Using the Trajectory Editor for the First Time" on page 132.) The Build route panel will open: 2. Enter an address for the first point of the new route. 3.
  • Page 151 4.9 Studioview Tasks Double-click on any waypoint to edit its elevations, its coordinates, or the speed set- ting. You may enter geographic coordinates in any of Degrees, Deg Min, Deg Min Sec format or ECEF coordinates. StudioView will recalculate the other formats auto- matically.

  • Page 152: Converting A Trajectory In Studioview

    4.9 Studioview Tasks Add or delete waypoints by clicking the icon, or the icon, respectively. By default, Stu- dioView will insert the waypoint at the end of list. However, you may manually set a Point #, which will add the waypoint to that place in the trajectory. Select a waypoint in the Waypoints table, and then drag its Google Maps pin to relocate it.
  • Page 153 Trajectories should always realistically reflect the dynamic capabilities of the type of vehicle in motion e.g., car, aircraft, ship. To this end, Orolia recommends using ‘smooth’ methods to describe the movements, i.e. changes in acceleration, heading or altitude should be gradual, not sudden or ‘hard’.

  • Page 154: Improving A Trajectory

    4.9 Studioview Tasks Open result in the new Trajectory Editor window Write to file and open result in the new Trajectory Editor window Write to file. With the latter two options, click the lower file folder icon, and select a file loc- ation and file format .
  • Page 155 4.9 Studioview Tasks Downsampling Downsampling means decreasing the number of points in a trajectory, so as to make those parts of a trajectory with constant movement parameters as long as possible. The down- sampling algorithm excludes points which are within a specified deviation from the general movement direction.

  • Page 156: Creating An Rsg Trajectory With Studioview

    4.9 Studioview Tasks Max vertical velocity defines the maximum permitted vertical movement between consecutive points. If the altitude has changed between two consecutive points, it will be interpolated, applying this not-to-exceed vertical velocity. Heading change threshold defines the maximum change of movement dir- ection at any particular point.

  • Page 157: Using The Rsg Trajectory Editor For The First Time

    4.9 Studioview Tasks Trajectory in StudioView" on page 130 ), an RSG trajectory is not defined by its geo- graphic position, but by relative changes of movement. These motion changes are captured in user-defined parameters which are assigned to SCPI commands (to learn more about SCPI commands, see "SCPI Guide: Introduction"...
  • Page 158 4.9 Studioview Tasks To open an existing RSG trajectory: Navigate to File > Open…, or click To create a RSG trajectory: 1. Enter a Start position, and an altitude in meters. Use a semicolon and a space as separators: Note that this data actually is not part of the trajectory, it is used only to assign a rel- ative location to the trajectory.

  • Page 159: Rsg Example: Racetrack Pattern

    4.9 Studioview Tasks Select the command you want to use, and enter the required parameters. Detailed command descriptions can be found in the "SCPI Guide" on page 223. 3. To edit an existing command, double-click it, or click the button. To delete a command, use the button.
  • Page 160 4.9 Studioview Tasks 1. Open the RSG Trajectory editor. 2. Enter a Start position and altitude (m), or leave the default. 3. Add VELOCITY with initial speed and heading. 4. Next, add a KEEP GOING instruction in order to assign a duration to the previous command.

  • Page 161: Kepler Orbit

    4.9 Studioview Tasks For the turn, select Left, Direction change: 180°, and Duration: 5 minutes. 6. Lastly, repeat all of the steps above to complete the racetrack pattern (replace the heading with the opposite heading). 4.9.11.3 Kepler Orbit KEPLER orbits are used to build a trajectory for space vehicles. The RSG trajectory editor's Command Editor offers a KEPLER trajectory that is –...
  • Page 162 4.9 Studioview Tasks Note: The preferred way to describe space vehicle trajectories are TLE- formatted trajectories, see "Trajectory Two-Line Element Format (TLE)" page 363. To access the Kepler trajectory dialog window: 1. In StudioView, navigate to the RSG Trajectory Editor. 2. Click to open the Command Editor.
  • Page 163 4.9 Studioview Tasks 4. Populate the fields. 5. Attach the Kepler trajectory to a scenario (see "Configuring a Scenario" on the next page). The result will look similar to the illustration below: User Manual GSG-5/6 Series Rev. 27...

  • Page 164: Playing Rsg Scenarios In Studioview

    4.9 Studioview Tasks Note: Higher-end GSG models have a sample Kepler trajectory for the ISS pre-installed. 4.9.12 Playing RSG Scenarios in StudioView StudioView's Realtime Scenario Player allows to play RSG scenarios in real-time. 1. To open the Realtime Player, navigate to Tools >...
  • Page 165 4.9 Studioview Tasks to the GSG unit. The GSG unit will execute the simulation in accordance with the para- meters specified in the scenario file. Scenario data is stored in a text file. To show/hide text of scenario file, click .To con- figure the scenario, fill in the appropriate fields under the tabs described below.
  • Page 166 4.9 Studioview Tasks Start time is specified using GPS Time. The GPS Time is always used when dis- playing time. This is not equal to the UTC time frequently displayed by the receivers. Contrary to the GPS time, UTC contains leap seconds. The Start Time can be a set time, or the current time derived from an NTP server specified in the Network Configuration settings of GSG device.
  • Page 167 4.9 Studioview Tasks encryption by clicking on the checkbox for the corresponding constellation and band. The availability of all elements for simulation (e.g., GPS L2C, L5 and Galileo) is dependent on the installed licensing options and your GSG model . For each constellation, you may specify the maximum number of signals in view...
  • Page 168 4.9 Studioview Tasks The simulation is carried out based on probability, applying different building dens- ities (sparse <> dense). The feature offers some adjustability. For more information, "Propagation Environment Models" on page 69. By specifying the Elevation mask, you define the satellite-in-view cut-off range. All satellites which are below this range will be dropped off and replaced with bet- ter/higher satellite (if available).
  • Page 169 4.9 Studioview Tasks this dropdown list, you have to create a new trajectory first and then save it in the repository. Events file describes some specified events during scenario execution. To create events file, see "Defining Events in StudioView" on page 155.
  • Page 170 If a satellite is blocked by an object from either the environment or vehicle model, i.e. it is not visible by the receiver antenna, its power level is set to OFF. more information, https://www.orolia.com/documents/environmental- modeling- gpsgnss- simulators GSG can successfully handle vehicle models with up to 130 triangles and models should be optimized for low polygon count.

  • Page 171: Defining Events In Studioview

    4.9 Studioview Tasks 200D, section 20.3.3.5.2.5. When set to Off, no delays caused by the Ionosphere are used in the simulation. GSG also supports simulation of Ionospheric delays using files in IONEX format. To specify a particular file, select Files and choose it from Repository.
  • Page 172 4.9 Studioview Tasks Adding an Event To add a new event, click To set the type of event, choose an option from the Event type drop-down menu: Change absolute power: Defines a power level for a given channel or PRN code. Change relative power: Defines a change in the power level for a given channel or PRN code.

  • Page 173: Adding A Jammer Signal In Studioview

    4.9 Studioview Tasks Change multipath signal parameters Change navigation message bits Change signal propagation model. To set the Time at which the event is to occur, specify the number of seconds from the beginning of scenario. Define a Target: Scenario will apply the specified event to all satellites simulated in scenario.

  • Page 174: Spoofing A Signal In Studioview

    4.9 Studioview Tasks 4. Locate the line item Jammer position, and turn it ON. 5. Enter the geographic position for the new interference signal. 6. Specify the frequency bands you wan to jam and other parameters for the new interference signal. Please note that now your jammer will be displayed on the map in the Trajectory Editor and the...
  • Page 175 4.9 Studioview Tasks used to challenge the capability of the receiver to discern between the genuine and the fake signal. Several parameters can be adjusted to tweak the test scenario, if needed. The testing environment illustrated below is used to test a system against spoofing vul- nerability.
  • Page 176 4.9 Studioview Tasks Spoofer Connection: Open the Connections Manager to establish a con- nection to the device that generates the spoofing data (simulated, recorded, or live sky) Scenario: Select a scenario for the "spoofed" simulation. Use the same scenario as for sky: [Yes/No] Check if you want to use the same scenario for both the sky data, and the spoofing data.

  • Page 177: Using Sbas In A Simulation

    4.9 Studioview Tasks Click the Start button in the bottom-left corner. The following parameters will be updated in real time: LiveSky position: Provides the actual position, as determined using the live sky satellite data. Receiver visible position: Provides the actual position, as measured by the receiver.
  • Page 178 4.9 Studioview Tasks The currently supported SBAS satellites are: EGNOS: 120, 124, and 126 WAAS: 133, 135, and 138 MSAS: 129, 137 GAGAN: 127, 128 The simulator uses two approaches for SBAS messages: 1. Default SBAS messages (MT63) 2. EGNOS/WAAS/MSAS message files The default SBAS messages are always available.

  • Page 179: Record And Playback

    4.9 Studioview Tasks 6 months for WAAS scenarios. Moreover, the start time shall not be too close to the cur- rent time. For EGNOS, there can be a one day delay before the SBAS messages are pub- lished on the FTP site. For WAAS the delay can possibly be longer (up to 3 or 4 days). The Internet connection is not always needed.

  • Page 180: Installation Of The Opt-Rp Software

    Record and Playback software. 4.9.14.3 Usage Notes i. The Record and Playback software is intended for use with a properly licensed GSG. If your GSG needs a Record and Playback license, please contact Orolia (see "Tech- nical Support" on page 207).

  • Page 181: Recording Data With Studioview

    4.9 Studioview Tasks strength (in dBm). An offset value of [‐ 160] is recommended to begin with. This value can be adjusted up or down until the offset is satisfactory. vi. You must also specify any scenario options that cannot be extracted from NMEA sen- tences.
  • Page 182 4.9 Studioview Tasks Figure 4-8: StudioView's Data Recorder The Data tab Under the Data tab you decide where the data to be recorded comes from (a GSG unit, or a GNSS receiver), and which data to log: RINEX navigation files RINEX observation files NMEA from GSG unit NMEA from connected receiver (This can be used to record NMEA data for the GSG...
  • Page 183 4.9 Studioview Tasks 1. Check the box unit, then click to configure the connection (for details, see "Connecting StudioView to GSG" on page 122.) 2. Choose which data to record: Navigation data, Observations, RSG data, Satellites data (e.g., satellite position, Doppler shift, etc), navigation messages. Select Output files for each recorded data category.

  • Page 184: Processing Recorded Data For Playback

    4.9 Studioview Tasks DO NOT start the scenario via the GSG unit , since the RINEX navigation data will not be captured! (Unless you manually submitted the SCPI navigation data logging command.) Once data starts to be generated, the Data Recorder will display the incoming raw data in the bottom section of the Data tab.
  • Page 185 4.9 Studioview Tasks 2. Click to open the Connections Manager tool (for details, see "Connecting Stu- dioView to GSG" on page 122.) 3. Select your recorded NMEA file as the source file by opening the file dialog navigating to file. Scenario Generator uses the GSG default scenario parameters for the Play- back function.

  • Page 186: Editing Rinex Files In Studioview

    4.9 Studioview Tasks 6. You may also choose Actions after generation is complete. Use the drop-down menu to choose to open the files in the editors or open the Uploader to load them onto the unit. 7. Click Generate to create the files. 4.9.15 Editing RINEX Files in StudioView RINEX files contain Ephemeris data that can be edited with StudioView's RINEX editor:...
  • Page 187 4.9 Studioview Tasks The following dialog box will appear if you double-click on a highlighted GPSA GPSB row: The Time Correction tab User Manual GSG-5/6 Series Rev. 27...
  • Page 188 4.9 Studioview Tasks Time Correction toolbar allows you to change the coefficients, Reference Time and the Continuous Week Number. Double-click a highlighted row to open the fol- lowing dialog box: The Leap tab User Manual GSG-5/6 Series Rev. 27...
  • Page 189 4.9 Studioview Tasks Under the Leap tab you can change the Leap seconds, Week number, an number. The Data tab Under the Data tab you can change the health of satellites. In each cell, you can enter a number directly, or click the Edit button and select a value from the dropdown list: User Manual GSG-5/6 Series Rev.

  • Page 190: Transmitting Rtcm Messages With Studioview

    4.9 Studioview Tasks To edit multiple cells at once, select the cells by holding down the Shift or Ctrl key while clicking, and then click the Edit button. 4.9.16 Transmitting RTCM Messages With StudioView RTCM Transmission function allows to re-transmit RTCM message from the GSG unit to the external receiver.

  • Page 191: Reference

    Reference This Chapter includes reference information, such as listings of default settings, logs, protocols, file formats and error messages. The following topics are included in this Chapter: 5.1 The GSG Web UI 5.2 Messages 5.3 Timing Calibration 5.4 NMEA Logging 5.5 Execution Log 5.6 Saving RINEX Data 5.7 YUMA Almanac File...

  • Page 192: The Gsg Web Ui

    5.1 The GSG Web UI The GSG Web UI Orolia GSG Series simulators feature a Web-based user interface (throughout this doc- umentation referred to as "Web UI"), accessible via a standard Web browser (e.g., Mozilla Firefox or Internet Explorer) installed on a computer with access to the same network to which your GSG unit is connected.
  • Page 193 5.2 Messages action. Could not initialize the keyboard. A possible hardware issue exists. Please contact service. Could not initialize web interface. A possible firmware issue exists. Re-install firmware. If problem persists, then contact ser- vice. Scenario is modified. Do you want to save changes using a different name? Scenario configuration has been modified.
  • Page 194 5.2 Messages Are you sure you want to restore factory defaults? Confirmation request before restoring factory defaults. IP address configuration failed. Configuring the Internet Protocol address failed. Please check your network settings and try again. Cannot save unit parameters. Saving of settings failed. Try restarting the device and saving parameters again. If it still fails, then please contact service.
  • Page 195 5.2 Messages Could not start signal. Unexpected problem occurred. Please restart the GSG-5/6. Please check start date! GPS Start date is invalid in scenario configuration or signal generator. (Note: The earliest allowed start date is 6.1.1980.) Please check the date and correct it. Invalid Rinex file selected.
  • Page 196 5.2 Messages Cannot delete directory. Removing a directory is forbidden. Cannot rename directory. Renaming directory is forbidden. No manageable files available. If this happens the device is faulty. Please contact service. Do you want to delete the file? Confirmation request when removing file. Cannot delete file.
  • Page 197 5.2 Messages Scenario failed to start. Please review scenario settings. Restart GSG-5/6. Could not start scenario. Restart GSG-5/6. No scenarios available. This message appears when there are no scenarios in the scenarios directory. Reset fact- ory defaults to restore the default scenarios, or transfer your own scenarios from a PC using the StudioView software.

  • Page 198: Timing Calibration

    5.3 Timing Calibration Timing Calibration GSG units with the Timing Calibration Option (OPT-TIM) have an additional timing cal- ibration file installed, named pps.cal. Provided the option is enabled, you can access and modify this file via the StudioView File Manager (>...

  • Page 199: Nmea Logging

    5.4 NMEA Logging NMEA Logging GSG offers the possibility to log a scenario’s execution in NMEA data. Every second a “snap- shot” of the user and satellites’ status is taken and recorded in the form of 3 standard NMEA sentence types. sentence describes essential GPS position, velocity and time sentence describes essential fix data, providing 3D location and accuracy data.

  • Page 200: Saving Rinex Data

    5.6 Saving RINEX Data Using the GSG Web UI on a connected PC, click on FILES, then navigate to observations, and click on executionlog.txt. The maximum size of the execution log file is 20,000 lines. Once the limit is reached, the oldest entries will be overwritten by new data.

  • Page 201: Yuma Almanac File

    5.7 YUMA Almanac File After each six hours or when the scenario is stopped, the navigation data is saved to: /observations/scenarioNameYYYYMMDDHHMMSS.nav The generated files can be retrieved via StudioView, the Web UI, or by using SCPI commands (see "MMEMory:COPY" on page 321).

  • Page 202: Rls (Return Link Service)

    5.8 RLS (Return Link Service) Argument of Perigee(rad): 1.117132574 Mean Anom(rad): –3.0896651067E+00 Af0(s): 1.7600243882E-04 Af1(s/s): 1.3415046851E-11 week: 755 RLS (Return Link Service) As part of the Cospas-Sarsat System, Galileo satellites are capable of picking up emer- gency signals emitted on 406 MHz by distress beacons, and transmitting a signal back to the beacon via the E1 frequency to confirm receipt of the distress signal.

  • Page 203: Requirements

    5.8 RLS (Return Link Service) 5.8.2 Requirements In order for the RLM simulation to work with GSG, the following pre-requisites must be met: The Galileo-Option OPT-GAL must be present GSG-5 or -6, with 8 channels (or 16 channels if GPS + GAL is required) Firmware version 6.6.1 or greater StudioView software Version 4.6.1.3 or greater 5.8.3...

  • Page 204: Galileo E6-B/C Signal

    5.9 Galileo E6-B/C Signal Galileo E6-B/C Signal GSG's optional Galileo E6-B/C signals are pseudo-signals for the Galileo Commercial Ser- vice (CS). Both signals are sent unencoded: A secondary code (pilot tone) is sent on the E6-C frequency band, with no data. On the E6-B band dummy data is sent at 448 bps. To utilize this optional functionality a GSG-6 unit with an available frequency band is required, as well as the OPT-GAL...
  • Page 205 5.11 Pre-Installed Scenarios More advanced scenarios, events, and trajectories can be found in the StudioView repos- itory. Table 5-1: Scenarios Model Scenario Position Start Time GPSStatic N043° 04' 01/07/2022 59.257",W077°35'20.674" 14:00 GSG-5/54/55/56/62/63/64 GPSCircle N043° 04' 01/07/2022 OPT-TRAJ 59.257",W077°35'20.674" 14:00 GSG-5/55/56/62/63/64 OPT- GPSStaticSBAS N043°...

  • Page 206: Default Scenario Satellites

    5.12 Default Scenario Satellites 5.12 Default Scenario Satellites As of spring 2015, the default GPS constellation consists of the following active satellites: 3 x Block IIA satellites 12 x Block IIR satellites 7 x Block IIR-M satellites 10 x Block IIF satellites GSG uses this constellation as the default for its scenarios.

  • Page 207: Scenario File Format

    5.13 Scenario File Format 5.13 Scenario File Format Scenarios are defined by means of text files which contain a set of keywords and values, as described below. Scenario files used with GSG-5/6 units must follow the described format. All fields are optional and will assume default values if not provided.
  • Page 208 5.13 Scenario File Format Vehicle FILENAME | None GpsSatellites INTEGER GlonassSatellites INTEGER GalileoSatellites INTEGER BeiDouSatellites INTEGER QZSSSatellites INTEGER IRNSSSatellites INTEGER Startpos DECIMAL degN DECIMAL degE DECIMAL m BaseStationPos DECIMAL degN DECIMAL degE DECIMAL m UserTrajectory FILENAME [0|1] | Static | 3GPP | Circle LeverArm DECIMAL DECIMAL DECIMAL DeltaLSF...
  • Page 209 5.13 Scenario File Format SvBlockIIIA Space delimited list of SVID’s SvGlonassM Space delimited list of SVID’s SvGlonassK1 Space delimited list of SVID’s GPSL1CA 1 | 0 GPSL1P 1 | 0 GPSL2P 1 | 0 GPSL2C 1 | 0 GPSL5 1 | 0 GPSPY 1 | 0 GLOL1...
  • Page 210 5.13 Scenario File Format powerChange DECIMAL powerInterval DECIMAL InterferenceSignals INTEGER [InterferenceSignal INTEGER] GPSL1CA 1 | 0 GPSL1P 1 | 0 GPSL2P 1 | 0 GPSL2C 1 | 0 GPSL5 1 | 0 GPSPY 1 | 0 GLOL1 1 | 0 GLOL2 1 | 0 GALE1...
  • Page 211 5.13 Scenario File Format Scenario File Key- Parameter Value Comment word StartTime Valid date in the format: Start time in the GPS Time time frame. MM/DD/YYYY Note that seconds must be set to zero. HH:MM:00 When scenario ephemeris data is set to Download, Source then StartTime must be in the past (typically with a Valid range limited to:...
  • Page 212 5.13 Scenario File Format Scenario File Key- Parameter Value Comment word BeiDouSatellites [-1, 37] Default: 0 Keyword -1 implies 'Auto' – maximum number of Satellites in view will be simulated. QZSSSatellites [-1, 4] Default: 0 Keyword -1 implies 'Auto' – maximum number of Satellites in view will be simulated.
  • Page 213 5.13 Scenario File Format Scenario File Key- Parameter Value Comment word IonoModel Keyword of comma- Default: On separated filenames Available keywords:[Off, 'Off' = 'Off' (in Graphical user interfaces) 'On' ='Klobuchar' (in Graphical user inter- faces) Tropo Model {'Saastamoinen' | 'Black Selected tropospheric model.
  • Page 214 5.13 Scenario File Format Scenario File Key- Parameter Value Comment word DefaultGpsSV {'Default', 'SvBlockII', Defines the default GPS satellite series simulated, 'SvBlockIIA', 'SvBlockIIR', would the ID not explicitly be specified to be of a 'SvBlockIIR-M', 'SvB- different type. Default: 'Default' lockIIF', 'SvBlockIIIA'} DefaultGlonassSV {'Default', 'SvGlonassM',...
  • Page 215 5.13 Scenario File Format Scenario File Key- Parameter Value Comment word GALE1 [0, 1] , where 0 cor- Default: 1 ('On') responds to 'Off' , and 1 to 'On' GALE5a [0, 1] , where 0 cor- Default: 1 ('On') responds to 'Off' , and 1 to 'On' GALE5b [0, 1] , where 0 cor-...
  • Page 216 5.13 Scenario File Format Scenario File Key- Parameter Value Comment word [MultipathSignal INTEGER range: [1, Mul- 'Header' for the parameters for each multipath sig- INTEGER] tipathSignals] nal. When MultipathSignals is 1 or greater, then a set of parameters must be specified for each multipath signal.
  • Page 217 5.13 Scenario File Format Scenario File Key- Parameter Value Comment word GPSL2C [0, 1] , where 0 cor- Specifies the type of signal interference responds to 'Off' , and 1 to 'On' GPSL5 [0, 1] , where 0 cor- Specifies the type of signal interference responds to 'Off' , and 1 to 'On' GPSPY...
  • Page 218 5.13 Scenario File Format Scenario File Key- Parameter Value Comment word IRNSSL5 [0, 1] , where 0 cor- Specifies the type of signal interference responds to 'Off' , and 1 to 'On' mode [0. 1, 2, 3] , where 0 is Specifies the type of signal interference modulated,1 is unmod- ulated, 2 is sweep and 3...

  • Page 219: Gsg Series Model Variants And Options

    5.14 GSG Series Model Variants and Options 5.14 GSG Series Model Variants and Options Orolia GSG Series GNSS constellation simulators and signal generators are available in sev- eral different Model configurations, and with numerous Option packages, in order to allow for application-specific customization:...

  • Page 220: Gsg Models & Variants

    BEIDOU QZSS Upgrade to 4-channel unit 5.14.2.2 GSG-5 Series Base unit: 4 channels, GPS L1 C/A Options for GSG-5: Upgrade to 8, or 16-channels Upgradable to GSG-6 Series Advanced Feature Set included: SBAS Trajectories User Manual GSG-5/6 Series Rev. 27...

  • Page 221: Series

    Antenna modeling Front Panel Lockout NTP Synchronization Arm and trigger Leap Second Simulation 5.14.2.3 GSG-6 Series Multi-frequency, Multi-system GNSS constellation simulators: Up to 64 Channels and 4 simultaneous frequencies GPS L1 C/A Includes Advanced Feature Set of GSG-5 GSG-6 Model variants:...
  • Page 222 5.14 GSG Series Model Variants and Options OPT-ECL: enabling this option loads and enables the predefined scenarios for eCall. OPT-FN: fixed bandwidth noise OPT-GLO: enables Glonass signals supported. OPT-GAL: enables all Galileo signals supported. OPT-HPWR: High Power Option OPT-HV: high velocity/altitude enables the simulation of high velocity vehicles. OPT-INTF: interference option to simulate interference signals.

  • Page 223: Problems

    Phone support is available during regular office hours under the telephone numbers listed below. 5.15.1.1 Regional Contact Orolia operates globally and has offices in several locations around the world. Our main offices are listed below: Table 5-2: Orolia contact information...
  • Page 224 5.16 License Notices Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. This version of the GNU Lesser General Public License incorporates the terms and con- ditions of version 3 of the GNU General Public License, supplemented by the additional per- missions listed below.
  • Page 225 5.16 License Notices 3. Object Code Incorporating Material from Library Header Files. The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your choice, provided that, if the incorporated material is not limited to numerical parameters, data structure lay- outs and accessors, or small macros, inline functions and templates(ten or fewer lines in length), you do both of the following:...
  • Page 226 5.16 License Notices modified version of the Linked Version. (If you use option 4d0, the Installation Information must accompany the Minimal Corresponding Source and Cor- responding Application Code. If you use option 4d1, you must provide the Installation Information in the manner specified by section 6 of the GNU GPL for conveying Cor- responding Source.) 5.
  • Page 227 5.16 License Notices The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users.
  • Page 228 5.16 License Notices 0. Definitions. "This License" refers to version 3 of the GNU General Public License. "Copyright" also means copyright-like laws that apply to other kinds of works, such as semi- conductor masks. "The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you".
  • Page 229 5.16 License Notices system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work)run the object code and to modify the work, including scripts to control those activities.
  • Page 230 5.16 License Notices under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. 4.
  • Page 231 5.16 License Notices 6. Conveying Non-Source Forms. You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: a.
  • Page 232 5.16 License Notices product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, indus- trial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
  • Page 233 5.16 License Notices additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission. Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: a.
  • Page 234 5.16 License Notices However, if you cease all violation of this License, then your license from a particular copy- right holder is reinstated (a)provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
  • Page 235 5.16 License Notices A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version". A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modi-...
  • Page 236 5.16 License Notices (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was gran- ted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
  • Page 237 5.16 License Notices Later license versions may give you additional or different permissions. However, no addi- tional obligations are imposed on any author or copyright holder as a result of your choos- ing to follow a later version. 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
  • Page 238 5.16 License Notices Some parts of this product use free software released under the terms of MIT/X11 License. Upon request Orolia will give out source code according to applicable licenses. orolia.com Contact information can be found at web address: This license applies to GeographicLib, versions 1.12 and later.

  • Page 239: Scpi Guide

    SCPI Guide The following topics are included in this Chapter: 6.1 SCPI Guide: Introduction 6.2 Protocol 6.3 Command Reference 6.4 Sensors Command Reference 6.5 RSG Command Reference 6.6 Programming 6.7 Revision History (SCPI Guide) User Manual GSG-5/6 Series...

  • Page 240: Scpi Guide: Introduction

    6.1 SCPI Guide: Introduction SCPI Guide: Introduction The SCPI Guide describes the data exchange between a GSG unit and a PC. SCPI (pro- nounced: "skippy") stands for Standard Commands for Programmable Instruments. The SCPI standard describes the syntax of commands widely used to communicate with programmable instruments.

  • Page 241: Protocol Errors

    6.2 Protocol responses (even empty ones) are terminated with an empty line (a line with no symbols except a newline symbol in it). When using, for example, a telnet client to control the unit, it is enough just type com- mands and press enter to send the command.
  • Page 242 6.2 Protocol -158,"String data not allowed". String data detected when number is expected. -160,"Block data error”. This error, as well as errors –161 through –169, is gen- erated when parsing a block data element. This particular error message is used when the instrument cannot detect a more specific error.

  • Page 243: Command Reference

    6.3 Command Reference -257,"File name error". File name is empty. -410,"Query INTERRUPTED”. Indicates that a condition causing an INTERRUPTED Query error occurred (see IEEE-488.2, 6.3.2.3). 1401,"Wrong program data checksum found". Checksum of file transferred is invalid. 1403,"File length error". In file transfer length is invalid. This can be happen if there is not enough memory or storage space on device to retrieve file.

  • Page 244: Esr

    6.3 Command Reference Command Syntax *ESE <decimal> Parameters <dec.data> = the sum (between 0 and 255) of all bits that are true. Event Status Enable Register (1 = enable) Weight Enables PON, Power-on occurred URQ, User Request CME, Command Error EXE, Execution Error DDE, Device Dependent Error QYE, Query Error...
  • Page 245 6.3 Command Reference Returned Format <Manufacturer>, <Model>, <Serial Number>, <Firmware Level>, <Options>. Example SEND: *IDN? READ: SPECTRACOM,GSG-5,163049,V6.0.3,16 SBAS TRAJ TRG FN NOW INTF MP PPS RSG Options The first option listed is the maximum number of channels the unit has been licensed for. SBAS –...

  • Page 246: Opc

    6.3 Command Reference – Record and Playback – Jamming Package – Sensor Simulation – QZSS – Visibility/Terrain Obscuration – IRNSS L5 6.3.1.5 *OPC Operation Complete Operation Complete command causes the device to set the operation complete bit in the Standard Event Status Register when all pending selected device operations have been finished.

  • Page 247: Opc

    6.3 Command Reference Then read the event status register to reset it: SEND: *ESR? 6.3.1.6 *OPC? Operation Complete Query The Operation Complete query places an ASCII character 1 into the device’s Output Queue when all pending device operations have been finished. When a scenario is running there will be a pending operation set that is released at the start of each 100 ms epoch.

  • Page 248: Sre

    6.3 Command Reference 6.3.1.8 *SRE Service Request Enable Sets the service request enable register bits. This enable register contains a mask value for the bits to be enabled in the status byte register. A bit that is set true in the enable register enables the corresponding bit in the status byte register to generate a Service Request.

  • Page 249: Sre

    6.3 Command Reference 6.3.1.9 *SRE? Service Request Enable Query Read the value of the service request enable register. Returned format <Integer> = the sum (between 0 and 255) of all bits that are true. See "*SRE" on the pre- vious page for a description of the individual bits.

  • Page 250: Wai

    6.3 Command Reference Returned format <Integer> Where: 0 = No error 1 = Error in reference clock 6.3.1.12 *WAI Wait-to-continue The Wait-to-Continue command prevents the device from executing any further com- mands or queries until execution of all previous commands or queries have been com- pleted.

  • Page 251: System:error

    6.3 Command Reference 6.3.2.1 SYSTem:ERRor? Function This SYSTem command queries the error queue for an ASCII text description of the next error and removes it from the queue. The error messages are placed in an error queue, with a FIFO (First In-First Out) structure. This queue is summarized in the Error AVailable (EAV) bit in the status byte.

  • Page 252: System:reset:factory

    6.3 Command Reference 6.3.2.2 SYSTem:RESET:FACTory Function This SYSTem command performs the factory reset. With parameter restore it only restores the factory default files. With parameter clean it cleans all user data and restores factory default files. Command Syntax SYSTem:RESET:FACTory <restore|clean> Note Communication interface is not reset in order to maintain connection to the unit.

  • Page 253: Source:power

    6.3 Command Reference Command Syntax SOURce:POWer <decimal> Note Setting not stored during scenario or 1-channel mode execution. If power is inside allowed limits, but other RF parameters need to be modified, such para- meters are modified and an error about settings conflict is set. Parameter decimal [-160,-65] dBm Example...

  • Page 254: Source:refpower

    6.3 Command Reference 6.3.3.3 SOURce:REFPOWer Function Changes the absolute power in dBm of the reference signal (GPS L1 C/A). Command Syntax SOURce:REFPOWer <decimal> Notes This command can only be used before starting a simulation. The setting is not stored dur- ing scenario or 1-channel mode execution.

  • Page 255: Source:abspower

    6.3 Command Reference SOURce:REFPOWer? READ: -121.3 6.3.3.5 SOURce:ABSPOWer Function Changes the absolute power for the given signal type and orbit type. Command Syntax SOURce:ABSPOWer <signal name>,[<orbit type name>,]<power> Notes This command can only be used before starting a simulation. The setting is not stored dur- ing scenario or 1-channel mode execution.

  • Page 256: Source:abspower

    6.3 Command Reference 6.3.3.6 SOURce:ABSPOWer? Function Returns the current absolute power in dBm for the given signal type and orbit type. Command Syntax SOURce:ABSPOWer?<signal name>,[<orbit type name>,]<power> Examples SEND: SOUR:ABSPOW? GLOL1 Returns power for GLONASS L1 SOUR:ABSPOW? BDSB1,GEO Returns power for BEIDOU B1 on geostationary orbit 6.3.3.7 SOURce:RELPOWer Function...

  • Page 257: Source:relpower

    6.3 Command Reference Examples SEND: SOUR:RELPOWer BDSB1,GEO,-123.2 SOURce:RELPOWer all,default This command will reset the relative power offsets to their default values. The ref- erence power, however, WILL NOT be changed (to change the reference power level also, use the command SOUR:ABSPOW all, default instead.) 6.3.3.8 SOURce:RELPOWer? Function...

  • Page 258: Source:extref

    6.3 Command Reference Example SEND: SOURce:EXTREF ON 6.3.3.10 SOURce:EXTREF? Function Get the currently selected clock source. Command Syntax SOURce:EXTREF? Example SEND: SOURce:EXTREF? READ: 6.3.3.11 SOURce:PPSOUTput Function Sets the PPS (pulses-per-second) output of the device. Command Syntax SOURce:PPSOUTput <value> Note This feature is not available on GSG-52. Parameter value = 1, 10, 100, 1000 pulses per second User Manual GSG-5/6 Series Rev.

  • Page 259: Source:ppsoutput

    6.3 Command Reference Example SEND: SOURce:PPSOUTput 10 6.3.3.12 SOURce:PPSOUTput? Function Get the current PPS output setting. Command Syntax SOURce:PPSOUTput? Note This feature is not available on GSG-52. Example SEND: SOURce:PPSOUT? READ: 6.3.3.13 SOURce:EXTATT Function Set the external attenuation of the device. Command Syntax SOURce:EXTATT <decimal>...

  • Page 260: Source:extatt

    6.3 Command Reference If the value is inside allowed limits, but other RF parameters need to be modified, they are modified and an error about settings conflict is set. Parameter decimal = [0,30] in dB Example SEND: SOURce:EXTATT 12.2 6.3.3.14 SOURce:EXTATT? Function Query the current external attenuation setting of the unit.

  • Page 261: Source:noise:control

    6.3 Command Reference Note Setting not stored during scenario or 1-channel mode execution. Parameter enum = {ON, OFF} Example SEND: SOURce:NOISE:CONTrol ON 6.3.3.16 SOURce:NOISE:CONTrol? Function Get the noise simulation state. Command Syntax SOURce:NOISE:CONTrol? Example SEND: SOURce:NOISE:CONTrol? READ: 6.3.3.17 SOURce:NOISE:CNO Function Set the maximum carrier-to-noise density of the simulated signals.

  • Page 262: Source:noise:cno

    6.3 Command Reference Note Setting not stored during scenario or 1-channel mode execution. The actual C/N of individual signals may be lower than this setting due to various reasons (distance, elevation, modified by event, etc). Parameter in dB·Hz. A decimal number, within the range [0.0 … 56.0]. Example SEND: SOURce:NOISE:CNO 44.1...

  • Page 263: Source:noise:bw

    6.3 Command Reference Command Syntax SOURce:NOISE:BW <decimal> Note Setting not stored during scenario execution or 1-channel mode execution. This command is only available with GSG-55 units. Parameter Noise simulation bandwidth in MHz:, Decimal number in range [0.001 … 20.46]. Example SEND: SOURce:NOISE:BW 18.001 6.3.3.20 SOURce:NOISE:BW?

  • Page 264: Source:noise:offset

    6.3 Command Reference 6.3.3.21 SOURce:NOISE:OFFSET Function Set the frequency offset of the simulated noise from the GPS L1 center frequency (1.57542 GHz). For example, if the noise bandwidth is set to be 20 MHz, and offset is 10 MHz, the noise will be simulated on frequency band 1575.42 …...

  • Page 265: Source:onechn:control

    6.3 Command Reference READ: -8.2 6.3.3.23 SOURce:ONECHN:CONTrol Function Control the execution of the Signal Generator. Command Syntax SOURce:ONECHN:CONTrol <START|STOP|ARM> Parameter enum {START,STOP,ARM} Example SEND: SOURce:ONECHN:CONTrol start 6.3.3.24 SOURce:ONECHN:CONTrol? Function Query the current state of the Signal Generator. Meaning of returned values is the fol- lowing: START: Signal Generator is started and running STOP: Signal Generator is stopped and thus not running...

  • Page 266: Source:onechn:satid

    6.3 Command Reference Returned values START, STOP, WAIT, ARMED or ARMING Example SEND: SOURce:ONECHN:CONTrol? READ: START 6.3.3.25 SOURce:ONECHN:SATid Function During RF generation , modify the current signal mode. While GSG is not generating RF, set & store the 1-channel mode satellite identifier and signal mode. While GSG is not generating RF, modify the current signal mode.
  • Page 267 6.3 Command Reference ‘G’ (or ‘g’) for GPS ‘R’ (or ‘r’) for GLONASS ‘E’ (or ‘e’) for Galileo 'C' (or 'c') for BeiDou ‘J’ (or ‘j’) for QZSS 'I' (or 'i') for IRNSS ‘S’ (or ‘s’) for SBAS The signal_mode_letter parameter can be: ‘U’...

  • Page 268: Source:onechn:satid

    6.3 Command Reference signal mode used when the signal generator was started. For example, if the signal gen- erator is started in PRN mode it is possible to switch to unmodulated mode and back to PRN mode, but not to modulated mode. If started in modulated mode it is possible to switch between all three signal modes.
  • Page 269 6.3 Command Reference Exx for Galileo, for example E01 Cxx for BeiDou, for example C11 Jxx for QZSS, for example J02 Ixx for IRNSS, for example I01 Sxxx for SBAS, for example S120 UG for unmodulated GPS signal UE for unmodulated Galileo signal UC for unmodulated BeiDou UJ for unmodulated QZSS UI for unmodulated IRNSS...

  • Page 270: Source:onechn:starttime

    6.3 Command Reference G5,R5 6.3.3.27 SOURce:ONECHN:STARTtime Function Set & store 1-channel mode start time (use this command only while the unit is not gen- erating any RF). Command Syntax SOURce:ONECHN:STARTtime <string> Note Seconds are omitted, always starts at 0 seconds. Parameter String of format DD/MM/YYYY hh:mm, where: DD=day, MM=month, YYYY=year, hh=hour, mm=minutes...

  • Page 271: Source:onechn:ephemeris

    6.3 Command Reference 23/11/2010 12:45 6.3.3.29 SOURce:ONECHN:EPHemeris Function Set & store 1-channel mode ephemeris files to be used (use this command only while the unit is not generating any RF). Ephemeris files may include RINEX v2 or newer navigation message files for GPS and/or GLONASS, “agl”...

  • Page 272: Source:onechn:frequency

    6.3 Command Reference READ: Default 6.3.3.31 SOURce:ONECHN:FREQuency Function Set & store 1-channel mode frequency offset (use this command only while the unit is not generating any RF). Parameter can also have optional suffix (MHz, kHz or Hz). Command Syntax SOURce:ONECHN:FREQuency <decimal> Parameter decimal [-6000000, 6000000] in Hz Example...

  • Page 273: Source:onechn:signaltype

    6.3 Command Reference SOURce:ONECHN:FREQuency? READ: 4.345 6.3.3.33 SOURce:ONECHN:SIGNALtype Function Sets signal(s) to be simulated (use this command only while the unit is not generating any RF). Signal type consists of comma separated list of signal names, as described under “Para- meters”...

  • Page 274: Source:onechn:signaltype

    6.3 Command Reference SOURce:ONECHN:SIGNALtype GPSL1CA,GLOL2 6.3.3.34 SOURce:ONECHN:SIGNALtype? Function Query 1-channel signal type in use. Signal type consists of comma-separated list of the sim- ulated signals. Command Syntax SOURce:ONECHN:SIGNALtype? Example SEND: SOURce:ONECHN:SIGNALtype? READ: GPS L1CA,GPSL2P SEND: SOURce:ONECHN:SIGNALtype? READ: GPS L1CA,GLOL1,GALE1,BDSB1,QZSSL1CA,IRNSSL5 6.3.3.35 SOURce:ONECHN:LOSDynamics:SETtings Function Set the line of sight dynamics parameters for the Signal Generator.
  • Page 275 6.3 Command Reference Parameters <J> – absolute jerk value in m/s³ <A> – maximum absolute acceleration value in m/s² <D > – duration of movement with constant acceleration, positive value, in seconds; <D > – duration of movement with constant velocity D , positive value, in seconds Introduction to line of sight dynamics profile This feature supports the simulation of line of sight (LOS) dynamics (velocity profile).

  • Page 276: Source:onechn:losdynamics:settings

    6.3 Command Reference Example SEND: SOURce:ONECHN:LOSD:SET 0.005, 0.1, 20, 20 Figure 6-1: Jerk [m/s³], acceleration [m/s²], velocity [m/s], and range [m] over time [s] 6.3.3.36 SOURce:ONECHN:LOSDynamics:SETtings? Function Queries the line of sight dynamics profile parameters previously set by the SOURce:ONECHN:LOSDynamics:SETtings command. User Manual GSG-5/6 Series Rev.

  • Page 277: Source:onechn:losdynamics:control

    6.3 Command Reference Command Syntax SOURce:ONECHN:LOSDynamics:SETtings? Example SEND: SOURce:ONECHN:LOSD:SET? READ: 0.005,0.1,20,2 6.3.3.37 SOURce:ONECHN:LOSDynamics:CONTrol Function Starts, restarts or stops the line of sight dynamics profile. This command can only be used while RF is generated. Before starting the profile its parameters must be set using the SOURce:ONECHN:LOSDynamics:SETtings command.

  • Page 278: Source:onechn:losdynamics:control

    6.3 Command Reference 6.3.3.38 SOURce:ONECHN:LOSDynamics:CONTrol? Function Queries the current status of the line of sight dynamics profile, i.e. whether it is running (active) or not. Command Syntax SOURce:ONECHN:LOSDynamics:CONTrol? Return values <START> – the profile is currently active <STOP> – the profile is not active Example SEND: SOUR:ONECHN:LOSD:CONT?

  • Page 279: Source:scenario:load

    6.3 Command Reference Example SEND: SOURce:SCENario:LOAD scen01.scen 6.3.3.40 SOURce:SCENario:LOAD? Function Query the current loaded scenario. Command Syntax SOURce:SCENario:LOAD? Example SEND: SOURce:SCENario:LOAD? READ: scen01.scen 6.3.3.41 SOURce:SCENario:CONTrol Function Control the execution of the scenario. Command Syntax SOURce:SCENario:CONTrol <START|STOP|HOLD|ARM> Notes The scenario must be loaded beforehand using SOURce:SCENario:LOAD. Calling a START command will first automatically stop any running scenarios.

  • Page 280: Source:scenario:control

    6.3 Command Reference Parameter enum {START,STOP,HOLD,ARM} Example SEND: SOURce:SCENario:CONTrol start 6.3.3.42 SOURce:SCENario:CONTrol? Function Query the current state of scenario execution. Meaning of returned values is the following: START: scenario is started and running STOP: scenario is stopped and thus not running HOLD: scenario is running, but the trajectory is on hold WAIT: scenario delays startup for 2 minutes to allow the simulation to load required data.

  • Page 281: Source:scenario:propenv

    6.3 Command Reference 6.3.3.43 SOURce:SCENario:PROPenv Function Sets built-in propagation environment model. The parameters sky_limit, obstruction_limit and nlos_probability are optional, either all of them or none should be set. Notes: The scenario must be running. Note that 0<= obstruction_limit <= sky_limit <=90. For additional information, see "Propagation Environment Models"...

  • Page 282: Source:scenario:log

    6.3 Command Reference Command Syntax SOURce:SCENario:PROPenv? Example SEND: SOURce:SCENario:PROPenv? READ: suburban,50,30,0.2 6.3.3.45 SOURce:SCENario:LOG? Function Get current position as NMEA data, available only when scenario is running. Command Syntax SOURce:SCENario:LOG? Example SEND: SOURce:SCENario:LOG? READ: $GPRMC,181810.000,A,6000.1041,N,2400.0553,E,019.4,284.9,060109,,*0B $GPGGA,181810.000,6000.1041,N,2400.0553,E,1,15,0.6,587.0,M,0.0,M,,,*0F $GPGSV,4,1,15,23,77.7,192.3,44,20,52.8,132.7,44,32,31.2,117.3,44,31,2- 4.6,44.0,44*00 $GPGSV,4,2,15,16,9.2,96.3,44,7,1.1,190.7,44,17,0.5,242.4,44,2,17.4,31- 9.9,44*00 $GPGSV,4,3,15,30,6.3,1.2,44,4,46.0,280.1,44,13,51.5,230.8,44,25,19.6,- 184.5,44*2A $GPGSV,4,4,15,126,22.0,178.8,44,124,21.9,182.9,44,120,14.3,223.6,44*E4 User Manual GSG-5/6 Series Rev.

  • Page 283: Source:scenario:advlog

    6.3 Command Reference 6.3.3.46 SOURce:SCENario:ADVLOG? Function The Advanced Log feature queries log records of the specified log. This feature is effect- ive as of firmware version 6.7.1. The following logs can be queried: log – contains realtime movement parameters of the object being modelled along with time information;...
  • Page 284 6.3 Command Reference General response structure A response to an advanced log command usually contains several lines of text, with each line containing several comma-separated fields. The order of these fields corresponds with the labels order in response to a SOURce:SCENario:ADVLOG:HEADER? query. Each line of the response is terminated with the line end symbol “\n”...

  • Page 285: Source:scenario:advlog:header

    6.3 Command Reference sour:scen:advlog? sat READ: 17803, SAT, 17803.0, 2014-05-09T19:56:26.000, 503803.0, G9, 13999325.9529469125, -21451840.2281696014, -7614347.5806083838, 23965993.35, -269.19, 1414.63, -0.37 6.3.3.47 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:SCENari- o:ADVLOG?, and allows to get a line of comma-separated labels for fields of corresponding log records.
  • Page 286 6.3 Command Reference Field label (in response to a Possible field values (in response to a Field meaning “SOURce:SCENario: “SOURce:SCENario:ADVLOG?” query) ADVLOG:HEADer?” query) Record numeric id Integer in range [0; 65535] Log identifier Always RSG record_type Record type ANTENNA or BODY_CENTER time Scenario time in Non-negative decimal...
  • Page 287 6.3 Command Reference Field label (in response to a Possible field values (in response to a Field meaning “SOURce:SCENario: “SOURce:SCENario:ADVLOG?” query) ADVLOG:HEADer?” query) vel_y Speed ECEF Y-pro- Decimal jection, m/s vel_z Speed ECEF Z-pro- Decimal jection, m/s acc_x Acceleration ECEF Decimal X-projection, m/s acc_y...
  • Page 288 6.3 Command Reference Field label Possible field values (in response to a (in response to a “SOURce:SCENario: Field meaning “SOURce:SCENario:ADVLOG?” ADVLOG:HEADer?” query) query) 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...
  • Page 289 6.3 Command Reference Field label (in response to a Possible field values Field “SOURce:SC- (in response to a mean- ENario: “SOURce:SCENario:ADVLOG?” ADVLOG:HEA- query) Der?” query) signal_type Signal For GPS satellites: L1CA, L1P, L1CAP, L2P; “L1CAP” is used when the satel- type of lite has both L1CA and L1P signals enabled.

  • Page 290: Source:scenario:observation

    6.3 Command Reference 6.3.3.48 SOURce:SCENario:OBServation Function Turn on scenario observations. All parameters are seconds. Start is the number of seconds from scenario start. Duration is length of observations from start. Interval is the interval between the individual observations in the resulting Rinex OBS file. Observations files are created in observations/ with name <scenarioName>...

  • Page 291: Source:scenario:nav

    6.3 Command Reference Example SEND: SOURce:SCENario:OBS? READ: 10,3600,1 6.3.3.50 SOURce:SCENario:NAV Function Turn ON/OFF RINEX navigation data logging. The generated files are in RINEX 3.0.2 mixed format, so the information for all the sim- ulated constellations/satellites will be written into one file. Note that the RINEX data is logged only when the GSG generates new navigation message sets, which is not done often.

  • Page 292: Source:scenario:satid[N]

    6.3 Command Reference Command Syntax SOURce:SCENario:NAV? Example SEND: SOURce:SCENario:NAV? READ: 6.3.3.52 SOURce:SCENario:SATid[n]? Function Query the current satellite identifier of channel n. The parameter n can be 1-5 for GSG- 52/53, 1-8 for GSG-54, 1-16 for GSG-55/GSG-56 and 1-32/48/64 for GSG-62/63/64. The returned satellite identifier can be: Gxx for GPS for example G12 Rxx for GLONASS, for example R15...

  • Page 293: Source:scenario:signaltype[N]

    6.3 Command Reference Command Syntax SOURce:SCENario:SATid[n]? Note Only available during scenario execution. Example SEND: SOURce:SCENario:SATid5? READ: 123.4,R23 6.3.3.53 SOURce:SCENario:SIGNALtype[n]? Function Query signal type of satellite. The parameter can be: 1-5 for GSG-52/53 1-8 for GSG-54 1-16 for GSG-55/GSG-56 and 1-32/48/64 for GSG-62/63/64. The signal type consists of a comma-separated list of frequency bands and codes (CA or P code) for GPS and frequency bands for GLONASS, Galileo, BeiDou, QZSS and IRNSS.

  • Page 294: Source:scenario:signaltype

    6.3 Command Reference 6.3.3.54 SOURce:SCENario:SIGNALtype? Function Query the signal satellite types in the form of comma-separated values. Command Syntax SOURce:SCENario:SIGNALtype? <satID> Parameter satID – The format is explained under "SOURce:ONECHN:SATid?" on page 252. Example SEND: SOURce:SCENario:SIGNALtype? G2 READ: GPSL1CA,GPSL2P 6.3.3.55 SOURce:SCENario:NAVBITS Function Sets bits in a navigation message.
  • Page 295 6.3 Command Reference Parameter satID – GPS, Glonass, BeiDou, QZSS and SBAS are supported, the format is explained under "SOURce:ONECHN:SATid?" on page 252. sigtype – One of the signal types supported by the satellite, allowed values are: For GPS: L1CA, GPSL1CA, L1P, GPSL1P, L1PY, GPSL1PY, L1CAP, GPSL1CAP, L1CAPY, GPSL1CAPY, L2P, GPSL2P, L2PY, GPSL2PY, L2C, GPSL2C, L5, GPSL5 Note: The signal types from the same group below share the same...
  • Page 296 6.3 Command Reference For SBAS: message type, where 0 means that the modification is applied on the next message independently of its type pageid – For GPS L1 and L2P signals: page id and 0 (not relevant) when subframe id is 1-3 For GPS L2C and L5 signals: 0 (not relevant) For Glonass: string id For Galileo E1 and E5b signals: 0/1 (even/odd)

  • Page 297: Source:scenario:frequency[N]

    6.3 Command Reference 06/10/2013 15:00:24 GPS GPS 23 L1CA repeat 1 sfid 1 pgid 0: 8b0c98374923e24b4108008aaaaab- f5555550d5555543ffff2b31048ca1600ffe3b780634a8 Set all bits to 0 in subframe 3 of GPS L1CA message: sour:scen:navbits IMM,G23,L1CA,3,0,1,300,0,0,0 Set bits 16-119 to 1 in the next QZSS L1SAIF message from satellite J3: sour:scen:navbits IMM,J3,L1SAIF,0,2,16,119,FF,0,1 6.3.3.56 SOURce:SCENario:FREQuency[n]? Function...

  • Page 298: Source:scenario:power[N]

    6.3 Command Reference Command Syntax SOURce:SCENario:FREQuency? <satID> Note Only available during scenario execution. Parameter For a list of satID satellite identifiers, see "SOURce:ONECHN:SATid?" on page 252. Example SEND: SOURce:SCENario:FREQuency? G32 READ: 123.4,-480.513 6.3.3.58 SOURce:SCENario:POWer[n] Function Sets the absolute power of channel or switch power ON or OFF when the scenario is run- ning.

  • Page 299: Source:scenario:power[N]

    6.3 Command Reference SOURce:SCENario:POWer[n] ON|OFF Note Only available during scenario execution. Parameters Decimal [-160.0,-65.0] dBm, if freqband is not ALL. For ALL, the relative change by which the power setting is to be modified, should be limited to a delta of 100 (e.g., chan- ging a power of -65 dBm to -165 dBm (by -100) and vice versa (+100).

  • Page 300: Source:scenario:power

    6.3 Command Reference If the freqband parameter is omitted, the L1 power is returned. Command Syntax SOURce:SCENario:POWer[n]? [<freqband>] Note Only available during scenario execution. Parameter FreqBand [L1, L2, L5, ALL] Example SOUR:SCEN:POWer3? Returns power of channel #3 Example return value: 123.4, -119.7 SOUR:SCEN:POWer2? L5 Returns L5 power of channel #2 Example return value: 123.4, -119.7...
  • Page 301 6.3 Command Reference SOURce:SCENario:POWer <SatSystem>,<decimal>[,<freqband>] Note Only available during scenario execution. Parameter Decimal [-160.0,-65.0] dBm, if freqband is not ALL. For ALL, the relative change by which the power setting is to be modified, should be limited to a delta of 100 (e.g., chan- ging a power of -65 dBm to -165 dBm (by -100) and vice-versa (+100).

  • Page 302: Source:scenario:power

    6.3 Command Reference 6.3.3.61 SOURce:SCENario:POWer? Function Query the current power setting of the satellite satID during scenario execution. The power is returned with a leading timestamp. Freqband is an optional parameter used to specify the frequency band whose power is returned. If freqband is omitted, the L1 power is returned.

  • Page 303: Source:scenario:freqband:power

    6.3 Command Reference 6.3.3.62 SOURce:SCENario:FREQBAND:POWer Function Set the power for a frequency band (all satellites) when scenario is running. Freqband used to specify the frequency band. The freqband value ALL means that the power for all bands is adjusted by the amount indicated. Command Syntax SOURce:SCENario:FREQBAND:POWer <decimal>[,<freqband>] Note...

  • Page 304: Source:scenario:svmodel[N]

    6.3 Command Reference Parameter Decimal [-160.0,-65.0] dBm, if freqband is not ALL. For ALL, the limits are [-100,100] dB. For a list of satID satellite identifiers, see "SOURce:ONECHN:SATid?" on page 252. Example SEND: SOURce:SCENario:SVmodel? G11 READ: Block IIR-M 6.3.3.64 SOURce:SCENario:SVmodel[n]? Function Query the satellite’s Space Vehicle model.

  • Page 305: Source:scenario:list

    6.3 Command Reference 6.3.3.65 SOURce:SCENario:LIST? Function List possible models which can be used in the scenarios. Note that for ionomodels, the options are limited to ‘ON, OFF’. Command Syntax SOURce:SCENario:LIST? <antennamodels | tropomodels | ionomodels> Example SEND: SOURce:SCENario:LIST? antennamodels READ: Zero model, Helix, Patch, Cardioid 6.3.3.66 SOURce:SCENario:ANTennamodel Function...

  • Page 306: Source:scenario:tropomodel

    6.3 Command Reference Command Syntax SOURce:SCENario:ANTennamodel? Example SEND: SOURce:SCENario:ANTennamodel? READ: Zero model 6.3.3.68 SOURce:SCENario:TROPOmodel Function Set the tropospheric model for the current scenario. Command Syntax SOURce:SCENario:TROPOmodel <tropomodel> Example SEND: SOURce:SCENario:TROPOmodel Black model 6.3.3.69 SOURce:SCENario:TROPOmodel? Function Query the tropospheric model of the current scenario. Command Syntax SOURce:SCENario:TROPOmodel? Example...

  • Page 307: Source:scenario:ionomodel

    6.3 Command Reference SOURce:SCENario:TROPOmodel? READ: Saastamoinen 6.3.3.70 SOURce:SCENario:IONOmodel Function Select the ionospheric model to be used in the current scenario. Permitted values are ON and OFF. Command Syntax SOURce:SCENario:IONOmodel <ionomodel> 6.3.3.71 SOURce:SCENario:IONOmodel? Function Query whether the Ionospheric model is used in the current scenario. The command returns: ‘OFF’, if the ionospheric model is not used ‘ON’...

  • Page 308: Source:scenario:position

    6.3 Command Reference SOURce:SCENario:IONOmodel? READ: SEND: SOURce:SCENario:IONOmodel? READ: codg0010.14i,codg0030.14i,codg0020.14i 6.3.3.72 SOURce:SCENario:POSition Function Set latitude, longitude and altitude for the geodetic position (WGS84) as the start position for the loaded scenario, or the current position if the scenario is running. Latitude and longitude are defined using decimal degrees. The altitude is given in meters as altitude over an ellipsoid.

  • Page 309: Source:scenario:position

    6.3 Command Reference Notes If a scenario is armed but not running yet, an error is returned. The maximum altitude for normal operation is 18470 meters. (With Extended Limits it is 20,200 km). This command changes position of the currently loaded scenario, but does not change the scenario file, so that when you try to edit the scenario, you will see unchanged parameters from the file.

  • Page 310: Source:scenario:ecefposition

    6.3 Command Reference The X, Y, and Z position is given in decimal meters. The recommended decimal accuracy of ECEF is 2 decimal digits. No benefit for ECEF positions is achieved at accuracies greater than 4 digits. Command Syntax SOURce:SCENario:ECEFPOSition TIME,<decimal>,<decimal>,<decimal> Note If a scenario is armed and not running yet, an error is returned.

  • Page 311: Source:scenario:datetime

    6.3 Command Reference Example SEND: SOURce:SCENario:ECEFPOSition? READ: 0.0,2920791.72, 1300420.26, 5500650.33 6.3.3.76 SOURce:SCENario:DATEtime Function Set the scenario start time as GPS time. Command Syntax SOURce:SCENario:DATEtime <MM-DD-YYYY hh:mm | NTP> Note If scenario is running or armed, an error is returned. Parameter String format: MM-DD-YYYY hh:mm …where MM=Month {01-12}, DD=day of month {01-31}, YYYY=year, hh=hours {00-23},...

  • Page 312: Source:scenario:datetime

    6.3 Command Reference 6.3.3.77 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 para- meter 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.

  • Page 313: Source:scenario:runtime

    6.3 Command Reference 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 6.3.3.78 SOURce:SCENario:RUNtime? Function Query the current length of time in seconds elapsed since the start of RF signal gen- eration. The time is returned including 3 digits of sub-seconds. The accuracy is equivalent to the system's internal update rate.

  • Page 314: Source:scenario:elapsedtime

    6.3 Command Reference 6.3.3.79 SOURce:SCENario:ELAPsedtime? Function Query the time of a scenario elapsed since the start of RF signal generation. The time returned is in units of days, hours, minutes, seconds, and 3 digits of sub-seconds. The accur- acy is equivalent to the system's internal update rate. Command Syntax SOURce:SCENario:ELAPsedtime? Notes...

  • Page 315: Source:scenario:rtcmcfg

    6.3 Command Reference Example (1006 message type read) SEND: SOURce:SCENario:RTCM? READ: D300153EE001038519731F728933157AC40A72ABE4310000061AC0 6.3.3.81 SOURce:SCENario:RTCMCFG? Function Queries the current RTCM configuration for output. Returns comma separated RTCM version (i.e., 3x or 2x), followed by the selected message types. Command Syntax SOURce:SCENario:RTCMCFG? Example SEND: SOURce:SCENario:RTCMCFG?

  • Page 316: Source:scenario:rlm

    6.3 Command Reference Parameter string - 1002, 1004, 1006, 1010, 1012 and 1033. Example SEND: SOURce:SCENario:RTCMCFG 3x,1004,1006 6.3.3.83 SOURce:SCENario:RLM Function This command supports the Galileo Return Link Acknowledgement Service by sending out Return Link Message to a user in distress, thereby informing him that his distress signal has been detected and located.
  • Page 317 6.3 Command Reference For additional information, see the Galileo Open Service Signal in Space Interface Control Document Examples Short RLM SOURce:SCENario:RLM 0,satid,int1,int2,int3,int4 Satid = Galileo satellite in view in running scenario Int1,int2,int3 – beacon id – 3x20bits converted to decimal 15 HEX ID ->...

  • Page 318: Source:scenario:duplicate

    6.3 Command Reference Long RLM SOURce:SCENario:RLM 1,satid,int1,int2,int3,int4,int5,int6,int7,int8 Satiid = Galileo satellite in view in running scneario Int1,int2,int3: Beacon ID – 3 x 20 bits convertd to decimal 15 HEX ID -> 60 binary bits (3 x 20) –> each 20 bit binary converted to decimal Int 4-8: 4bit message ID, 96 bit parameter data SOUR:SCEN:RLM 1,8,711888,141509,1025,983040,1048575,1048575,1048575,1- 048575...

  • Page 319: Source:scenario:duplicate[N]

    6.3 Command Reference Command Syntax SOURce:SCENario:DUPlicate <TIME>,<satID>,<decimal>,<decimal>, <decim- al>,<decimal>,<decimal>,<integer>,<decimal>,<decimal>, <integer>[,<sa- tID>] Parameter TIME – As TIME argument only IMMediate is supported. satID – Satellite identifier of the satellite to duplicate Decimal [-999.999,999.999] – Range offset in meters Decimal [-99.999,99.999] – Range Change rate in meters/interval Decimal [0.0,600.0] –...
  • Page 320 6.3 Command Reference Notes Multipath satellites require 60 seconds to be created and are introduced at modulo 30 second intervals. The GSG can only introduce 4 duplicate satellites at a time and at a max- imum rate of one satellite every two seconds. Multipath, SBAS and interference/jamming channels cannot be the duplicated.

  • Page 321: Source:scenario:duplicate

    6.3 Command Reference Example SEND: SOURce:SCENario:DUPlicate9 IMM,3,1.0,2.0,0.0,4.0,5.0,6,7.0,-8.0,9 6.3.3.86 SOURce:SCENario:DUPlicate? Function The command returns a comma delimited list of the channel numbers which are duplicates of the satID given. Command Syntax SOURce:SCENario:DUPlicate? <satID> Parameter satID – For a list of satellite identifiers, see "SOURce:ONECHN:SATid?"...

  • Page 322: Source:scenario:duration

    6.3 Command Reference <mode> could be ONCE/FOREVER/LOOPING. If only <duration> is given, then <mode> is ONCE by default. If <mode> is FOREVER, <duration> cannot be specified. Notes This command changes duration of the currently loaded scenario, but does not change the scenario file, so that when you try to edit the scenario, you will see unchanged parameters from the file.

  • Page 323: Source:scenario:multipath[N]

    6.3 Command Reference RESPONSE: LOOPING,1800 6.3.3.89 SOURce:SCENario:MULtipath[n] Function This command sets the multipath parameters for satellite with a satID. The parameters include the Range Offset, Range Change, Range Interval, Doppler Offset, Doppler Change, Doppler Interval, Power Offset, Power Change and Power Interval. After issuing the command the target satellite becomes a multipath satellite and this is reflected in the satID as multipath satellites have a trailing character ‘D’...

  • Page 324: Source:scenario:multipath[N]

    6.3 Command Reference Decimal [-999.0,999.0] – Range offset in meters Decimal [-99.0,99.0] – Range Change rate in meters/interval Decimal [0.0,600.0] – Range Interval in seconds Decimal [-99.0,99.0] – Doppler offset in meters Decimal [-99.0,99.0] – Doppler Change rate in meters/sec/interval Integer [0,600] –...

  • Page 325: Source:scenario:delete[N]

    6.3 Command Reference Parameter Integer [1:N] – Maximum is number of defined multipath satellite channels satID – the satellite identifier of the satellite Example Before execution: SEND: SOURce:SCENario:MULtipath1? READ: 3,1.0,2.0,3,4.0,5.0,6,7.0,-8.0,9 During execution: SEND: SOURce:SCENario:MULtipath? G17 READ: G17D,1.0,2.0,3,4.0,5.0,6,7.0,-8.0,9 6.3.3.91 SOURce:SCENario:DELete[n] <TIME> Function This command deletes the satellite at channel n.

  • Page 326: Source:scenario:delete

    6.3 Command Reference Example SEND: SOURce:SCENario:DELete17 IMM 6.3.3.92 SOURce:SCENario:DELete <TIME>,<satID>[,<satID>] Function This command deletes the comma-delimited list of satellites. Command Syntax SOURce:SCENario:DELete <TIME>,<satID>[,<satID>] … Note Command is allowed only during scenario execution. SBAS and interference channels can- not be deleted. Only one satellite with the same satID string can be deleted at a time. Satel- lites which are still valid in the constellation will be restarted 1-2 minutes after deletion.

  • Page 327: Source:scenario:clkmdl

    6.3 Command Reference Note Command is allowed only during scenario execution. SBAS and interference/jamming channels cannot be deleted. Parameter TIME – As TIME argument only IMMediate is supported. satID – Satellite identifier string. Example SEND: SOURce:SCENario:DELete2 IMM,G10D 6.3.3.94 SOURce:SCENario:CLKMDL Note: This SCPI command is only supported if the Spoofing Range Option is installed (OPT-SPF license, see "GSG Series Model Variants and Options"...

  • Page 328: Source:scenario:clkmdl

    6.3 Command Reference Parameter Unit Range Description ±10000 Clock bias measured at t ±100 Clock drift at t m/s² ±10 Rate of clock drift. At the time t, the clock offset is then calculated as follows: = t – t Δ...

  • Page 329: Source:file:type

    6.3 Command Reference Example SOURce:SCENario:clkmdl? Return Format 2.010000E+01,1.899000E+03,1.000000E+01,2.000000E+03,- 1.000000E+01,0.000000E+00 6.3.3.96 SOURce:FILe:TYPe Function This commands are used to transfer a file to the unit. The order of commands is fixed: Type, name, length checksum and data. SOURce:FILe:TYPe sets the type of the file transferred. Valid files types are: CALibration FIRMware...

  • Page 330: Source:file:name

    6.3 Command Reference 6.3.3.97 SOURce:FILe:NAMe Function This command sends the file name to be used to store the file to the unit. The name shall only contain alphanumeric characters. Command Syntax SOURce:FILe:NAMe Note Command not allowed during scenario execution, and will result in the error code “- 190,"Execution in progress"”.

  • Page 331: Source:file:data

    6.3 Command Reference Note This command not allowed during scenario execution, and will result in the error code “- 190,"Execution in progress"”. The checksum is calculated using the following algorithm, presented here in a Python lan- guage example. The array s passed in must be read from a file opened with attributes read and binary (rb).

  • Page 332: Source:keylock:password

    6.3 Command Reference line characters cannot be identified from the text below. A space must separate the DATA command from the “#” character. This command not allowed during scenario execution, and will result in the error code “- 190,"Execution in progress"”. Example Sending a scenario file to the unit: SEND:...

  • Page 333: Source:keylock:password

    6.3 Command Reference Command Syntax SOURce:KEYLOCK:PASSWord <password> Parameter 4-8 numerical characters. Example SEND: SOURce:KEYLOCK:PASSWord 123456 6.3.3.102 SOURce:KEYLOCK:PASSWord? Function Queries the current password used in front panel lock. Command Syntax SOURce:KEYLOCK:PASSWord? Example SEND: SOURce:KEYLOCK:PASSWord? READ: 123456 6.3.3.103 SOURce:KEYLOCK:STATus Function Sets the state of the front panel lock. Command Syntax SOURce:KEYLOCK:STATus <ON|OFF>...

  • Page 334: Source:keylock:status

    6.3 Command Reference Parameter enum = {ON, OFF} Example SEND: SOURce:KEYLOCK:STATus ON 6.3.3.104 SOURce:KEYLOCK:STATus? Function Queries the state of the front panel lock. Command Syntax SOURce:KEYLOCK:STATus? Example SEND: SOURce:KEYLOCK:STATus? READ: 6.3.4 Mass Memory Subsystem Commands All Mass Memory Subsystem commands and queries are not allowed during scenario exe- “-190,"Execution in progress"”...

  • Page 335: Mmemory:cdirectory

    6.3 Command Reference Command Syntax MMEMory:CATalog? <dirname> Example SEND: MMEMory:CATalog? events READ: 3145728,72351744,AGPS1e,ASCII,208,AGPS2e,ASCII,110,AGPS3e, ASCII,208,EventAGPS1,ASCII,59,EventAGPS2,ASCII,29,EventAGPS3, ASCII,29,EventAGPS4,ASCII,180,EventAGPS5,ASCII,250,EventAGPS6, ASCII,29,event0,ASCII,146,event007,ASCII,146,event01,ASCII, 1,eventAGPS1,ASCII,61,eventAGPS2,ASCII,30,eventAGPS3,ASCII, 30,eventAGPS4,ASCII,186,eventAGPS5,ASCII,256,eventAGPS6, ASCII,30,events1,ASCII,874,events2,ASCII,384,events3, ASCII,122 6.3.4.2 MMEMory:CDIRectory Function Change current directory on the device. The <dirname> must be/start with nav- igationData, events, trajectories or scenarios. Command Syntax MMEMory:CDIRectory <dirname>...

  • Page 336: Mmemory:data

    6.3 Command Reference Command Syntax MMEMory:CDIRectory? Example SEND: MMEMory:CDIRectory? READ: events 6.3.4.4 MMEMory:DATA? Function Get contents of file. At the start of the response is the header e.g., #800001234, con- taining the information about the length of the file. The first digit after “#” symbol tells how many next symbols are used to encode the file size.

  • Page 337: Mmemory:delete

    6.3 Command Reference UserTrajectory Circle TrajectoryParameters 400 10 -1 AntennaModel Zero model IonoModel 1 TropoModel Saastamoinen Temperature 15 Pressure 1100 Humidity 50 MinElev 0 NrSBASChannels 2 6.3.4.5 MMEMory:DELete Function Delete a file in device. If <dirname> is omitted, file is assumed to be in current directory oth- erwise the file is deleted from <dirname>.

  • Page 338: Mmemory:move

    6.3 Command Reference 6.3.4.7 MMEMory:MOVE Function Move a file in current directory or directory <srcdir>. Note that moving between dir- ectories is forbidden, so <srcdir> must be equal to <dstdir>. Command Syntax MMEMory:MOVE <srcfile>[,<srcdir>],<dstfile>[,<dstdir>] Example SEND: MMEMory:MOVE scen02,scenarios,scen022,scenarios 6.3.5 Network Subsystem Commands 6.3.5.1 NETwork:MACaddress? Function...

  • Page 339: Status: Subsystem Commands

    6.3 Command Reference 6.3.6 STATus: Subsystem Commands 6.3.6.1 STATus:OPERation:CONDition? Function Reads out the contents of the operation status condition register. This register reflects the state of the GSG operation. Command Syntax STATus:OPERation:CONDition? Returned Format <Decimal data> = the sum (between 0 and 97) of all bits that are true. See table below: Bit Weight Condition Waiting for bus arming...

  • Page 340: Status:operation[:Event]

    6.3 Command Reference Bit Weight Condition Waiting for bus arming Waiting for triggering and / or external arming Returned Format <Decimal data> Example SEND: STAT:OPER:ENAB 32 In this example, waiting for triggering, bit 5, will set the OPR-bit of the Status Byte. 6.3.6.3 STATus:OPERation[:EVENt]? Function...

  • Page 341: Status:questionable:enable

    6.3 Command Reference Bit Weight Condition 16384 Unexpected command parameter 6.3.6.5 STATus:QUEStionable:ENABle Function Enable the Questionable Data/Signal Status Reporting by setting the enable bits of the status questionable enable register. This enable register contains a mask value for the bits to be enabled in the status ques- tionable event register.

  • Page 342: Status:preset

    6.3 Command Reference Command Syntax STATus:QUEStionable[:EVENt]? Returned Format <decimal data> = the sum (between 0 and 16384) of all bits that are true. See the table for STATus:QUEStionable:CONDition 6.3.6.7 STATus:PRESet Function Enables Device Status Reporting. This command has an SCPI standardized effect on the status data structures.

  • Page 343: Sensors Command Reference

    6.4 Sensors Command Reference Sensors Command Reference As the GSG unit simulates a user’s movement along a given trajectory, it can also be con- figured to output sensor data generated by the user dynamics. The generated sensor out- put data is a result of the user exercising his six degrees of freedom: forward/backward left/right up/down , as well as the rotations around the three perpendicular axes:...

  • Page 344: Accelerometer

    6.4 Sensors Command Reference Sensor SENSOR_TYPE keyword Gyroscope GYRoscope Odometer ODOmeter 3D Odometer ODOMETER3D, ODO3D 6.4.1.1 Accelerometer The accelerometer outputs acceleration in the XYZ axis. The typical case where the device is flat relative to the surface of the Earth appears as -STANDARD_GRAVITY in the Z axis, and X and Y values as zero.

  • Page 345: Odometer

    6.4 Sensors Command Reference values[2] – Angular speed around the z-axis, in radians/second 6.4.1.5 Odometer The odometer sensor keeps track of the total traveled distance. Sensor data values[0] – Traveled distance in meters 6.4.1.6 Odometer 3D The 3D odometer sensor keeps track of the total traveled distance in a 3D ENU vector form.

  • Page 346: Source:scenario:sensor:register

    6.4 Sensors Command Reference 6.4.2.2 SOURce:SCENario:SENSor:REGister? Function Queries if a given sensor is registered. Command Syntax SOURce:SCENario:SENSor:REGister? <SENSORTYPE> 6.4.2.3 SOURce:SCENario:SENSor:UNREGister Function This command unregisters a sensor of a given type, after which the sensor data is no longer output. Command Syntax SOURce:SCENario:SENSor:UNREGister <SENSORTYPE>...

  • Page 347: Source:scenario:sensor:normalize? Sensor_Type

    6.4 Sensors Command Reference Command Syntax SOURce:SCENario:SENSor:NORMalize SENSOR_TYPE <ON|OFF> 6.4.2.6 SOURce:SCENario:SENSor:NORMalize? SENSOR_TYPE Function Queries if a sensor of a given type is normalized or not. Command Syntax SOURce:SCENario:SENSor:NORMalize? SENSOR_TYPE 6.4.2.7 SOURce:SCENario:SENSor:MAXrange SENSOR_TYPE Function The command specified the max range of a sensor. The minrange equals –maxrange. Command Syntax SOURce:SCENario:SENSor:MAXrange SENSOR_TYPE <decimal>...

  • Page 348: Rsg Command Reference

    6.5 RSG Command Reference RSG Command Reference 6.5.1 Data Types The Real-time Scenario Generation (RSG) commands transfer the data as ASCII strings. However, coordinate systems, units of measure, Earth Models, base data types and accur- acy limits are required to implement this in the software. These attributes and values are lis- ted in this section.

  • Page 349: Time Parameter

    6.5 RSG Command Reference Field Type Default Units Roll (phi) <DOUBLE > +/- radians Pitch Rate <DOUBLE > radians/sec Roll Rate <DOUBLE > radians/sec Yaw Rate <DOUBLE > radians/sec 6.5.2 TIME Parameter In all cases where the TIME parameter is allowed, it can be specified as: IMMediate, which indicates that the command is to be applied in REAL time <decimal>, indicating in seconds from Scenario start time when the information is to be applied when using uploaded Scenario/Trajectory files.

  • Page 350: Source:scenario:position

    6.5 RSG Command Reference Command Syntax SOURce:SCENario:POSition TIME,<decimal>,<decimal>,<decimal> Parameter TIME must be IMMediate. Decimal Latitude [-89.99999999, +89.99999999] degrees North Decimal Longitude [-360.00000000, +360.00000000] degrees East Decimal Altitude [-1000.00, +20,200,000.00] meters Notes If a scenario is armed but not running yet, an error is returned. The maximum altitude for normal operation is 18470 meters.

  • Page 351: Source:scenario:ecefposition Time

    6.5 RSG Command Reference SOURce:SCENario:POSition? READ: 123.4,-77.58895432,43.08332157,168.58 6.5.3.3 SOURce:SCENario:ECEFPOSition TIME Function Sets the ECEF position in X, Y and Z coordinates. The X, Y, and Z position is given in decimal meters. The decimal accuracy of ECEF is recommended as 2 decimal digits. No benefit is achieved for ECEF positions at accuracies greater than 4 digits.

  • Page 352: Source:scenario:speed Time

    6.5 RSG Command Reference Command Syntax SOURce:SCENario:ECEFPOSition? [<ANTenna|BODYcenter>] Example SEND: SOURce:SCENario:ECEFPOSition? READ: 123.4,2920791.72, 1300420.26, 5500650.33 6.5.3.5 SOURce:SCENario:SPEed TIME Function Sets the vehicle’s speed over ground (WGS84 ellipsoid). Command Syntax SOURce:SCENario:SPEed TIME,<decimal> Parameter Decimal 1D Speed [0.00 to +20000.00] m/s Note The maximum allowed speed for normal operation is 520 m/s.

  • Page 353: Source:scenario:heading Time

    6.5 RSG Command Reference Command Syntax SOURce:SCENario:SPEed? [<ANTenna|BODYcenter>] Example SEND: SOURce:SCENario:SPEed? READ: 123.4,30.10 6.5.3.7 SOURce:SCENario:HEADing TIME Function Sets the vehicle’s true heading. The heading is expressed in clockwise direction from the true north (WGS84 ellipsoid) representing 0 degrees, increasing to 359.999 degrees. Command Syntax SOURce:SCENario:HEADing TIME,<decimal>...

  • Page 354: Source:scenario:rateheading Time

    6.5 RSG Command Reference Example SEND: SOURce:SCENario:HEADing? READ: 123.4, 90.000 6.5.3.9 SOURce:SCENario:RATEHEading TIME Function Sets the heading change rate. Rate is expressed as degrees per second. Heading will be updated each epoch according to the specified constant rate. Next position is calculated using direct rhumb line method (movement with constant heading).

  • Page 355: Source:scenario:turnrate Time

    6.5 RSG Command Reference SOURce:SCENario:RATEHEading? READ: 123.4, 5.500 6.5.3.11 SOURce:SCENario:TURNRATE TIME Function Sets the rate of turning. Rate is expressed as degrees per second. Next position is cal- culated using direct orthodromic method (moving along shortest path with non-constant heading). Use this command to simulate movement along arc of circle or closed circle tra- jectory with constant velocity.

  • Page 356: Source:scenario:turnradius Time

    6.5 RSG Command Reference READ: 123.4, 5.500 6.5.3.13 SOURce:SCENario:TURNRADIUS TIME Function Sets the radius of turning. Radius is expressed in meters. The next position is calculated using direct orthodromic method (moving along shortest path with non-constant heading). Use this command to simulate movement along arc of circle regardless of velocity changes. Heading rate is varying each epoch, but radius of turning will be constantly equal to value specified.

  • Page 357: Source:scenario:velocity Time

    6.5 RSG Command Reference 6.5.3.15 SOURce:SCENario:VELocity TIME Function Sets the vehicle’s speed over ground (WGS84 ellipsoid) and heading in degrees. Command Syntax SOURce:SCENario:VELocity TIME,<decimal>,<decimal> Parameter Decimal 1D Speed [0.000 to +20000.000] m/s Decimal Bearing [0, 359.999] true bearing in decimal degrees Note The maximum allowed speed for normal operation is 520 m/s.

  • Page 358: Source:scenario:vspeed Time

    6.5 RSG Command Reference 6.5.3.17 SOURce:SCENario:VSPEed TIME Function Sets the vehicle’s vertical speed. Command Syntax SOURce:SCENario:VSPEed TIME,<decimal> Parameter Decimal 1D Speed [-20000.00 to +20000.00] m/s Note The maximum allowed speed for normal operation is 520 m/s. (For Extended Limits it is limited by interface above.) Example SEND:...

  • Page 359: Source:scenario:enuvelocity Time

    6.5 RSG Command Reference 6.5.3.19 SOURce:SCENario:ENUVELocity TIME Function Sets the velocity expressed in ENU coordinates when scenario is running. The Velocity terms are defined in m/s. Command Syntax SOURce:SCENario:ENUVELocity TIME,<decimal>,<decimal>,<decimal> Note The local plane of the coordinates will always be re-aligned with ellipsoid surface, meaning the Up-Down velocity can be seen as a velocity with respect to ellipsoid (and not the local plane formed by the position the user was at TIME).

  • Page 360: Source:scenario:ecefvelocity

    6.5 RSG Command Reference Example SEND: SOURce:SCENario:ENUVELocity? READ: 123.4,-4.00,3.00,0.00 6.5.3.21 SOURce:SCENario:ECEFVELocity Function Sets the current ECEF velocity in X, Y and Z coordinates when the scenario is running. The Velocity terms are defined in m/s. Command Syntax SOURce:SCENario:ECEFVELocity TIME,<decimal>,<decimal>,<decimal> Parameter Decimal Velocity X [-20000.00, +20000.00] m/s Decimal Velocity Y [-20000.00, +20000.00] m/s...

  • Page 361: Source:scenario:acceleration Time

    6.5 RSG Command Reference Command Syntax SOURce:SCENario:ECEFVELocity? [<ANTenna|BODYcenter>] Example SEND: SOURce:SCENario:ECEFVELocity? READ: 123.4,-4.00,3.00,1.00 6.5.3.23 SOURce:SCENario:ACCeleration TIME Function Sets the 1D acceleration expressed in m/s when scenario is running. Command Syntax SOURce:SCENario:ACCeleration TIME,<decimal> Parameter Decimal 1D Acceleration [-981 to +981] m/s , equivalent to [-100G to +100G] Example SEND:...

  • Page 362: Source:scenario:vaccel Time

    6.5 RSG Command Reference Example SEND: SOURce:SCENario:ACCeleration? READ: 123.4,0.50 6.5.3.25 SOURce:SCENario:VACCel TIME Function Sets the vehicle’s vertical acceleration. Command Syntax SOURce:SCENario:VACCel TIME,<decimal> Parameter Decimal 1D Acceleration [-981 to +981] m/s , equivalent to [-100G to +100G] Example SEND: SOURce:SCENario:VACCel 123.4,0.50 6.5.3.26 SOURce:SCENario:VACCel? Function Query the vehicle’s vertical acceleration.

  • Page 363: Source:scenario:enuaccel Time

    6.5 RSG Command Reference SOURce:SCENario:VACCel? READ: 123.4,0.50 6.5.3.27 SOURce:SCENario:ENUACCel TIME Function Sets the acceleration expressed in ENU coordinates when scenario is running. The accel- eration terms are defined in m/s Command Syntax SOURce:SCENario:ENUACCel TIME,<decimal>,<decimal>,<decimal> Note The local plane of the coordinates will always be re-aligned with ellipsoid surface, meaning the Up-Down velocity can be seen as a velocity with respect to ellipsoid (and not the local plane formed by the position the user was at TIME).

  • Page 364: Source:scenario:ecefaccel Time

    6.5 RSG Command Reference Command Syntax SOURce:SCENario:ENUACCel? [<ANTenna|BODYcenter>] Example SEND: SOURce:SCENario:ENUACCel? READ: 123.4,-2.83,2.83,0.00 6.5.3.29 SOURce:SCENario:ECEFACCel TIME Function Sets the ECEF acceleration in 3-dimensions as Acceleration X, Y, and Z when scenario is running. The Acceleration terms are defined in m/s Command Syntax SOURce:SCENario:ECEFACCel TIME,<decimal>,<decimal>,<decimal>...

  • Page 365: Source:scenario:ecefaccel

    6.5 RSG Command Reference 6.5.3.30 SOURce:SCENario:ECEFACCel? Function Queries the current ECEF acceleration in 3-dimensions as Acceleration X, Y, Z during scen- ario execution. Command Syntax SOURce:SCENario:ECEFACCel? [<ANTenna|BODYcenter>] Example SEND: SOURce:SCENario:ECEFACCeleration? READ: 123.4,-2.83,2.83,1.00 6.5.3.31 SOURce:SCENario:PRYattitude TIME Function Sets the Vehicle Attitude in 3-dimensions about the center of mass as Pitch, Roll, and Yaw when scenario is running.

  • Page 366: Source:scenario:pryattitude

    6.5 RSG Command Reference Example SEND: SOURce:SCENario:PRYattitude -2.0000,2.0000,1.0000 6.5.3.32 SOURce:SCENario:PRYattitude? Function Query the current Vehicle Attitude in 3-dimensions about the center of mass as Pitch, Roll, and Yaw during scenario execution. Command Syntax/Example SEND: SOURce:SCENario:PRYattitude? READ: 123.4,-2.0000,2.0000,1.0000 6.5.3.33 SOURce:SCENario:DPRYattitude TIME Function Sets the Vehicle Attitude in 3-dimensions about the center of mass as Pitch, Roll, and Yaw when scenario is running.

  • Page 367: Source:scenario:dpryattitude

    6.5 RSG Command Reference Decimal Yaw [-180, +180] Degrees Example SEND: SOURce:SCENario:DPRYattitude -2.0000,2.0000,1.0000 6.5.3.34 SOURce:SCENario:DPRYattitude? Function Queries the current Vehicle Attitude in 3-dimensions about the center of mass as Pitch, Roll, and Yaw during scenario execution. Returned values are defined in Degrees. Command Syntax SOURce:SCENario:DPRYattitude? Example...

  • Page 368: Source:scenario:pryrate

    6.5 RSG Command Reference Parameter Decimal Pitch Rate [-π, +π] Radians per second Decimal Roll Rate [-π, +π] Radians per second Decimal Yaw Rate [-π, +π] Radians per second Example SEND: SOURce:SCENario:PRYRate 123.4,-2.0000,2.0000,1.0000 6.5.3.36 SOURce:SCENario:PRYRate? Function Queries the current rate of change in Vehicle Attitude in 3-dimensions about the center of mass as Pitch, Roll, and Yaw during scenario execution.

  • Page 369: Source:scenario:dpryrate

    6.5 RSG Command Reference Parameter Decimal Pitch Rate [-3600, +3600] Degrees per second Decimal Roll Rate [-3600, +3600] Degrees per second Decimal Yaw Rate [-3600, +3600] Degrees per second Example SEND: SOURce:SCENario:DPRYRate 123.4,-2.0000,2.0000,1.0000 6.5.3.38 SOURce:SCENario:DPRYRate? Function Queries the current rate of change in Vehicle Attitude in 3-dimensions about the center of mass as Pitch, Roll, and Yaw during scenario execution.

  • Page 370: Source:scenario:kepler

    6.5 RSG Command Reference Parameter Decimal Mean anomaly [–π ] Radians Decimal Eccentrity Decimal Semi-major axis Decimal Ascension of ascending node [-π, +π] Radians Decimal Inclination [-π, +π] Radians Decimal Argument of perigee [-π, +π] Radians Example SEND: SOURce:SCENario:KEPLER 0,1.30280292873,0.995806301944E- 03,0.075377837181E+08,- 0.159728922636E+01,0.957334107483E+00,0.296123313943E+01 6.5.3.40 SOURce:SCENario:KEPLER?

  • Page 371: Source:scenario:rsgunderflow

    6.5 RSG Command Reference Command Syntax SOURce:SCENario:RSGUNDERflow <integer> Parameter Integer – Enable or disable {1,0}, respectively. Example SEND: SOURce:SCENario:RSGUNDERflow 1 6.5.3.42 SOURce:SCENario:RSGUNDERflow? Function Queries RSG underflow detection status, whether enabled or disabled. Command Syntax/Example SEND: SOURce:SCENario:RSGUNDERflow? READ: 6.5.3.43 SOURce:SCENario:DOPPler? Function Queries a satellite’s Doppler for a specific signal supported by that satellite.

  • Page 372: Source:scenario:prange

    6.5 RSG Command Reference If the satellite does not support the signal type, an error is returned. Parameters satID – GPS, Glonass, Galileo, BeiDou, QZSS, IRNSS and SBAS are supported. For more information on the format, see "SOURce:ONECHN:SATid?" on page 252. sigtype –...
  • Page 373 6.5 RSG Command Reference Command Syntax SOURce:SCENario:PRANge? <satID>,<sigtype>,<location> Notes If no scenario is running, an error is returned. If the satellite does not support the signal type, an error is returned. If the base station location is not enabled, 0 values are returned. Parameters satID –...

  • Page 374: Source:scenario:chinview

    6.5 RSG Command Reference 6.5.3.45 SOURce:SCENario:CHINview? Function Queries a comma separated list of values ranging from 1 to 64 which indicate which satel- lite index values are active in view in the simulated sky. Duplicate and interference chan- nels are ignored. Command Syntax SOURce:SCENario:CHINview? <ALL|GPS|GLO|GAL|BDS|QZSS|IRNSS|SBAS>...

  • Page 375: Source:scenario:svpos[N]

    6.5 RSG Command Reference Parameter constellation – ALL returns all active channels, while a constellation value returns satellite IDs for that constellation only. No argument is the same as ALL. Example SEND: SOURce:SCENario:SVINview? GLO READ: R2,R5,R9,R11,R12,R17 6.5.3.47 SOURce:SCENario:SVPos[n]? Function Queries a satellite’s ECEF position using channel number. Command Syntax SOURce:SCENario:SVPos[n]? Note...

  • Page 376: Source:scenario:svpos[N]

    6.6 Programming 6.5.3.48 SOURce:SCENario:SVPos[n]? Function Queries a satellite’s ECEF position using a Satellite ID. The user can specify all satellite types supported including their multipath duplicates by satID. An optional location argu- ment is specified to allow use with GSG’s simulating user position or with systems using base station operation.

  • Page 377: Usage Recommendations

    6.6 Programming 6.6.1 Usage Recommendations 6.6.1.1 Communication Interface It is strongly recommended to use USB in conjunction with RSG. USB is more reliable due to being a dedicated interface as opposed to Ethernet which can be more susceptible to network traffic. Ethernet should hence be avoided if attempting advanced steering using high message rates or requiring synchronization at the GSG 10Hz epoch rate.

  • Page 378: Underflow And Overflow

    6.6 Programming sour:scen:elapsedTime? *OPC? syst:err? 6.6.1.3 Underflow and Overflow Underflow and overflow errors are signaled by the GSG unit. The possible errors which can be retrieved with the command SYSTem:ERRor[:NEXT]?. The relevant error codes are: -193 “RSG command overflow occurred.” -194 “RSG command underflow detected.”...

  • Page 379: Trajectory File Format (.Traj)

    6.6 Programming Communication over GPIB is not currently working for RSG commands – syn- chronization fails. 6.6.2 Trajectory FILE Format (.traj) Files in the .traj file format can be created with the StudioView RSG Trajectory Editor, but an RSG license is not required to use these commands in a file. All positioning commands can be written to the file as: SOURce:SCENario:POSition TIME,<decimal>,<decimal>,<decimal>...

  • Page 380: Revision History (Scpi Guide)

    6.7 Revision History (SCPI Guide) 3. Select the file for use in a scenario the same way as any trajectory is selected. Revision History (SCPI Guide) SCPI Guide Revision History Description Date 1.0draft N/A Initial issue. 4/2/2011 Minor comments & layout changes 11/2/2011 Added *SRE? and details about overlapping commands 8/3/2011...
  • Page 381 6.7 Revision History (SCPI Guide) SCPI Guide Revision History Description Date 000421 New/updated commands to support 6.4.1 firmware release May 2015 000587 New/updated commands (mainly Propagation Environment) to sup- Sept 2015 port 6.5.1 firmware release. New layout due to carry-over into new Authoring tool. Integration of SCPI Guide into GSG User Manual: Future revision his- tory tracking see GSG User Manual revision table (see Appendix) User Manual GSG-5/6 Series Rev.
  • Page 382 6.7 Revision History (SCPI Guide) BLANK PAGE. User Manual GSG-5/6 Series Rev. 27...

  • Page 383: Appendix

    Appendix The following topics are included in this Chapter: 7.1 Lists of Tables and Images 7.2 GSG User Manual Revision History User Manual GSG-5/6 Series • APPENDIX...

  • Page 384: Lists Of Tables And Images

    APPENDIX Lists of Tables and Images Tables in this document: Table 2-1: Orolia safety symbols Table 3-1: Propagation environment type parameters Table 3-2: Transmit power offsets Table 4-1: The Trajectory Editor Toolbar Table 4-2: Speed conversion table (Note: mph and knots are rounded down.)
  • Page 385 APPENDIX Figure 3-16: Base station configuration dialog Figure 3-17: ITU multipath propagation model Figure 3-18: Tropospheric delay vs. elevation angle Figure 3-19: GPS satellite configuration Figure 3-20: Assigning one constellation block to all satellites Figure 3-21: GPS Constellation configuration (StudioView) Figure 3-22: Turning pseudo encryption ON/OFF Figure 3-23: GNSS SBAS systems Figure 3-24: Configuring transmit power...

  • Page 386: Gsg User Manual Revision History

    APPENDIX Figure 6-1: Jerk [m/s³], acceleration [m/s²], velocity [m/s], and range [m] over time [s] GSG User Manual Revision History Description Date First release. November 2010 Updated to include GSG-55. March 2011 2673 Changes in support of the 2.06 software release. June 2011 2702 Updated address information.
  • Page 387 APPENDIX Description Date 3254 Updated to support latest software & software release modi- June 2013 fications 3347 Updated to support latest software & software release modi- March fications 2014 3458 Updated to support latest software & software release modi- April 2014 fications 000073 Updated to support latest software &...
  • Page 388 BLANK PAGE. User Manual GSG-5/6 Series...
  • Page 389 1PPS output C/No (Carrier- to- noise dens- ity) Calibration Calibration, timing Active Signals Carrier- to- noise density (C/No) Almanac Almanac file Cold start, GNSS receiver Antenna, compliance Constellations, satellite Antenna, models contact, Spectracom Antenna, specifications Cooling ANTEX armed, unit Atmospheric modeling Desk-Top Setup Attenuation, external Dimensions...
  • Page 390 INDEX Elevation mask Emissions Electro-magnetic compliance HOLD Encryption Hold key ENU (East, North, Up) Hold, scenario Environmental modeling Environmental specifications Ephemeris Interference signal Ionosphere model Epoch IP configuration Event data EXTREF Jamming Jamming, jammer Factory default settings Factory defaults, restore File management Files, uploading Keyboard un/-locking...
  • Page 391 INDEX Return Link Message Return Link Service Network configuration RF connector NMEA logging RF output Noise generation RINEX data NTP configuration NTP server Numeric keys RTCM message OCXO DAC value Safety precautions One-Go, scenario duration Satellite ID Options, GSG Satellite systems Orientation SBAS Scenario, configuring...
  • Page 392 INDEX Symbols, display System information, show Web UI Week number, GPS WGS84 (positioning) Technical support TLE format Trajectory YUMA Trajectory, altitude Trajectory, file size Trajectory, looping Trajectory, NMEA Trajectory, one-line Trajectory, predefined Trajectory, RSG Trajectory, timestamping Trajectory, user-created 87-88 Transmit power Transmit Power, adjust Transmit Power, manage Transmit Power, set...

This manual is also suitable for:

Gsg-5 series

Table of Contents