Customer Service Center

There is no fixed answer for this question. The length of time it will take for a scenario to start running after the user clicks the 'RUN' button or sends remote commands to start the scenario will depend on the following:-

• What simulator model is in use?
• How many GNSS constellations are active in the scenario?
• How many simulator channels need to be started?
• Has the scenario been 'armed' before a 'run' is sent?
• Are trigger modes being used? 

In general, basic use of a scenario will mean it is loaded and run manually. This means that the user will click the 'RUN' button in the GUI to start the test. When the RUN button is used the software actually performs an ARM sequence, which initialises all the channels on all the simulators which will be used in the scenario, before running the scenario. Since every scenario may require a different number of simulator channels to be used and different customer systems may involve different simulators there is no simple answer to the question "how long does a scenario take to start running?". It can be anything from ~3s for a simple GPS only scenario using a GSS6700 to ~30s for a multi-constellation scenario using 2 or more GSS8000's.

The most appropriate way to control the start of the scenario is to send the remote ARm command first. This then takes care of the simulator channel initialisation sequence BEFORE the scenario starts running. Let us take the example of using the DISABLED trigger mode (default trigger state):-

1. Instead of clicking the 'RUN' button use some simple remote control to send an ARm remote command, e.g. the socket string send utility provided with PosApp, located via the [Tools-->General Utilities] menu
2. Once the scenario has completed it's ARm it will move into an "ARMED" state (if refering to the GUI this is shown in the bottom right-hand corner).
3. Then the user may then send the remote RUn command.
4. As long as the RUn is sent within 100ms of a 1PPS rising edge the scenario will start on the 'next' 1PPS. Hence there will be a consistent ~1s delay between sending the RU command and the scenario starting.
       - NOTE : This clearly requires that you are monitoring the 1PPS output from the simulator and are able to issue the RU command in a controlled way (probably requiring a little more software control for accuracy).
5. Typically, just trying this method manually you will find a variation between ~1s and ~2s from sending the RU command and seeing the scenario start.

Some users however simply become familiar with their system and know approximately how long a particular scenario configuration will take to start running. This is acceptable as long as they have no need for precise timing between starting the scenario and the scenario actually running.

Higher precision control requires better remote control of the start of the scenario, being able to monitor the simulator 1PPS or using external triggering. To learn more about trigger modes please refer to article SOL10180 or the SimREMOTE manual DGP00792AAA.