|
Size: 1393
Comment:
|
← Revision 20 as of 2009-07-15 14:32:36 ⇥
Size: 1272
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| The '''testcontrol-server''' application has to be started from an account that has access to the '''cus''' engine (usually account cususer@PACS1 here at MPE). The communication between TOPE and CUS is done by the system wide '''X-server''' application. Hence, '''testcontrol-server''' has to be associated, via the DISPLAY variable, with the '''''irmultia''''' processor. The association is implemented as {{{ (setenv DISPLAY irmultia:0 ; testcontrol-server &) }}} That is, redefine DISPLAY only for the '''testcontrol-server''' application and start the control application as a background task. |
The '''testcontrol-server''' application is started automatically by the procedure that updates '''cus''' following adding or editing a script module into the CUS registry. |
| Line 10: | Line 7: |
| [wiki:Self:PACS/FM_ILT_Procedures/DatabaseProcedures DatabaseProcedures] | [[PACS/FM_ILT_Procedures/DatabaseProcedures|DatabaseProcedures]] |
| Line 14: | Line 11: |
| attachment:dbsetup7.jpg | {{attachment:dbsetup7.jpg}} |
| Line 16: | Line 13: |
| * In the current configuration PACS5 is the operational database * "pacs_fm_ilt_2" is used as operational database * "pacs_fm_ilt_2" is used for commanding and telemetry ingestion |
|
| Line 17: | Line 17: |
| [wiki:Self:PACS/FM_ILT/SetupCUS Setup to schedule CUS from TOPE] | * In the current configuration PACS1 is used for development of the CUS definitions and procedures. * "sftcode" is the CUS development database * "sftcode" is accessed from within MPE and remote via cusgui |
| Line 19: | Line 21: |
| [wiki:Self:PACS/FM_ILT/CorrectCUS Correcting CUS procedures] | [[PACS/FM_ILT/SetupCUS|Setup to schedule CUS from TOPE]] |
| Line 21: | Line 23: |
| [wiki:Self:PACS/FM_ILT/SupportCUS Support Procedures] | [[PACS/FM_ILT/CorrectCUS|Correcting CUS procedures]] |
| Line 23: | Line 25: |
| [wiki:Self:PACS/FM_ILT/Use CUS for commanding] | [[PACS/FM_ILT/SupportCUS|Support Procedures]] |
| Line 25: | Line 27: |
| [wiki:Self:PACS/FM_ILT/CUSDev CUS Procedures Development] | [[PACS/FM_ILT/CUSDev|CUS Procedures Development]] |
| Line 27: | Line 29: |
| [wiki:Self:PACS/FM_ILT/CUSExp CUS Procedure export and configuration control] | [[PACS/FM_ILT/CUSExp|CUS Procedure export and configuration control]] |
| Line 29: | Line 31: |
| [wiki:Self:PACS/FM_ILT/CUSLoad CUS Procedures loading into operational Database] | [[PACS/FM_ILT/CUSLoad|CUS Procedures loading into operational Database]] |
To schedule a CUS "mode" script from TOPE requires the intervention of the testcontrol-server application.
The testcontrol-server application is started automatically by the procedure that updates cus following adding or editing a script module into the CUS registry.
The setup of the PACS MPE FM Databases are described : DatabaseProcedures
Current Datbase configuration for CUS use : 
* In the current configuration PACS5 is the operational database
- "pacs_fm_ilt_2" is used as operational database
- "pacs_fm_ilt_2" is used for commanding and telemetry ingestion
- In the current configuration PACS1 is used for development of the CUS definitions and procedures.
- "sftcode" is the CUS development database
- "sftcode" is accessed from within MPE and remote via cusgui
Setup to schedule CUS from TOPE