button
is only active when is set to .|
1. Common Settings
2. GPS Settings |
3. GLONASS Settings Output GLONASS Assistant Data and Ephemeris Files Output GLONASS Raw Senario Data GLONASS Ephemeris File (Optional)
4. Galileo Settings Output Galileo Assistant Data and Ephemeris Files Output Galileo Raw Senario Data Galileo Ephemeris File (Optional)
5. Beidou Settings Output Beidou Assistant Data and Ephemeris Files Output Beidou Raw Senario Data Beidou Ephemeris File (Optional)
6. Leap Second Settings
7. Antenna Pattern Settings |
Couplings: This button
is only active when is set to .
Clicking this button displays a dialog box, asking you to specify the file path and name, and then creates the scenario file. When the scenario is successfully created, the graphic panel under the 'Scenario Graphics' tab displays the content of satellite channels in the scenario. Any related error messages are appended to the log window.
Couplings: This button
is only active when is set to .
Clicking this button displays a dialog, asking you to specify the file path and name, and then save the edited scenario file. When the scenario file is saved, the message 'Save to scenario file <path and file name>' is appended to the log window.
Couplings: This button
is only active when is set to .
Clicking this button performs the edit operation to the selected scenario and related parameters, as specified by . When the operation is complete, the graphic panel under 'Scenario Graphics' tab will be updated to reflect the changes made to the scenario. A record of operation details and error messages are appended to log window, as well.
|
Edit Mode |
Related Parameter |
Sample log text |
|---|---|---|
|
Delete Channel |
Source Channel |
Delete channel 1 |
|
Apply Power Offset |
Source Channel Start Stop Power Offset |
Apply power scale of -10 dB to channel 1 from 0 to 3600 seconds |
|
Equalize Power |
none |
Set power of all satellite channels to equal values. |
|
Create Multipath |
Source Channel Destination Channel Start Stop Power Offset Delay offset Doppler Shift |
Add path – channel 1 from 0 to 3600 seconds to channel 7 with power offset -10 dB, Doppler offset 1000 Hz, delay offset 10 chips |
|
Trim |
Start Stop |
Trim scenario – keep time range from 0 to 1800 seconds |
Choice: Create | Edit
Default: Create
Couplings: 'Apply' button is only active in Edit mode. Switching to 'Edit' mode will cause a graphic panel update and log text window update based on selected scenario file for edit.
Create | This mode creates a new scenario file with the input parameters provided by user. |
Edit | In this mode, edit an existing scenario file, and then either save the changes, or rename the scenario and save the changes. |
Default: C:\Program Files\Agilent\PXB\Infrastructure\Applications\Gnss\Scenarios\20110709_Beijing.ags
Couplings: This property is only visible when editing an existing scenario.
Select an existing scenario file for editing. After loading a scenario, graphic panel will be updated to display the content of the scenario.
Choice: On | Off
Default: Off
This property indicates whether edit log will be saved to a text file along with the scenario. The log file will have the same path and name with scenario file but different extension (.log).
Choice: Delete Channel | Apply Power Offset | Equalize Power | Create Multipath | Trim
Default: Delete Channel
Couplings: This property is only visible when editing an existing scenario. Each time when a certain type of edit is made to selected scenario, the graphic panel will have some updates accordingly and a new record will be appended to edit log.
Select an edit operation to be applied to the scenario file.
Delete Channel | This mode deletes a satellite channel from the scenario with specified channel index. A 'Satellite Channel' is a basic resource unit in scenario for playing satellite data. During scenario playback, a channel could either be blank (no satellite data), or transmitting data from a satellite with specified SV ID. And at certain time, it may make a transition to another satellite as defined in scenario. See channel plot under 'Scenario Graphics' tab to have in-depth understanding on channel concept. |
Apply Power Offset | This mode adds some offset to the power level of some portion in the scenario. The 'Start' and 'Stop' properties specify the time frame over which the power level will be adjusted. |
Equalize Power | This mode sets power of all satellites to equal values. |
Create Multipath | This mode creates a new multipath channel from a source channel with provided time delay, Doppler shift and power offset. The new channel could be either placed at an existing channel to overwrite it or at a next available channel (index = number of currently used channels + 1). |
Trim | This mode removes the satellite data from the scenario that falls out of the time range specified by 'Start' and 'Stop'. |
You can choose to apply a positive power offset to a channel as well as a negative power offset. If a large positive power offset (> 10 dB) is applied to one of the channels, a GPS receiver might show a higher C/N ratio than what is expected for that satellite, compared to the other satellite channels. For example, if a 15 dB power boost is applied to one channel, the GPS receiver might report the C/N ratio on that satellite to be 20 dB higher than the non-boosted channels instead of the expected 15 dB. The reason for this is that GPS is a CDMA signal, so for any one C/A code, the signals from the other satellites and other C/A codes appear as noise. If you have one satellite that is a very high power signal compared to the others, this strong signal appears as noise to all of the other C/A codes, and it will reduce the apparent C/N ratio for the lower-power signals. Thus the difference in C/N between those lower-power signals and the boosted signal will appear to be greater than the nominal power offset value.
Range: 1 - max channel
Default: 1
Couplings: This property is only visible when editing an existing scenario and the edit mode is not or .
Enter the index of the satellite channel that is to receive the edit operation.
Range: 1 - number of used channels + 1
Default: 1
Couplings: This property is only visible when editing an existing scenario and the edit mode is .
Enter the index of the channel where to store the newly created multipath channel data. A value of existing channel index will bring up a dialog asking user whether to overwrite the channel data or cancel it. A value of unused channel number (number of used channels + 1) will place the new multipath channel on the next unused channel. The maximum supported channel number is 24.
Range: 0 - duration of scenario
Default: 0 s
Couplings: This property is only visible when editing an existing scenario and the edit mode is , , or . The Start Time in the scenario cannot be larger than the Stop Time.
Enter the start time in the scenario in seconds for a specific edit operation, with a resolution of 0.6 second.
Range: 0 - duration of scenario
Default: 3600 s
Couplings: This property is only visible when editing an existing scenario and the edit mode is , , or . The Stop Time in the scenario can not be less than Start Time.
Enter the stop position in the scenario in seconds for a specific edit operation, with a resolution of 0.6 second.
Range: -40 dB to 20 dB
Default: 0.00 dB
Couplings: This property is only visible when editing an existing scenario and the edit mode is either or .
Enter the power offset to be applied to a specific satellite channel. Adjust this offset value to control the relative power levels among satellite channels.
Range: -102300 chip to 102300 chip
Default: 0.00 chip
Couplings: This property is only visible when editing an existing scenario and the edit mode is .
Enter the time delay of the multipath channel in chips.
Range: -125 kHz to 125 kHz
Default: 0.00 Hz
Couplings: This property is only visible when editing an existing scenario and the edit mode is .
Enter the Doppler shift of the multipath channel in Hz.
Range: 0 degrees - 30 degrees
Default: 5.00
Couplings: This property is only visible in Create mode.
Enter the angle above the horizon for the location of desired satellite to use in the scenario. Satellites below this angle will not be used. Increasing this angle will reduce the number of visible satellites in the generated scenario.
Choice: No Model | NATO
Default: No Model
Couplings: This property is only visible in Create mode.
Select the troposphere model to be applied to satellite signals in the generated scenario.
Choice: No Model |
Default: No Model
Couplings: This property is only visible in Create mode.
Select the ionosphere model to be applied to satellite signals in the generated scenario.
Default: 4.6566129E-09, 1.4901161E-08, -5.96046E-08, -5.96046E-08, 79872, 65536, -65536, -393216
Couplings: This property is only visible when is
Set the Alpha and Beta parameters for ionosphere model calculation. The format is , ,, , , , , . See table below for Alpha and Beta setup:
Parameter | Default | Min | Max |
|---|---|---|---|
Alpha[0] | 4.6566129e-9 | -1.1920928955078125e-7 | 1.1920928955078125e-7 |
Alpha[1] | 1.4901161e-8 | -9.5367431640625e-7 | 9.5367431640625e-7 |
Alpha[2] | -5.96046e-8 | -7.62939453125e-6 | 7.62939453125e-6 |
Alpha[3] | -5.96046e-8 | -7.62939453125e-6 | 7.62939453125e-6 |
Beta[0] | 79872 | -2.62144e+5 | 2.62144e+5 |
Beta[1] | 65536 | -2.097152e+6 | 2.097152e+6 |
Beta[2] | -65536 | -8.388608e+6 | 8.388608e+6 |
Beta[3] | -393216 | -8.388608e+6 | 8.388608e+6 |
Choice: Static | Dynamic
Default: Static
Couplings: This property is only visible in Create mode.
Select the scenario type to be generated.
Static | Scenario will be generated for a static GPS receiver with fixed longitude, latitude and altitude. |
Dynamic | Scenario will be generated for a moving GPS receiver based on the provided trajectory data. |
Default: C:\Program Files\Agilent\PXB\Infrastructure\Applications\Gnss\Scenarios\Beijing.gga
Couplings: This property is only visible when creating a Dynamic scenario. When a new NMEA file is selected, will be updated according to the content of the file.
Select a NMEA message file for dynamic scenario creation, which contains RMC/GGA messages generated by a GPS receiver. The recommended sampling rate of input NMEA message file is 0.1 Hz- 20 Hz.
The software requires that the GGA file contain a minimum of three sentences with each sentence having a different data point.
Choice: Hold Last Location | Round Trip | Auto Rewind.
Default: Hold Last Location
Couplings: This property is only visible when creating a Dynamic scenario and the in GNSS1 node is Scenario Generator Settings.
Since the length of NMEA data is limited while the real time scenario generation can be infinite length, when the NMEA message files reaches the end, there are three different Trajectory Modes available shown below. Select each of the following modes to import NMEA data into scenario generation.
Trajectory Mode | Descriptions |
|---|---|
Hold Last Location | When the NMEA message file reaches the end, user can choose to hold at the last location. |
Round Trip | When the NMEA message file reaches the end, user can choose to make an auto rewind to the beginning. |
Auto Rewind | When the NMEA message file reaches the end, user can choose to make a round trip back. |
When the NMEA message file reaches the end, user can choose to hold at the last location, make an auto rewind to the beginning, or make a round trip back.
Couplings: This property is only visible when creating a Dynamic scenario.
When generating a dynamic scenario, the NMEA data will be imported from this time offset into the file.
Default: 116.478479 E
Couplings: This property is only visible when creating a Static scenario.
Enter the initial longitude in degrees of GPS receiver position to be simulated in a static scenario.
Default: 40.0096856 N
Couplings: This property is only visible when creating a Static scenario.
Enter the initial latitude in degrees of GPS receiver position to be simulated in a static scenario.
Range: -100 m to 10000 m
Default: 100.00 m
Couplings: This property is only visible when creating a Static scenario.
Enter the initial altitude in meters of GPS receiver position to be simulated in a static scenario.
Default:2011-07-09
Couplings: This property is only visible in Create mode.
Use the date time editor or manually enter the start date for the simulated scenario in yyyy-MM-dd format. The start date must be later than 1980-01-06.
The start date is automatically updated by the TOA information in the selected almanac files.While the software provides the capability to ignore the auto-updated date and manually enter another value, it is recommended that the Start Date property uses the same date as the almanac date.
To use the date editor, click the cell and then the 
button to access the Date Time Editor dialog box. The editor allows the entry of the date time either in Week/Tow mode or in Year/Month/Day/Hour/Minute/Second mode. For Static Test scenarios, start time must be on a 6 second boundary.
Default:2010-01-01 10:05:54
Couplings: This property is only visible in Create mode.
Click the cell and then the button to access the Start Date Time Dialog Box.
The editor allows user to enter date time either in Week/Tow mode or in Year/Month/Day/Hour/Minute/Second mode.
For static scenarios, start time must be on a 6 second boundary.
To ensure the simulated scenario reflects real-world conditions, the start date should be within 4 weeks of the GPS almanac file and within 1 week of the GLONASS almanac file. Otherwise, software will display a warning or fail to generate the scenario. It’s strongly recommended to use almanac files on the same day with Start Date Time.
Default: 01:00:00
Couplings: This property is only visible when creating a Static scenario, and with the GNSS1 node property of Scenario Source set to User Scenario File.
Enter the duration of the scenario to be created in <HH:mm:ss> format. Scenario Duration must be a multiple of 3 seconds.
Choice: On| Off
Default: On
Couplings: This property is only visible in Create mode.
Enable or disable GPS constellation in scenario generation.
Choice: On | Off
Default: Off
Couplings: This property is only visible in Create mode.
Indicate whether A-GPS parameter file and matching ephemeris file will be created along with the scenario file.
This property indicates whether GPS raw scenario data file will be created along with the scenario file. This property can be turned on only when connected to an instrument with required scenario generator option.
Choice: On| Off
Default: Off
Default: No file selected
Couplings: This property is only visible in Create mode.
Select the ephemeris data file in comma-separated
format for scenario creation. Click on the cell and then the button to launch the Open dialog box for navigating to and selecting the file. This property is optional for creating a
scenario and could be left with no file selected.
If you use an ephemeris file created with the cell, before using it, you must modify the file by removing the first line (header line) of the file. To modify the file, use either a text editor or Microsoft® Excel. Ensure to resave the file in the same format, comma separated values (.csv).
Default: C:\Program Files\Agilent\PXB\Infrastructure\Applications\Gnss\Scenarios\20110709.alm
Couplings: This property is only visible in Create mode.
Select the almanac data file in YUMA format for scenario creation.
Choice: On| Off
Default: On
Couplings: This property is only visible in Create mode.
Enable or disable GLONASS constellation in scenario generation.
Choice: On| Off
Default: Off
Couplings: This property is only visible in Create mode.
This property indicates whether GLONASS assistant data file and matching ephemeris file will be created along with the scenario file.
Choice: On| Off
Default: Off
This property indicates whether GLONASS raw scenario data file will be created along with the scenario file. This property can be turned on only when connected to an instrument with required scenario generator option.
Couplings: This property is only visible in Create mode.
GLONASS ephemeris files in Rinex format can be downloaded at ftp://ftp.glonass-iac.ru/IGS/DATA/. To select the file once download, click on the cell and then the button to launch the Open dialog box for navigating to and selecting the file.
Default: C:\Program Files\Agilent\PXB\Infrastructure\Applications\Gnss\Scenarios\20110709.alm
Couplings: This property is only visible in Create mode.
Select GLONASS almanac data file in AGL format for scenario creation. Refer to GLONASS Almanac - AGL File format for more details.
Choice: XOR | NXOR
Default: NXOR
Couplings: This property is only visible in Create mode.
Select the method of how meander sequence is applied to GLONASS information bits. XOR means bit '0' is coded to '10' and bit '1' to '01', while NXOR means bit '0' is coded to '01' and bit '1' to '10'.
Choice: On| Off
Default: On
Couplings: This property is only visible in Create mode.
Enable or disable Galileo constellation in scenario generation.
Choice: On| Off
Default: Off
Couplings: This property is only visible in Create mode.
This property indicates whether Galileo assistant data file and matching ephemeris file will be created along with the scenario file.
Choice: On| Off
Default: Off
This property indicates whether Galileo raw scenario data file will be created along with the scenario file. This property can be turned on only when connected to an instrument with required scenario generator option.
Couplings: This property is only visible in Create mode.
Select the ephemeris data file in a comma-separated format for scenario creation. Click on the cell and then the button to launch the Open dialog box for navigating to and selecting the file. This property is optional for creating a scenario and could be left with no file selected.
Default: C:\Program Files\Agilent\PXB\Infrastructure\Applications\Gnss\Scenarios\20110709_Gal.agl
Couplings: This property is only visible in Create mode.
Select the almanac data file in YUMA format for scenario creation. The Start Date and Start Time (GPS Time) properties are always updated to the TOA (Time of Application) found in the currently selected almanac file.
Couplings: This property is only visible in Create mode.
Click the cell and then the button to display the Galileo Navigation Message Editor, which enables you to configure navigation parameters.
To view help for a parameter in the Message Editor, hover the mouse pointer on a parameter name to display a tool tip.
Choice: On| Off
Default: On
Couplings: This property is only visible in Create mode.
Enable or disable Beidou constellation in scenario generation.
Choice: On| Off
Default: Off
Couplings: This property is only visible in Create mode.
This property indicates whether Beidou assistant data file and matching ephemeris file will be created along with the scenario file.
Choice: On| Off
Default: Off
This property indicates whether Beidou raw scenario data file will be created along with the scenario file. This property can be turned on only when connected to an instrument with required scenario generator option.
Couplings: This property is only visible in Create mode.
Select Beidou ephemeris data file in csv format for scenario creation. This property is optional for creating a scenario and could be left with no file selected.
Select Beidou almanac data file in YUMA format for scenario creation.
Choice: Official | User
Default: Official
Select the mode on how to apply leap seconds to scenario creation.
Official | Scenario will be generated using the official leap seconds defined by the International Earth Rotation and Reference System Service (IERS). 15 leap seconds at 2010.1.1. |
User | Scenario will be generated which allows user to edit leap seconds by their own. |
Couplings: This property is only visible when the Leap Seconds Mode is User.
Click the cell and then the button to access the Leap Seconds Editor.
When using user-defined leap seconds in creating a scenario, the scenario length needs to be at least 12.5 minutes long to ensure that the user-defined leap second information will be included in the scenario. The leap second information is contained in frame 4, page 18 of the navigation message. The entire 25-page navigation message repeats every 12.5 minutes, and where the navigation message starts in the scenario depends on the scenario start date and time. For a dynamic scenario, since the scenario length is determined by the length of the NMEA message (GGA) file, the file must contain a trajectory that lasts at least 12.5 minutes.
Choice: On | Off
Default: Off
This property indicates whether gain mask for antenna pattern will be enabled for the generated scenarios.
Range: 5° - 90°
Default: 10.00°
Enter the satellite elevation resolution for creating the gain mask of antenna pattern. When this value is changed, gain mask for antenna pattern will be rebuilt and reset to default values(0 dB).
Range: 5° - 90°
Default: 30.00°
Enter the satellite azimuth resolution for creating the gain mask of antenna pattern. When this value is changed, gain mask for antenna pattern will be rebuilt and reset to default values(0 dB).
Range: 0° - 360°
Default: 0°
Enter the rotation of configuring antenna pattern from the base pattern, in which 0° azimuth pointing to the north. When this value is changed, antenna pattern panel will be updated to reflect the rotation.
