Differences between revisions 1 and 9 (spanning 8 versions)

KAGRA VIS Operations Manual - Troubleshooting

Check List

デジタルシステムトラブル
- RTモデルが動かない等の問題はひとまず以下を参照：DGS Checklist
- 伝達関数等を測定中にdiagguiが落ちて、excitationが止まらない：[解決策]

Clearing Excitation Testpoints

If excitation from diaggui won't stop, the fix is to clear all the test points for the real time model. You need to know the number of the user process running on the front end, which can be read from the GDS_TP screen, accessible from a button on the OVERVIEW screen and other places:
K1VISSR2GDSTP Screen.png
(Process number is 97 for SR2.)

伝達関数等を測定中にdiagguiが落ちて、excitationが止まらなくなった場合に以下を実行。(Open a terminal window and run the diag -l command.)

diag -l

でdiagnostic toolを起動。止めたいプロセスのID番号を確認し (You should get a diag> prompt. Then...)

diag> tpclear 97 * # for SR2

でtestpointをすべてクリアする。

KAGRA/Subgroups/VIS/OpsManual/Troubleshooting (last edited 2019-03-12 10:55:12 by EnzoTapia)

-  ⇤ ← Revision 1 as of 2014-10-24 10:57:35 → 
  Size: 656
  Editor: TakanoriSekiguchi
  Comment:
+   ← Revision 9 as of 2019-03-12 10:55:12 → ⇥
  Size: 1228
  Editor: EnzoTapia
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 3:
-== デジタルシステムのトラブル ==
+== Check List ==
 Line 5:
-RTモデルが動かない等の問題はひとまず以下を参照：[[KAGRA/Subgroups/DGS/Manual/CheckList|DGS Checklist]]
+ * デジタルシステムトラブル
  * RTモデルが動かない等の問題はひとまず以下を参照：[[KAGRA/Subgroups/DGS/Manual/CheckList|DGS Checklist]]
  * 伝達関数等を測定中にdiagguiが落ちて、excitationが止まらない：[[#tpclear| [解決策] ]]
  * 
  *
-Line 7:
+Line 11:
-=== Cleaning Excitation Testpoints ===
伝達関数等を測定中にdiagguiが落ちて、excitationが止まらなくなることがある。これを止めるには{{{
+----

<<Anchor(tpclear)>>
=== Clearing Excitation Testpoints ===
If excitation from `diaggui` won't stop, the fix is to clear all the test points for the real time model. You need to know the number of the user process running on the front end, which can be read from the `GDS_TP` screen, accessible from a button on the `OVERVIEW` screen and other places:<<BR>>
{{attachment:K1VISSR2GDSTP Screen.png||width=600}}<<BR>>
(Process number is 97 for SR2.)

伝達関数等を測定中にdiagguiが落ちて、excitationが止まらなくなった場合に以下を実行。(Open a terminal window and run the `diag -l` command.) {{{
-Line 10:
+Line 21:
-}}}でまずdiagnostic toolを起動する。止めたいプロセスのID番号を確認し{{
tpclear * (ID NUMBER)
}}
でtestpointをすべてクリアできる。diagnostic toolから出るにはquitとコマンドを打てばよい。
+}}}でdiagnostic toolを起動。止めたいプロセスのID番号を確認し (You should get a `diag>` prompt. Then...){{{
diag> tpclear 97 * # for SR2
}}}
でtestpointをすべてクリアする。