sirds

TOC

Command line usage

/usr/local/sdrr.3.1.2/bin/sirds --help

 Usage: sirds [options] [cfgfile [cfgfile]...] [-s scenfile | -n]

 Note: since multiple cfgfile specifications are allowed the [-s scenfile | -n ] is added to identify the scenario file, or 
       the -n for no scenario file.

    cfgfile is in SDRR_CONFIG_PATH (unless it starts with a '.')
    scenfile is in SDRR_SCENARIO_PATH (unless it starts with a '.')
    psyncd options are auto determined if not specified
         --logfile LOGFILE
         --logDev device
         --preview
         --connect="dev1,dev2"
         --scenTime="hh:mm:ss"
         --startDate="MM/dd/yyyy"
         --simTime="hh:mm:ss"
         --runLength="hh:mm:ss"
         --start
         --utc
         --nopsync
         --psync
         --giStart[="text"]
         --autota secs
         --version
         --dysim[=device]    (default device is multi:224.1.1.1/9600)
         --msg[=device]      (default device is multi:224.1.1.1/9601)
         --avid=[full path to avid executable]
         --ecgp[=port,port]  (default port is default ecgpoutd port)
         --tgf=device
         --tgf-options option=value[,option=value[..]]
           Valid Options are :
           DefaultRunLength
         --handshake="adaptation"
         --tile-windows
         --about-text <text>
         --proxy=server/port  (for avid use)
         --ssrvautostart
         --sskbautostart
         --opengl
         --norappi
         --embedX11=winID
         --dysimpositions="1,2,3" 
         --noscenario
         --help

Command line arguments

• --logfile LOGFILE - LOGFILE is the name and optional absolute or relative path to the SDRR log file. By default sirds automatically creates a log file in $SDRR_LOG_PATH called log.xml.MMDDYYYY.hhmmss using the time and date of the application launch. SDRR_LOG_PATH=/usr/local/log by default

• --logDev device - SDRR log data can also be written to an SDRR device. Typically this is a network device for remote monitoring or recording such as --logDev=udp:192.168.1.2/5566 or --logDev=multi:239.239.239.239/2392 TGF uses this for contact controller pilot propmting.

• --connect="dev1,dev2" Connects 2 devices together directly; sdrr will simply pass messages between the 2 devices. This is useful for lab-to-lab communications when using TCP mode with the ECG's. for example, if ZDC is running in one lab, and ZOB in another, or even running multiple adaptations in split-channel mode in a single lab, the two hosts have no way to talk to each other. using --connect will allows this. See 'JvnDeviceSpec'? for details of jvn device specifications.

• --scenTime="hh:mm:ss" - synonym for --startTime. positions data sources input to the specified startTime. will also set simulation time to this time, unless --utc is specified.

• --startDate="MM/dd/yyyy" - used as an adjunct to scenTime; allows the user to set a specific start date. It is used by some scenarios which need to run on a specific date because it falls on a Monday, for example.

• --preview - Normally sirds runs in real-time - one second of wall clock time equals one second of simulation time. This option enables a mode that allows single second stepping or running in fast-time. Useful for debugging SDRR scenarios.

• --startTime="hh:mm:ss" - Set the simulation start time to hh:mm:ss. Only applies to SDRR scenarios. If a message has a timestamp of 00:05:00 setting the start time to 00:04:59 will make that message go out 1 second after the user clicks start. Probably not very useful to TGF.

• --runLength="hh:mm:ss" - Used for automating SDRR scenarios. Causes sirds to quit after running for given time. Probably not very useful to TGF.

• --start - Effectively clicks the start button once sirds finishes loading. This will start the sensors sending out static messages (RTQCs, test targets, status messages, etc.) so it can be useful in making monitor and control workstations happy before starting sims. Realize that the SDRR scenario (if any) will begin playing back.

• --utc - Adjust time fields in injected messages relative to current UTC time. The only time NOT to use this is when running with Host not set to UTC time. Automatically enabled by --live, --dysim, --msg, and --tgf options.

• --nopsync - by default, sdrr will use the psyncd daemon if running on a multi-CPU box;else it will do network timing internally. these options override the sdrr auto-determination logic. rarely (if ever) needed.

• -psync - by default, sdrr will use the psyncd daemon if running on a multi-CPU box;else it will do network timing internally. these options override the sdrr auto-determination logic. rarely (if ever) needed.

• --giStart[="text"] - sdrr will enter auto-start mode waiting for a GI message on any interface. if text is specified, SDRR will not start unless the GI message contains the specified text.

• --live - Deprecated option for forwarding live radar. Will eventually disappear.

• --autota secs - How man seconds after issuing a DA to a TI will the facility issue a TA to take ownership of a track. It is better to use the autoTa attribute int the config file for each facility.
• --version - print out SDRR version information

• --dysim[=device] - Puts sirds in DYSIM mode. The optional device specifies an SDRR device to listen to for dynamic target information instead of using the default device. TGF uses its own dynamic input with the --tgf option, so this isn't too useful for TGF.

• --msg[=device] - Allow dynamic remote message injection. By default listens on multi:224.1.1.1/9601. Device can optionally be specified. This allows TGF to inject messages into system(s) under test. Used to send FPs and TIs to terminal (STARS/CARTS) systems and probably eventually enroute systems as well.
• --avid=[full path to avid executable] - AVID is an airspace visualization tool (shares some capabilities with JPVD). This option specifies a path to AVID software for embedding RAPPI displays in SDRR. May be of some use to TGF in the future.

• --tgf=device - Instructs sirds to accept target information from TGF and generate surveillance reports (RADAR, ADS-B, MLAT, etc.) for those targets. Typically the device string will be udp:<TGF_DIS_broadcast_port>,<TGF_DIS_broadcast_port>. The first port is the port to listen on for TGF DIS data. The second is the port to broadcast on (this is usually only the start message when used with EES to start TGF/NIEC/HFL software when the EES PSIM issues the start to SDRR)

• --tgf-options option=value[,option=value..] - Option/value pairs for specifying TGF specific options. Initially implemented to support a runtime-defined default value for target radar runlength, will probably eventually support other such options.

• --handshake="adaptation" - Specifies adaptation name (located in $ADAPTATION_PATH) to use for handshake mode. This mode is intended to determine when handoffs happen and dynamically generate appropriate system messages. This is currently in development.

• --tile-windows - Automatically perform the tile windows operation (see the windows menu) on every tab in the sirds window. Some may like this window layout than the default tiled layout.

• --about-text <text> - Override some of the about window text. You could be famous.

• --proxy=server/port - Specify a proxy server for acquiring map information in AVID RAPPI. Not likely needed by TGF.

• --ssrvautostart - Start the SDRR sim upon reception of an SSIM message from SSRV (ERAM/EES). If in TGF mode a DIS start packet will be transmitted allowing multiple systems to perform a synchronized start.

• --sskbautostart - Start the SDRR sim upon reception of an exercise start STARS simulation message from STARS CGW. Currently STARS sim keyboard injection is only supported in STARS test mode, not operational mode (STARS limitation).

• --opengl - Use OpenGL hardware acceleration if available. Only benefits AVID RAPPI.

• --norappi - Do not automatically create a RAPPI window in sirds. Unnecessary if avid is not installed.

• --dysimpositions="1,2,3" - allows SDRR to be auto-started by the specified GSGT dysim positions. not used by TGF.
• --noscenario -specifies that the user is not using any scenario input nor any dynamic input. Same as -n

SDRR Device Specification

SDRR/sirds takes a device specification with a flexable syntax

device = "devSpec" indevice = "devSpec"

The format is generally devSpec = protocol:arguments each protocol has it's own arguments

You can send to multiple devices with (devSpec1+devSpec2) You can specify alternative devices with (devSpec1 | devSpec2)

Supported Protocols:

ecgrdr:

ecgif:

pipe:

ipop:

ecgp:

multi:

hgi:

For Example:

device="ecgif:bipa/ZDV"

device="(ecgrdr:pipa/BAM1,BAM2,BAM3+ecgrdr:pipb/BAM1,BAM2,BAM3+ecgrdr:bipa/BAM1,BAM2,BAM3+ecgrdr:bipb/BAM1,BAM2,BAM3)"

device="pipe:zlc-zoa"

The Configuration file (cfgfile?)

sirds uses a config file to specifiy a meriad of configurations. The latest releases of sirds accepts multiple cfgfile's, but also now -s scenarioFile or -n (for no scenario file is required to distingush configuraton files from scenarioFiles, see cgffile? for details

The Scenario file ( scenfile?)

sirds plays back data from the Scenario File. see scenfile? for details

install sirds (sdrr)

scp jvnoffice:/raid/slack1337/jvn-sdrr.3.2.6.eng_avid.3.2.6.eng-i486-1.tgz   .

su

root@rbx4h:/home/tgfsim# installpkg jvn-sdrr.3.2.6.eng_avid.3.2.6.eng-i486-1.tgz
Verifying package jvn-sdrr.3.2.6.eng_avid.3.2.6.eng-i486-1.tgz.
Installing package jvn-sdrr.3.2.6.eng_avid.3.2.6.eng-i486-1.tgz:
PACKAGE DESCRIPTION:
# 
# JVN Communications
# Slackware 13.37.0
# 
# sdrr.3.2.6.eng
# avid.3.2.6.eng
# 
Executing install script for jvn-sdrr.3.2.6.eng_avid.3.2.6.eng-i486-1.tgz.
Package jvn-sdrr.3.2.6.eng_avid.3.2.6.eng-i486-1.tgz installed.