ATC Training

Scenario Locations

HOU

• sdrr3:/usr/local/scenarios/ATC-Training-HOU
• sdrrdc:/usr/local/scenarios/ATC-Training-HOU

SLC

• sdrr4:/usr/local/scenarios/ATC-Training-SLC
• sdrrdc:/usr/local/scenarios/ATC-Training-SLC

SDRR with EIB

EIB

• Login to sdrrdc as task23
• Execute: eibGenGui
• Create your desired VTL config (there are pre-loaded config files in /home/task23/TT_EGG_Configs/)
  • ATC_TRAINING_EAD3_STP10_ZHU_LIVE_DCNS.ini
  • ATC_TRAINING_EAD4_STP10_ZHU_LIVE_DCNS.ini
• Copy eib directory to desired stp and generate

SDRR

• On sdrrdc execute the runsdrr script in the /sdrr directory
• Scenario will start upon doing PSIM/SSIM
• All FPL and AM messages will be injected within first 5 minutes of scenario run time

SDRR with TB3/TB4 Labs

• Login to sdrr3 as task23
• cd /home/task23/ATC-Training-HOU
• Execute: ./runsdrr-zhu
• Scenario will start once PSIM/SSIM is executed in the lab

Altys Bring Up

• Open rdesktop as peer3
  • Start PEERMaster
    • Select MasterConf file for Radios 3 and 4
    • EACP File: /PEER3/work/ScenarioMng/ScenarioFiles/ATC-Training/ATC-Training-HOU-r3-r4.eacp
    • Groups File:
      • Standard Run: /PEER3/work/ScenarioMng/Groups/Groups-ATC-Training-HOU.xml
      • Push DCL: /PEER3/work/ScenarioMng/Groups/Groups-ATC-Training-HOU-push-DCL.xml

Additional Notes

• Ensure that Altys and the scenario are started as close to the same time as possible. If Altys is started too far ahead of sdrr scenario then the logins will be entered before flight plans which will cause them to be rejected.

back to: DatacommProcedures