Size: 1125
Comment:
|
← Revision 6 as of 2009-07-15 14:32:37 ⇥
Size: 7
Comment: converted to 1.6 markup
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
= Use CUS for commanding = The setup of the PACS MPE FM Databases are described : [wiki:Self:PACS/FM_ILT_Procedures/DatabaseProcedures DatabaseProcedures] |
|
Line 5: | Line 2: |
Current Datbase configuration for CUS use : attachment:dbsetup7.jpg * In the current configuration PACS5 is the operational database * "pacs_fm_ilt_1" is used as operational database * "pacs_fm_ilt_1" 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 * When the development database "sftcode" contain a valid and stable configuration * Log in as"cususer" on PACS1 * Export CUS definitions and procedures : DIEGO , incl. which directories etc. * Commit the CUS definitions and procedures to CVS * Tag the release using tag conventiens ... * Log in as "oper" on PACS5 * Import tagged cvs release into local cvs repository * stop cusgui * Import release into cus |