wiki:Enterprise

  1. Short CPDLC Regression Run (Groups 1-3)
  2. Extended CPDLC Regression Run (Groups 4a-b, 5)
  3. Fallback to PDC Run (Groups 12a-e )
  4. KBOI Manual CPDLC/PDC Run (Groups 21 & 22)
  5. KBOI Logons Runs - Nominal (Group 25)
  6. KBOI Logons Runs - Non-Nominal (Group 26)
  7. Enterprise Regression 510
  8. ERAM Version 500 510 testing

Enterprise

Short CPDLC Regression Run (Groups 1-3)

Scenario Locations

  • sdrr4:/usr/local/scenarios/Enterprise
  • sdrrdc:/usr/local/scenarios/Enterprise

SDRR Bring Up

  • For TB4
    • Login to sdrr4 as task23/task50
    • cd Enterprise
    • Launch sdrr: ./runsdrr
  • For VTL
    • Login to sdrrdc as task23/task50
    • cd Enterprise
    • Launch sdrr: ./runsdrr

Run Scenario Injector

  • For TB4
    • Login to sdrr4 as task23/task50
    • cd Enterprise
    • Execute injector script:
    • Using port 9601: ./enterprise-msg-inj -g "group #"
    • Using port 9602: ./enterprise-msg-inj-9602 -g "group #"
      • Example: ./enterprise-msg-inj -g 1
  • For VTL
    • Login to sdrrdc as task23/task50
    • cd Enterprise
    • Execute injector script:
    • Using port 9601: ./enterprise-msg-inj -g "group #"
    • Using port 9602: ./enterprise-msg-inj-9602 -g "group #"
      • Example: ./enterprise-msg-inj -g 1

  • *Note need to hit enter twice to start injecting messages

Altys Bring Up

  • Open rdesktop as peer3
    • Open the bat-files folder
    • Select: Enterprise-KSLC-Short-CPDLC-Groups1-3.bat - Shortcut

Additional Notes

  • Ensure that Altys and the scenario injector 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.



Extended CPDLC Regression Run (Groups 4a-b, 5)

Scenario Locations

  • sdrr4:/usr/local/scenarios/Enterprise
  • sdrrdc:/usr/local/scenarios/Enterprise

SDRR Bring Up

  • For TB4
    • Login to sdrr4 as task23/task50
    • cd Enterprise
    • Launch sdrr: ./runsdrr
  • For VTL
    • Login to sdrrdc as task23/task50
    • cd Enterprise
    • Launch sdrr: ./runsdrr

Run Scenario Injector

  • For TB4
    • Login to sdrr4 as task23/task50
    • cd Enterprise
    • Execute injector script:
    • Using port 9601: ./enterprise-msg-inj -g "group #"
    • Using port 9602: ./enterprise-msg-inj-9602 -g "group #"
      • Example: ./enterprise-msg-inj -g 4a
  • For VTL
    • Login to sdrrdc as task23/task50
    • cd Enterprise
    • Execute injector script:
    • Using port 9601: ./enterprise-msg-inj -g "group #"
    • Using port 9602: ./enterprise-msg-inj-9602 -g "group #"
      • Example: ./enterprise-msg-inj -g 4a
  • *Note need to hit enter twice to start injecting messages

Altys Bring Up

  • Open rdesktop as peer3
    • Open the bat-files folder
    • Select: Enterprise-KSLC-Extended-CPDLC-Groups4-5.bat - Shortcut

Additional Notes

  • Ensure that Altys and the scenario injector 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.



Fallback to PDC Run (Groups 12a-e )

Scenario Locations

  • sdrr4:/usr/local/scenarios/Enterprise
  • sdrrdc:/usr/local/scenarios/Enterprise

SDRR Bring Up

  • For TB4
    • Login to sdrr4 as task23/task50
    • cd Enterprise
    • Launch sdrr: ./runsdrr
  • For VTL
    • Login to sdrrdc as task23/task50
    • cd Enterprise
    • Launch sdrr: ./runsdrr

Run Scenario Injector

  • For TB4
    • Login to sdrr4 as task23/task50
    • cd Enterprise
    • Execute injector script:
    • Using port 9601: ./enterprise-msg-inj -g "group #"
    • Using port 9602: ./enterprise-msg-inj-9602 -g "group #"
      • Example: ./enterprise-msg-inj -g 12a
  • For VTL
    • Login to sdrrdc as task23/task50
    • cd Enterprise
    • Execute injector script:
    • Using port 9601: ./enterprise-msg-inj -g "group #"
    • Using port 9602: ./enterprise-msg-inj-9602 -g "group #"
      • Example: ./enterprise-msg-inj -g 12a
  • *Note need to hit enter twice to start injecting messages

Altys Bring Up

  • Open rdesktop as peer3
    • Open the bat-files folder
    • Select: Enterprise-KSLC-Fallback-PDC-Group12.bat - Shortcut

Additional Notes

  • Ensure that Altys and the scenario injector 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.



KBOI Manual CPDLC/PDC Run (Groups 21 & 22)

Scenario Locations

  • sdrr4:/usr/local/scenarios/Enterprise
  • sdrrdc:/usr/local/scenarios/Enterprise

SDRR Bring Up

  • For TB4
    • Login to sdrr4 as task23/task50
    • cd Enterprise
    • Launch sdrr: ./runsdrr
  • For VTL
    • Login to sdrrdc as task23/task50
    • cd Enterprise
    • Launch sdrr: ./runsdrr

Run Scenario Injector

  • For TB4
    • Login to sdrr4 as task23/task50
    • cd Enterprise
    • Execute injector script:
    • Using port 9601: ./enterprise-msg-inj -g "group #"
    • Using port 9602: ./enterprise-msg-inj-9602 -g "group #"
      • Example: ./enterprise-msg-inj -g 21
  • For VTL
    • Login to sdrrdc as task23/task50
    • cd Enterprise
    • Execute injector script:
    • Using port 9601: ./enterprise-msg-inj -g "group #"
    • Using port 9602: ./enterprise-msg-inj-9602 -g "group #"
      • Example: ./enterprise-msg-inj -g 21

  • *Note need to hit enter twice to start injecting messages

Altys Bring Up

  • Open rdesktop as peer3
    • Open the bat-files folder
    • Select: Enterprise-KBOI-Manual-CPDLC-PDC-Groups21-22.bat - Shortcut



KBOI Logons Runs - Nominal (Group 25)

Scenario Locations

  • sdrr4:/usr/local/scenarios/Enterprise
  • sdrrdc:/usr/local/scenarios/Enterprise

SDRR Bring Up

  • For TB4
    • Login to sdrr4 as task23/task50
    • cd Enterprise
    • Launch sdrr: ./runsdrr
  • For VTL
    • Login to sdrrdc as task23/task50
    • cd Enterprise
    • Launch sdrr: ./runsdrr

Run Scenario Injector

  • For TB4
    • Login to sdrr4 as task23/task50
    • cd Enterprise
    • Execute injector script:
    • Using port 9601: ./enterprise-msg-inj -g "group #"
    • Using port 9602: ./enterprise-msg-inj-9602 -g "group #"
      • Example: ./enterprise-msg-inj -g 25
  • For VTL
    • Login to sdrrdc as task23/task50
    • cd Enterprise
    • Execute injector script:
    • Using port 9601: ./enterprise-msg-inj -g "group #"
    • Using port 9602: ./enterprise-msg-inj-9602 -g "group #"
      • Example: ./enterprise-msg-inj -g 25
  • *Note need to hit enter twice to start injecting messages

Altys Bring Up

  • Open rdesktop as peer3
    • Open the bat-files folder
    • Select: Enterprise-KBOI-Logons-Nominal-Group25.bat - Shortcut



KBOI Logons Runs - Non-Nominal (Group 26)

Scenario Locations

  • sdrr4:/usr/local/scenarios/Enterprise
  • sdrrdc:/usr/local/scenarios/Enterprise

SDRR Bring Up

  • For TB4
    • Login to sdrr4 as task23/task50
    • cd Enterprise
    • Launch sdrr: ./runsdrr
  • For VTL
    • Login to sdrrdc as task23/task50
    • cd Enterprise
    • Launch sdrr: ./runsdrr

Run Scenario Injector

  • For TB4
    • Login to sdrr4 as task23/task50
    • cd Enterprise
    • Execute injector script:
    • Using port 9601: ./enterprise-msg-inj -g "group #"
    • Using port 9602: ./enterprise-msg-inj-9602 -g "group #"
      • Example: ./enterprise-msg-inj -g 26
  • For VTL
    • Login to sdrrdc as task23/task50
    • cd Enterprise
    • Execute injector script:
    • Using port 9601: ./enterprise-msg-inj -g "group #"
    • Using port 9602: ./enterprise-msg-inj-9602 -g "group #"
      • Example: ./enterprise-msg-inj -g 26
  • *Note need to hit enter twice to start injecting messages

Altys Bring Up

  • No Altys scenario, test uses avionics CMUs



Enterprise Regression 510

Scenario Locations

  • sdrr4:/usr/local/scenarios/EnterpriseRegression-510
  • sdrrdc:/usr/local/scenarios/EnterpriseRegression-510

SDRR Bring Up

  • For TB4
    • Login to sdrr4 as task23/task50
    • cd EnterpriseRegression-510
    • Launch sdrr: ./runsdrr
  • For VTL
    • Login to sdrrdc as task23/task50
    • cd EnterpriseRegression-510
    • Launch sdrr: ./runsdrr
      • ensure that ./runsdrr includes option --cmdDev=udp:localhost/9603

Run Scenario Injector

  • For TB4
    • Login to sdrr4 as task23/task50
    • cd EnterpriseRegression-510
    • Execute injector script:
    • Using port 9603: ./enterprise-510-msg-inj -g "group #" (only 1 and 2 available)
      • Example: ./enterprise-510-msg-inj -g 1
  • For VTL
    • Login to sdrrdc as task23/task50
    • cd EnterpriseRegression-510
    • Execute injector script:
    • Using port 9603: ./enterprise-510-msg-inj -g "group #" (only 1 and 2 available)
      • Example: ./enterprise-510-msg-inj -g 1

Note: when running with ALTYS edit the injector scripts to remove the datacommMsgs.xml file

Altys Bring Up

  • bat file: e:/RUNALTYS/Enterprise-510.bat
  • eacp file: e:/RUNALTYS/ScenariosFiles/EnterpriseRegression-510.eacp

NOTE: Altys needs to restart when prompted to execute runInjector2

ERAM Version 500 510 testing

Scenario Locations

  • sdrr4:/usr/local/scenarios/ERAMVersioningTest
  • sdrrdc:/usr/local/scenarios/ERAMVersioningTest

SDRR Bring Up

  • For TB4
    • Login to sdrr4 as task23
    • cd configs/VERSIONING/ZLC
    • Launch sdrr: ./runsdrr_ZLC_DCNS_ead500_ead510

Run Scenario Injector

  • For TB4
    • Login to sdrr4 as task23
    • cd /usr/local/scenarios/ERAMVersioningTest
    • Execute injector script: runGroup1 or runGroup2



back to: DatacommProcedures

Last modified 8 years ago Last modified on 2016-08-02T07:38:24-04:00