Configuring EIB to run in the ZTV Lab

eibGenGui Setup

Example: 3 site key site configuration: ZKC (local & nap), ZID (local) and ZME (local)

• Execute eibGenGui from sdrrdc/tgfsdrr1
  • Select all options needed to create ZID/ZME/ZKC local release harnesses and the ZKC nap harness
  • Select the desired stp under the "ztv" section of the drop down
    • click (here) for sample screen shots
    • click here​ to download sample ini file
  • Click generate

• Copy the created eib top level directory to the stp and sdrr

STP Setup

• On stpXX.ztv in the eib dir execute: ./generateEib.ksh
• Make sure the setup_override_displays file is executable -rwxr-xr-x
  • This file will setup your displays for running in the ztv lab only
  • When using eibGenGui you should specify which displays you want to use and it will automatically created this file. However, if needed this file can be modified to make changes.
  • Click here​ for an example setup_override_displays file

• Your eram software is now ready to start, however need to do some additional things before executing ./runeib

Lab Displays Setup

• In the ztv display lab you will need to login to each of the displays that you intend on using for your RPOS/DPOS/ATS/MCWS displays
  • These displays are all labeled with IP Addresses that should match what is in your setup_override_displays file
• You will need to open the appropriate script depending on what you intend that position to be (ex: RPOS/DPOS, etc)
  • Example script files located: /home/vtl/phillich/Example-SDRR-DISPLAYS
    • Copy this directory into your home /Desktop dir

SDRR Setup

• Ensure that you successfully completed the step above to copy your newly created eib top level to the sdrr
• Login to the sdrr, change directory to your top level sdrr dir
  • execute ./runsdrr

DYSIM Setup

• The dysim needs to be executed from within your scenario source directory
• For running DYSIM mode we actually execute a script called eramDriver
• Change directory into your scenario source dir and execute eramDriver script
  • eramDriver can take many options just like for example sdrr. See below for an example:

Example: eramDriver --tgtOutDev="tcp:tgfsdrr1/9605" --sdrrCmdDev="tcp:tgfsdrr1/9606" --fac="zid,tcps:9607" --fac="zkc,tcps:9608" --fac="zme,tcps:9609" --cmuDev=tcp:tgfsdrr1/9800

Bringup

• You will want to load everything in the following order:
  • EIB display scripts
  • sdrr (./runsdrr)
  • dysim (./eramDriver)
  • stp (./runeib)

• Once everything is loaded need to do a PSIM/SSIM on EIB and make sure you see the messages in the sdrr ssrv tabs
• Finally just click Start on the dysim window and your scenario will begin

back to: DatacommProcedures