Enterprise

Short CPDLC Regression Run (Groups 1-3)

Scenario Locations

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

SDRR Bring Up

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

Run Scenario Injector

• For SLC/TB4
  • Login to sdrr4 as task23
  • cd Enterprise
  • Execute injector script: ./enterprise-msg-inj-ead400 -g "group #"
    • Example: ./enterprise-msg-inj-ead400 -g 1 (this will inject messages from group 1)
    • *Note need to hit enter twice to start injecting messages

Altys Bring Up

• Open rdesktop as peer3
  • Start PEERMaster
    • Select MasterConf file for Radios 3 and 4
    • EACP File: /PEER3/work/ScenarioMng/ScenarioFiles/Enterprise/Enterprise-short-cpdlc-r3-r4.eacp
    • Groups File: /PEER3/work/ScenarioMng/Groups/Groups-Enterprise.xml

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-ead400
• sdrrdc:/usr/local/scenarios/Enterprise-ead400

SDRR Bring Up

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

Run Scenario Injector

• For SLC/TB4
  • Login to sdrr4 as task23
  • cd Enterprise
  • Execute injector script: ./enterprise-msg-inj-ead400 -g "group #"
    • Example: ./enterprise-msg-inj-ead400 -g 4a (this will inject messages from group 4a)
    • *Note need to hit enter twice to start injecting messages

Altys Bring Up

• Open rdesktop as peer3
  • Start PEERMaster
    • Select MasterConf file for Radios 3 and 4
    • EACP File: /PEER3/work/ScenarioMng/ScenarioFiles/Enterprise/Enterprise-Extended-r3-r4.eacp
    • Groups File: /PEER3/work/ScenarioMng/Groups/Groups-Enterprise.xml

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-ead400
• sdrrdc:/usr/local/scenarios/Enterprise-ead400

SDRR Bring Up

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

Run Scenario Injector

• For SLC/TB4
  • Login to sdrr4 as task23
  • cd Enterprise
  • Execute injector script: ./enterprise-msg-inj-ead400 -g "group #"
    • Example: ./enterprise-msg-inj-ead400 -g 12a (this will inject messages from group 12a)
    • *Note need to hit enter twice to start injecting messages

Altys Bring Up

• Open rdesktop as peer3
  • Start PEERMaster
    • Select MasterConf file for Radios 3 and 4
    • EACP File: /PEER3/work/ScenarioMng/ScenarioFiles/Enterprise/FallbackToPDC-r3-r4.eacp
    • Groups File: /PEER3/work/ScenarioMng/Groups/Groups-Enterprise.xml

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.

back to: DatacommProcedures