Herschel: Diff for "PACS/EQM_IMT_Procedures/RouterSetup"

There are 8 scripts available located in hos4-d:~hcss/bin to start the

• packetDistribution (start all seven scripts using different konsoles)
• Router
• EGSEgateway (the link to SCOS 2000)
• PipeGW (the link to the CCS)

• CcsHandler (the link to HCSS/CUS)

• Router2 (additional router for second SCOS machine)
• EGSEgateway2 (additional gateway for second SCOS machine)
• Routergateway (to link the two routers)

To use those scripts login as user "hcss" on host "hos4-d" using the secure shell command:

ssh -X hcss@hos4-d

If you like to see the default arguments of this scripts, look at :

more bin/packetDistribution

Router

The router is started with the

router

command. There are no options nor arguments. The router will be running on the host hos4-d, port 9877.

EGSEgateway

The EGSEgateway is started with the

egsegateway APIDS

command. It requires a single argument, the list of APIDs to be transferred to SCOS 2000. The list is a comma separated list of single APID values or APID ranges specified with a minus sign. For example, "1100-1200,2043" would request all APIDs between 1100 and 1200 and also the APID 2043. The EGSEgateway will be running on the host hos4-d supplying port 9876 as service port to SCOS 2000.

The APIDS range to be used at Astrium shall be 1-1155,1158-2047 which request all APIDS but PACS science packets.

PipeGW

The PIPE gateway is started with the

pipeGW

command. There are no options nor arguments. The PipeGW will be running on the host hos4-d supplying port 12345 as service port to the CCS.

CcsHandler

• The CcsHandler started using the hcss account is connected to a standard test database for the hcss account. Usually the instrument teams start the CssHandler from their instrument accounts to connect it properly with their databases.

For PACS the CcsHandler is started :

ssh -X pacs@hos4-d
psetup
ccshandler -server

In general the CcsHandler is started with the

ccshandler [localOptions] -- [ccshandlerOptions]

command. The ccshandler options are those described in the TestControl/CcsHandler user manual. In addition following "local" options are available:

• -d or --TMdelay: requires a single argument
  • Specifies the delay in msecs between the transmission of two TM packets transmitted to the CCS. Defaults to 50 msecs.
  -n or --nTMS: requires a single argument
  • Specifies how often the TM packet SEQUENCE will be transmitted to the CCS. Defaults to 1.
  -w or --TMSwait: requires a single argument
  • Specifies the delay in msecs between two TM packet

    SEQUENCES. This option is only relevant if nTMS > 1. Defaults to 1000 msecs.

All "local" options are only relevant in the CcsHandler server mode.

Example:

• ccshandler -n 2 -- -server

  This will start the CcsHandler in server mode with sending each TM packet sequence twice.

Router2 (additional router for backup SCOS machine (with merged MIBS))

The router is started with the

router2

command. There are no options nor arguments. The router will be running on the host hos4-d, port 19877.

EGSEgateway (additional gateway for backup SCOS machine (with merged MIBS))

The EGSEgateway is started with the

egsegateway2 APIDS

command. It requires a single argument, the list of APIDs to be transferred to SCOS 2000. The list is a comma separated list of single APID values or APID ranges specified with a minus sign. For example, "1100-1200,2043" would request all APIDs between 1100 and 1200 and also the APID 2043.

The APIDS range to be used at Astrium shall be 1-1155,1158-2047 which request all APIDS but PACS science packets.

The EGSEgateway will be running on the host hos4-d supplying port 19876 as service port to SCOS 2000.

Routergateway

The router gateway to link the two routers is started with the command

routergateway

packetDistribution

This script start all four above applications using four different konsole windows. It might be used as convenient method to start all at once or as example how to use them.